| 1 |
On 10/12/2011 07:10 AM, Rich Freeman wrote: |
| 2 |
> That leads me to another concern. The defaults should be the safe |
| 3 |
> options, and the options should be to make the actions less safe. |
| 4 |
> |
| 5 |
> In my thinking the most conservative options right now are either |
| 6 |
> emerge -uDN world or emerge -uDN --with-bdeps=y world. |
| 7 |
> |
| 8 |
> I'd almost prefer to see that -D, -N, and --with-bdeps go away, and |
| 9 |
> that instead we add options like --shallow, --ignoreusechanges, and |
| 10 |
> --without-bdeps be added (ok, those are lousy names but you get the |
| 11 |
> picture). The default without any option should be to do the "right" |
| 12 |
> thing for most people, and specifying an option should be to make the |
| 13 |
> system do something less conservative. |
| 14 |
> |
| 15 |
> I just think about Debian where you tell people run "apt-get update" |
| 16 |
> and then "apt-get upgrade" and that is it. Their typical behavior is |
| 17 |
> not specifying anything and you get everything updated. With Gentoo |
| 18 |
> the equivalent is "emerge world" but when you do that you potentially |
| 19 |
> miss a lot of stuff. |
| 20 |
> |
| 21 |
> (And I realize the --with-bdeps part of this is debatable.) |
| 22 |
|
| 23 |
|
| 24 |
How about if we add a `emerge --upgrade` target that is analogous to |
| 25 |
`apt-get upgrade`? If we hide the new defaults behind a target like |
| 26 |
--upgrade, rather than change the defaults globally, then it allows |
| 27 |
people's existing scripted and habitual emerge commands to continue to |
| 28 |
work in a backward compatible manner. |
| 29 |
-- |
| 30 |
Thanks, |
| 31 |
Zac |
Archives