unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Should guix track package aliases?
Date: Sun, 24 May 2020 15:25:58 -0400	[thread overview]
Message-ID: <CAFkJGRf3heu76R5TvpZb7K0+xmR2Dz2Qctztjzji6ZqrGC9x2g@mail.gmail.com> (raw)
In-Reply-To: <CAFkJGRd0tyQQgo7=g5Q5Y_w7q6yYO=xbmhJn0RtUJDFrOtPkjw@mail.gmail.com>

Checking http://guix.gnu.org/packages.json again, it seems like the
server changes to not misrepresent dates have not been applied yet.
Can someone get in and do that?

On Sun, May 10, 2020 at 2:16 PM Josh Marshall
<joshua.r.marshall.1991@gmail.com> wrote:
>
> This back and forth is what I've been having going on in my head.  We might be able to leverage repology.org for their work on mapping packages across distros.  Yesterday, civodul entered a bug to remove the Etag and last-modified headers in the nginx config to fix a bug on our side so repology will update info on guix.  That code is GPL'd so some of it could be incorporated, and maybe even be leveraged to interpret foreign distro's packages to create package prototypes which we could then use to more rapidly expand what packages are available through guix.  I could see this as a high-payoff medium effort development for guix.
>
> On Sun, May 10, 2020 at 9:34 AM zimoun <zimon.toutoune@gmail.com> wrote:
>>
>> Hi Julien,
>>
>> On Sun, 10 May 2020 at 14:13, Julien Lepiller <julien@lepiller.eu> wrote:
>>
>> > The proposal was about suggesting anotger nameqwhen no package was found, not to install something else.
>>
>> Sorry I misinterpreted.
>>
>>
>> > >Well, do you have specific example in mind?
>> >
>> > $ guix install gcc
>> > guix install: error: gcc: unknown package
>> > Hint: did you mean `guix install gcc-toolchain`?
>> >
>> > Since not being able to install gcc is surprising, and you don't always know about gcc-toolchain.
>>
>> I understand even if this one is the wrong example. :-)
>> It even deserves an entry in the manual.
>> Well, but I understand what you mean.
>>
>>
>> > $ guix install gpg
>> > Hint: did you mean `guix install gnupg`?
>>
>> The question is: why do you type 'gpg'?
>>
>> I mean, the upstream name is really GnuPG so it is not one "stupid"
>> Guix devs arbitrary rename because in their infinite wisdom they
>> decided to. ;-)
>>
>> Well, do you type 'gpg' because
>> a) it is the name of the binary?
>> or b) it is the name of the package in your previous favourite distro?
>>
>> If it is a), then a proposal by Pierre named "filesearch" is floating
>> around.  And this should improve the situation.
>>
>> If it is b), then I do not see how to improve the situation in the
>> general case.  But maybe there is some well-known cases.
>>
>>
>> > Often a name is used to refer to a package, and it's annoying to go through a search, especially when you have to filter a big output.
>>
>> I agree.  From my point the issue is that "guix search" is not doing
>> the job and the improvement should come from this.  And your 'gpg'
>> example is a good one, IMHO:
>>
>> --8<---------------cut here---------------start------------->8---
>> $ guix search gpg | recsel -C -p name,relevance
>> name: signing-party
>> relevance: 16
>> name: qgpgme
>> relevance: 15
>> name: libgpg-error
>> relevance: 14
>> name: python2-gpg
>> relevance: 11
>> name: python-gpg
>> relevance: 11
>> name: ledger-agent
>> relevance: 9
>> name: python2-pygpgme
>> relevance: 8
>> name: python-pygpgme
>> relevance: 8
>> name: gpgme
>> relevance: 8
>> name: kgpg
>> relevance: 6
>> name: jetring
>> relevance: 6
>> name: emacs-pinentry
>> relevance: 6
>> name: trezor-agent
>> relevance: 5
>> name: python-trezor-agent
>> relevance: 5
>> name: keepkey-agent
>> relevance: 5
>> name: qtpass
>> relevance: 2
>> name: pinentry
>> relevance: 2
>> name: pinentry-tty
>> relevance: 2
>> name: pinentry-qt
>> relevance: 2
>> name: pinentry-gtk2
>> relevance: 2
>> name: pinentry-gnome3
>> relevance: 2
>> name: pinentry-emacs
>> relevance: 2
>> name: pinentry-efl
>> relevance: 2
>> name: kleopatra
>> relevance: 2
>> name: gnupg
>> relevance: 2
>> name: gnupg
>> relevance: 2
>> name: git-remote-gcrypt
>> relevance: 2
>> name: gajim
>> relevance: 2
>> name: emacs-extend-smime
>> relevance: 2
>> name: assword
>> relevance: 2
>> --8<---------------cut here---------------end--------------->8---
>>
>> The expected package 'gnupg' appears... piouf!
>>
>> I fully agree that the experience with "guix search" is frustating.
>> And maybe using both the 'upstream-name' and an extra 'properties'
>> such as 'alternative-names' or 'extra-keywords' should help for
>> discoverability.
>>
>>
>> WDYT?
>>
>> All the best,
>> simon


  reply	other threads:[~2020-05-24 19:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 20:18 Should guix track package aliases? Josh Marshall
2020-05-10  9:10 ` Nikita Gillmann
2020-05-10  9:57 ` zimoun
2020-05-10 12:13   ` Julien Lepiller
2020-05-10 13:33     ` zimoun
2020-05-10 18:16       ` Josh Marshall
2020-05-24 19:25         ` Josh Marshall [this message]
2020-05-25 10:41           ` zimoun
2020-05-25 11:57             ` Josh Marshall
2020-05-25 12:04               ` Nicolò Balzarotti
2020-05-25 14:20                 ` Josh Marshall
2020-05-25 21:57                   ` Vincent Legoll
2020-05-25 22:30                     ` Josh Marshall
2020-05-25 23:14                       ` zimoun
2020-05-25 23:19                         ` Josh Marshall
2020-05-10 10:08 ` Vincent Legoll
2020-05-10 12:53   ` zimoun
2020-05-28 16:27     ` Ludovic Courtès

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=CAFkJGRf3heu76R5TvpZb7K0+xmR2Dz2Qctztjzji6ZqrGC9x2g@mail.gmail.com \
    --to=joshua.r.marshall.1991@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.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.
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).