>-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >This bug covers the use of "sudo" and "emerge". Because sudo'ing >doesn't change the PATH variable portage will often fail after it can't >find binaries because /sbin, /usr/sbin are not in it's PATH. > >Do we make the user manage their own path, or make portage force sbin >into the environment when it is doing it's thing? > >- -Alec Warner (antarus) > I am very interested in this. We have just added sudo functionality to porthole for most of the root needed functionality. So far nobody has reported any problems with the path as you describe. If it is something that we need to do before doing any "sudo emerge" calls, then we need to do it before we release porthole-0.5.0, which is very soon.
Once gnome-python-extras-2.12.0 comes out we will be able to use libgksu for su functionality which will enable porthole to run as a user much better, but in the meantime sudo is our only other option. Brian -- [email protected] mailing list
