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 1R3Bo9-0006y6-1c for garchives@archives.gentoo.org; Mon, 12 Sep 2011 19:04:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4B39821C1BD; Mon, 12 Sep 2011 19:04:27 +0000 (UTC) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by pigeon.gentoo.org (Postfix) with SMTP id 1093021C14C for ; Mon, 12 Sep 2011 19:02:41 +0000 (UTC) Received: (qmail invoked by alias); 12 Sep 2011 19:02:40 -0000 Received: from p5B083DA8.dip.t-dialin.net (EHLO pc.localnet) [91.8.61.168] by mail.gmx.net (mp072) with SMTP; 12 Sep 2011 21:02:40 +0200 X-Authenticated: #13997268 X-Provags-ID: V01U2FsdGVkX182EVE3b6M2xTOaFa/nBs6fGl6Dkx9njIhMJJgNnB eRQa/dOCfsZVme From: Michael Schreckenbauer To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: package.provided messes up emerging of package slots? Date: Mon, 12 Sep 2011 21:02:34 +0200 Message-ID: <2037937.Ts9Eii1Yvy@pc> User-Agent: KMail/4.7.1 (Linux/2.6.38-gentoo; KDE/4.7.1; x86_64; ; ) In-Reply-To: References: <2494723.cpEDGkQfFl@pc> 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 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Y-GMX-Trusted: 0 X-Archives-Salt: X-Archives-Hash: 3ac4aec85149e4098d6d914380a4a03d On Monday, 12. September 2011 21:31:59 Nikos Chantziaras wrote: > On 09/12/2011 08:17 PM, Michael Schreckenbauer wrote: > > On Monday, 12. September 2011 20:04:47 Nikos Chantziaras wrote: > >> On 09/12/2011 07:42 PM, Michael Schreckenbauer wrote: > >>> On Monday, 12. September 2011 18:41:37 Nikos Chantziaras wrote: > >>>> In my /etc/portage/profile/package.provided, I have this: > >>>> media-libs/freetype-1.4_pre20080316-r2 > >>>> > >>>> When I try to emerge freetype however, instead of emerging the > >>>> newer > >>>> > >>>> version, I get: > >>>> $ emerge freetype > >>>> > >>>> WARNING: A requested package will not be merged because > >>>> it is > >>>> listed > >>>> > >>>> in package.provided: > >>>> freetype pulled in by 'args' > >>>> > >>>> Nothing to merge; would you like to auto-clean packages? > >>>> [Yes/No] > >>>> > >>>> Trying "emerge freetype:2" also won't work. The only only to > >>>> emerge > >>>> it > >>>> seems is by using the whole version ("emerge =freetype-2.4.6"). > >>>> Is > >>>> this > >>>> a bug? > >>> > >>> At least it's inconsistent. I would expect that the emerge with > >>> complete version also fails. > >> > >> It's slotted, so it shouldn't fail. Freetype 1 and 2 can be installed > >> at the same time. > > > > Yes, that's true for the packages provided by portage. portage does not > > know anything about the freetype you provide, so it shouldn't install > > any freetype from any slot by any command. > > I don't see how it doesn't know anything about it, given that it > requires me to list a full package atom in package.provided. So it > always knows which version should be considered as being provided. Yes. freetype version 1. So if a package depends on freetype version 1, portage assumes, the dep is already installed. It does not know, where it is installed, or what files it installed. So it has to assume, that an emerge of freetype-2 actually could overwrite some of your freetype-1 files. Therefore it should not install freetype-2 with any command, if you have any version of freetype in package.provided. Best, Michael