[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Parameterized packages
From: |
Pierre Neidhardt |
Subject: |
Re: Parameterized packages |
Date: |
Wed, 15 Jan 2020 10:40:04 +0100 |
Hi Simon!
You are making a good point: there are different levels of
"accessibility" when it comes to inputs:
- The source.
- The explicit inputs.
- the implicit inputs.
- The build inputs.
- The build system inputs.
- Recursive inputs.
- ...?
Which one should we expose? I don't know. If we want the system to
have some set of properties, I guess only the resulting packages matther
and the build inputs don't.
Should we touch implicit inputs, we would have to parse all the
references and not just the explicit inputs like --with-input does.
> but be able to
> recompile a matrix of combinaison would be really cool!
Indeed. But now I'm starting to wonder if it is really doable :p
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
- Re: Parameterized packages, Pierre Neidhardt, 2020/01/02
- Re: Parameterized packages, Pierre Neidhardt, 2020/01/09
- Re: Parameterized packages, Ludovic Courtès, 2020/01/10
- Re: Parameterized packages, Pierre Neidhardt, 2020/01/11
- Re: Parameterized packages, zimoun, 2020/01/14
- Re: Parameterized packages,
Pierre Neidhardt <=
- Re: Parameterized packages, zimoun, 2020/01/15
- Re: Parameterized packages, Pierre Neidhardt, 2020/01/15
- Re: Parameterized packages, zimoun, 2020/01/15
- Re: Parameterized packages, ison, 2020/01/16
- Re: Parameterized packages, Ricardo Wurmus, 2020/01/16
- Re: Parameterized packages, Pierre Neidhardt, 2020/01/17
- Re: Parameterized packages, Nicolò Balzarotti, 2020/01/16
- Re: Parameterized packages, Pierre Neidhardt, 2020/01/17
- Re: Parameterized packages, Ludovic Courtès, 2020/01/19
- Re: Parameterized packages, L p R n d n, 2020/01/17