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? > > 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. > If we have such a list, we can find out which packages are required > to provide the tools in the list. > > 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, hit a failure, try and figure out what atom would fix the failure, retry, wash rinse repeat. Short version is that what you're proposing is basically a set of tricks portage knows about to deal with failures; the problem is that 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 osx (got a dyld equiv, but have yet to see anyone do a sandbox equiv via it). ~harring
pgpDuedBtMYXe.pgp
Description: PGP signature
