GNU Guix diagram

GNU Guix diagram

[myglc2]

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

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

[-- Attachment #2: gnuguix2.dot --]
[-- Type: application/octet-stream, Size: 1966 bytes --]

// Overview of GNU Guix
digraph G {
	compound=true
	size="12,12"
	edge [fontname = helvetica]
	graph [fontname = helvetica]
	node  [fontname = helvetica]
	{ node [shape=box style = filled fillcolor="white" color = transparent]
		pkgsource [label = "Source"]
		substitutes [label = "Prebuilt\nPackage"]
	}
	{ node [shape=box style = filled fillcolor=pink color = transparent]		
		spkgs [label = "System Packages\nInstall: 'sudo guix system reconfigure CONFIG.scm'\nUpdate: 'sudo guix pull && guix system reconfigure CONFIG.scm'"]
	}
	{ node [shape=box style ="filled,rounded" fillcolor=pink color = transparent]		
		guixd [label = " guix-daemon "]
	}
	{ node [shape=box style ="filled,rounded" fillcolor=lightblue color = transparent]		
		user1 [label = "user1"]
	}
	{ node [shape=box style ="filled" fillcolor=lightblue color = transparent]		
		u1pkgs [label = "user1 Packages\nInstall: 'guix package -i PACKAGE'\nUpdate: 'guix pull'"]
		guix2 [label="user1 guix\nUpdate: 'guix pull'"]
	}
	subgraph cluster_pkgsource {
		label = "Developer"
		labelloc = "t"
		style = filled fillcolor= azure2 color = transparent
		pkgsource
	}
	subgraph cluster_hydra {
		label = "Guix  Hydra"
		style = filled fillcolor= azure2 color = transparent
		substitutes
	}
	subgraph cluster_guixSD {
		label = "Computer Running GNU Guix"
		labelloc = "t"
		style = filled fillcolor= azure2 color = transparent
		user1 -> spkgs  [ label = " /run/current-system/profile  "]
		user1 -> guix2  [ label = " ~/.config/guix/latest  " ]
		user1 -> u1pkgs  [ label = " ~/.guix-profile  " ]
		subgraph cluster_guixstore {
			label = "Guix Package Store /gnu/store"
			labelloc = "b"
			style = filled fillcolor= tan color = transparent
			u1pkgs
			guix2
			spkgs
		}
		guixd
		spkgs -> guixd  [dir = back ltail=cluster_guixstore ]
	}
	pkgsource -> substitutes [lhead=cluster_hydra ltail=cluster_pkgsource]
	pkgsource -> guixd [ltail=cluster_pkgsource]
	substitutes -> guixd [ltail=cluster_hydra]
}

[-- Attachment #3: gnuguix2.png --]
[-- Type: image/png, Size: 51753 bytes --]

Re: GNU Guix diagram

[Adam Pribyl]

On Thu, 3 Mar 2016, myglc2 wrote:

> 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

I agree this deserves explanation, as this is not a common approach in 
mainstream distros. As I do understand this now, I can hardly judge this 
image will be understood by newcomer, but if this is a part of guix doc + 
the explanation in words (is it not there?), then it would be definitely 
good.

Adam Pribyl

Re: GNU Guix diagram

[Amirouche Boubekki]

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).

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

-- 
Amirouche ~ amz3 ~ http://www.hyperdev.fr

Re: GNU Guix diagram

[John Darrington]

[-- Attachment #1: Type: text/plain, Size: 808 bytes --]

On Thu, Mar 03, 2016 at 10:31:47PM -0500, myglc2 wrote:
     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

The problem with pictures is, that whilst it is true that "A picture paints
a thousand words" - it paints a thousand different words to a thousand 
different people.

J'



-- 
Avoid eavesdropping.  Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: GNU Guix diagram

[myglc2]

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?