From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JZpDj-0002la-Mf for garchives@archives.gentoo.org; Thu, 13 Mar 2008 15:19:52 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AB5B1E0761; Thu, 13 Mar 2008 15:19:49 +0000 (UTC) Received: from aei-tech.com (static-69-95-200-80.ind.choiceone.net [69.95.200.80]) by pigeon.gentoo.org (Postfix) with ESMTP id 7C4E8E0761 for ; Thu, 13 Mar 2008 15:19:49 +0000 (UTC) Received: (qmail 25700 invoked from network); 13 Mar 2008 15:19:46 -0000 Received: from unknown (HELO www.aei-tech.com) (192.168.1.1) by 192.168.1.1 with SMTP; 13 Mar 2008 15:19:46 -0000 Received: from 192.168.2.159 (SquirrelMail authenticated user ctennis) by www.aei-tech.com with HTTP; Thu, 13 Mar 2008 11:19:46 -0400 (EDT) Message-ID: <34622.192.168.2.159.1205421586.squirrel@www.aei-tech.com> In-Reply-To: <1205418357.15182.6.camel@woix.comwax.com> References: <430880c50803121635g294f505av259707f7e6a746bb@mail.gmail.com> <1205415290.17945.19.camel@nc.nor.wtbts.org> <47D92F32.8070703@gentoo.org> <47D930BC.3050708@gentoo.org> <52737.192.168.2.159.1205417733.squirrel@www.aei-tech.com> <1205418357.15182.6.camel@woix.comwax.com> Date: Thu, 13 Mar 2008 11:19:46 -0400 (EDT) Subject: Re: [gentoo-dev] Help offered - Portage tree From: "Caleb Tennis" To: gentoo-dev@lists.gentoo.org User-Agent: SquirrelMail/1.4.10a Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 0f5f1bc9-9328-4298-bf80-5d1c934009c2 X-Archives-Hash: 24c6382be74e0e7e2fe78f77be69db45 > I think remi was more speaking about incorrect deps (say misplaced in > RDEPEND) than problems concerning the package manager. > > In any case, openssl is the perfect example of what can go wrong becaus= e > of upstream's behavior. The problem is that program A compiled against > version X of openssl won't work with version Y>X. Currently we need to > keep X's libs around and run revdep-rebuild to fix this. Right, my example was mildly contrived. But I've run into this same issu= e with packages like ruby and glibc, where the build system had newer versions a= nd you run into symbol issues (or errors like "invalid binary format") because you n= eed to upgrade underlying libraries. > Most librairies don't cause this problem though so I don't really see > this as a bug on the gentoo side even if it's annoying. It's not really Gentoo's fault, no, but it's a problem that could be some= what fixed. > Anyway, to keep machines using binary in sync without much headache, my > current solution is to use a squashfsed portage tree with --deep. It > works pretty well. Agreed, but the problem is (at least in my case) we're talking about prod= uction machines that are actively running, and the customer needs an upgrade of = a package but we don't want to take a chance at ruining something else by upgrading= --deep if we can help it. >From their perspective, they just want it to work (and don't care about w= hat has to be upgraded), but from a sysadmin perspective it's a difficult problem to= solve over time, especially when you have 10+ other sysadmins, who all may not know = that when you upgrade package X be sure to remember to also upgrade packages Y and = Z at the same time or you'll run into problems. --=20 gentoo-dev@lists.gentoo.org mailing list