From: zimoun <zimon.toutoune@gmail.com>
To: Meiyo Peng <meiyo@riseup.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix package --search slow ?
Date: Wed, 15 May 2019 16:08:05 +0200 [thread overview]
Message-ID: <CAJ3okZ3GipBrPrvNz4MqXkY-Z6BoR9CdGZ7gzW6O70PW-05hEw@mail.gmail.com> (raw)
In-Reply-To: <87ef505udr.fsf@riseup.net>
Hi,
On Wed, 15 May 2019 at 04:22, Meiyo Peng <meiyo@riseup.net> wrote:
>
> I remember "guix package --search" has always been pretty fast since
> this patch series of Ludovic is merged into guix:
> https://lists.gnu.org/archive/html/guix-patches/2019-01/msg00254.html.
>
> Before that, "guix package --search" is slow.
From the message of the pointed patch, only `guix package -A` uses
this new cache. If I understand well.
I mean, this cache is loaded in the function `fold-available-packages'
used by the option `--list-available` but not in the functions used by
the option `--search`.
Ludo pointed the commit 94aeec0aef03ab44e41bfc3e77c3b623cb3d607c which
improves the search by doing directly on the raw Texinfo instead.
Maybe you remembered this one.
Thank you to pointing me this patch, now I know a bit more about the
internals. Not sure to understand well. :-)
All the ebst,
simon
prev parent reply other threads:[~2019-05-15 14:08 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ3GipBrPrvNz4MqXkY-Z6BoR9CdGZ7gzW6O70PW-05hEw@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=meiyo@riseup.net \
/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.