[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] P2 profile and osgi.configuration.area

Thanks for the reply, Simon,
Is there any chance that bug 267926 would be fixed in the near future? For our product we have to re-direct the configuration area to users' home since a lot of our customers have shared installs. Now our users won't see the pre-defined repositories in their personal profiles. They have to add them manually in order to get product updates from our update site. This alone is a regression from pre-3.4 Eclipse bahaviour.
I would submit an enhancement request on showing sub-features in the "Installation Details".

From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Simon Kaegi
Sent: June 18, 2009 9:49 AM
To: P2 developer discussions
Subject: Re: [p2-dev] P2 profile and osgi.configuration.area

> Re: [p2-dev] P2 profile and osgi.configuration.area
> Andy Jin

> to:

> P2 developer discussions

> 06/18/2009 09:20 AM

> Sent by:

> p2-dev-bounces@xxxxxxxxxxx

> Please respond to P2 developer discussions

> It happens even I don't modify the "config.ini".
> On Linux when the product is a shared installed owned by super-user
> "root" and run by a normal user, Equinox notices that the default
> "eclipse/configuration" area is not write-able and creates a personal
> ".eclipse/<configuration>" area. I see the same problem happening in
> this settings.
> Is it an expected behavior or is it a regression?

Hi Andy,
This is the expected behavior and what we've had since 3.4 to support "shared install". This is the scenario where there's a base install that everyone uses and then individual installs are free to further customize their install by adding additional features etc. The minimal user profile you're seeing is setup so that it refers back to the shared profile's contents when a provisioning operation occurs.

For the two points you er... pointed out:
1) There's a enhancement request to cascade profile preferences (where the available update sites are stored) here. https://bugs.eclipse.org/bugs/show_bug.cgi?id=267926
2) Showing sub-features installed in the parent profile in "Installation Details" sounds reasonable. Please open an enhancement request.


> Andy Jin wrote:
> > Is there a way to change the default "osgi.configuration.area" while
> > maintaining P2 profile?
> >
> > Here is the problem I have, I am using Eclipse 3.5 RC4.
> >
> > 1) I build the product using PDE headless productBuild.xml, and enable
> > P2 with the followings settings in the build.properties:
> >
> > p2.gathering=true
> > p2.flavor=MyProduct
> > p2.director.profile="">> >
> > 2) In my "MyProduct.product" file, I define only one top level feature
> > which includes all the sub-features and Eclipse platforms, CVS, CDT.
> > The build generates P2 metadata and runs the P2 director. I have a
> > final product at the end.
> >
> > 3) In
> > "<MyProduct>/eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry"
> > directory I have several profiles. I launch the product and I can see
> > all my features listed in the "About -> Installation Details" panel.
> > My product update site URL shows at the "Preference -> Install/Update
> > -> Available Software Sites".
> >
> > 4) However if I modify the "config.ini" file, add
> > "osgi.configuration.area=@xxxxxxxxx/.MyProduct/configuration" and
> > launch the product again, things mess up. I only see my top level
> > feature, the update site URL does not show. I have a new profile under
> > "@user.home/.MyProduct/p2/org.eclipse.equinox.p2.engine/profileRegistry"
> > directory which only has very minimal configuration.
> >
> > Is there a way to re-define the osgi.configuration.area while still
> > maintaining my original P2 profiles?
> >
> > Thanks,
> > Andy
> > _______________________________________________
> > 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