[Bug 208613] New: Review Request: libgcj - separate libgcj srpm

[bugzilla redhat com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.




https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208613

           Summary: Review Request: libgcj - separate libgcj srpm
           Product: Fedora Core
           Version: devel
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: normal
         Component: Package Review
        AssignedTo: jkeating redhat com
        ReportedBy: tromey redhat com
         QAContact: extras-qa fedoraproject org
                CC: fedora-package-review redhat com,notting redhat com


Spec URL: http://people.redhat.com/~tromey/libgcj-srpm/libgcj41.spec
SRPM URL: http://people.redhat.com/~tromey/libgcj-srpm/libgcj-4.1.1-20.src.rpm

Description:

This is a separate source RPM for libgcj.  The idea is to allow pushing
libgcj updates separately from GCC updates, enabling faster bug fix
turnaround.

There's a separate patch for the GCC spec file.  I've sent a version of it
to Jakub, but it needs an update.  This patch reduces the build requirements
of GCC; for instance we no longer need gtk to build the GCC rpms.

There is a helper script in the libgcj SRPM to create the initial source
tar from the gcc srpm.  I think maintenance-wise the best approach is to
start with the current gcc sources and then apply libgcj patchese as needed.
Rebasing to a new gcc is simply and automated with the script.

With my patch the gcc spec file still builds libgcj.  This lets us continue
to run 'make check' to verify that compiler changes don't break the libgcj
build.  However, the libgcj built here has reduced functionality (e.g., 
no AWT peers -- this is why we can remove build requirements) and is not
packaged.

With this change, fastjar and grepjar move from the libgcj RPM into the
gcc RPM.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.