From: zimoun <zimon.toutoune@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>,
help-guix@gnu.org, yasu <yasu@yasuaki.com>
Subject: Re: Bug? coqide missing? (in package coq, version 8.11.2)
Date: Sat, 20 Mar 2021 17:39:20 +0100 [thread overview]
Message-ID: <86k0q1wzif.fsf@gmail.com> (raw)
In-Reply-To: <08B18747-D14D-4D0E-91ED-A7E06BCFAA77@lepiller.eu>
Hi Julien,
On Sat, 20 Mar 2021 at 06:48, Julien Lepiller <julien@lepiller.eu> wrote:
> This is not a bug: coqide brings a lot of dependencies, so it's in a
What do you mean?
--8<---------------cut here---------------start------------->8---
$ guix package -i coq -n
The following package would be installed:
coq 8.11.2
125.8 MB would be downloaded
$ guix package -i coq:ide -n
The following package would be installed:
coq:ide 8.11.2
125.8 MB would be downloaded
$ guix package -i coq coq:ide -n
The following packages would be installed:
coq 8.11.2
coq:ide 8.11.2
125.8 MB would be downloaded
--8<---------------cut here---------------end--------------->8---
> separate output, as you can see with guix search or guix show. To
> install it, install the ide output, like so:
>
> guix install coq:ide
I am always confused by these multi-outputs packages, as git:send-email
or coq:ide or th recent “ocaml-z3“. They often increase the number of
build-time dependencies and they are less discoverable, IMHO.
They make sense for -doc or -debug but otherwise they appear to me
confusing.
Cheers,
simon
next prev parent reply other threads:[~2021-03-20 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 6:11 Bug? coqide missing? (in package coq, version 8.11.2) yasu
2021-03-20 10:48 ` Julien Lepiller
2021-03-20 12:26 ` yasu
2021-03-20 16:39 ` zimoun [this message]
2021-03-20 23:53 ` Julien Lepiller
2021-03-21 0:34 ` zimoun
2021-03-21 2:04 ` Julien Lepiller
2021-03-21 12:06 ` zimoun
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=86k0q1wzif.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=yasu@yasuaki.com \
/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.
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).