Re: [linuxtools-dev] System-installed dependencies

[Alistair Bush <ali_bush@xxxxxxxxxx>]

> * Matt Whitlock <matt@xxxxxxxxxxxxx> [2009-11-12 18:12]:
> > External bundle-classpath entries are claimed to be an alternative (I
> > read it somewhere in the Eclipse documentation).
> 
> I think it's probably best if you query the Equinox community.  These
> are probably good places to start:
> 
> http://www.eclipse.org/forums/index.php?t=thread&frm_id=31&S=a9191c46420098
> a13becfed1d9c14f31 https://dev.eclipse.org/mailman/listinfo/equinox-dev
> 
> > (I'm sick of wasting tens of hours trying to hack the Eclipse build
> > into being built-from-source friendly.)
> 
> I'm confident _you_ know this, Matt, but for those playing along at
> home, this is the goal of the eclipse-build effort.
> 

Hi Andrew.

How do you foresee eclipse-build handling the bundling of external jars?   FYI 
I know absolutely nothing about OSGI but I have the impression that I large 
amount of the time it is actually downstream that adds the osgi manifest info 
into the dependencies.  The situation I'm concerned about is that 2 projects 
will both depend on package/jar "A" but will have 2 incompatible manifest 
files.  This will mean that we are having to duplicate packages.....

Currently gentoo is inserting the manifest info into eclipse-3.4's 
dependencies but this is a real pain and make packaging eclipse far harder 
than it needs to be.  That combined with us not having a dedicated maintainer 
for eclipse results in a rather crappy eclipse installation ( Matt is doing a 
fantastic job with 3.5 tho).

I (and possibly Matt, hint hint) should also look at how you have separated 
eclipse into its "modules".  it would really be nice to have equinox, etc as 
separate packages.  Do you do this "post-build" or does linux-build handle 
this?  seems like your todo-list suggests you currently do it post-build.

Overall how do you envision the final packaging solution to look like?

All the best and thanks for the hard work

Alistair