From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: "Ludovic Courtès" <ludo@gnu.org>, zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix package --search slow ?
Date: Wed, 15 May 2019 15:48:28 +0200 [thread overview]
Message-ID: <e3ca56e4-2b8d-0c8d-28bb-6d00ef9510af@web.de> (raw)
In-Reply-To: <87r28zu9hs.fsf@gnu.org>
On 5/15/19 3:34 PM, Ludovic Courtès wrote:
> We could probably improve the cold-cache timings by adding synopses and
> descriptions to the package cache that ‘guix pull’ builds in
> ~/.config/guix/current/lib/guix/package.cache, but that would also make
> that cache bigger. Not sure if it’s worth it.
Another idea would be to have some kind of simple search which only
includes the package name and maybe the synopsis. So this could go to
the cache and I would assume that a cold-cache search will also be
faster. And as a nice give away, it doesn't include so much scrolling :)
So something like:
$ guix search --simple numpy
python-numpy | Fundamental package for scientific...
python-numpy-documentation | Documentation for the python-numpy...
python-numpydoc |
python2-numpy |
python2-numpy |
python2-numpy-documentation |
python2-numpydoc |
But in general I don't find the search so slow. Sometimes zypper for
example has to refresh the repos and than "guix search" is faster, even
with cold cache...
next prev parent reply other threads:[~2019-05-15 13:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 17:19 guix package --search slow ? zimoun
2019-05-14 20:17 ` Ricardo Wurmus
2019-05-15 9:54 ` zimoun
2019-05-15 11:35 ` Ricardo Wurmus
2019-05-15 13:34 ` Ludovic Courtès
2019-05-15 13:43 ` Pierre Neidhardt
2019-05-16 15:13 ` Ludovic Courtès
2019-05-15 13:48 ` Jonathan Brielmaier [this message]
2019-05-15 14:08 ` Pierre Neidhardt
2019-05-15 14:50 ` zimoun
2019-05-15 15:11 ` Pierre Neidhardt
2019-05-15 14:31 ` zimoun
2019-05-15 14:23 ` zimoun
2019-05-15 18:32 ` zimoun
2019-05-15 20:30 ` Giovanni Biscuolo
2019-05-15 2:22 ` Meiyo Peng
2019-05-15 9:59 ` zimoun
2019-05-15 14:08 ` zimoun
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=e3ca56e4-2b8d-0c8d-28bb-6d00ef9510af@web.de \
--to=jonathan.brielmaier@web.de \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.