all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, Guix Devel <guix-devel@gnu.org>
Subject: Re: File search
Date: Fri, 21 Jan 2022 21:53:17 -0500	[thread overview]
Message-ID: <87pmok8orm.fsf@gmail.com> (raw)
In-Reply-To: <874k5w38s7.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 22 Jan 2022 01:37:28 +0100")

Hi Ludovic,

Thank you for this valuable initiative :-).  I like that it sits in few
lines and should already be useful for local searches with a minimal
front command to query it.

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Vagrant Cascadian <vagrant@debian.org> skribis:
>
>> What about ... a roughly weekly job that runs on ci.guix. to create the
>> database and packages of parts of the database and a channel that
>> includes those and utilities to query them so that you can install the
>> packages and refresh them at your leisure...
>>
>> Or just put the packages in the main repository, and update it manually
>> roughly weekly?
>
> Making the database a package (or set of packages) sounds quite weird or
> at least very unusual from a Guix viewpoint, where packages normally
> describe build procedures.
>
> But a cron job publishing a file somewhere, why not!

I also had the idea of making it a package... this way only the people
who opt to install the database locally would incur the cost (in
bandwidth).

Perhaps a question for Vagrant: talking about size, is this SQLite
database file comparable or smaller in size to the apt-file database
that needs to be downloaded?  With the Debian software catalog being
about 30% bigger, I'd expect a similarly bigger file size.

If Debian is doing better in terms of database file size, we could look
at how they're doing it.

Thank you!

Maxim


  reply	other threads:[~2022-01-22  2:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21  9:03 File search Ludovic Courtès
2022-01-21 10:35 ` Mathieu Othacehe
2022-01-22  0:35   ` Ludovic Courtès
2022-01-21 19:00 ` Vagrant Cascadian
2022-01-22  0:37   ` Ludovic Courtès
2022-01-22  2:53     ` Maxim Cournoyer [this message]
2022-01-25 11:15       ` Ludovic Courtès
2022-01-25 11:20         ` Oliver Propst
2022-01-25 11:22           ` Oliver Propst
2022-01-22  4:46 ` raingloom
2022-01-22  7:55   ` Ricardo Wurmus
2022-01-24 15:48     ` Ludovic Courtès
2022-01-24 17:03       ` Ricardo Wurmus
2022-02-02 16:14         ` Maxim Cournoyer
2022-02-05 11:15           ` Ludovic Courtès
2022-01-25 23:45 ` Ryan Prior
2022-02-05 11:18   ` Ludovic Courtès
2022-02-06 13:27 ` André A. Gomes
  -- strict thread matches above, loose matches on Subject: below --
2022-12-02 17:58 antoine.romain.dumont
2022-12-02 18:22 ` Antoine R. Dumont (@ardumont)
2022-12-03 18:19   ` Ludovic Courtès
2022-12-04 16:35     ` Antoine R. Dumont (@ardumont)
2022-12-06 10:01       ` Ludovic Courtès
2022-12-06 12:59         ` zimoun
2022-12-06 18:27         ` (
2022-12-08 15:41           ` Ludovic Courtès
2022-12-09 10:05         ` Antoine R. Dumont (@ardumont)
2022-12-09 18:05           ` zimoun
2022-12-11 10:22           ` Ludovic Courtès
2022-12-15 17:03             ` Antoine R. Dumont (@ardumont)
2022-12-19 21:25               ` Ludovic Courtès
2022-12-19 22:44                 ` zimoun
2022-12-20 11:13                 ` Antoine R. Dumont (@ardumont)

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=87pmok8orm.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=vagrant@debian.org \
    /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.