On Tuesday 03 Jan 2012 02:00:48 Michael Orlitzky wrote: > On 01/02/2012 07:22 PM, Dale wrote: > > I always knew I was "odd". Looks like I have some company tho. Welcome > > to the "odd user" group Michael. > > It ain't us =)
Nope. It ain't just you. It's me too. ;-) I'd rather the old default behaviour was retained/returned to. I have to admit even after all this time I will occasionally forget and run emerge -u some_package, only to notice that it was added into world at the end of the emerge. Even worse, it wasn't updated (because no update was available) but was just added in world all the same. Of course when I notice this I go and remove it from world manually and make a mental note not to do this again. When I miss it, the package ends up in world. :-( However, I do wonder how confused could a new user end up being with this (superficially) inconsistent behaviour. The -u option works fine on world (it just updates packages already in world, but not on individual packages (it updates *and* adds said packages in world). I understand the logic, but for the reasons explained by Michael and Dale I also prefer the old behaviour to be the default: nothing gets added in world as a result of updating alone. An enotice message that informs the user that just updating the particular package(s) does not mean they are added to the world file and won't be automatically updated when running 'emerge -u world' in the future, would educate users, along with options for adding the said packages in world. Of course, the opposite will work too; flashing a fat enotice to educate us old dogs to remember to run -1 instead of -u. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
