On 11/04/2013 04:46 PM, Duncan wrote: > > I imagine were emerge being written today, -1 /would/ be the default, and > there'd be an option like --select to add to the @world file if > necessary. That's actually the way I setup my scripts, with -1 the > default, and an extra "2" suffix script variant that did add to the world > file. But backward compatibility being what it is, I guess by the time > portage authors realized they had a backward default, they couldn't > really fix it, except by something like EMERGE_DEFAULT_OPTS. >
Actually, this behavior has flipped back and forth three or four times (silently!), to the detriment of my @world sets. The last time I brought it up was in, https://bugs.gentoo.org/show_bug.cgi?id=397313 but you can chase the bug trail back to 2004. There are plenty of people on both sides. I haven't changed my mind, but the problem is "solved" here. I spend hours writing metapackages for the things that I want recorded in @world so that they can be differentiated from the things that were --updated without --oneshot (which is easy to forget). The servers that were alive during the silent changes in behavior were physically retired.
