On Tue, 2005-03-08 at 12:27 -0600, Phil Muldoon wrote:
> On Tue, 2005-03-08 at 11:13 -0700, Tom Tromey wrote:
> > I think the key point is that whatever we do has to be supported by
> > eclipse.org. Any other way means maintaining our own build system.
>
> It's going to have to work with releng plug-ins then, as that is their
> build approach. Releng plug-ins produce tarballs now on a Linux
> platform, so we are halfway there. The releng plug-ins are fairly
> atomic in nature too, so it is all good. This is completely different to
> how jpackage.org build eclipse-* rpms, so pick one or the other I guess.
My proposal is definitely more in line with the releng build approach.
For the first part of the proposal, I want to give the releng process
the ability to generate a srcIncluded zips [1] for all plugins. This zip
file would be very similar to what we generate ourselves right now. Part
of this solution involves coming up with a way to build native code in
an automatic way - at least from the perspective of the person building
the plugin. Patches for this are in bugzilla but it needs a little more
work (see below).
For second part of the proposal, I want to extend this work so that
plugins and features can generate the same srcIncluded zip without the
need for a releng plugin. IMO, releng plugins are only needed if you
want automatic builds of some kind - nightly builds or whatever. A lot
of the open source plugins that I have come across generate their
releases by calling one of the targets in the generated build.xml. So
I'd like to add a target to the generated build.xml will make a
srcIncluded zip.
BTW, I updated the proposal again if you're interested.
[1] zip files will be used because there are problems with eclipse and
non-GNU tar.
> > Ideally building an RPM for an Eclipse plug-in should be nearly
> > completely automatic. I don't see why we couldn't achieve this... but
> > it depends on upstream cooperation.
>
> Ben has some patches on eclipse.org (Ben can you post the direct link
> here), but I don't think it has seen any eclipse maintainer traffic. :(
The patches are posted here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=71637
I'm just waiting for some comments so that I can finish this part off. I
suspect if I post a message to the releng mailing list now that my
proposal is a little more developed, I would get a response. I've been
distracted by this native eclipse stuff :)
> In building the RPM, are you proposing the the releng plug-in should
> deliver an RPM, or just a tarball like it delivers now? I can see merit
> in both ways, but how we would be add on all the %post/%postun stuff,
> and the actual jar -> so building bits on an automatic releng approach?
> All that stuff is pretty Fedora specific.
>
> If it is as it is now, the SPEC files for eclipse-* are totally generic
> in nature (were written that way), so it is sort of automatic. Not
> automatic enough, though ;)
If we get my proposed solution upstream, the spec files would become
more generic - it might even be possible to write a small script to
automatically package plugins.
Cheers, Ben
