--- Begin Message ---
|
Subject: |
[PATCH 2/2] doc: Document the --manifest option for guix pack. |
|
Date: |
Sat, 10 Feb 2018 12:35:41 +0100 |
* doc/guix.texi (Invoking guix pack): Document --manifest.
---
doc/guix.texi | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index 13187f2e8..f64f95929 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -2841,6 +2841,19 @@ This has the same purpose as the same-named option in
@command{guix
build} (@pxref{Additional Build Options, @code{--expression} in
@command{guix build}}).
address@hidden address@hidden
address@hidden -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.
+
@item address@hidden
@itemx -s @var{system}
Attempt to build for @var{system}---e.g., @code{i686-linux}---instead of
--
2.14.3 (Apple Git-98)
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: [bug#30410] [PATCH 2/2] doc: Document the --manifest option for guix pack. |
|
Date: |
Thu, 15 Feb 2018 15:24:00 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Konrad Hinsen <address@hidden> 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.
> address@hidden address@hidden
> address@hidden -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’.
--- End Message ---