On 22/09/2015 17:55, James wrote: > Dale <rdalek1967 <at> gmail.com> writes: > > >>> I usually remember --oneshot but if I'm tired or distracted I >>> forget it. > > >> To avoid this, I added it to my make.conf. When I *really* want to have >> something in the world file, I can either add it myself or use --select >> on the command line to add it. Result, shouldn't be anything in the >> world file that shouldn't be there. > > OK, I'll try this. > I'll add --oneshot to the EMERGE_DEFAULT_OPTS= in make.conf. > > Works great. > >> I sometimes wonder why that isn't the default way. I guess because it >> would confuse folks for a bit and because it has always been that way. > > One thing I see, is now you have a system that is full of pkg that do > not update normally. I guess I'm say if you install pakages with --oneshot, > they are not automatically updated, or are they? (discussion). > > 'emerge -uDNv world' is the most common form of update, probably, used > by gentoo users. So how to best ferret out those oneshot packages for > update; and that's if they should be updated.... semantics on that?
I think you two have it backwards. The intended workflow is that if you emerge something, you know what it is, you don't have to make further decisions about it and you want it in world. @world, by definition, is the list of packages you want. That plus @system plus all deps constitutes the set of what should be on the system, anything you have not in that set is subject to depcleaning If you are not sure about some package, by all means emerge it with -1. Check it out, verify it, make sure it does what you want then get it in world with emerge -n. Why would you want to have stuff around for extended periods that is not in world? If you have a package that you no longer want (as you know what is in your world right), unmerge it with -C Don't make life difficult for yourself. It's MUCH easier to know what's in world than to try and remember what should be and isn't. -- Alan McKinnon alan.mckin...@gmail.com
