Alan McKinnon wrote: > 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. > > >
For me at least, this way works best. Before I did it this way, if I had to workaround a portage block or some other issue, I would forget to add -1 and ended up with a world file full of stuff that shouldn't be there. By the way, this doesn't effect updating at all, at least it doesn't for me. If say I emerge googleeath and I want to keep it installed and added to world, I then emerge it with --select y on the command line and it gets added to the world file. Basically, if something gets added to the world file, I took a extra step to make sure it got there. It doesn't get there by mistake. Since I've been doing it this way, I have not had a single thing added to my world file that I didn't want to be there. For me at least, it works. It's just to easy to forget to add that -1. It's not hard at all to remember to add --select y when needed tho. If it was something you were testing, --select y -n works like a charm. For my way of thinking, I think having a extra step to add something to the world file leads to a cleaner system. I wouldn't set it on a new install until I was doing installing all the things I do want tho. After I had my usual stuff installed, that -1 would be added. To each his own tho. Dale :-) :-)
