Jakub - I should have copied you on the original thread.
We had been discussing decoupling the libgcj SRPM from the gcc SRPM so
we can push java runtime fixes out more frequently than gcc updates.
The idea would be for you to continue to build & test libgcj as part of
the gcc package, but delete it after installation and don't package it.
Then we'll just make a new SRPM based on the gcc sources that we can
patch and push out on a more frequent basis. What do you think of this
On Fri, 2006-06-09 at 01:17 -0700, Anthony Green wrote:
Here's what a libgcj source RPM could look like (using FC5)...
This source RPM builds, so feel free to try it.
You'll see that the SOURCES directory contains a script called
libgcj-copy-source.sh. This script generates the libgcj source tarball
from portions of the prepped gcc sources.
Using a libgcj source RPM like this means we can easily add our own
patches, rebuild and deploy on a schedule that is independent from the
gcc update schedule.
I'm going to have sporadic email access for the next 10 days or so. I
just wanted to get this out for comment before I take off.
fedora-devel-java-list mailing list