From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RhpYI-0005dO-Jk for garchives@archives.gentoo.org; Mon, 02 Jan 2012 21:36:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EF66F21C160; Mon, 2 Jan 2012 21:35:59 +0000 (UTC) Received: from mail-ey0-f181.google.com (mail-ey0-f181.google.com [209.85.215.181]) by pigeon.gentoo.org (Postfix) with ESMTP id E5DB621C03B for ; Mon, 2 Jan 2012 21:34:12 +0000 (UTC) Received: by eaai1 with SMTP id i1so10545315eaa.40 for ; Mon, 02 Jan 2012 13:34:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4pSj/4CKWA2wy/wEa8YyXggCGQqvwqW4hoFNZIEWOD8=; b=eMO+lc7JXmSqKK3irZWxfV6RYHVA4iP0gv65YfL2jpKjdsX9c4gN4TdYyk0n+6QvD9 9znIud7DVQjdh8t/2lZvPc0YhyJLFpQfobABAHEt/J62KAp0JBt4jmAyAQ02trx2X31Y lgEhre1571l+2RFKldiXd2zdYbXUaYttWI8vk= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.133.207 with SMTP id g15mr11072027bkt.17.1325540052112; Mon, 02 Jan 2012 13:34:12 -0800 (PST) Received: by 10.204.177.18 with HTTP; Mon, 2 Jan 2012 13:34:11 -0800 (PST) In-Reply-To: <4F021F1F.3090807@orlitzky.com> References: <4F00D521.1030702@orlitzky.com> <4F00DA99.8050502@orlitzky.com> <4F00DEC5.5090500@gmail.com> <4F00E741.6050002@orlitzky.com> <4F01CED2.5090806@libertytrek.org> <4F01D6A2.9000002@orlitzky.com> <4F01DC67.7070305@orlitzky.com> <20120102231103.58da25d5@rohan.example.com> <4F021F1F.3090807@orlitzky.com> Date: Mon, 2 Jan 2012 16:34:11 -0500 Message-ID: Subject: Re: [gentoo-user] emerge --update behavior From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 62c0ad12-b7e3-4963-8585-eb8732f28901 X-Archives-Hash: 634af19a914e04ee9d2fb122800d8eb9 On Mon, Jan 2, 2012 at 4:18 PM, Michael Orlitzky 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