From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Parameterized packages Date: Fri, 17 Jan 2020 17:56:31 +0100 Message-ID: <871rry10ow.fsf@ambrevar.xyz> References: <8736ldq74z.fsf@netris.org> <20190719202906.lbanx5puk7t6q4cr@cf0> <87a7753boq.fsf@ambrevar.xyz> <87h813wah0.fsf@gnu.org> <87v9piut40.fsf@ambrevar.xyz> <87o8v5ukgb.fsf@ambrevar.xyz> <87d0blhr9s.fsf@ambrevar.xyz> <20200116190644.uytvzvypuvdwh2iq@n0> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:49216) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1isUvI-0006L1-EW for guix-devel@gnu.org; Fri, 17 Jan 2020 11:56:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1isUvD-0005i7-Uo for guix-devel@gnu.org; Fri, 17 Jan 2020 11:56:39 -0500 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:50435) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1isUvD-0005g5-O6 for guix-devel@gnu.org; Fri, 17 Jan 2020 11:56:35 -0500 In-Reply-To: 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-mx.org@gnu.org Sender: "Guix-devel" To: zimoun , ison Cc: Guix Devel --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Zimoun! zimoun writes: > Well, it would ease comparison in the HPC world. :-) > > > It is not related to the "parametrized package" in the sense of flag > options. :-) > > And I do not know if it make sense. What do you think? I think you are making a lot of sense and yes, parameters should probably be able to customize the builder as well. But as I understand it, all the "configurable part" of the builder is expose through the #:arguments field. A simple example of this is python: the python-build-system has an argument which allows the package to specify whether we use python-2 or python-3. In this case, it's trivial to use parameters to influence which compiler the build system will use. For gnu-build-system (with gcc, clang, etc.) we can probably do similar things already by setting CC. The solution to your problem in my opinion is simply to expose just the right amount of options through #:arguments for all build systems. Would that be satisfactory to you? =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl4h5z8ACgkQm9z0l6S7 zH+zYAgAg/VJhf32B8/02Tw+ap60oaQMQD7LleqYbLYgkjDcVtEl6LzmnSaCAlCy HFzTdNy/UmaT/sjCHhQfHvOEc6LjSCZkhjRlR2FsId6Uw8UQHiw9/qL6YDSPswyp LYUEL+YZvetsvBlFC4EZY5uxpX0St8NPSq2ED5bbzmRQIub8jmA9ojtmieBxb+Xn rHbelKEjKEVM7wYjjYbaiK35LQ//UiuQrXB44vGqZdxTPOb8xUDmCtp3PqeRyZLi 9JhYw2CrnwIC0cgRux8qR+1rVEZRflhYyNr4x8XBifMTC6pN+I1Epv+0FJkcFbJB LEoQiNjAwspmjydjZJAWuCW5GF4wQA== =nuCv -----END PGP SIGNATURE----- --=-=-=--