(Apologies for top-posting; my mobile email client doesn't seem to let me post in any other way...)
Regarding your diagrams, I guess the one that shows GuixSD using Guix makes a little more sense to me than the one that shows GuixSD as a total replacement for Guix. However, I'm not sure exactly how GuixSD uses Guix when managing the system, so I will defer to the opinion of others on the mailing list who know more about theses things than me. It isn't clear to me what you want to know. Perhaps if you can ask a more concrete question, it will be easier for the others to answer? To reiterate what I said before: my current understanding is that Guix is a functional package manager (with a lot of fantastic features) that you can run anywhere. That's all, really. And GuixSD is a full GNU operating system which currently uses Linux-Libre as its kernel, Guix as its package manager, and Shepherd (formerly DMD) as its init system. Similar to a GNU/Linux distribution, the GuixSD system comes with some extra "glue" which makes all those separate components work together out of the box. But the way that those components are glued together in GuixSD allows you to enjoy certain benefits that you don't get with other systems (software freedom, system configuration in guile, easy rollback of system upgrades, etc). I don't yet know much about how GuixSD's "glue" is implemented, but I think that's the gist of it. On Mon, Feb 15, 2016, 09:37 myglc2 <myg...@gmail.com> wrote: > Chris Marusich <cmmarus...@gmail.com> writes: > [...] > > I think you're asking "What is the difference between Guix and > > GuixSD", and you don't feel that the manual is clear enough about > > this. Is that right? > > No, the problem is at a higher level than the manual. > > The current packaging of Guix within GuixSD obfuscates what is going on > and makes understanding the Guix-verse difficult. > > I drew the diagrams: To illustrate and stimulate a discussion of this. > > Do you have any thoughts about the diagrams? > > > >
