From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Blog: Guix packaging tutorial Date: Tue, 09 Oct 2018 01:05:54 +0200 Message-ID: <87muro9gz1.fsf@ambrevar.xyz> References: <878t38t5gz.fsf@jnanam.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55527) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9ebH-0004F1-IT for guix-devel@gnu.org; Mon, 08 Oct 2018 19:06:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g9ebF-00031A-9W for guix-devel@gnu.org; Mon, 08 Oct 2018 19:06:07 -0400 In-reply-to: <878t38t5gz.fsf@jnanam.net> 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: Benjamin Slade Cc: guix-devel , guix-blog@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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=20https://gitlab.com/pjotrp/guix-notes/blob/master/HACKING.org: =2D-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 th= e 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 mo= dules) 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 =2D-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? =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlu74tIACgkQm9z0l6S7 zH+fLgf9GVp4OMGM8YhPZLbUOFna9AzePxI7YbyDysdlVRXh0x90bh/NSj0Q5AbM vM9nePI1NUnxxk/ij4dKCsgSgrDFStEDUcjPjCjFpzLjhzugpemHaXAMjZBbSiwh Ip45hE9DF67st4Ai8KRnHMfXvJGMUfQfejM+NFFSWZNiZkV33mg5ADpmPiP9aYkf 2Pfkb7KWVXhDAFjSoHARwe7Zzy20PulaDQZQiXHsYy9GdmXEaJJOYqfF5abxhQFy W4uyukVJj1ZjUAusTqu0T0MW4pzoyzq8+bqQzMwBXSxJD9MaXUu2e4kCxSHyUbVY BpQK3A3hY+Y6C5JuAugMjGM19RI0AA== =nbhf -----END PGP SIGNATURE----- --=-=-=--