Pacho Ramos <pa...@gentoo.org> wrote: > >> > 3: multilib.eclass >> > > > This is my preferred solution
However, it has some serious drawbacks; most importantly: It implies that the same USE-flags must be used for the native and 32-bit variant. This is really a severe restriction since the motivation for installation can be very different for these variants. For instance, for a native ffmpeg the user might want support for a lot of codecs/devices while for the 32 bit variant the user might want only support for those codecs/devices which are needed for some special application. Nevertheless, the same useflags mean that he has to build the same (with all implied dependencies) also for 32 bit. Currently, this particular example is not so bad, since currently de facto ffmpeg:0.10 is the 32 bit version while ffmpeg:0 is the native version, and so the useflags can differ. However, it seems more like an accident that this does not occur here, in the moment. A "cleaner" solution would somehow treat the 32bit and 64bit variant like separate packages, each having its own set of USE-Flags, and also the possibility to rebuild one without rebuilding the other. AFAIK multilib-portage can do this.