From: Andreas Enge <andreas@enge.fr>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: Andy Tai <atai@atai.org>, guix-devel@gnu.org
Subject: Re: guidelines for package names (namespaces?)
Date: Thu, 6 Jul 2023 16:23:30 +0200 [thread overview]
Message-ID: <ZKbOYoDxkO_Fr_Z4@jurong> (raw)
In-Reply-To: <87fs62kt5s.fsf@protonmail.com>
Am Wed, Jul 05, 2023 at 08:19:48PM +0000 schrieb John Kehayias:
> This is a good question and one I wonder about when packaging
> sometimes. The general guideline I've seen expressed in Python land at
> least (not sure if this is in the manual, but this discussion can go
> towards clarifying) is that generally "libraries" get the "python-"
> prefix but end user "applications" don't. I believe this is true for
> Golang as well, though exceptions abound.
See here:
https://guix.gnu.org/de/manual/devel/en/html_node/Package-Naming.html
https://guix.gnu.org/de/manual/devel/en/html_node/Python-Modules.html
https://guix.gnu.org/de/manual/devel/en/html_node/Perl-Modules.html
I think there are no explicit rules for other languages, but the Perl and
Python approach has been taken as a general model.
> 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.
> the relationship between these two is not clear, there are no formal rules, or even guidelines. they are pretty much orthogonal.
See the first link above: "Both are usually the same and correspond to the
lowercase conversion of the project name chosen upstream (...)".
Andreas
next prev parent reply other threads:[~2023-07-06 14:24 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 [this message]
2023-07-06 9:28 ` Attila Lendvai
2023-07-06 15:24 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
-- 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=ZKbOYoDxkO_Fr_Z4@jurong \
--to=andreas@enge.fr \
--cc=atai@atai.org \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.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).