Starting with the Eclipse 3.1 SRPM in Rawhide, I've managed to build
"non-native" packages on Fedora Core 4. I had to work around the
following issues:
* nspr-devel vs. mozilla-nspr-devel: Since nspr-devel (in Rawhide)
provides mozilla-nspr-devel, I changed the BuildRequires to
mozilla-nspr-devel. The location of the header files also changes,
so I modified eclipse-libswt-mozilla.patch to look in both
/usr/include/nspr4 and /usr/include/mozilla-1.7.10/nspr.
* Location of libjawt.so: The SWT build script seems to have the IBM
JDK file layout hardcoded in its build scripts. I've bugzilla'ed
this at https://bugs.eclipse.org/bugs/show_bug.cgi?id=110199. For
now, I'm inclined to simply BuildRequire an IBM JDK for non-native
builds. Any thoughts on exactly what I should require and how I
should set JAVA_HOME would be appreciated.
* Non-native builds are not noarch. I set the ExclusiveArch's for
non-native builds to %{ix86} x86_64 ppc ppc64 ia64, which are the
architectures supported by Eclipse itself.
The real question is what next? It would be nice if the resulting SPEC
file could be used for both Fedora Core (4 and devel) and JPackage. How
should I go about "conditionalizing" things?
Note BTW, that changing the package VERSION to 3.1.0_fc is pretty nasty.
Can this be moved to the RELEASE?
Thanks!
--
========================================================================
Ian Pilcher i.pilcher@xxxxxxxxxxx
========================================================================
