| 1 |
Dirk Heinrichs <dirk.heinrichs@××××××.de> ïèñàë(à) â ñâî¸ì ïèñüìå Thu, 01 |
| 2 |
Oct 2009 22:45:40 +0300: |
| 3 |
|
| 4 |
> Am Donnerstag 01 Oktober 2009 21:32:56 schrieb forgottenwizard: |
| 5 |
> |
| 6 |
>> However, I'm also wondering why the ebuild doesn't make use of the |
| 7 |
>> EDITOR variable as was mentioned. |
| 8 |
> |
| 9 |
> Because that's the worst thing to do. An ebuild's behaviour should not |
| 10 |
> depend |
| 11 |
> on env variables (like it's still the case for this stupid grub ebuild), |
| 12 |
> because the user never get's to see this. |
| 13 |
|
| 14 |
Oh, really? |
| 15 |
Snipped from sudo's ebuild: |
| 16 |
econf --with-secure-path="${ROOTPATH}" |
| 17 |
|
| 18 |
What do you think about this line? There's an issue connected with that |
| 19 |
string by the way. |
| 20 |
You may want to check it: |
| 21 |
http://bugs.gentoo.org/show_bug.cgi?id=286014 |
| 22 |
|
| 23 |
The maintainer didn't even notice user about hardcoding ROOTPATH in sudo. |
| 24 |
And, even more, he didn't check that manual page is saying that secure_path |
| 25 |
is unset by default. And again I (the enduser) was forced to go check the |
| 26 |
ebuilds |
| 27 |
to see why sudo doesn't work as expected. |
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, Spinal |
Archives