GNU bug report logs -
#39258
Faster guix search using an sqlite cache
Previous Next
Full log
Message #164 received at 39258 <at> debbugs.gnu.org (full text, mbox):
Hi,
On Sat, 7 Mar 2020 at 21:33, Ludovic Courtès <ludo <at> gnu.org> wrote:
> Arun Isaac <arunisaac <at> systemreboot.net> skribis:
> > Why not use a simpler package search results format like Arch Linux or Debian
> > does? We could just display the package name, version and synopsis like so.
> >
> > inkscape 0.92.4
> > Vector graphics editor
> > inklingreader 0.8
> > Wacom Inkling sketch format conversion and manipulation
> >
> > Why do we need the entire recutils format? If the user is interested, they can
> > always use `guix package --show` to get the full recutils formatted
> > info. Having shorter search results will make everything even faster and much
> > more readable. WDYT?
>
> What I like about the recutils format in this context is that it’s both
> human- and machine-readable. The examples in the manual show how it can
> be useful to select the information displayed or to refine the search
> (info "(guix) Invoking guix package").
>
> Also: I’d recommend tackling one thing at a time. :-)
I agree with Ludo.
And IMHO, we should add "guix search --format=<options>" mimicking how
"git log" works.
By default, displays as Arun proposes. Using '--format=full" as it is
done now by default.
And we could imagine "--format=%name \t %version \n %description" etc.
> I think we should look at a profile of ‘package->recutils’, there’s
> probably room for improvement there.
Interesting. Note that speed was the initial motivation but accuracy
is another important one. As we discussed earlier when I showed an
example with TF-IDF. And Xapian implemets the state-of-art (BM25) for
scoring.
All the best,
simon
This bug report was last modified 37 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.