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 1RhrsC-0003aW-PU for garchives@archives.gentoo.org; Tue, 03 Jan 2012 00:05:01 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BB6C321C193; Tue, 3 Jan 2012 00:04:17 +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 E916121C028 for ; Tue, 3 Jan 2012 00:01:54 +0000 (UTC) Received: by eaai1 with SMTP id i1so10615709eaa.40 for ; Mon, 02 Jan 2012 16:01:54 -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:content-transfer-encoding; bh=rK862sMH6kx8nxfg+ojy0UlFWV3lVrYpqBlvKHYqsgA=; b=upsguBu3K0qxo7I+T5w64LqWnDJOIx6zBIzaXL8p1U7aXtZx9iYZR4bRrAaqAlC8qe E+TSn43fjgQ90dgKfOCCFrg/5X9Smey4yCWL69NytGuxmO86X4SP97lgiXghlEbA2B1C z0wkaATTMDe1ZYVBffxv4HImZhwD/5EnfVBL0= 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.205.120.14 with SMTP id fw14mr11118077bkc.53.1325548914087; Mon, 02 Jan 2012 16:01:54 -0800 (PST) Received: by 10.204.177.18 with HTTP; Mon, 2 Jan 2012 16:01:53 -0800 (PST) In-Reply-To: <20120103013312.3872601b@rohan.example.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> <20120103013312.3872601b@rohan.example.com> Date: Mon, 2 Jan 2012 19:01:53 -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 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 6bda9e08-12cc-409d-9a9a-ee3fb0150136 X-Archives-Hash: 2d0acc18158f918cd3d931ef5a8f5e89 On Mon, Jan 2, 2012 at 6:33 PM, Alan McKinnon wro= te: > On Mon, 2 Jan 2012 11:20:19 -0500 > Michael Mol wrote: > >> On Mon, Jan 2, 2012 at 11:16 AM, Michael Mol >> wrote: >> > On Mon, Jan 2, 2012 at 11:09 AM, Michael Orlitzky >> > wrote: >> >> On 01/02/2012 11:01 AM, Mark Knecht wrote: >> >>> >> >>> >> >>> I tell by knowing which files I want in @world. Everything in >> >>> world should be a package __I__ specifically want to use. >> >>> Everything in world (on my machines anyway) is something: >> >>> >> >>> 1) =C2=A0I'd call from the command line >> >>> 2) Need to write a little software myself, most specifically a >> >>> library 3) Aid in displaying things, like font packages >> >>> 4) Something required by Gentoo that I don't totally understand, >> >>> like a virtual package. >> >>> >> >>> I just look through every so often and make sure everything seems >> >>> to meet those sorts of requirements. When I find a library or >> >>> something else then: >> >>> >> >>> 1) I make sure I'm clean with emerge -DuN @world AND emerge -p >> >>> --depclean 2) I'll delete the questionable item >> >>> 3) I'll see what happens with the two commands in #1 >> >>> >> >>> To me it's pretty straight forward, but I'm also not bothered at >> >>> all by the idea that emerge package and emerge -u package do the >> >>> same thing. A machine that doesn't have a package, when updated, >> >>> should have the package and it should (IMO) be in world, but >> >>> that's just me. >> >> >> >> >> >> Fine for your home PC, doesn't cut it on servers. I have the >> >> following in one of my world files: >> >> >> >> =C2=A0dev-php/PEAR-Mail >> >> =C2=A0dev-php/PEAR-Mail_Mime >> >> =C2=A0dev-php/PEAR-PEAR >> >> =C2=A0dev-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=3Dy @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. >> >> It just occurred to me...in the future, you might be able to build >> ebuilds for managing customer requests, to ensure that dependencies on >> particular packages with USE flags and version requirements are met. >> >> I haven't built ebuilds myself yet, but it's on my TODO list. >> > > It's quite easy actually, doubly so if the package follows some sane > rational build process (like eg configure && make && make install). In > that case the ebuild is very small as the portage framework does all > the heavy lifting automagically. > > I'd move that TODO item higher up on the priority list if I were you, > you'll be glad you did :-) Oh, I know. There's a bunch of things I want to add or fix. Even if that means taking some degree of ownership of them. --=20 :wq