| 1 |
On Fri, 18 Jul 2008 16:21:24 +0100 |
| 2 |
Robert Bridge <robert@××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Fri, 18 Jul 2008 16:30:20 +0200 |
| 5 |
> Arfrever Frehtes Taifersar Arahesis <arfrever.fta@×××××.com> wrote: |
| 6 |
> |
| 7 |
> > IMHO it would be better to teach users to explicitly specify |
| 8 |
> > '@system' during updates, e.g. `emerge -uDN @system @world`. |
| 9 |
> |
| 10 |
> Why not just re-instate the implicit dependency of world on system? |
| 11 |
|
| 12 |
Because that doesn't actually fix the problem, it just covers it up to |
| 13 |
some degree (there has never been a guarantee that "system" is |
| 14 |
actually satisifed when you install a package). Also the new solution is |
| 15 |
more flexible as it still allows you to include system in world easily, |
| 16 |
or update/rebuild system and world separately. And for a full system |
| 17 |
updates there is a new target available that actually includes all |
| 18 |
installed packages. |
| 19 |
Yes, this is going to require some user reeducation, and yes, this will |
| 20 |
take some time, but it isn't as dramatic as some people make it. The |
| 21 |
whole "implicit-system-dependency" thing has never existed, it was |
| 22 |
always a broken assumption that only didn't blow up badly because a) the |
| 23 |
"system" target rarely changes b) most packages only depend on a tiny |
| 24 |
part of "system" and c) most users actually do full system updates |
| 25 |
regulary. |
| 26 |
As soon as you want to install a package that actually implicitly |
| 27 |
depends on something in "system" that isn't already installed the whole |
| 28 |
thing breaks down. |
| 29 |
|
| 30 |
Marius |
| 31 |
-- |
| 32 |
gentoo-dev@l.g.o mailing list |
Archives