Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] Shared installs and our EPP Packages 
It makes sense.

When the share installation is updated to SR2 by admin, how the user
gets SR2 + his installation? Can '-clean' option work for it?

________________________________

From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Ian Bull
Sent: Thursday, August 12, 2010 3:32 PM
To: P2 developer discussions
Subject: Re: [p2-dev] Shared installs and our EPP Packages


The thinking here is that the 'base' (the shared area) contains the base
platform (say Helios).  Then, when you install a new bundle 'foo', this
goes in your local area.  Now, your local bundles.info file contains all
the bundles from the base + foo.  When Eclipse launches, it checks that
this is really the case (it checks that the shared bundles.info is a
subset of the local one).  I think there are two reasons for this.

1. The definition of 'shared' installs.  If each user could update the
base then this is not really 'shared' anymore.  Some users have SR1,
some have SR2, etc... 

2. Consistency.  If a users updates some bundles in the shared area, and
then the admin updates the base, what should we use now? 

There could be other reasons for this too. 

cheers,
ian


On Thu, Aug 12, 2010 at 6:11 AM, Zhu, Mengxin (Kane)
<Kane.Zhu@xxxxxxxxxxxxx> wrote:


	I'm wondering what's the intent of current mechanism(* part in
Ian's
	post) where picking up the bundles, share configuration or user
	configuration?
	
	I think it should load the bundles from user configuration if it
exists,
	which is created and maintained by p2 as well.
	
	________________________________
	
	From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On
	Behalf Of Ian Bull
	Sent: Thursday, August 12, 2010 4:47 AM
	To: Eclipse Packaging Project; P2 developer discussions
	Subject: [p2-dev] Shared installs and our EPP Packages
	


	Hi everyone,
	
	There have been a number of bugs opened regarding shared
installs not
	working [1,2,3,4,5,6].  While I don't know if they are all
related, I
	have tracked down a configuration problem with some EPP packages
that is
	causing this (at least it's causing it in some cases).  In both
Eclipse
	for Java Developers and the PHP package (I didn't check the
others)
	there are bundles listed in the bundles.info file that are not
in the p2
	profile. When Eclipse is launched in a shared install scenario
this
	configuration problem will limit our ability to install
additional
	bundles. See below for the technical reasons*.
	
	While shared installs were not very common in the past, they are
	standard install on Windows 7 (when someone installs Eclipse in
the
	C:\program files directory).  So this means that anybody using
an
	affected Helios package on Windows 7 (installed in c:\program
files\)
	cannot install additional bundles using either the p2 UI or the
MPC.
	
	So this brings up a few questions.
	1. Is this a known problem?
	2. Do we want to address this for SR1?
	3. How are the Helios packages created?  I created a helios
package
	manually using the director command**, and it was configured
properly.
	There must be additional steps that the helios epp builder is
doing that
	I'm not aware of.  There are also two p2 profiles in our EPP
packages,
	which seems odd to me.
	
	[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=320153
	[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=317896
	[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=321239
	[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=320383
	[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=317897
	[6] https://bugs.eclipse.org/bugs/show_bug.cgi?id=317757
	
	* When we run in a shared install scenario, we create a
bundles.info
	file from the p2 profile. When Eclipse is launched, our
generated
	bundles.info file is checked against the shared one, and if any
	inconsistencies are found, we ignore ours and use the shared
one.
	However, the shared one is read only, and will never contain the
	additional bundles.
	
	**  I used the following director command when installing an EPP
package
	from the Helios repository:
	./eclipse -application org.eclipse.equinox.p2.director
	-repository http://download.eclipse.org/releases/helios
	-installIU epp.package.java
	-destination /home/irbull/eclipse/eppinstall/
	-profile eppProfile
	-p2.os linux
	-p2.ws gtk
	-p2.arch x86
	
	cheers,
	ian
	
	--
	R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
	http://eclipsesource.com | http://twitter.com/eclipsesource
	
	
	_______________________________________________
	p2-dev mailing list
	p2-dev@xxxxxxxxxxx
	https://dev.eclipse.org/mailman/listinfo/p2-dev
	




-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource

Back to the top