-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 16/01/13 11:49 AM, Michael Orlitzky wrote:
> On 01/16/2013 11:47 AM, Michael Orlitzky wrote:
>> On 01/16/2013 11:36 AM, Michael Weber wrote:
>>> 
>>>>> emerge --upgrade
>>> with a predefined EMERGE_UPGRADE_OPTS in make.conf (where 
>>> EMERGE_DEFAULT_OPTS lives).
>> 
>> +1 so I can stop adding --oneshot onto every upgrade.
> 
> Oh, damn, this isn't suggesting what I thought. Allow me to suggest
> that having both --update and --upgrade might be confusing, then
> =)
> 
> 
> p.s. EMERGE_UPDATE_OPTS would still be nice.
> 

- --upgrade wouldn't (couldn't, imo) replace --update.

"emerge --upgrade" would ideally meant to be run with no options
(except for maybe --keep-going and --jobs), and would consider @world
without specifying it.  We would, I think, need to define what happens
when other things are specified as options (ie throw them out and/or
error), which is why I have reservations of "emerge --upgrade" over a
separate say, "eupgrade" command; i don't think the usual pile-on
should occur.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlD24joACgkQ2ugaI38ACPA4vwD8DqGsXOXKiKEzeQI98VytM9zg
4FX6fQ1ENwBeiZu17rkA/2IxItrBer06jy5bIWONCxjy+ysqj+BBTrY5oININVNE
=3chs
-----END PGP SIGNATURE-----

Reply via email to