From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Slade Subject: Re: Blog: Guix packaging tutorial Date: Mon, 08 Oct 2018 18:04:59 -0600 Message-ID: <875zyct26s.fsf@jnanam.net> References: <878t38t5gz.fsf@jnanam.net> <87muro9gz1.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41931) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9fWe-0000ry-LJ for guix-devel@gnu.org; Mon, 08 Oct 2018 20:05:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g9fWT-00051Z-TN for guix-devel@gnu.org; Mon, 08 Oct 2018 20:05:19 -0400 In-reply-to: <87muro9gz1.fsf@ambrevar.xyz> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Pierre Neidhardt Cc: guix-devel , guix-blog@gnu.org 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.)=20 But in retrospect, maybe this would be better as a separate post. cheers, =E2=80=94Ben On 2018-10-08T17:05:54-0600, Pierre Neidhardt wrote: > Hi Ben! > I've sent two versions so far and I'm going to send the final version ju= st now. > As for the checklists: hmm... Which steps do you have in mind? The tric= k 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 =E2=80=98rules=E2=80=99 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 =E2=80=98guix import=E2=80=99 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 =E2=80=98guix lint=E2=80=99 > 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 t= he > 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 )