[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A plan for parameterized packages
From: |
zimoun |
Subject: |
Re: A plan for parameterized packages |
Date: |
Sun, 15 Nov 2020 22:16:44 +0100 |
Dear,
On Sun, 15 Nov 2020 at 21:46, Danny Milosavljevic <dannym@scratchpost.org>
wrote:
> * Enable/disable building the documentation. I really don't need a 40 MiB
> manual stored onto a 16 MiB firmware flash chip. If that's better done as an
> extra output, fair enough.
Related (I hope) is: build packages with several outputs. For instance,
’git’ has several 'outputs' ("send-email", "svn", etc.), so the list of
"inputs" provides e.g., "subversion" even if I am only interested by
e.g., "git:send-email". This matters about closure.
And it is maybe an occasion to revisit the museum, i.e., the TODO file:
** extend ‘propagated-build-inputs’ with support for multiple outputs
#+BEGIN_SRC scheme
(outputs '("out" "include"))
(propagated-build-inputs
`(((("i1" ,p1 "o1")
("i2" ,p2))
=> "include")
("i3" ,p3)))
#+END_SRC
For one reference:
<https://lists.gnu.org/archive/html/guix-devel/2020-06/msg00284.html>
All the best,
simon
- Re: A plan for parameterized packages, (continued)
Re: A plan for parameterized packages, zimoun, 2020/11/15
Re: A plan for parameterized packages, Taylan Kammer, 2020/11/15
Re: A plan for parameterized packages, Danny Milosavljevic, 2020/11/15
- Re: A plan for parameterized packages,
zimoun <=
Re: A plan for parameterized packages, raingloom, 2020/11/15
Re: A plan for parameterized packages, Denis 'GNUtoo' Carikli, 2020/11/19
Re: A plan for parameterized packages, Ludovic Courtès, 2020/11/20
Re: A plan for parameterized packages, zimoun, 2020/11/20
Re: A plan for parameterized packages, Christopher Baines, 2020/11/20