Ciaran McCreesh wrote: > On Wed, 06 Jun 2007 11:24:00 +0200 > Luca Barbato <[EMAIL PROTECTED]> wrote: >> PMS overlords what's your take? > > You need to start by identifying use cases. Are you discussing handling > cross compiling,
Yes multilib, Ok C++ / python ABIs Aaaaaargh, ehm, should we really throw them in the mix? anyway let me see if the same rules apply: - they have to reside in a separate path if possible? - the linker must not pick wrong ones in place of the ones you want to use. - an application using a former abi must link depend on stuff from the same place but MAY use stuff from another place. - is up to the loader pick the right paths on execution - the dep resolver should ignore packages built using the other C++/Python abi. The issue is more complex and I just ignored it basically because the library abi mismatch is an error that should be rectified and not something you want and no it isn't because I don't care about binary only stuff right now, it's just because looks like there is already too much meat w/out something that fits just halfway on the constraints. or all of them? Then you > need to identify what packages would need to do to handle those things. All. > Don't even think about the package manager side until you've worked out > what ebuilds would do. autotooled programs more or less are already doing the right thing, non autotools packages supporting cross development may require some additional checks to pass the right target. lu -- Luca Barbato Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- [EMAIL PROTECTED] mailing list
