| 1 |
On 7/7/06, Rafael Fernández López <info@××××××××××××××××××.com> wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> Hi, |
| 6 |
> |
| 7 |
> This is not flame war. I love Gentoo, and it is the distribution that |
| 8 |
> fits me perfectly, but I've been wondering this last year what things |
| 9 |
> can be improved in this wonderful distro. |
| 10 |
> |
| 11 |
> The first thing that I'd change is "etc-update" or "dispatch-conf". I'd |
| 12 |
> suggest to create some kind of tool like "dpkg-reconfigure" in Debian. |
| 13 |
> More intuitive than reading /etc files and writing them by hand that is |
| 14 |
> more probably to be mistaken when writing. |
| 15 |
|
| 16 |
This has been already discussed in the list, and a good discussion |
| 17 |
too. There are tools that do the job better/faster for someone's |
| 18 |
opinnion (not mine, I still like etc-update). You can choose that |
| 19 |
tools, I don't know Debian, but I doubt a combination of all tools |
| 20 |
mentioned at that thread would not come close to what you want. |
| 21 |
|
| 22 |
> |
| 23 |
> Second thing that I'd improve is a security one. I know that "emerge" |
| 24 |
> is a very cared package, but it is a script. Suppose that someone |
| 25 |
> commits portage with a emerge failure in its code (he forgot a comma |
| 26 |
> !!)... if someone updates portage won't be able to update it again |
| 27 |
> because it will fail ever and ever again... So I suggest to have a |
| 28 |
> backuped emerge script that we are sure that worked (like the last |
| 29 |
> emerge tool that was used), and if the new emerge tool is mistaken (so |
| 30 |
> that user doesn't need to know python) only has to run "regenemerge" for |
| 31 |
> example, and will have the latest emerge working tool. |
| 32 |
> |
| 33 |
|
| 34 |
There are SO MANY ways to recover portage. A snapshot, a binary |
| 35 |
package. If you run stable, its almost impossible, to say the least, |
| 36 |
that you're gonna get a trivial error in emerge that prevents it from |
| 37 |
running, if you run testing, still, gentoo devs are responsable people |
| 38 |
and would not do something like that. If we count with that kind of |
| 39 |
error, your "regenemerge" command would have to redownload and compile |
| 40 |
python, portagem, pycrypt, gcc, glibc and a lot of other packages that |
| 41 |
emerge depends on. You can always "quickpkg portage" once in a while, |
| 42 |
but any portage snapshot untared at / would recover most of portage |
| 43 |
for you. |
| 44 |
|
| 45 |
No flames intended, I just say there are ways to do all this |
| 46 |
already... But you still can post a feature request anytime. |
| 47 |
|
| 48 |
-- |
| 49 |
Daniel da Veiga |
| 50 |
Computer Operator - RS - Brazil |
| 51 |
-----BEGIN GEEK CODE BLOCK----- |
| 52 |
Version: 3.1 |
| 53 |
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- |
| 54 |
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ |
| 55 |
------END GEEK CODE BLOCK------ |
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-user@g.o mailing list |
Archives