unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: calcium <calcium@disroot.org>
Cc: 53030@debbugs.gnu.org
Subject: bug#53030: Can't (specification->package "package@version:output")
Date: Wed, 05 Jan 2022 21:36:02 +0100	[thread overview]
Message-ID: <87wnjdhot8.fsf@nckx> (raw)
In-Reply-To: <90c20a11-e5a7-4e13-7f75-0538aebe957d@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]

Calcium,

Thanks for the report!

In future, please submit separate issues separately, it helps keep 
discussion, er, separate.  It's easier to merge issues than to 
split them.

> Can't (specification->package "package@version:output")

Short answer: it is not intended to work.  Use 
specification->package+output if you want outputs.  This is not a 
bug but a design decision.  Which are not above critique, but 
guix-devel@ might be a better place for that.

I've considered in the past to submit a cheeky patch silently 
renaming specification->package+ouput to specification->package, 
just to avoid this FAQ.  It should be almost perfectly backwards 
compatible in that no existing code should break with the same 
input.

However I think clarity the greater value here, and did not submit 
such a patch.

calcium via Bug reports for GNU Guix 写道:
> The syntaxe to specify a package version and desired output
> only works on guix install package@version:output
>
> guix remove package@version:output doesn't works

I cannot reproduce this:

  $ guix install git@2.34.0:send-email
  $ guix remove git@2.34.0:send-email
  $

Can you provide an example?

> guix remove package@version doesn't works

‘package@version’ means ‘package@version:out’, not (a 
hypothetical) ‘package@version:*’ wildcard.  It neither installs 
nor removes ‘all outputs’.

I did notice that, e.g.,

  $ guix install git@2:send-email
  $ guix remove git@2:send-email
  guix remove: error: package 'git@2:send-email' not found in 
  profile
  $

is asymmetrical.  I wonder if there are any drawbacks to making it 
work.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      reply	other threads:[~2022-01-05 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 17:18 bug#53030: Can't (specification->package "package@version:output") calcium via Bug reports for GNU Guix
2022-01-05 20:36 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]

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=87wnjdhot8.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=53030@debbugs.gnu.org \
    --cc=calcium@disroot.org \
    --cc=me@tobias.gr \
    /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).