[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Sharing Your Shared Install Issues
- From: sami wagiaalla <swagiaal@xxxxxxxxxx>
- Date: Fri, 23 Sep 2011 12:01:55 -0400
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20110906 Thunderbird/6.0.2
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
/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.