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.43) id 1DoQYO-0005Hv-2X for garchives@archives.gentoo.org; Fri, 01 Jul 2005 18:47:56 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j61IkwfP020560; Fri, 1 Jul 2005 18:46:58 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j61IjI5H004043 for ; Fri, 1 Jul 2005 18:45:18 GMT Received: from adsl-67-39-48-193.dsl.milwwi.ameritech.net ([67.39.48.193] helo=exodus) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1DoQVq-0002e4-Ca for gentoo-dev@lists.gentoo.org; Fri, 01 Jul 2005 18:45:18 +0000 Date: Fri, 1 Jul 2005 13:45:20 -0500 From: "Brian D. Harring" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] splitting build deps out from depends Message-ID: <20050701184520.GF11634@exodus.wit.org> References: <20050701162524.GB11634@exodus.wit.org> <20050701183536.GR19598@kfk4ever.com> 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="gDGSpKKIBgtShtf+" Content-Disposition: inline In-Reply-To: <20050701183536.GR19598@kfk4ever.com> User-Agent: Mutt/1.5.8i X-Archives-Salt: 2eceacbe-efdd-4fdb-b8f7-4a4962f530ec X-Archives-Hash: e8fbcba6f69d53314bee0d5dfee95981 --gDGSpKKIBgtShtf+ Content-Type: text/plain; charset=utf8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 01, 2005 at 08:35:36PM +0200, Maurice van der Pot wrote: > If the point is to make dependencies complete, isn't there a way to > build in some support for detecting it into some tool or other? >=20 > If we have a program that can create an environment and detect which > programs are run within the environment (maybe sandbox can do this, > maybe something with LD_PRELOAD, I'm sure we can think of something), > then we can build a list of programs that are run during the build.=20 > If we have such a list, we can find out which packages are required=20 > to provide the tools in the list.=20 >=20 > Such a tool could be used to generate the correct build dependencies > automatically or verify the existing bdeps. Not tenuable What you're effectivelly suggesting is that portage stomp ahead and,=20 hit a failure, try and figure out what atom would fix the failure,=20 retry, wash rinse repeat. Short version is that what you're proposing is basically a set of=20 tricks portage knows about to deal with failures; the problem is that=20 these failures can manifest themselves in a lot of crazy ways. Aside from that, LD_PRELOAD style hacks aren't exactly easy to do on=20 osx (got a dyld equiv, but have yet to see anyone do a sandbox equiv=20 via it). ~harring --gDGSpKKIBgtShtf+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCxY9AvdBxRoA3VU0RAs3zAJwJDaNLjZSRV/Q5jEjRQiuphTlllACffPRo G64O2cgE3aS09KhgKFvTeZw= =fETw -----END PGP SIGNATURE----- --gDGSpKKIBgtShtf+-- -- gentoo-dev@gentoo.org mailing list