From: myglc2@gmail.com
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 30410@debbugs.gnu.org
Subject: [bug#30410] [PATCH 2/2] doc: Document the --manifest option for guix pack.
Date: Mon, 12 Feb 2018 14:15:14 -0500 [thread overview]
Message-ID: <86r2pq81fh.fsf@gmail.com> (raw)
In-Reply-To: <m1zi4hm4ta.fsf@ordinateur-de-catherine--konrad.home> (Konrad Hinsen's message of "Sat, 10 Feb 2018 12:35:41 +0100")
Hi Konrad,
Very cool patch!
On 02/10/2018 at 12:35 Konrad Hinsen writes:
> +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.
FWIW, here are a few thoughts ...
It would be helpful to add an example or two of "list of packages".
The term manifest has a few meanings in guix. There are the "input
manifests" forms accepted by '--manifest=' and the "output manifests"
produced by 'guix package' (e.g.,$HOME/.guix-profile/manifest). Only
input manifests are documented now. But ISTM there may eventually be a
tool to produce an input manifest from a user's profile that has grown
organically through install/remove operations. If/when that happens,
"output manifests" might also be mentioned in the doc.
Currently the doc doesn't show an actual manifest. Rather it shows 2
"input manifest" forms that are acceptable to '--manifest=' ...
(use-package-modules guile emacs)
(packages->manifest
(list emacs
guile-2.0
;; Use a specific package output.
(list guile-2.0 "debug")))
... and ...
(specifications->manifest
'("emacs" "guile@2.2" "guile@2.2:debug"))
These can be a source of confusion, typos, and error (or at least they
were to me). So I wonder: Does adding a 3rd "list of packages" form make
the option murkier? Would a separate option be simpler to document/use?
HTH - George
next prev parent reply other threads:[~2018-02-12 19:16 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 [this message]
2018-02-13 8:23 ` Konrad Hinsen
2018-02-14 4:04 ` myglc2
2018-02-15 14:24 ` bug#30410: " Ludovic Courtès
[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=86r2pq81fh.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=30410@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).