| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi, |
| 5 |
|
| 6 |
This is not flame war. I love Gentoo, and it is the distribution that |
| 7 |
fits me perfectly, but I've been wondering this last year what things |
| 8 |
can be improved in this wonderful distro. |
| 9 |
|
| 10 |
The first thing that I'd change is "etc-update" or "dispatch-conf". I'd |
| 11 |
suggest to create some kind of tool like "dpkg-reconfigure" in Debian. |
| 12 |
More intuitive than reading /etc files and writing them by hand that is |
| 13 |
more probably to be mistaken when writing. |
| 14 |
|
| 15 |
Second thing that I'd improve is a security one. I know that "emerge" |
| 16 |
is a very cared package, but it is a script. Suppose that someone |
| 17 |
commits portage with a emerge failure in its code (he forgot a comma |
| 18 |
!!)... if someone updates portage won't be able to update it again |
| 19 |
because it will fail ever and ever again... So I suggest to have a |
| 20 |
backuped emerge script that we are sure that worked (like the last |
| 21 |
emerge tool that was used), and if the new emerge tool is mistaken (so |
| 22 |
that user doesn't need to know python) only has to run "regenemerge" for |
| 23 |
example, and will have the latest emerge working tool. |
| 24 |
|
| 25 |
If I have more ideas I'll tell ya. |
| 26 |
|
| 27 |
Thanks in advance, |
| 28 |
Rafael Fernández López. |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v1.4.4 (GNU/Linux) |
| 31 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 32 |
|
| 33 |
iD8DBQFErrR1WFfYaTyFH8oRAkm7AJ0ekcFfFxUMZnqLfX0AFQYd0gd8WgCgnEmL |
| 34 |
6ZxTZyAHJz7BhVtVt94BTbk= |
| 35 |
=XISq |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-user@g.o mailing list |
Archives