From: Simon South <simon@simonsouth.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Specifying dependencies among package outputs?
Date: Thu, 15 Oct 2020 19:45:58 -0400 [thread overview]
Message-ID: <87lfg7aw95.fsf@simonsouth.net> (raw)
In-Reply-To: <87imbbazy2.fsf@nckx> (Tobias Geerinckx-Rice's message of "Fri, 16 Oct 2020 00:26:13 +0200")
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Sound good?
Yep, that feels like a natural division.
Thanks again, and thanks also for the notes on
"propagated-inputs". Onwards and upwards.
--
Simon South
simon@simonsouth.net
next prev parent reply other threads:[~2020-10-15 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 22:32 Specifying dependencies among package outputs? Simon South
2020-10-15 0:07 ` Julien Lepiller
2020-10-15 0:37 ` Tobias Geerinckx-Rice
2020-10-15 0:43 ` Tobias Geerinckx-Rice
2020-10-15 11:44 ` zimoun
2020-10-15 14:54 ` Simon South
2020-10-15 22:26 ` Tobias Geerinckx-Rice
2020-10-15 23:45 ` Simon South [this message]
2020-10-16 17:32 ` Tobias Geerinckx-Rice
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=87lfg7aw95.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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.
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).