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 1Rhkrk-0007YP-5j for garchives@archives.gentoo.org; Mon, 02 Jan 2012 16:36:04 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AE12D21C2D4; Mon, 2 Jan 2012 16:35:50 +0000 (UTC) Received: from mail2.viabit.com (mail2.viabit.com [65.246.80.16]) by pigeon.gentoo.org (Postfix) with ESMTP id D66AF21C26C for ; Mon, 2 Jan 2012 16:33:44 +0000 (UTC) Received: from [172.17.29.6] (unknown [65.213.236.242]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.viabit.com (Postfix) with ESMTPSA id 677B237AD8 for ; Mon, 2 Jan 2012 11:33:44 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orlitzky.com; s=mail2; t=1325522024; bh=RJxE3s7zGCCb3gT2KSUqWKi8GUC7aGG8X5WwlMhWBAI=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Bd3T49NoKvPJG7qpSWNhqn2TmAqk96W7dBj+yeA4CaL3yUF5HKlSDbGe+4uPBT7Un gazfmgWzLeevX3F6lzy2Zf/rzmDBMnyvAW4nPDk3s3ZCZV14XqFeYm4pKVEuFdVVqH 7GgwHkIcD3+/ViYqnZB69IUdXIuEgstSeB55bYcY= Message-ID: <4F01DC67.7070305@orlitzky.com> Date: Mon, 02 Jan 2012 11:33:43 -0500 From: Michael Orlitzky User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111202 Thunderbird/8.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge --update behavior 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> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: b8d87485-8c58-4e29-b4d9-96f836d9734e X-Archives-Hash: b13f3024cce8fc607f44b13c3403c7eb On 01/02/2012 11:16 AM, Michael Mol wrote: >> >> Fine for your home PC, doesn't cut it on servers. I have the following in >> one of my world files: >> >> dev-php/PEAR-Mail >> dev-php/PEAR-Mail_Mime >> dev-php/PEAR-PEAR >> dev-php/PEAR-Structures_Graph >> >> which of those do I want? At least one of them was installed to support a >> customer's custom PHP application. Maybe all of them were and they all >> belong in world. No one knows, this server is older than the current >> --update behavior. >> >> So which ones can I remove? >> >> Solutions involving time travel and/or losing customers will be >> disqualified. > > Make a backup copy of your world file. > > 1a. Remove those four lines. > 2a. emerge -p --depclean > 3a. Did any of those show up in the to-be-removed set? Add them back. > > Alternately: > 1b. emerge -pev --tree --with-bdeps=y @world > 2b Find those packages in the output. The tree form of the display > will help you see if anything is depending on them. > 3b. If anything is depending on them, you should be able to safely > remove them from your world file. I'd follow up with the 1a, 2a, 3a > solution to be sure. > Sorry, but these won't work. Let's say that dev-php/PEAR-Mail_Mime has a dependency on dev-php/PEAR-Mail, but I have a customer who needs dev-php/PEAR-Mail for a contact form. Following your process, I would remove dev-php/PEAR-Mail from my world file. If I ever remove dev-php/PEAR-Mail_Mime, depclean will remove PEAR-Mail and break the guy's site.