From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GQQCY-0006hH-C1 for garchives@archives.gentoo.org; Thu, 21 Sep 2006 15:10:58 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8LF9Mol021250; Thu, 21 Sep 2006 15:09:22 GMT Received: from alnrmhc12.comcast.net (alnrmhc12.comcast.net [204.127.225.92]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8LF6wvT027738 for ; Thu, 21 Sep 2006 15:06:59 GMT Received: from seldon (c-24-21-135-117.hsd1.or.comcast.net[24.21.135.117]) by comcast.net (alnrmhc12) with SMTP id <20060921145157b1200en8lje>; Thu, 21 Sep 2006 14:51:57 +0000 Date: Thu, 21 Sep 2006 07:51:55 -0700 From: Brian Harring To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFC about another *DEPEND variable Message-ID: <20060921145155.GE30105@seldon> References: <45126B07.6030403@gentoo.org> <451279D3.9020605@gentoo.org> <20060921115916.GB30105@seldon> <4512A3D0.9080301@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YkJPYEFdoxh/AXLE" Content-Disposition: inline In-Reply-To: <4512A3D0.9080301@gentoo.org> User-Agent: Mutt/1.5.11 X-Archives-Salt: 1a5700d7-8f22-4967-a21b-a8ab5d9e3297 X-Archives-Hash: a34777f7a1dbf4fca9672e352bbc2d51 --YkJPYEFdoxh/AXLE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 21, 2006 at 05:38:08PM +0300, Alin Nastac wrote: > Brian Harring wrote: > > On Thu, Sep 21, 2006 at 01:38:59PM +0200, Luca Barbato wrote: > > =20 > > There is one flaw with this though; packages can provide both=20 > > libraries _and_ binaries. Our dependencies don't represent whether=20 > > the dep is actual linkage, or just commandline consuming, so (using=20 > > the openssl example) any package that invokes openssl via the=20 > > commandline to do a few simple chksum ops gets rebuilt, despite the=20 > > fact it wasn't affected by linkage change ups. > > =20 > I like BINCOMPAT proposal but it solves only half of the problem. You > assume that all dependent packages cares about binary compatibility. > Why not using a BDEPEND var in those dependent packages affected by the > BINCOMPAT values of their dependencies? >=20 > For instance, I would set the following: > - in net-dialup/ppp ebuild: BINCOMPAT=3D${PV} > - in net-dialup/pptpd ebuild: BDEPEND=3D"net-dialup/ppp" BDEPEND was actually a seperate proposal/idea, intention there was to=20 have that be the deps that *must* be CHOST (gcc would be an example);=20 bits that are used to actually build the pkg, not data it consumes in=20 building (headers would be data). Meanwhile, for this I don't see the point in using a seperate metadata=20 key. Overload DEPEND and add a marker char that is used to indicate=20 that a particular dependency is 'binding', ie, it is linkage. ~harring --YkJPYEFdoxh/AXLE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFFEqcLsiLx3HvNzgcRAoA8AJ0Zc2G64+zUsUwTdLlj5sTzBlmSzwCfSupu wCFpqkRgpHGT3AhADqNzoiA= =KxBC -----END PGP SIGNATURE----- --YkJPYEFdoxh/AXLE-- -- gentoo-dev@gentoo.org mailing list