On Sun, 20 Jan 2013 23:33:39 +0100
Michał Górny <mgo...@gentoo.org> wrote:
[...]
> > Do you plan to keep precise depends for packages?
> > like glibc[abi_x32]/gcc[abi_x32] for all libraries requesting x32.
>
> Yes. ${MULTILIB_USEDEP} is for that (it currently evaluates
> to 'multilib?').
In that very precise case (gcc/glibc) I'd say no: it's probably saner
to leave the toolchain as it is, ie, able to build all supported abis.
It probably means an end to implicit system deps for the rest of the
system set though.
[...]
> > like on ABI=amd64 media-libs/glu[ABI=x32] could not be used by
> > any of ABI=amd64 users.
> >
> > In order to track such depends precisely you would need to add
> > ABI flags to each revdep recursively. It's quite invasive. Is it
> > worth the effort?
>
> A good point. I'd say that the default impl should be built then.
> But... how about making it a USE flag with use.force logic? That way,
> it would be explicitly visible, and if someone really wanted to
> disable it, he would be able to do it on his own responsibility.
+1
[...]
> > Looks like insane amount of metadata growth for each
> > plagued package.
>
> I don't think metadata is really important here. I believe that
> the amount of additional metadata introduced by the packages affected
> by multilib is not really one worth worrying.
>
+1 too
OTOH, if you don't have this metadata you cannot really distinguish
between packages needing multilib and those that do not care (I
wouldn't want to run texlive-latexextra src_* phases twice or three
times because I want multilib).
Alexis.
