On Thu, 2010-03-11 at 11:53 +0100, Alexander Kahl wrote:
> Most of what is described here is already covered by Nix (leaving out
> the hardware driver part).
>
> This is why I endorse dumping yum, RPM *and* the stupid FHS in favor of
> Nix, focusing all development on something that is clearly superior by
> substantiating the synthesis of DOS (*cough*) and POSIX style
> installations: Minimal redundancy, maximum compatibility, (mostly)
> predictable rollbacks, atomicity, referential transparency: Purely
> functional package management.
>
> Oh, and by the way, we could leave behind all those discussions
> regarding dynamic linking: RPATH for everything and everyone. If you've
> linked against libfoo-4.2-2 during build time, libfoo-4.2-2 will be
> present during runtime, same location, same file. Period. :)
I'm sorry for not studying the Nix concepts in depth, but can you please
answer me just a simple question how security or other critical bugfixes
_in libraries_ are handled under this "RPATH for everything" paradigm?
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
