bug#47911: Package outputs should be described in the UI

bug#47911: Package outputs should be described in the UI

[Leo Famulari]

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.

I had the idea that package outputs besides 'out' and 'debug' should
have very brief descriptions that are exposed in `guix show` and `guix
search` and the `guix package` equivalents.

So, maybe it would look like this:

------
$ guix show git
name: git
version: 2.31.1
outputs: out send-email svn credential-netrc credential-libsecret subtree gui
  * send-email: Tools for an email-based Git workflow
  * svn: Provides git-svn, for bidirectional operation between Subversion and Git repositories
  * credential-libsecret: Whatever that is
  * subtree: Who knows?
  * gui: A graphical interface for exploring a Git repository
  * etc...
systems: x86_64-linux i686-linux
dependencies: asciidoc-py3@9.0.1 bash-minimal@5.0.16 bash@5.0.16 curl@7.74.0 docbook-xsl@1.79.1 expat@2.2.9 gettext-minimal@0.20.1 glib@2.62.6 libsecret@0.20.4 openssl@1.1.1i pcre2@10.35
+ perl-authen-sasl@2.16 perl-cgi@4.51 perl-io-socket-ssl@2.066 perl-net-smtp-ssl@1.04 perl-term-readkey@2.38 perl@5.30.2 pkg-config@0.29.2 python@3.8.2 subversion@1.14.1 tcl@8.6.10 tk@8.6.10
+ xmlto@0.0.28 zlib@1.2.11
location: gnu/packages/version-control.scm:173:2
homepage: https://git-scm.com/
license: GPL 2
synopsis: Distributed version control system  
description: Git is a free distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
------

The output of `guix show` and `guix search` are in recutils format, and
we'd need to make sure that these new UI elements continued that
valuable tradition.

bug#47911: Improving the package outputs UI

[Leo Famulari]

Another idea I had is to make Guix accept the concatenation of
packagename-output in the UI.

For example, `guix install git-send-email`, instead of `git:send-email`.

But maybe that is going too far, I'm not sure.

By the way, the #guix IRC discussion was here

https://logs.guix.gnu.org/guix/2021-03-11.log#194558

bug#47911: Package outputs should be described in the UI

[Bone Baboon via Bug reports for GNU Guix]

Leo Famulari writes:

> 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.
>
> I had the idea that package outputs besides 'out' and 'debug' should
> have very brief descriptions that are exposed in `guix show` and `guix
> search` and the `guix package` equivalents.

I ran into this issue when I started using Guix.

I like this idea.

bug#47911: Package outputs should be described in the UI

[Ludovic Courtès]

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

bug#47911: Improving the package outputs UI

[Tobias Geerinckx-Rice via Bug reports for GNU Guix]

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

Leo Famulari writes:
> Another idea I had is to make Guix accept the concatenation of
> packagename-output in the UI.

I'm firmly against this (but read on :-)

>
> For example, `guix install git-send-email`, instead of 
> `git:send-email`.
>
> But maybe that is going too far, I'm not sure.

I think it is, but the intention is good.

Instead, Guix could suggest (‘did you mean...?’) like it does for 
commands.

  ~ λ guix install git-send-email
  guix install: error: git-send-email: unknown package
  hint: Did you mean one of:
  git:send-email

Kind regards,

T G-R

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

bug#47911: Improving the package outputs UI

[Leo Famulari]

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

On Wed, Apr 21, 2021 at 12:05:05AM +0200, Tobias Geerinckx-Rice wrote:
> Leo Famulari writes:
> > Another idea I had is to make Guix accept the concatenation of
> > packagename-output in the UI.
> 
> I'm firmly against this (but read on :-)
> 
> > For example, `guix install git-send-email`, instead of `git:send-email`.
> > 
> > But maybe that is going too far, I'm not sure.
> 
> I think it is, but the intention is good.

It's definitely pie-in-the-sky daydreaming :)

> Instead, Guix could suggest (‘did you mean...?’) like it does for commands.
> 
>  ~ λ guix install git-send-email
>  guix install: error: git-send-email: unknown package
>  hint: Did you mean one of:
>  git:send-email

I think that's a better idea.

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

bug#47911: Package outputs should be described in the UI

[Leo Famulari]

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