LWN article on Guix

LWN article on Guix

[Ludovic Courtès]

Hello!

If you’ve missed it, the Aug. 1st edition of Linux Weekly News (LWN) had
an article about Guix: https://lwn.net/Articles/560760/ .

It’s well written and conveys the important ideas, though there are a
couple of misunderstandings (such as “Some of the key fields to consider
are build-system, which tells Guix how to compile the package from
source if no binary is available”; see
<http://www.gnu.org/software/guix/manual/guix.html#Defining-Packages>
for the explanation of ‘build-system’.)

Guix is so fashionable, spread the word!  :-)

Thanks
Ludo’.

Re: LWN article on Guix

[Matthew Lien]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB2312, Size: 838 bytes --]

Congrads to all the Guix Geeks!


2013/8/20 Ludovic Court¨¨s <ludo@gnu.org>

> Hello!
>
> If you¡¯ve missed it, the Aug. 1st edition of Linux Weekly News (LWN) had
> an article about Guix: https://lwn.net/Articles/560760/ .
>
> It¡¯s well written and conveys the important ideas, though there are a
> couple of misunderstandings (such as ¡°Some of the key fields to consider
> are build-system, which tells Guix how to compile the package from
> source if no binary is available¡±; see
> <http://www.gnu.org/software/guix/manual/guix.html#Defining-Packages>
> for the explanation of ¡®build-system¡¯.)
>
> Guix is so fashionable, spread the word!  :-)
>
> Thanks
> Ludo¡¯.
>
>


-- 
/ Just another [ Perl | FOSS | Security ] Hacker. /
/ BlueT = Matthew Lien = ¾š†´Ã÷ /
/ http://BlueT.org /
/ GPG: 4A293CBD /

[-- Attachment #2: Type: text/html, Size: 1728 bytes --]

Re: LWN article on Guix

[Andreas Enge]

Am Dienstag, 20. August 2013 schrieb Ludovic Courtès:
> If you’ve missed it, the Aug. 1st edition of Linux Weekly News (LWN) had
> an article about Guix: https://lwn.net/Articles/560760/ .

Thanks for the link!

> It’s well written and conveys the important ideas, though there are a
> couple of misunderstandings

Rather annoying is the misunderstanding in: "For example, Guix's package 
store model works by linking a single directory in the system-wide store to 
a directory in the user's profile. This assumes that a package only 
installs files to one location, which is often not the case. Packages that 
install content in multiple output directories (e.g., /usr/bin and 
/usr/share/doc) are split up into separate pieces for Guix, so the GNU 
Distribution's glib package contains the Glibc binaries, while glib:doc 
contains its corresponding documentation."

Each file is symlinked separately, and splitting into several packages is 
just an option (like in this case to avoid that a user needs to install 
heavy documentation).

Andreas

Re: LWN article on Guix

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> Am Dienstag, 20. August 2013 schrieb Ludovic Courtès:
>> If you’ve missed it, the Aug. 1st edition of Linux Weekly News (LWN) had
>> an article about Guix: https://lwn.net/Articles/560760/ .
>
> Thanks for the link!
>
>> It’s well written and conveys the important ideas, though there are a
>> couple of misunderstandings
>
> Rather annoying is the misunderstanding in: "For example, Guix's package 
> store model works by linking a single directory in the system-wide store to 
> a directory in the user's profile. This assumes that a package only 
> installs files to one location, which is often not the case. Packages that 
> install content in multiple output directories (e.g., /usr/bin and 
> /usr/share/doc) are split up into separate pieces for Guix, so the GNU 
> Distribution's glib package contains the Glibc binaries, while glib:doc 
> contains its corresponding documentation."
>
> Each file is symlinked separately, and splitting into several packages is 
> just an option (like in this case to avoid that a user needs to install 
> heavy documentation).

Yeah, indeed.

Ludo’.