| 1 |
On Sun, Jul 31, 2011 at 01:38:58PM +0200, Alan McKinnon wrote: |
| 2 |
> It's sensible really - portage is not the only package manager out |
| 3 |
> there and therefore should not be in @system. The user did not put |
| 4 |
> portage in world, and did not use -D, so portage is not updating the |
| 5 |
> package. |
| 6 |
> |
| 7 |
> The solution is simple - all users should put their preferred package |
| 8 |
> manager into world and what Stroller is seeing will stop happening. |
| 9 |
> |
| 10 |
> Zac can't force portage into system like he could with less and nano |
| 11 |
> and have few or non side-effects. A virtual package manager only says |
| 12 |
> that you *have* one, not *which* one. So as usual for Gentoo, the user |
| 13 |
> gets to tell the software which one it is. |
| 14 |
> |
| 15 |
> I don't see a problem. |
| 16 |
|
| 17 |
Though it is silly IMHO that portage would want to remove itself with |
| 18 |
depclean. Could it not be hardcoded into portage that it should try to |
| 19 |
keep itself updated and not commit suicide? (Independently of the |
| 20 |
@system sets.) |
| 21 |
|
| 22 |
W |
| 23 |
-- |
| 24 |
Willie W. Wong wwong@××××××××××××××.edu |
| 25 |
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire |
| 26 |
et vice versa ~~~ I. Newton |
Archives