| Re: [p2-dev] Sharing Your Shared Install Issues |
Hi Sami, please capture these thoughts in the wiki. It will save us from trying to track down this email later. :-)
Thanks.
p2-dev-bounces@xxxxxxxxxxx wrote on 2011/09/23 12:01:55 PM:
> From: sami wagiaalla <swagiaal@xxxxxxxxxx>
> To: p2-dev@xxxxxxxxxxx
> Date: 2011/09/23 12:18 PM
> Subject: Re: [p2-dev] Sharing Your Shared Install Issues
> Sent by: p2-dev-bounces@xxxxxxxxxxx
>
> Hi Domenico, DJ, all
>
> > [...] This bundle pool holds all of the
> > features/plugins already in installed format. So, when a user uses P2 to
> > install from here, really it just updates the bundles.info, platform.xml
> > and SDK profile to load from this bundle pool.
>
> This kind of functionality would make work nicely with rpm. RPM really
> needs to do the adding and removing of the files being installed. With a
> solution like the above we can do something like this:
>
> The platform rpm would install the platform plugins into:
> /usr/lib/eclipse/{feature,plugins}
>
> Then a plugin rpm like eclipse-jdt can install things (in a runnable
> state) into:
> /usr/lib/eclipse/repos/jdt (or any other suitable location inside or
> outside the eclipse directory)
>
> Then run the director to install things from this location (bundle
> pool?) into /usr/lib/eclipse/configuration/.../bundles.info et. al.
> without moving the artifacts of course.
>
> The other thing needed for rpm is to be able to verify that the
> provisioning will go through successfully before actually doing it. This
> is important because the rpm is doing this as root user. I believe
> -verifyOnly accomplishes this. If so, then this is just meant to
> emphasize its importance.
>
> DJ, would you like me to put a more detailed version of the above on the
> wiki and/or the bug, or does this email suffice.
>
> Cheers,
> Sami
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev