From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Blog: Guix packaging tutorial Date: Fri, 14 Sep 2018 13:07:44 +0200 Message-ID: <87woro5ocf.fsf@ambrevar.xyz> References: <87in397jsd.fsf@ambrevar.xyz> <20180913191151.GA1865@jurong> 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]:44456) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g0lx7-00087c-JO for guix-devel@gnu.org; Fri, 14 Sep 2018 07:07:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g0lx4-00064u-D1 for guix-devel@gnu.org; Fri, 14 Sep 2018 07:07:57 -0400 In-reply-to: <20180913191151.GA1865@jurong> 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: Andreas Enge Cc: guix-devel , guix-blog@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > https://gitlab.com/pjotrp/guix-notes/blob/master/HACKING.org Wow, this is a fantastic document! Is it mentioned anywhere? I wish I had known about this before. I guess you've done most of the work already. I'll make sure to mention your work and credit you in the blog article. I could spot some mistakes: =2D it's "%outputs" with and "s", not "%output". =2D "=E2=80=93no-substites". Ricardo has a very good point. Initially I did not think of orienting the = blog towards contributing to upstream, and I think you are right, it's something= very important we should do, especially considering that Guix is one of the very distributions that welcomes user contributions regardless of their "status". On the other hand, I can also see a different population of users, those who simply don't intend to contribute for whatever reasons (think the "fear of = the first commitment" when newborn hackers send their first patch). Those users might get a feeling that Guix is not "hackable for their own purposes" if t= hey can't define a package for their own private use. My suggestion is to quickly mention GUIX_PACKAGE_PATH, insist on contributi= ng upstream and underline the friction that results from moving from GUIX_PACKAGE_PATH to upstream, as Ricardo pointed out. Complex packages and trivial build system: I think a tutorial is not so use= ful if it only covers the basics that many users can figure out by themselves. = An advanced tutorial covering the parts that are hard to learn alone would be = more than welcome in my opinion. In my personal experience, I got started with "inxi" which uses the trivial build system, and it was _very hard_, even while I could get a grasp of the gnu-build-system. Pjotr Prins writes: > A second advanced hacking tutorial could discuss more advanced > features. I also agree with your point that starting off with complex packaging could scare people away. So my suggestion is as follows: =2D Part 1: basics + gnu-build-system + importers =2D Part 2: trivial-build-system + debug and REPL interaction. What do you think? Andreas Enge writes: > You could have a look at the slides of a talk I gave at GHM 2013 in the > "maintenance" git repo, inside the talks/ghm-2013/andreas directory. > Some things are outdated (we did not have the macros to manipulate build > phases yet). Will have a look, thanks! =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlubloAACgkQm9z0l6S7 zH+5+gf9EKJzQzVKzfKQcxQnruxSFdgIWkk+xohgcS2s1/EIKKURjrM6kx8L/AQy dxNabnBVLMsIcMKtPz4G8zDuKtLOJgSFxrgXheCqGFBmwQkl0QP5zltp+OnRDpHT mN7BdviT4sJ6fsEyzpfewd5OWMtbijWQrvaXseyDBcUxrjIbDjJQV+9T7+fFsW6x yKCHmXm7AxhGxCf0afulf8frcUe5cMGCTFyCeR4jJkHSPPJxbzVsXtk0FZ4qpg0q fawHDFp4OTDJlBd25D1PKQA6PZzPzbBuKdZLcO7csANSI18ntWEZJYDhM2i1tK5r vJoYQVjTiqRxkJ7cco7J6jqBL02T4g== =7Fdm -----END PGP SIGNATURE----- --=-=-=--