From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Abhishek Cherath <abhi@quic.us>, 59520@debbugs.gnu.org
Subject: [bug#59520] [PATCH] doc: Note that guix package can operate on outputs.
Date: Thu, 24 Nov 2022 01:00:08 +0100 [thread overview]
Message-ID: <87h6ypb4dg.fsf@nckx> (raw)
In-Reply-To: <86bkoxfe7y.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
Heyo,
zimoun 写道：
> How do you get the store path in the first place?
‘guix build’, for example.
> …what is missing is a way to provide an expression to “guix
> package” or
> “guix install”.
Indeed, but as it would address only a subset of such use cases,
it should be a separate proposal.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-11-24 0:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 18:37 [bug#59520] [PATCH] doc: Note that guix package can operate on outputs Abhishek Cherath
2022-11-20 0:05 ` [bug#59520] [PATCH] doc: Note that ‘guix package’ accepts file names Tobias Geerinckx-Rice via Guix-patches via
2022-11-23 21:58 ` Abhishek Cherath
2022-11-23 22:02 ` bug#59520: " Tobias Geerinckx-Rice via Guix-patches via
2022-11-23 23:54 ` [bug#59520] " zimoun
2022-11-24 0:10 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-24 0:24 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-24 10:08 ` zimoun
2022-11-23 22:05 ` Abhishek Cherath
2022-11-23 22:08 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-23 22:19 ` Abhishek Cherath
2022-11-23 18:47 ` [bug#59520] [PATCH] doc: Note that guix package can operate on outputs Abhishek Cherath
2022-11-23 20:35 ` zimoun
2022-11-23 21:02 ` Abhishek Cherath
2022-11-23 23:22 ` zimoun
2022-11-24 0:00 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-11-24 0:09 ` Abhishek Cherath
2022-11-24 10:27 ` zimoun
2022-11-23 21:42 ` Tobias Geerinckx-Rice via Guix-patches via
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=87h6ypb4dg.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=59520@debbugs.gnu.org \
--cc=abhi@quic.us \
--cc=me@tobias.gr \
--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).