Dirk Heinrichs wrote:
Hi,
there has been a lengthy discussion on bugzilla ([1]), about the best
packaging method for the gnat Ada compiler. The outcome seems to be that
gnat will still have its own ebuild in the future and not be part of the
GCC ebuild. It also has a mention that gcj will eventually be split out
from the GCC ebuild in the future.
So my question is: Would it be a good idea to generally turn GCC into split
ebuilds (like KDE/X.org)? Pros/Cons?
The only case where we actually split anything is for the few C-only kernel
compiler packages, gcc-mips64, gcc-sparc64, gcc-powerpc64, etc.. These disable
everything else but C, as this compiler is explicitly only for kernel building.
Anything else...good luck. Aim for manipulating USE flags properly, though, to
disable features of gcc you don't want or need. This works better than
splitting everything.
--Kumba
--
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees
"Such is oft the course of deeds that move the wheels of the world: small hands
do them because they must, while the eyes of the great are elsewhere." --Elrond
--
gentoo-dev@gentoo.org mailing list
