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 1ObkG4-0000b7-AJ for garchives@archives.gentoo.org; Thu, 22 Jul 2010 01:07:32 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8CF12E0960 for ; Thu, 22 Jul 2010 01:07:31 +0000 (UTC) Received: from wlym.com (wlym.com [66.135.63.43]) by pigeon.gentoo.org (Postfix) with ESMTP id 5A725E0C15 for ; Thu, 22 Jul 2010 00:37:22 +0000 (UTC) Received: from ccs.covici.com (pool-71-171-112-166.clppva.fios.verizon.net [71.171.112.166]) (authenticated bits=128) by wlym.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id o6M0bJAH006789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 21 Jul 2010 19:37:21 -0500 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.4/8.14.4) with ESMTP id o6M0bGRQ030436 for ; Wed, 21 Jul 2010 20:37:19 -0400 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: I don't understand Perl. What do I do after an update? In-reply-to: <201007220014.44732.alan.mckinnon@gmail.com> References: <201007212134.21252.alan.mckinnon@gmail.com> <28563.1279746875@ccs.covici.com> <201007220014.44732.alan.mckinnon@gmail.com> Comments: In-reply-to Alan McKinnon message dated "Thu, 22 Jul 2010 00:14:44 +0200." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.2.1 Date: Wed, 21 Jul 2010 20:37:16 -0400 Message-ID: <30435.1279759036@ccs.covici.com> From: covici@ccs.covici.com 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 X-Archives-Salt: 98d2a2f0-4587-4b1e-9cf4-a831838df9c1 X-Archives-Hash: 8592fb831e4acabb536e6d8ff34c0801 Alan McKinnon wrote: > On Wednesday 21 July 2010 23:14:35 covici@ccs.covici.com wrote: > > > This is a painful process. It's enough to drive a sysadmin to drink or > > > (god forbid), to Windows. Portage can't help as the ebuild doesn't know > > > what you have installed. So you must run a script to go and dig out all > > > this crap for you. > > > > > > > > > > > > All I can say is, every day I get down on my knees and offer thanks that > > > perl is not slotted. > > > > But portage should be sensible enough to either run this for you, or > > stop emerging -- I had a lot of trouble during the last update where I > > kept getting errors and I emerged a couple of them before I knew I had > > to run perl-cleaner. > > You haven't thought this through and haven't consider how portage knows what > to do. > > Portage doesn't do it because portage can't. > You want portage to do it != portage can do it. > > Consider this: > > [I] dev-lang/perl > Installed versions: 5.12.1-r1(23:11:24 21/07/10)(berkdb gdbm -build - > debug -doc -ithreads) > > [I] dev-perl/DateManip > Installed versions: 5.56(19:39:11 17/07/10)(-test) > > > When I upgraded perl to 5.12.1-r1, DateManip was not upgraded. Why not? > because it's version number did not change and that is the ONLY thing portage > considers. DateManip depends on perl, not on =perl-whatever-I-used-to-have > > So portage does not know of the link between these two things and cannot take > them into account. Portage won't be expanded anytime soon either - you saw how > long it took for perl-cleaner to run, must portage go through something like > that with every emerge? > > Similarly, one could say portage should detect rev-dep breakage. Surprise! It > doesn't. revdep-rebuild does that (comparable to perl-cleaner) and you know > how long that takes to run. > > So you wasted some time with an upgrade. Well that's a shame. But we don't > care much, especially if you don't read the elog messages. If you feel that > portage should does this automagically, and have a plan to make it run REAL > quick, and have proven, workable, debugged, solid, stable patches, then I'm > sure Zac would be very happy indeed to hear from you. > > In the meantime, read the elog messages. But I could not read the elog messages, the emerge was going on, till I got the first error and I didn't realize that portage had upgraded perl -- the only thing I would like portage to do is to know that something must be run and stop so I can do this. You could have a list of packages which require a stop after emerging or something. I am thinking out loud here, but this is what I am trying to say. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com