On 7/29/07, Paul Dann <[EMAIL PROTECTED]> wrote: > Well, the reasons for having ChrootCompile seem to me to apply just as > much to a single user as an admin. For the sake of simplicity, I think it's > best to have a single tool to compile, whether you're a user or admin.
How does Compile not already work for both root and non-root users? > > [Why not just tweak the PATH instead using chroot?] > Yes, that looks like it would work a treat. However, I think the > problems I have with this are: > > * It is not that easy to learn or remember. > * It could take some time to type in. > * Tweaking environment variables can be confusing, especially to a new / > desktop user. It seems to me that it's more of a backend system, and not > used too much for general tasks. > * What do you do when you want to switch versions in the same session? I > may well be mistaken, but I don't think there's an easy way to remove > something from the PATH, is there? 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. -mpb _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
