From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, "Barnabás Béres" <beresbarnus03@gmail.com>
Subject: Re: Submitting new packages
Date: Thu, 05 Nov 2020 06:37:17 -0500 [thread overview]
Message-ID: <BD16368A-2F5D-4FA0-906E-331631B66AB8@lepiller.eu> (raw)
In-Reply-To: <5A28C3A4-B6CC-4C11-B246-AE39D1161479@gmail.com>
Le 5 novembre 2020 06:03:18 GMT-05:00, "Barnabás Béres" <beresbarnus03@gmail.com> a écrit :
>Hey Guixers,
>
>I’m quite new to Guix but I would like to contribute. I created two
>font packages (fort awesome and nerd fonts). Can you please help my how
>can send in and later maintain my packages?
Hi Barnabás!
If you're talking about font-awesome, we already have it (although version 4, since version 5's build system is not free: https://issues.guix.gnu.org/32916)
Now, for patches. You need to clone the git repository, apply your changes. When adding packages make sure to create one commit per added package. You'll find examples of such commits in the history. The message should look like this, on two lines with a blank line in the middle:
gnu: Add foo.
* gnu/packages/foo.scm (foo): New variable.
Once you've added a package to a file, build your package with ./pre-inst-env guix build foo, lint it with ./pre-inst-env guix lint foo and commit.
You can generate a patch with git format-patch -1 (or -2 for the latest two commits, etc). Then send that (those) file(s) to guix-patches@ and wait for a bit until someone reviews it (them).
The manual has this page that you might find useful:
https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html#Submitting-Patches
Don't hesitate to ask if you have further questions or if that was confusing :)
>Thanks for your help!
>
>Best regards,
>Barnabas Beres
next prev parent reply other threads:[~2020-11-05 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 11:03 Submitting new packages Barnabás Béres
2020-11-05 11:35 ` Ekaitz Zarraga
2020-11-05 11:37 ` Julien Lepiller [this message]
2020-11-05 13:27 ` raingloom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BD16368A-2F5D-4FA0-906E-331631B66AB8@lepiller.eu \
--to=julien@lepiller.eu \
--cc=beresbarnus03@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).