unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix CLI, thoughts and suggestions
Date: Sun, 4 Feb 2024 13:21:01 +0100	[thread overview]
Message-ID: <CAEtmmeztpa7rksh0tvYb+0zpZF8ngyxzqQ801jAAwGk3-0pW0g@mail.gmail.com> (raw)
In-Reply-To: <87plxuz07x.fsf@zancanaro.id.au>

This is something we're capable of too, right?
https://everything.curl.dev/libcurl/libcurl

Bost

Le lun. 22 janv. 2024 à 01:22, Carlo Zancanaro <carlo@zancanaro.id.au> a écrit :
>
> Hi Ian,
>
> On Sat, Jan 20 2024, Ian Eure wrote:
> > I agree that this would make sense, but my understanding is that `guix
> > package' doesn’t work like that -- it only performs the final
> > operation in the list.  IMO, it should either do *everything* the
> > commands specify, or print an error and take no action.
>
> It can accumulate multiple commands. As an example, if you create a
> profile with a single package in it:
>
>   $ guix package -i hello
>   The following package will be installed:
>      hello 2.12.1
>   ... more output...
>
> then you can remove that package and install another package in a single
> transaction:
>
>   $ guix package -r hello -i coreutils
>   The following package will be removed:
>      hello 2.12.1
>
>   The following package will be installed:
>      coreutils 9.1
>   ... more output...
>
> The inconsistency here is that some commands can be combined
> (specifically adding and removing), whereas others cannot (probably
> everything else).
>
> > I agree, I don’t think the situation can be improved without finding a
> > solution to preserve BC.  But, I didn’t think it was worth making
> > detailed plans for any of this before gauging whether the problem was
> > one broadly considered to be worth solving.
>
> I think it would be great to have a consistent CLI, so I would love it
> if we were able to solve this problem.
>
> Carlo
>


  reply	other threads:[~2024-02-04 12:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 19:24 Guix CLI, thoughts and suggestions Ian Eure
2024-01-15 21:01 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-15 22:08 ` Carlo Zancanaro
2024-01-20 22:50   ` Ian Eure
2024-01-22  0:21     ` Carlo Zancanaro
2024-02-04 12:21       ` Rostislav Svoboda [this message]
2024-01-17  7:21 ` Efraim Flashner
2024-01-18 13:51   ` Rostislav Svoboda

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=CAEtmmeztpa7rksh0tvYb+0zpZF8ngyxzqQ801jAAwGk3-0pW0g@mail.gmail.com \
    --to=rostislav.svoboda@gmail.com \
    --cc=guix-devel@gnu.org \
    /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).