Stewart Stremler wrote: > > The fact is, an application shouldn't _care_ what UID it's being run > as -- it should just do the install in the directory it's been pointed > at, and if it doesn't have permissions, it should log the failure and > tell the user it couldn't do something. It should *not* check the UID > and refuse to install unless it's run as UID 0.
I have worked around this issue with fakeroot. This is nice, because you can set up a sendbox, of sorts, (mkdir /usr/local/stow/package-1.0) and point the package at that dir, and ensure that it writes only there. THs even works for vmware, except actually loading the modules. http://fakeroot.alioth.debian.org/ -john -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
