| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hemmann, Volker Armin wrote: |
| 5 |
> On Friday 07 July 2006 21:22, Rafael Fernández López wrote: |
| 6 |
> |
| 7 |
>> Second thing that I'd improve is a security one. I know that "emerge" |
| 8 |
>> is a very cared package, but it is a script. Suppose that someone |
| 9 |
>> commits portage with a emerge failure in its code (he forgot a comma |
| 10 |
>> !!)... if someone updates portage won't be able to update it again |
| 11 |
>> because it will fail ever and ever again... So I suggest to have a |
| 12 |
>> backuped emerge script that we are sure that worked (like the last |
| 13 |
>> emerge tool that was used), and if the new emerge tool is mistaken (so |
| 14 |
>> that user doesn't need to know python) only has to run "regenemerge" for |
| 15 |
>> example, and will have the latest emerge working tool. |
| 16 |
> |
| 17 |
> once upon a time, there was a portage-rescue.... |
| 18 |
> |
| 19 |
> seems, that it is gone (why?) but you can still find it here: |
| 20 |
> http://dev.gentoo.org/~carpaski/portage_rescue/ |
| 21 |
> |
| 22 |
|
| 23 |
Look inside $PORTDIR/sys-apps/portage/files/README.RESCUE and you'll see this: |
| 24 |
|
| 25 |
Please see http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml |
| 26 |
for a recovery guide for a broken portage installation. |
| 27 |
|
| 28 |
Zac |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v1.4.4 (GNU/Linux) |
| 31 |
|
| 32 |
iD8DBQFErxcY/ejvha5XGaMRAi8xAJ92qQJwuahjZ3IQzVJdoZ9fh8QZvACcCsDc |
| 33 |
ml2Uz4PQWYGAOClpZVhDajg= |
| 34 |
=s4iZ |
| 35 |
-----END PGP SIGNATURE----- |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives