| 1 |
Neil Bothwick wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> so you go to a lot of trouble to circumvent portage's dependency |
| 5 |
> handling, then you rely on portage to fix things up after your break |
| 6 |
> them. You need to keep lists of what you have merged and unmerged simply |
| 7 |
> to compensate for having broken portage's own list for no good reason. |
| 8 |
|
| 9 |
Well I don't have the feeling I go to a lot of trouble and I *absolutely |
| 10 |
don't circumvent portage's dependency handling* and I don't see anything |
| 11 |
broken in my system even it is about 2 years old. |
| 12 |
Keeping lists happens in very rare occasions. Testing a package means I |
| 13 |
install, look around and uninstall it. I'm not randomly emerging other |
| 14 |
stuff in the mean time. |
| 15 |
|
| 16 |
|
| 17 |
> What happens if you reboot after unmerging "c", and its absence causes |
| 18 |
> the system to fail to boot? What if you remove something that stops |
| 19 |
> emerge working? |
| 20 |
> |
| 21 |
|
| 22 |
Highly unlikely. For two reasons: |
| 23 |
|
| 24 |
1) How come that I was able to boot w/o the package in question in first |
| 25 |
place? :) |
| 26 |
2) The kind of package you're talking about is listed in the system |
| 27 |
profile. If you try to remove such a package portage yells out a big fat |
| 28 |
warning. |
| 29 |
|
| 30 |
|
| 31 |
> Gentoo is all about choice, so you are free to choose to use it like |
| 32 |
> this, just as you are free to do "rm -fr /*". But don't expect someone to |
| 33 |
> come up with a magic fix when things get screwed up. |
| 34 |
> |
| 35 |
> |
| 36 |
|
| 37 |
Correct. And I triggered this discussion here about a different way of |
| 38 |
handling packages. A way that is not forbidden neither mentioned as |
| 39 |
inappropriate in the official documentation. So there shouldn't be |
| 40 |
anything wrong with it, right? |
| 41 |
I find your comparison involving "rm -rf /*" to be irrelevant. Using a |
| 42 |
system one way or another is not the same as making a "human error". |
| 43 |
|
| 44 |
So far I haven't made the choice of doing "rm -rf /" but actually once I |
| 45 |
did "cat /dev/zero > /dev/hda" instead of "cat /dev/zero > /dev/hda2" by |
| 46 |
mistake. In cases like this there's no package management system that |
| 47 |
could help, no matter if it is portage, apt, yast, swaret or whatever. |
| 48 |
Long live the...backups! :) |
| 49 |
|
| 50 |
|
| 51 |
Last but not least. When it comes to redundant packages in the system. |
| 52 |
What happens when you do (the right way?): |
| 53 |
|
| 54 |
1) emerge a |
| 55 |
2) "a" pulls-in "b" and "c" as dependencies |
| 56 |
3) emerge -C a |
| 57 |
4) "a" goes out but "b" and "c" stay there just to take place |
| 58 |
5) emerge --depclean |
| 59 |
|
| 60 |
Well...The first thing one can see reads: |
| 61 |
" *** WARNING *** --depclean is known to be broken." |
| 62 |
|
| 63 |
So you prefer to clean the system up using procedure that is "known to |
| 64 |
be broken" or you just leave useless packages to take space on your HDDs? |
| 65 |
|
| 66 |
It is my opinion that Gentoo's documentation and portage's behavior |
| 67 |
suggest leaving junk packages on your system. |
| 68 |
Which indeed is "the right way"? |
| 69 |
|
| 70 |
|
| 71 |
-- |
| 72 |
Best regards, |
| 73 |
Daniel |
| 74 |
|
| 75 |
-- |
| 76 |
gentoo-user@g.o mailing list |
Archives