1 |
On Sun, 2007-10-21 at 15:12 +0200, Marius Mauch wrote: |
2 |
> On Sun, 21 Oct 2007 05:23:45 -0700 |
3 |
> Ned Ludd <solar@g.o> wrote: |
4 |
> |
5 |
> > On Sun, 2007-10-21 at 13:01 +0200, Marius Mauch wrote: |
6 |
> > > So, what do people think about removing (some) of the special |
7 |
> > > treatment for the "system" and "world" targets? |
8 |
> > > Mainly I'm interested in removing the "selective" parameter that's |
9 |
> > > currently enabled for them (so for example without that parameter |
10 |
> > > `emerge world` would default to remerging packages, unless --update |
11 |
> > > or --noreplace are specified). That change has already been |
12 |
> > > requested a few times in the past by users, but OTOH it could |
13 |
> > > probably upset people who don't use --update with world/system. |
14 |
> > |
15 |
> > What would such a disruptive change really gain us? |
16 |
> |
17 |
> The goal is to make package sets behave in a consistent way. |
18 |
> |
19 |
> > I personally feel our users need consistency from Gentoo. If they |
20 |
> > grew up doing 'emerge world' and have come to expect that behavior |
21 |
> > and all of the sudden we change behavior on them.. Yeah I can see |
22 |
> > how ppl would get upset. |
23 |
> |
24 |
> As do I, which is why I haven't simply changed it. |
25 |
> |
26 |
> > Perhaps a less intrusive way would be to introduce another |
27 |
> > flag to get the specified behavior you are after. |
28 |
> |
29 |
> Well, the primary goal is to make all sets behave in a consistent way. |
30 |
> And some sets have the explicit purpose to rebuild stuff, so making |
31 |
> sets "selective" by default also has issues. |
32 |
> The proposed change would also make sets behave in the same way as |
33 |
> packages which is IMO another benefit. |
34 |
> But as I said, I can see that it could upset people. |
35 |
> |
36 |
> One possible solution that I've thought about would be to remove the |
37 |
> hardcoded "selective" parameter and let the set configuration determine |
38 |
> if a set is selective or not (with missing = "false"), and then enable |
39 |
> it for world and system in our default config, e.g. |
40 |
> |
41 |
> [world] |
42 |
> class = portage.sets.files.WorldSet |
43 |
> selective = True |
44 |
> |
45 |
> and extend the --rebuild option with new arguments "always" and "never". |
46 |
> Don't really like the additional complexity though (and I haven't |
47 |
> checked how much work it would be). |
48 |
|
49 |
|
50 |
To me this really sounds like it's -e world but just with the world |
51 |
file. Literally as if you were to do an |
52 |
emerge -p $(</var/lib/portage/world) |
53 |
Assuming that is what you intend for it to behave like then how about |
54 |
using -E for this behavior? Everybody would profit and nobody would |
55 |
become disgruntled when all of the sudden emerge started spiking |
56 |
the power bills. :) |
57 |
|
58 |
-- |
59 |
Ned Ludd <solar@g.o> |
60 |
|
61 |
-- |
62 |
gentoo-portage-dev@g.o mailing list |