From: Ricardo Wurmus <rekado@elephly.net>
To: Liam Wigney <liamwigney950@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: How'd Guix end up in the Gnu project?
Date: Mon, 21 Aug 2017 13:30:04 +0200 [thread overview]
Message-ID: <87k21xw43n.fsf@elephly.net> (raw)
In-Reply-To: <A4CEC09A-6C03-4576-8F84-B16D74541774@gmail.com>
Hi Liam,
I wasn’t around when this happened, but often when packages join GNU
there isn’t much of a story to be told.
Guix clearly fits into the bigger picture painted by GNU.
One of the core ideas of GNU is to give users more freedom and the tools
to meaningfully exercise that freedom. The Hurd, for example, does this
by putting more parts of the operating system under the control of
regular users, even on shared systems. The super user is no longer as
important as on other systems.
With Guix users gain the freedom to install their own package variants,
freeing them from arbitrary restrictions of system administrators.
Again, the need for a super user is reduced. Users also gain practical
software freedom in that they can easily access the sources of software
they have installed and replace a package with a variant of their own.
It is only fitting that Guix is part of GNU.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-08-21 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 8:56 How'd Guix end up in the Gnu project? Liam Wigney
2017-08-21 11:30 ` Ricardo Wurmus [this message]
2017-08-22 9:53 ` 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=87k21xw43n.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=liamwigney950@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.
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).