[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Sharing Your Shared Install Issues
- From: Pascal Rapicault <pascal@xxxxxxxxxxxx>
- Date: Sun, 2 Oct 2011 22:30:28 -0400
- Delivered-to: firstname.lastname@example.org
Sami, Niels, did you had a chance to capture your requirements wrt Linux installs?
I did not see the description of what was below on http://wiki.eclipse.org/Equinox/p2/Shared_Install
From the initial description, I believe that it should not take much change to p2 to make the install of plugins through the native package manager work. That said, I'd rather be sure we have a complete description of the pb, and agrees on the solution that is suitable for the package managers.
Another thing to think about is uninstallation. Can it be assumed that the interdependencies of sets of plugins laid down by the package managers are captured in the metadata of the package. For example GMF depends on EMF and depends on GEF. If there is a package for each of these things, would the GMF package have deps on the EMF and GEF one?
On 2011-09-23, at 12:01 PM, sami wagiaalla wrote:
> 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:
> 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.
> p2-dev mailing list