From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Attila Lendvai <attila@lendvai.name>
Cc: Andy Tai <atai@atai.org>, guix-devel@gnu.org
Subject: Re: guidelines for package names (namespaces?)
Date: Thu, 6 Jul 2023 08:24:07 -0700 [thread overview]
Message-ID: <CAFHYt554kAh9SHkg2QPC_A1wgsVqJLqnrfTDUFEpsCo3Zb1n4A@mail.gmail.com> (raw)
In-Reply-To: <j7TwIbj4RUtaGaBq_TJBCISnVQ6z4QzPOUMGlGhmGMRGHYtWTqG3i4sJN0bvTcBh8KyBYdTDAEXGPbX5JEE-w7rvdoeoj4atRMyVwTt9Eek=@lendvai.name>
Hi,
On Thu, Jul 6, 2023 at 2:29 AM Attila Lendvai <attila@lendvai.name> wrote:
>
> a related issue is that currently there are two parallel registries for guix packages:
>
> 1) module-global variables in the guile module system
> 2) the reified package registry of guix.
Veering even further from Andy's topic of namespaces, please allow me
to suggest that we unite those two approaches.
Like Attila, I prefer the variables (except on the Guix command line).
Let's provide package variables—perhaps ending with asterisks—that
allow selections just like on the 'guix shell' command line.
They would look like that:
(ldns* #:version "1.8.3" #:output "drill") for "ldns@1.8.3:drill"
Meaningful symbolic selections for the version would also be possible,
like 'stable or 'latest. When the field is omitted, the caller would
get the most recent stable version available.
Kind regards,
Felix
next prev parent reply other threads:[~2023-07-06 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 20:55 guidelines for package names (namespaces?) Andy Tai
2023-07-05 20:19 ` John Kehayias
2023-07-06 4:53 ` Csepp
2023-07-06 14:23 ` Andreas Enge
2023-07-06 9:28 ` Attila Lendvai
2023-07-06 15:24 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-04 18:30 Juliana Sims
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=CAFHYt554kAh9SHkg2QPC_A1wgsVqJLqnrfTDUFEpsCo3Zb1n4A@mail.gmail.com \
--to=guix-devel@gnu.org \
--cc=atai@atai.org \
--cc=attila@lendvai.name \
--cc=felix.lechner@lease-up.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 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).