unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 47911@debbugs.gnu.org
Subject: bug#47911: Package outputs should be described in the UI
Date: Tue, 20 Apr 2021 20:59:10 -0400	[thread overview]
Message-ID: <YH943sJUUqP9iW0k@jasmine.lan> (raw)
In-Reply-To: <87h7k08vvu.fsf@gnu.org>

On Tue, Apr 20, 2021 at 11:54:29PM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> > 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.

That's true. And I don't have any other packages in mind, really.

I first had this idea after roptat was talking about adding ocaml
bindings for z3 [0]. He wrote:

"it builds the bindings in a separate output, instead of a separate
package, because they're part of the same source, and it doesn't look
like it's possible to build them separately
[...]
I'm just not very happy it's part of the same package, because it's less
discoverable vs ocaml-z3"

So, I do think there is room for improvement to this aspect of the UI.

> 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”.

Right, and it would not be worthwhile to add anything to the UI for
these.

The 'output synopsis' would only be printed in the UI if we actually
defined a synopsis for it. That way, we wouldn't have 16000 lines of
noise like "debug symbols for foo" in `guix package --search=.`

> 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.

Good question. The Git package is super complicated, so I'm not feeling
very motivated to think about how to rewrite it :)

[0] https://logs.guix.gnu.org/guix/2021-03-11.log#194242
https://issues.guix.gnu.org/46329




      reply	other threads:[~2021-04-21  1:00 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
2021-04-21  0:59   ` Leo Famulari [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=YH943sJUUqP9iW0k@jasmine.lan \
    --to=leo@famulari.name \
    --cc=47911@debbugs.gnu.org \
    --cc=ludo@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).