From: Benjamin Slade <slade@jnanam.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>, guix-blog@gnu.org
Subject: Re: Blog: Guix packaging tutorial
Date: Mon, 08 Oct 2018 18:04:59 -0600 [thread overview]
Message-ID: <875zyct26s.fsf@jnanam.net> (raw)
In-Reply-To: <87muro9gz1.fsf@ambrevar.xyz>
Hi Pierre,
Maybe it really falls outside of the scope of this packaging tutorial
since some of it is not about creating packages per se but about how to
submit them....
...But I was thinking about something a bit like Pjotr's list, though
with a bit more detail. (E.g. things like using `git format-patch' to
create patches for submission.)
But in retrospect, maybe this would be better as a separate post.
cheers,
—Ben
On 2018-10-08T17:05:54-0600, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> Hi Ben!
> I've sent two versions so far and I'm going to send the final version just now.
> As for the checklists: hmm... Which steps do you have in mind? The trick is
> that the is little to repeat once the Git checkout has been set up.
> Pjotr has a checklist however, let me know what you think:
> From https://gitlab.com/pjotrp/guix-notes/blob/master/HACKING.org:
> --8<---------------cut here---------------start------------->8---
> Workflow for packaging
> The general workflow for adding and maintaining packages is a bit
> complex. Everything goes via de guix-dev mailing list and includes a
> review process which can be discouraging and is more geared towards
> reviewers than towards newbies. This should not discourage you because
> GNU Guix is great. Note that the reviewers do this work voluntarily
> and most ‘rules’ have been agreed by the community. In the end your
> labours will get rewarded. So, how to start?
> 1 - Work on a recent git checkout of guix
> 2 - Use ‘guix import’ if you can (e.g. for python and R modules)
> 3 - Build the package yourself
> 4 - If tests are there, make sure they pass
> 5 - Test your work with ‘guix lint’
> 6 - Create a patch as described above
> 7 - Send it to debbugs as described above
> 8 - Submit one patch at a time and submit the next one when it goes in
> 9 - Be patient, review can take a while - monitor debbugs
> --8<---------------cut here---------------end--------------->8---
> I'm not sure those are exactly steps, while some items actually belong the
> manual's check list "(guix) Submitting Patches".
> Opinions?
> --
> Pierre Neidhardt
> https://ambrevar.xyz/
--
Benjamin Slade - https://babbagefiles.xyz
`(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
'(sent by mu4e on Emacs running under GNU/Linux . https://gnu.org )
`(Choose Linux ,(Choose Freedom) . https://linux.com )
next prev parent reply other threads:[~2018-10-09 0:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 22:54 Blog: Guix packaging tutorial Benjamin Slade
2018-10-08 23:05 ` Pierre Neidhardt
2018-10-09 0:04 ` Benjamin Slade [this message]
2018-10-10 9:02 ` Ludovic Courtès
2018-10-11 1:38 ` Benjamin Slade
2018-10-11 9:37 ` Gábor Boskovits
2018-10-11 13:39 ` Ludovic Courtès
2018-10-12 1:05 ` Benjamin Slade
-- strict thread matches above, loose matches on Subject: below --
2018-09-13 10:50 Pierre Neidhardt
2018-09-13 11:16 ` Pjotr Prins
2018-09-13 11:53 ` Ricardo Wurmus
2018-09-13 12:04 ` Pjotr Prins
2018-09-13 19:11 ` Andreas Enge
2018-09-14 11:07 ` Pierre Neidhardt
2018-09-14 11:33 ` Pjotr Prins
2018-09-24 17:00 ` Pierre Neidhardt
2018-09-24 17:37 ` Pierre Neidhardt
2018-09-27 13:43 ` Ludovic Courtès
2018-09-27 17:34 ` Pierre Neidhardt
2018-09-29 16:28 ` Ludovic Courtès
2018-09-29 21:18 ` Ricardo Wurmus
2018-09-30 19:01 ` Pierre Neidhardt
2018-09-30 19:44 ` Ludovic Courtès
2018-09-30 21:14 ` Pierre Neidhardt
2018-10-02 12:12 ` Ludovic Courtès
2018-10-02 16:02 ` Pierre Neidhardt
2018-10-02 19:46 ` Ricardo Wurmus
2018-10-03 8:10 ` Pierre Neidhardt
2018-10-03 18:16 ` Pierre Neidhardt
2018-10-08 12:20 ` Ludovic Courtès
2018-10-08 15:18 ` Ricardo Wurmus
2018-10-08 18:41 ` Pierre Neidhardt
2018-10-08 19:06 ` Pierre Neidhardt
2018-10-08 19:59 ` Ricardo Wurmus
2018-10-08 22:09 ` Pierre Neidhardt
2018-10-08 22:33 ` Pierre Neidhardt
2018-10-08 23:45 ` Pierre Neidhardt
2018-10-10 11:56 ` Ludovic Courtès
2018-10-10 13:20 ` George Clemmer
2018-10-10 13:31 ` Pierre Neidhardt
2018-10-10 14:13 ` Ricardo Wurmus
2018-10-20 19:58 ` Divan
2018-10-21 10:30 ` Pierre Neidhardt
2018-10-21 11:21 ` Pierre Neidhardt
2018-10-22 20:40 ` Divan Santana
2018-10-22 21:11 ` Pierre Neidhardt
2018-09-26 10:20 ` Ludovic Courtès
2018-09-26 10:28 ` Pierre Neidhardt
2018-09-27 11:56 ` Ludovic Courtès
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=875zyct26s.fsf@jnanam.net \
--to=slade@jnanam.net \
--cc=guix-blog@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).