unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 62264@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Antoine R. Dumont" <antoine.romain.dumont@gmail.com>,
	guix-devel@gnu.org
Subject: [bug#62264] [PATCH v2 0/3] Add 'guix locate'
Date: Thu,  8 Jun 2023 00:09:51 +0200	[thread overview]
Message-ID: <cover.1686175352.git.ludo@gnu.org> (raw)
In-Reply-To: <87zg5e27cd.fsf_-_@gnu.org>

Hello!

Here is the “camera-ready” version of the new ‘guix locate’ command
(formerly ‘guix index’) that Antoine and myself have worked on.
I think it’s ready to go.

This version relies only on local knowledge, which means you can
only find packages already in your store.  In a future iteration,
we’ll add an optional mechanism to download the database from
elsewhere.

Thoughts?

Ludo’.

Ludovic Courtès (3):
  store: Tolerate non-existent GC root directories.
  Add 'guix locate'.
  DRAFT news: Add entry for 'guix locate'.

 Makefile.am             |   2 +
 doc/guix.texi           | 118 ++++++++
 etc/news.scm            |  17 ++
 guix/scripts/locate.scm | 657 ++++++++++++++++++++++++++++++++++++++++
 guix/store/roots.scm    |  12 +-
 po/guix/POTFILES.in     |   1 +
 tests/guix-locate.sh    |  72 +++++
 tests/store-roots.scm   |  18 +-
 8 files changed, 892 insertions(+), 5 deletions(-)
 create mode 100644 guix/scripts/locate.scm
 create mode 100755 tests/guix-locate.sh


base-commit: e8f9fb3e03ea8fee0e13f13706a6b16414f74a7b
-- 
2.40.1





       reply	other threads:[~2023-06-07 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87zg5e27cd.fsf_-_@gnu.org>
2023-06-07 22:09 ` Ludovic Courtès [this message]
2023-06-09  3:57   ` [bug#62264] [PATCH v2 0/3] Add 'guix locate' Ryan Prior
2023-06-15 22:02     ` bug#62264: [PATCH] Add 'guix locate' command 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=cover.1686175352.git.ludo@gnu.org \
    --to=ludo@gnu.org \
    --cc=62264@debbugs.gnu.org \
    --cc=antoine.romain.dumont@gmail.com \
    --cc=guix-devel@gnu.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 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).