[gentoo-portage-dev] bug 56407 Sudo path mangling.

[gentoo-portage-dev] bug 56407 Sudo path mangling.

[Alec Warner]

-----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)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQv13nWzglR5RwbyYAQL8AA//RwK9NDYaw1YLTXfL8/hd1QYnYkRUidaU
taI+Jxf+JKnLK42EjmxyG7zL+lItRjaFFICHWnr7C8ZtzzNIPJWFvHZ1UJcqr7go
8brMixKruZWS3X75GKSrnaRNExqpSyZHu7g8EL8G9cs5yknv6ioflK42mMUq3niU
PSxbt9zeQROBoOijVVQ5xTpLpEQSDkz06QeJvhgNbnLH4XrT6VuWb+hbVsRTPF4K
Vg4EzNV16EENNvAaPwnjPir3vD7epWDjOX6aC9LdaXxle8mXIF6AbDkzBGVrXman
YyFk32l0ygIN6BxuciEsgBUZvzNV38rOjrvsmVjLnrQScGmHnnTI5voWt72YQq47
iKcPeAWyeuAIofPFt3eoxIqWo4YT6RMVwrI3Vqy6Ib4VfTnV7R3eevg9TgVc2tIz
cVLVbWwoH1H0XmMerxzoYpITRDRvBxE0uvH/5UYkIIrRWyT4lD8yKSTUat5q7Hkg
GsIiFBZ7sAJi0uSRn7TdDtrDXoTnQROw7xyAiSTY6IIdNb4qo4eShCGQaoskTSvB
OV4x0Zdm2BpjYVXYDH8S8WEHvlMId9Qu28KH7xIcMF+9UnK11mhfSRn36zF1CXsd
EUn81fAvWEQvcbHssuAGU2SJR8Y99WVlNfAHQSssWkEB44BAQlnLWKVH+se99OMg
La/EZFRG+xI=
=16XI
-----END PGP SIGNATURE-----
-- 
gentoo-portage-dev@gentoo.org mailing list

[gentoo-portage-dev] bug 56407 Sudo path mangling.

[Brian Dolbec]

>-----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

-- 
gentoo-portage-dev@gentoo.org mailing list