Michael Orlitzky posted on Mon, 04 Nov 2013 20:23:17 -0500 as excerpted: > 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 >> > Actually, this behavior has flipped back and forth three or four times > (silently!), to the detriment of my @world sets.
I guess that demonstrates the degree to which I use my scripts, as I wasn't even aware of that... > [T]he 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). I jumped on sets for that, putting everything in sets and checking the world file occasionally so that if there's anything it it at all, it's either because I put it there specifically as a package purgatory, or because I forgot... but evidently I've used my scripts so consistently that I've never forgotten., as I've yet to find anything there I didn't deliberately put in package purgatory. Actually, I ended up using sets back when I setup my netbook, as I needed some way to sort thru the main machine's world file and figure out what listings I wanted for the netbook and which not, and I was familiar with the then new sets feature from the kde overlay, and decided sets were the perfect way to category-sort everything, figuring out what I wanted on the netbook at the same time. I don't update the netbook anything even close to as consistently, however, often ending up going a year or even two between updates (security isn't a big issue as I deliberately keep anything sensitive off the netbook already, and use it more offline than as as a NETbook in any case), but because I keep the sets identical except for #-commenting a package here or there on one side or the other, when I /do/ update it's a relatively simple matter to diff the sets along with the use file (separate and sourced from make.conf) and package.* files, updating the netbook's files based on the main machine's files as I go. Then it's mostly a matter of iteratively updating what can be updated, skipping what can't as the jump is too large and other packages need updated first, dealing with the problems one at a time, until everything updated and I can once again do an emerge empty-tree world without issue. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
