From: Simon Josefsson via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: advanced?
Date: Mon, 28 Nov 2022 15:44:50 +0100 [thread overview]
Message-ID: <871qpnp28t.fsf@latte> (raw)
In-Reply-To: <874juje38n.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 28 Nov 2022 12:18:48 +0100")
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
Thanks Liliana, zimoun, Ryan and Vagrant for feedback!
Ludovic Courtès <ludo@gnu.org> writes:
> Or if we do want to explain more, then perhaps we need a list of
> features that would also include things like Docker/VM image generation,
> declarative home environments, etc. But that’s broader topic.
Yes, that makes sense. I'm not the best person to summarize it, but
starting pointers if someone wants to take it further:
* Dedication to free software goals and the GNU community
* Shepherd init system written in Guile
* Declarative stateless system configurations
* Transactional upgrades and roll-backs
* Reproducible build environments
* Designed towards bootstrappable builds
Maybe this fits better directly in the Introduction section of the
manual? https://guix.gnu.org/manual/en/html_node/Introduction.html
> PS: For the record, the phrase “advanced distribution of the GNU system”
> was coined by RMS at a time where he insisted that this thing cannot
> be called “the GNU system”. All this makes little sense, even less
> so today, but if you’re curious you may enjoy Andreas’ entertaining
> talk: https://10years.guix.gnu.org/video/ten-years-of-failures/
Ah, thanks, the wording of that paragraph is more understandable now! I
can see how that wording came about, and also how it clarify compared to
the GNU system. I think this knowledge was the missing piece I didn't
have. As an introduction to what Guix is for someone without earlier
understanding of GNU etc, I still believe that the word 'advanced' does
not contribute though.
/Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2022-11-28 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 21:47 advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-27 8:51 ` advanced? Liliana Marie Prikler
2022-11-27 12:39 ` advanced? zimoun
2022-11-27 17:22 ` advanced? Ryan Prior
2022-11-27 18:35 ` advanced? Vagrant Cascadian
2022-11-28 11:18 ` advanced? Ludovic Courtès
2022-11-28 14:44 ` Simon Josefsson via Development of GNU Guix and the GNU System distribution. [this message]
2022-11-28 18:36 ` advanced? zimoun
2023-01-04 11:00 ` advanced? Ludovic Courtès
2023-01-09 12:02 ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 15:35 ` advanced? Denis 'GNUtoo' Carikli
2023-01-04 10:54 ` advanced? Ludovic Courtès
2023-01-09 11:12 ` advanced? Ludovic Courtès
2023-01-09 11:37 ` advanced? Julien Lepiller
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=871qpnp28t.fsf@latte \
--to=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=simon@josefsson.org \
--cc=vagrant@debian.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).