From: Brandon Invergo <brandon@invergo.net>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org, gnu-system-discuss@gnu.org
Subject: Re: Guix != GNU GSD ==> True
Date: Wed, 28 Jan 2015 14:22:02 +0000 [thread overview]
Message-ID: <1422454922.1090.83.camel@invergo.net> (raw)
In-Reply-To: <87k307rxg3.fsf@taylan.uni.cx>
I recognize that the Guix / GSD naming matter is settled, but some
extra, more general thoughts, prompted by this:
On Wed, 2015-01-28 at 11:50 +0100, Taylan Ulrich Bayırlı/Kammer wrote:
> We really need a break from, or almost a fight against, this whole
> "distro" culture
More practically, perhaps we should push a more accurate term than
"distribution". Setting aside what this word has come to mean today,
when I think of "software distribution", I think of simply a collection
of software packages that one can install (e.g. a bunch of independent
software archives distributed on a CD-ROM...in fact, I guess this could
fairly well describe the first distros). In this sense of the word, the
GNU Source Release Collection (GSRC) is more accurately described as a
software distribution: it consists of a means to easily install a
variety of GNU software packages. GSD, Parabola, etc offer more than
that, so calling them "distributions" does them a disservice.
What we call software distributions today encompass a lot more than just
the collection of software that they offer. In particular, this
includes all of the configuration, init scripts, package management
tools, and other glue that tie it all together. The "GNU System", on
the other hand, is a bit different and more general: it is the result of
the interactions between that software (a system is always more than the
sum of its parts), regardless of the specific configuration. That's why
Trisquel, Parabola, GSD, et al. can all implement the GNU system, even
though the specific software packages (and versions), their
configuration and the "glue" that ties the software together are very
different: the overall pattern of interaction between the components is
the same, resulting in a recognizable system.
So, I would say that "distro" is not sufficient to describe what these
projects do, while the "system" is something else that they ultimately
implement in common. This is why I previously suggested referring to
Guix (now GSD) as the "reference implementation of the GNU
system" (ignoring now the argument over "reference", please).
I would suggest changing our terminology in general from "GNU/Linux
distro" to "GNU implementation" but it's feels a bit clunky to say.
"GNU variant" implies that one can find reference (which was resolutely
rejected). "GNU version" just doesn't have a good ring to it. I don't
know...Any other suggestions? Or am I talking nonsense?
-brandon
--
Brandon Invergo
http://brandon.invergo.net
next prev parent reply other threads:[~2015-01-28 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Y0kYi-00007u-3r@fencepost.gnu.org>
[not found] ` <8761dcc693.fsf@invergo.net>
[not found] ` <E1Y15KU-0002IJ-U9@fencepost.gnu.org>
[not found] ` <87sigemze4.fsf@gnu.org>
[not found] ` <E1Y2y6a-0002HW-2d@fencepost.gnu.org>
[not found] ` <20150121193716.GF11138@alien.local>
[not found] ` <874mrgo399.fsf@gnu.org>
[not found] ` <87h9vccs2h.fsf_-_@unicorn.home>
[not found] ` <54C7B7B9.6050706@gnu.org>
[not found] ` <E1YGFrr-0001qy-FV@fencepost.gnu.org>
2015-01-28 2:49 ` Guix != GNU GSD ==> True Bruno Félix Rezende Ribeiro
2015-01-28 3:07 ` Nala Ginrut
2015-01-28 10:50 ` Taylan Ulrich Bayırlı/Kammer
2015-01-28 13:45 ` Svetlana Tkachenko
2015-01-28 16:13 ` Richard Stallman
2015-01-28 14:22 ` Brandon Invergo [this message]
2015-01-28 16:21 ` Taylan Ulrich Bayırlı/Kammer
2015-01-29 12:31 ` Richard Stallman
2015-01-29 14:48 ` Alfred M. Szmidt
2015-01-29 22:01 ` Richard Stallman
2015-01-29 12:30 ` Richard Stallman
2015-01-29 13:20 ` Bruno Félix Rezende Ribeiro
2015-01-29 14:03 ` Luis Felipe López Acevedo
2015-01-28 16:05 ` Ludovic Courtès
2015-01-28 16:11 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1422454922.1090.83.camel@invergo.net \
--to=brandon@invergo.net \
--cc=gnu-system-discuss@gnu.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.