From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: Parameterized packages Date: Mon, 20 Jan 2020 15:34:03 +0100 Message-ID: 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> <871rry10ow.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42105) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itY88-0000Qs-QG for guix-devel@gnu.org; Mon, 20 Jan 2020 09:34:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1itY87-00065P-Il for guix-devel@gnu.org; Mon, 20 Jan 2020 09:34:16 -0500 Received: from mail-qk1-x729.google.com ([2607:f8b0:4864:20::729]:45375) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1itY87-000658-Dg for guix-devel@gnu.org; Mon, 20 Jan 2020 09:34:15 -0500 Received: by mail-qk1-x729.google.com with SMTP id x1so30205444qkl.12 for ; Mon, 20 Jan 2020 06:34:15 -0800 (PST) In-Reply-To: <871rry10ow.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-mx.org@gnu.org Sender: "Guix-devel" To: Pierre Neidhardt Cc: Guix Devel Hi Pierre, On Fri, 17 Jan 2020 at 17:56, Pierre Neidhardt wrote: > In this case, it's trivial to use parameters to influence which compiler > the build system will use. I am not sure that "trivial" is the correct word. ;-) > For gnu-build-system (with gcc, clang, etc.) we can probably do similar > things already by setting CC. Yes, and about Rust, Ruby, Perl, etc. I do think it is the right abstraction. :-) > 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? Maybe. I am not sure to see what do you mean by '#:arguments'. If you mean something that does what does `package-with-explicit-python' to rewrite the 'arguments' field, yes it is something in this flavor. But generic enough. For example compare `package-with-explicit-python' and `package-with-explicit-ocaml'. Well, something to tweak `lower'. And the question is: what is the right abstraction? All the best, simon