On Mon, Jan 2, 2012 at 4:18 PM, Michael Orlitzky <mich...@orlitzky.com> wrote: > On 01/02/2012 04:11 PM, Alan McKinnon wrote: >> >> cocktail >> Neil's suggestion of sets sounds like what you want here. Unfortunately >> it only works smoothly on first emerge (later on you have to dig >> through dep graphs to find the full dep list): >> >> First run emerge -p to find all the packages that will be pulled in, >> and add the whole lot to a set with a clear name that indicates it's >> function. Then emerge that set. As you discover further deps you can >> manually add them to the set >> >> It's quite a lot of extra work and you have to remember to do it, but >> it has the benefit of being somewhat self-documenting, at least in >> terms of having a record of what set pulled a package in initially. >> > > Requires time travel, not a solution!
Seriously. Do you want a solution, or do you just want to rant about a change to the behavior of --update? Without some existing log of the things your existing customers specifically need, and without some means to intuit what they need by the web apps they've uploaded to their accounts, there isn't going to be any solution that isn't going to involve either a risk of breakage to your existing clients' sites, preservation of your damaged world file as an "assume this is what I need" set, or a great deal of work coming up with the list of things you actually need. Without that request log, you're in a *recovery* scenario, and there is no quick fix. All solutions offered that aren't time travel (better termed, "change your practices so this doesn't happen again"), are going to require a lot of effort and legwork on your part, and will *all* carry risk. Here's another time travel solution, but this one doesn't require changing past actions: Go through your log files and look for 'Updating world file", and look at what portage was doing at the time. Go through your emails with your customers and identify which packages they requested. Look at your own public-facing website and look at the list of packages you promise. If you either have all your emerge logs, or all your customer contact logs, it's doable. -- :wq
