1 |
On Wednesday 12 October 2011 23:26:28 Rich Freeman wrote: |
2 |
> On Wed, Oct 12, 2011 at 11:20 PM, Mike Frysinger <vapier@g.o> wrote: |
3 |
> > On Wednesday 12 October 2011 11:09:56 Zac Medico wrote: |
4 |
> >> How about if we add a `emerge --upgrade` target that is analogous to |
5 |
> >> `apt-get upgrade`? |
6 |
> > |
7 |
> > isn't that already done with @installed ? `emerge --upgrade @installed` |
8 |
> |
9 |
> Well, you'd arguably at least need a -N in there. |
10 |
|
11 |
that's orthogonal to the issue and the target. the OP wanted to upgrade "all |
12 |
packages" which is @installed. if you want to rebuild when USE flags change, |
13 |
then use --newuse. no target should imply different option behavior. |
14 |
|
15 |
> Also, this doesn't work in stable portage - I assume this is something |
16 |
> available in the newer branch. |
17 |
|
18 |
it works for me, but i'm using latest portage (the _alpha## stuff). any |
19 |
proposed change would require an update anyways ... |
20 |
|
21 |
> Also - will doing an emerge -u @installed add those packages to @world |
22 |
> - ie do we need to throw a -1 in there, or is this behavior coded in |
23 |
> as an exception? |
24 |
|
25 |
i don't know about set behavior and the world file. it would make sense to me |
26 |
that "world" would special case @system and @installed and not add it to |
27 |
@world unlike other sets (i know that other sets do get added to world). Zac |
28 |
would know of course. |
29 |
-mike |