On 7/30/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > On 7/29/07, mpb <[EMAIL PROTECTED]> wrote: > > So write a "UseProgram" tool to manage PATH for you. > > > > > * It uses the binary path directly, whereas GoboLinux seems to be > promoting > > > the notion of the Program as a whole, which is a good idea in my > opinion. > > > If possible, the average user shouldn't need to know too much about the > > > inside of a Program (meaning program directory) in order to add it to > the > > > path. > > > > "UseProgram GCC 4.1.2" versus "MountProgram GCC 4.1.2". > > > > Both are just as easy to remember and use. "UseProgram" saves you the > > bother of having to mess with chroots. > > Also, that should involve the evaluation Resources/Environment, as > well as LD_LIBRARY_PATH. The interesting thing about MountProgram, > though, is that one could specify a wide range of programs so that a > completely isolated environment could be created, composed *only* by > the desired applications -- that's not possible with an approach based > on UseProgram.
This is exactly the same as setting up a ChrootCompile environment and running a shell inside it instead of Compile. -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
