[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: Fw: [p2-dev] Using the new "sofware site" target provisioner

On Sat, May 2, 2009 at 4:09 AM, Thomas Hallgren <thomas@xxxxxxx> wrote:
I think the trick is to use the profile but skip the planner phase. This means that a the full closure of IU's must be computed in a different way but that's the only difference as far as I can tell. One simple way of doing the computation is to use the PermissiveSlicer to select the transitive closure of the selected top features. Once the set of IU's has been determined, an InstallableUnitOperand is created for each one and then the collect phase is executed as normal.

The result is an IBundleContainer that is polymorph, i.e. you don't need to reload it just because you change the target platform os/ws/arch.

The really interesting thing about this is that if such a container was present, there would be no need at all for the delta-pack. It would become obsolete in an instance. Just point to the platform repository at Eclipse.org and you're all set.

If you're interested, I can provide a patch that alters the current IUBundleContainer to do it this way. IMO, it would make the "Sofware site" provisioner a lot more useful.

The PDE team loves patches. Can you attach it to this bug where we're looking at spoofing the JRE profile at the moment?

I'm a bit curious what the main difference would be when not using the planner. What do we lose.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=272750

Cheers,

--
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk