From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: Build systems and implicit inputs Date: Tue, 21 Jan 2020 13:24:33 +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> <87o8uxdqnh.fsf_-_@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50859) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itsaN-0004N2-S5 for guix-devel@gnu.org; Tue, 21 Jan 2020 07:24:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1itsaM-0001WU-SG for guix-devel@gnu.org; Tue, 21 Jan 2020 07:24:47 -0500 In-Reply-To: <87o8uxdqnh.fsf_-_@gnu.org> 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: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: Guix Devel Hi Ludo, On Tue, 21 Jan 2020 at 11:56, Ludovic Court=C3=A8s wrote: > > 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? > > I think the issue of tweaking the build system and its implicit inputs > must be addressed separately. We first need a good API to do that. > When we have it, it=E2=80=99ll be nice and easy to drive it via package > parameters. :-) Now I have a better understanding about "package parameters", I agree that it is 2 separate stories. > Currently each build system has ad-hoc keyword parameters to customize > its implicit inputs: #:python for =E2=80=98python-build-system=E2=80=99, = #:cmake for > =E2=80=98cmake-build-system=E2=80=99, #:implicit-inputs? for =E2=80=98gnu= -build-system=E2=80=99, etc. > > For each of them, it would be quite easy to provide a procedure that > takes a list of implicit inputs and returns a . It may > not be all that convenient, and perhaps a bit too ad-hoc still. I was inclined for this option. :-) > Another option would be to make implicit inputs a field of > . Not sure to understand... > Needs more thought! ...so yes! :-) Cheers, simon