On 5/13/07, Stewart Stremler <[EMAIL PROTECTED]> wrote:
No, it can't prevent dependency hell (that's a problem with programs, not with systems) -- it *CAN* prevent DLL hell (or so it seems from reading the website). It helps *manage* dependency hell by encapsulating the dependency chain into a package (all the way up to compiling the compiler, if necessary, according to the webpage).
IMHO your first statement is wrong. Systems are collections of programs. Programs are collections of data (source code) processed by tools. NIX defines functions that proceed from its inputs (source and tools) to its outputs. For any given set of inputs there is only one set of outputs. Dependency is always explicit in a Nix system. Dependency hell comes about when implicit dependencies not captured in the build system raise their ugly heads by breaking the system. Perhaps you can explain your statement. BobLQ -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
