From: ludo@gnu.org (Ludovic Courtès)
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 30410-done@debbugs.gnu.org
Subject: bug#30410: [PATCH 2/2] doc: Document the --manifest option for guix pack.
Date: Thu, 15 Feb 2018 15:24:00 +0100 [thread overview]
Message-ID: <878tbu9vr3.fsf@gnu.org> (raw)
In-Reply-To: <m1zi4hm4ta.fsf@ordinateur-de-catherine--konrad.home> (Konrad Hinsen's message of "Sat, 10 Feb 2018 12:35:41 +0100")
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> * doc/guix.texi (Invoking guix pack): Document --manifest.
I’ve squashed this one with the patch that adds the code, so the commit
is self-contained.
> +@item --manifest=@var{file}
> +@itemx -m @var{file}
> +Use the packages contained in the manifest object
> +returned by the Scheme code in @var{file}.
> +
> +This has a similar purpose as the same-named option in @command{guix
> +package} (@pxref{profile-manifest, @option{--manifest}}) and uses the
> +same manifest files. It allows you to define a collection of packages
> +once and use it both for creating profiles and for creating archives
> +for use on machines that do not have Guix installed. Note that you can
> +specify @emph{either} a manifest file @emph{or} a list of packages,
> +but not both.
On second thought, I wonder if we should allow both -m and a list of
packages. After all, ‘guix package’ supports it, and it doesn’t cost us
anything. WDYT?
Thanks!
Ludo’.
next prev parent reply other threads:[~2018-02-15 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 11:35 [bug#30410] [PATCH 2/2] doc: Document the --manifest option for guix pack Konrad Hinsen
2018-02-12 19:15 ` myglc2
2018-02-13 8:23 ` Konrad Hinsen
2018-02-14 4:04 ` myglc2
2018-02-15 14:24 ` Ludovic Courtès [this message]
[not found] ` <handler.30410.D30410.151870464424102.notifdone@debbugs.gnu.org>
2018-02-15 19:14 ` [bug#30410] closed (Re: [bug#30410] [PATCH 2/2] doc: Document the --manifest option for guix pack.) Konrad Hinsen
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=878tbu9vr3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30410-done@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.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).