unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitri Paduchikh <dpaduchikh@gmail.com>
To: bug-guix@gnu.org
Subject: Re: Distro name
Date: Thu, 03 Jan 2013 03:33:28 +0600	[thread overview]
Message-ID: <87sj6jjmmv.fsf@dpaduchikh.invalid> (raw)
In-Reply-To: <87zk0r8nv4.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 02 Jan 2013 19:02:23 +0100")

Ludovic Courtès wrote:

> The (distro ...) name for modules of the distro wasn’t meant to last.
> Initially, I thought we could find a name for the distro, and substitute
> that name to “distro”.  Possible names:

>   • Jinn, as in “Jinn is not Nixpkgs/NixOS”;
>   • Guixotic, as Guix + Exotic (suggested by RMS).

These seem rather baroque to me. Especially the reference to nixpkgs in
such a context. The name "Unix" is pretty much widespread so the
abbreviation "GNU" can be seen as ingenious. nixpkgs is much less known
and hence this looks weird, IMHO.

I would propose Guix World as a externally visible name, and just world
or distro for internal namespace usage.

> However, I’ve come to think that we don’t necessarily need a separate
> name for the distro, but we do need a name for the module name space.

It would be good to have name for distro. How would you refer to it
otherwise?

> The obvious solution would be (gnu ...).  There’d be modules like
> (gnu packages openssl), which does not mean that OpenSSL is a GNU
> package, but I think that should be clear in this context.  Anyway,
> that’s the option that I like the most currently.

It may be clear, but your example demonstrates internal inconsistency of
such naming. Is Guix intended for GNU software only? If not, then be
fair to all the others. ;)

-- 
With best regards
Dmitri Paduchikh

  parent reply	other threads:[~2013-01-02 21:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02 18:02 Distro name Ludovic Courtès
2013-01-02 21:05 ` Jason Self
2013-01-02 21:38   ` Ludovic Courtès
2013-01-02 22:51     ` Jason Self
2013-01-02 23:32       ` Ludovic Courtès
2013-01-02 21:49   ` Dmitri Paduchikh
2013-01-02 23:14     ` Jason Self
2013-01-02 21:33 ` Dmitri Paduchikh [this message]
2013-01-02 21:42   ` Ludovic Courtès
2013-01-03  1:22   ` Nikita Karetnikov
2013-01-02 22:42 ` Andreas Enge
2013-01-02 22:48   ` Ludovic Courtès
2013-01-02 23:09     ` Dmitri Paduchikh
2013-01-03  8:45     ` Andreas Enge
2013-01-03 14:37       ` Ludovic Courtès
2013-01-03 16:42         ` Andreas Enge
2013-01-03  1:12 ` Nikita Karetnikov
2013-01-15 21:36 ` Ludovic Courtès
2013-01-16  8:38   ` Andreas Enge
2013-01-16 16:56     ` Ludovic Courtès
2013-01-17 15:02       ` Andreas Enge
2013-01-18  1:28   ` 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=87sj6jjmmv.fsf@dpaduchikh.invalid \
    --to=dpaduchikh@gmail.com \
    --cc=bug-guix@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).