On Thursday 23 March 2006 21:38, Gustavo Sverzut Barbieri wrote: > Ok... this discussion is missing my initial point that is how to > provide binary dependency and avoid many crashes we have now with > almost no effort. > > My initial proposal was to, after compile and before install is done, > we should parse linker information and check for each library it > depends, which package-version provides it and then mark the just > compiled package runtime-dependent on them. If the dependency was not > installed by portage, then issue a warning/error and take some action > (ask user, abort or ignore)
Ok, my counterproposal: Don't do it automatically. Use a heuristic by default (within the same BINSLOT, higher or equal version). Allow ebuilds to override this. Then we can do automatic verification as you propose. My way allows binary dependencies to work more broadly. It also makes things explicit. Changing detection to verification should catch the same bugs. Not detecting does however mean that we can be better than a fallible autodetection system. And trust me, autodetection WILL fail for some packages. > Cons: > - it's not the final solution to the problem, as said, interfaces > would be better... but interfaces would demand much more effort and > not being automatically generated, would be async and probably > incorrect at some point Interfaces, while nice, would overcomplicate things. They are also not needed as we have depend atoms. Paul -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net
pgpnYPdywgo0M.pgp
Description: PGP signature
