l...@gnu.org (Ludovic Courtès) writes:
Actually, each user as a forest of symlinks under ~/.nix-profile
pointing to packages installed by the user.
So in the above example, you would typically have $HOME/.nix-profile/lib
in $LIBRARY_PATH, and you would link against libfoo from there, and the
Hi,
Richard Stallman r...@gnu.org skribis:
[2]
https://gitorious.org/guix/guix/blobs/master/distro/packages/base.scm
Any particular reason it uses kernel.org Linux instead of Linux libre?
No. Currently it s just a user-land software distro, like GSRC, so only
the
Hi Simon,
Simon Josefsson si...@josefsson.org skribis:
l...@gnu.org (Ludovic Courtès) writes:
Actually, each user as a forest of symlinks under ~/.nix-profile
pointing to packages installed by the user.
So in the above example, you would typically have $HOME/.nix-profile/lib
in
Hi,
Richard Stallman r...@gnu.org skribis:
Perhaps you were asking about previously installed packages linked
against a vulnerable libc, for example? Again, those packages remain
vulnerable, until you upgrade to the new version, that links against the
fixed libc.
Why can't
Yes, I ll do that. Technically though, Linux-Libre is a set of scripts
that touch .c files.
The maintenance of Linux-Libre is done using these scripts,
but that's not what it _is_. It is a modified version of Linux.
We release it as Linux sources, and binaries too.
Please point at those
No. Basically, each package is installed in its own directory, pretty
much à la GNU Stow. However, the directory name contains the hash of
all the inputs used to build that package (source code, compiler,
libraries, build scripts, etc.) Thus, when an input changes, the new
