For the SDK the steps are to: - unzip the SDK - mark the SDK read only but be sure to not run the app before that. I'm not sure if this is still required, but this was because the fwk would find file there and decide to use them btu would never be able to switch to the configuration from the shared install. - run. This will create a configuration in the user home director.
Note that because some update manager code never got ported to p2, you will have to have update configurator be around for the user specific configuration to be created. HTH On 2011-06-03, at 5:57 AM, Thomas Hallgren wrote: > Hi, > > I have a question regarding shared installs, configurations, and the p2 > director. > > The problem: > We have a shared Buckminster installation at /shared/common/buckminster-3.7. > It's created using the p2 director. As it stands right now some projects have > problem using it since they don't have access to the configuration area. If I > grant them access, they create artifacts there using their own accounts which > I then cannot remove. A sample error printout here: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=345993#c0 > > What I'd like: > I want to provide a read-only install, configured to the extent possible and > then have each user use their own configuration on top of that but I haven't > managed to find any good example of how to set this up using the p2 director. > If anyone knows about such an example, or is willing to describe the steps > here, I'd be very grateful. > > TIA, > Thomas Hallgren > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
