[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [p2-dev] Shared install with p2 director?
|
On 2011-07-20 21:38, Pascal Rapicault wrote:
Sorry but I'm not following what you are talking about for updates.
When other users are allowed to write to the <installation>/configuration directory we are at the mercy of their umasks.
They might well create entries there with file permissions that make it impossible for me to remove them. That in turn
means that if I update the product (using the director), then some of the created entries might be rendered obsolete and
the whole install is broken. It is also impossible for me to remove the product in order to reinstall it from scratch.
I think it's essential that the install is read-only and not in any way writable by other users than the ones managing
the install.
- thomas
On 2011-07-19, at 2:49 PM, Thomas Hallgren wrote:
On 2011-07-19 14:44, Pascal Rapicault wrote:
If you remove it, does it work?
It does, provided I allow other users to create it. But that in turn invalidates future updates since I don't have the privilege to remove what's been created. I don't want other users to create things beneath the install location.
On 2011-07-19, at 2:43 PM, Thomas Hallgren wrote:
On 2011-07-19 14:39, Pascal Rapicault wrote:
Do you know if the configuration folder already contains a org.eclipse.osgi folder
It does, yes. I've started once with -initialize
- thomas
On 2011-07-13, at 4:56 PM, Thomas Hallgren wrote:
Hi Pascal,
I'm probably doing something wrong, but the users of our installation still get the same error:
<title>Invalid Configuration Location</title>The configuration area
at '/opt/public/common/buckminster-3.7/configuration' is not writable. Please
choose a writable location using the '-configuration' command line option.
The update configurator is installed but that doesn't seem to help much. Do you have any other suggestions or hints that I could work with?
Thanks,
Thomas Hallgren
On 2011-06-03 14:27, Pascal Rapicault wrote:
Yes, this is what I would like to believe :)
On 2011-06-03, at 7:40 AM, Thomas Hallgren wrote:
Hi Pascal,
So what you are saying is that if we just add the update configurator to the set of installed bundles, everything will work out of the box?
- thomas
On 2011-06-03 12:48, Pascal Rapicault wrote:
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
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
