On Thu, 2006-06-08 at 18:39 +0000, Michael Koch wrote:
> Then we could simply maintain a separate SRPM for libgcj, and
> shackled to the gcc update schedule. The SRPM would only have to
> contain the appropriate target directories, and we could incorporate
> mauve testing into the release process.
Debian does something like this since some time. We have two source packages,
gcc-4.1 and gcj-4.1. The first builds and packages all of GCC except Java. The
second one builds C/C++/Java and packages only the Java parts. this works quite
good. We take care that both source packages are from the same upstream sources
but its easily possible to add patches and bug fixes to one of the packages and
just rebuild it.
It would be nice if we can coordinate the patch-set between fedora and
debian. And maybe, if it all seems to work out find, we could even
suggest that patch-set for a new 4.1.x release. Even if that breaks
binary compatibility. Because if it is what the distributions ship then
it must be good :)