From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: (propagated) 'inputs' depends on 'outputs'?
Date: Fri, 19 Jun 2020 22:47:25 +0200 [thread overview]
Message-ID: <87ftaqeqaq.fsf@gnu.org> (raw)
In-Reply-To: <86d05zqaj3.fsf@gmail.com> (zimoun's message of "Tue, 16 Jun 2020 17:45:52 +0200")
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> I am not sure to get the point. From my understanding, it could be
> possible to add information to native-inputs, inputs and
> propagated-inputs, e.g.,
>
> ;; For 'git-svn'.
> ("subversion" ,subversion "svn")
> ("perl-term-readkey" ,perl-term-readkey "svn")
>
> or whatever other mean. Then it becomes possible to only build e.g.,
> git:svn and/or propagate specific inputs depending on the outputs.
The ‘TODO’ file, which is really a museum, has this:
[-- Attachment #2: Type: text/x-org, Size: 258 bytes --]
** 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
[-- Attachment #3: Type: text/plain, Size: 46 bytes --]
Is this what you have in mind?
Ludo’.
next prev parent reply other threads:[~2020-06-19 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 11:01 (propagated) 'inputs' depends on 'outputs'? zimoun
2020-06-13 11:16 ` Christopher Baines
2020-06-16 12:31 ` zimoun
2020-06-16 15:34 ` Ricardo Wurmus
2020-06-16 15:52 ` zimoun
2020-06-13 11:38 ` Julien Lepiller
2020-06-16 12:41 ` zimoun
2020-06-16 14:28 ` Julien Lepiller
2020-06-16 15:45 ` zimoun
2020-06-19 20:47 ` Ludovic Courtès [this message]
2020-06-19 21:44 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftaqeqaq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).