From: Brett Gilio <brettg@gnu.org>
To: Simon South <simon@simonsouth.net>
Cc: guix-devel@gnu.org, help-guix@gnu.org
Subject: Re: Specifying dependencies among package outputs?
Date: Wed, 14 Oct 2020 17:55:36 -0500 [thread overview]
Message-ID: <878sc8zac7.fsf@debian> (raw)
In-Reply-To: <87eem0l9qc.fsf@simonsouth.net> (Simon South's message of "Wed, 14 Oct 2020 18:32:27 -0400")
Simon South <simon@simonsouth.net> writes:
> Am I right in thinking there is no way to specify dependencies among the
> outputs of a single package? To specify that a package's "out" output
> depends on its "lib" output, for instance.
>
> I ask because the Knot package (in gnu/package/dns.scm) builds a number
> of logically distinct targets---daemon, libraries, administrative
> utilities, general-purpose utilities, and documentation---and it would
> be nice to separate at least some of these into individual outputs, in
> part because we could then specify only the libraries as a dependency of
> Knot Resolver.
>
> However, Knot's daemon and utilities have the same dependency on its own
> libraries, so pulling those into a separate "lib" output would be liable
> to break everything else.
>
> I've searched and can't find an example of this being done, nor can I
> find any mention of it in the documentation. So I assume it's simply not
> possible, and you would need to define an entirely separate package that
> builds from the same source code---right?
Unless I am mistaken, this is not possible. When using a specific
output, it still fetches the entire package closure. But only that
specific output propagates to the profile. Adding an output as a
dependency would surely cause a non-termination situation with the
interpreter.
I have cc'ed guix-devel as I think that is the better fit for this
question.
Best
--
Brett M. Gilio
<brettg@gnu.org>
https://brettgilio.com
parent reply other threads:[~2020-10-14 22:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87eem0l9qc.fsf@simonsouth.net>]
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=878sc8zac7.fsf@debian \
--to=brettg@gnu.org \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=simon@simonsouth.net \
/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).