unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: guidelines for package names (namespaces?)
Date: Thu, 06 Jul 2023 09:28:18 +0000	[thread overview]
Message-ID: <j7TwIbj4RUtaGaBq_TJBCISnVQ6z4QzPOUMGlGhmGMRGHYtWTqG3i4sJN0bvTcBh8KyBYdTDAEXGPbX5JEE-w7rvdoeoj4atRMyVwTt9Eek=@lendvai.name> (raw)
In-Reply-To: <CAJsg1E_Z-0neB+c46G-TT-+E+Z2tt9MfO=dauGBOKts886qvxg@mail.gmail.com>

> Or GNU Guix maintainers may want to consider some type of name space
> support in the package name space because I think name collisions will
> be more and more likely as more packages are submitted for inclusion
> in Guix.


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.

i don't have a specific issue with this, besides that it was rather confusing for me as a newcomer, and that it bothers the gut instinct of the engineer inside me.

the idea of namespaces is nothing new, and has already been solved by 1). i'm not sure about all the implications, but i think picking 1) and dropping 2) is worth considering. it would automatically keep track of a namespace hierarchy, and the guix GUI would have enough data to act intelligently in situations like package-name clashes.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“All experience is a drug experience. Whether it’s mediated by our own [endogenous] drugs, or whether it’s mediated by substances that we ingest that are found in plants, cognition, consciousness, the working of the brain, it’s all a chemically mediated process. Life itself is a drug experience.”
	— Dennis Mckenna (1950–)



  parent reply	other threads:[~2023-07-06  9:29 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 [this message]
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='j7TwIbj4RUtaGaBq_TJBCISnVQ6z4QzPOUMGlGhmGMRGHYtWTqG3i4sJN0bvTcBh8KyBYdTDAEXGPbX5JEE-w7rvdoeoj4atRMyVwTt9Eek=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=atai@atai.org \
    --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).