unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: guix-devel@gnu.org, guix-devel-bounces+amirouche=hypermove.net@gnu.org
Subject: Re: GNU Guix diagram
Date: Fri, 04 Mar 2016 12:52:28 -0500	[thread overview]
Message-ID: <87fuw6i10j.fsf@gmail.com> (raw)
In-Reply-To: <445c54bf7ca1941552e7c64de4a3f688@hypermove.net> (Amirouche Boubekki's message of "Fri, 04 Mar 2016 13:36:33 +0100")

Amirouche Boubekki <amirouche@hypermove.net> writes:

> Le 2016-03-04 04:31, myglc2 a écrit :
>> Upon installing GuixSD a month ago I found it difficult to get a
>> grip on
>> GNU Guix' stucture. Because I like pictures I made a diagram showing
>> what I think I now understand about how GNU Guix' works. I am thinking
>> it might be helpful to Guix newcomers. Comments &/or corrections would
>> be most welcome. - George
>
> This kind of incorrect because there is a directory which stores every
> installed (or past installed) software which is linked inside profiles
> (system, users, and custom profiles).

Thanks. I agree that generations are a key feature of guix. But they
seem secondary to showing where guix packages are, how they are
referenced, and how to install & update them. I also chose not to show
generations because the diagram is at the limit of complexity that can
be reasonably digested. Generations might be the subject of another
diagram

> Users can't install program in the system profile, it can only be done
> through system config.scm.

Thanks. I tried to suggest this by using a different color for system
components and showing 'sudo' for system operations. Can you suggest a
better way to handle it?

  reply	other threads:[~2016-03-04 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  3:31 GNU Guix diagram myglc2
2016-03-04 10:21 ` Adam Pribyl
2016-03-04 12:36 ` Amirouche Boubekki
2016-03-04 17:52   ` myglc2 [this message]
2016-03-04 13:22 ` John Darrington

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=87fuw6i10j.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=amirouche@hypermove.net \
    --cc=guix-devel-bounces+amirouche=hypermove.net@gnu.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).