I certainly wouldn't be opposed to making p2 its own project, but how much
extra overhead in involved (*managerial* -- release, docware, etc... and *
technical* -- builds, platform contribution, etc..)?  Also, there are a few
components (simple configurator for example), which are kinda p2 and kinda
platform and sorta equinox. I guess Pascal and Tom would have a good idea
of where to place these things (they're in p2 right now).

cheers,
ian


On Fri, Dec 7, 2012 at 12:07 AM, Gunnar Wagenknecht
<[email protected]>wrote:

> Am 06.12.2012 23:46, schrieb Pascal Rapicault:
>
>  Another solution is to make p2 a project in of itself.
>>
>
> That's what I was thinking.
>
> -Gunnar
>
>
>
> --
> Gunnar Wagenknecht
> [email protected]
> http://wagenknecht.org/
>
>
> ______________________________**_________________
> equinox-dev mailing list
> [email protected]
> https://dev.eclipse.org/**mailman/listinfo/equinox-dev<https://dev.eclipse.org/mailman/listinfo/equinox-dev>
>



-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Reply via email to