all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 47911@debbugs.gnu.org
Subject: bug#47911: Package outputs should be described in the UI
Date: Tue, 20 Apr 2021 23:54:29 +0200	[thread overview]
Message-ID: <87h7k08vvu.fsf@gnu.org> (raw)
In-Reply-To: <YH8Rl4J57UHo87Kg@jasmine.lan> (Leo Famulari's message of "Tue, 20 Apr 2021 13:38:31 -0400")

Hi,

Leo Famulari <leo@famulari.name> skribis:

> At least once a month I have to help somebody on IRC who didn't notice
> that our Git package is split into multiple outputs.
>
> They can't find `git send-email`, and the Guix package UI doesn't make
> this clear enough.

Just a side note: our ‘git’ package uses outputs in a rather unusual
way.  There are other packages that provide different features in
different outputs, but the majority of multiple-output packages have the
“standard” outputs: “doc”, “bin”, “lib”, “debug”.

So maybe we could look at the ‘git’ package (can it be split into
several packages? would that help?) in addition to the UI, and also make
sure the UI is optimized for the most frequent cases.

Ludo’.




  parent reply	other threads:[~2021-04-20 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 17:38 bug#47911: Package outputs should be described in the UI Leo Famulari
2021-04-20 17:43 ` bug#47911: Improving the package outputs UI Leo Famulari
2021-04-20 22:05   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-21  0:52     ` Leo Famulari
2021-04-20 19:42 ` bug#47911: Package outputs should be described in the UI Bone Baboon via Bug reports for GNU Guix
2021-04-20 21:54 ` Ludovic Courtès [this message]
2021-04-21  0:59   ` Leo Famulari

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=87h7k08vvu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47911@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.