From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 56612@debbugs.gnu.org
Subject: [bug#56612] [PATCH] guix install: Add '--manifest' option.
Date: Thu, 21 Jul 2022 11:09:54 +0200 [thread overview]
Message-ID: <87r12en865.fsf@gnu.org> (raw)
In-Reply-To: <dfe98b1254828d8b2f4f90bf9d38284d7e5d02f0.camel@ist.tugraz.at> (Liliana Marie Prikler's message of "Tue, 19 Jul 2022 12:01:04 +0200")
Hi,
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> skribis:
> Am Sonntag, dem 17.07.2022 um 12:20 +0200 schrieb Ludovic Courtès:
>> * guix/scripts/install.scm (show-help, %options): Add "--manifest".
>> * tests/guix-package-aliases.sh" Test "guix install -m".
>> ---
>> guix/scripts/install.scm | 8 ++++++--
>> tests/guix-package-aliases.sh | 16 +++++++++++++---
>> 2 files changed, 19 insertions(+), 5 deletions(-)
>>
>> Hi!
>>
>> I think it’s convenient and quite natural to be able to type:
>>
>> guix install -m manifest.scm
>>
>> Hence this patch. Objections? :-)
> I think the semantics of `guix install -m' are somewhat unclear. It
> can mean both "add all of manifest to what I already have installed"
> and "use manifest exactly as the manifest". The latter is equivalent
> to `guix package -m' (which has clearer semantics here) and also the
> implementation chosen IIUC. Personally, I don't think I'd want
> "install" to remove packages.
Right. To me, ‘-m’ is always declarative: you get what the manifest
prescribes, nothing else; this is how it’s currently documented.
Do you think it could be interpreted as “add all of manifest to what I
already have installed”?
Ludo’.
next prev parent reply other threads:[~2022-07-21 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 10:20 [bug#56612] [PATCH] guix install: Add '--manifest' option Ludovic Courtès
2022-07-19 10:01 ` Liliana Marie Prikler
2022-07-21 9:09 ` Ludovic Courtès [this message]
2022-07-21 10:37 ` Tobias Geerinckx-Rice via Guix-patches via
2022-07-22 20:58 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r12en865.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=56612@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.