[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Platform agnostic profile

Hi Pascal and Helmut,
Very interesting. I understand the issue with platform specific install handles, etc. But you seem to have cracked my problem. How do you avoid "osgi.os"? Do you simply skip the PROP_ENVIRONMENT setting in the profile?

Regards,
Thomas Hallgren

Haigermoser, Helmut wrote:
Ciao Thomas :)
Our p2-based installer does the same, it installs IUs for every platform
into a single profile. We need this to support multi-OS installations.
The way we do it is to avoid osgi.os...
Like Pascal said there are limitations, installing the IU containing
"firefox.exe" on linux will be OK but the associated Start Menu entry
for windows can't be registered etc. 

Another idea is to use layers of profiles, one per osgi.os, or some form
of local profile that would look at the IUs in the central profile and
execute all Start Menu creation etc. for the local host...

HTH,
Ciao, hh

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Pascal Rapicault
Sent: Tuesday, February 10, 2009 4:22 PM
To: P2 developer discussions
Cc: P2 developer discussions; p2-dev-bounces@xxxxxxxxxxx
Subject: Re: [p2-dev] Platform agnostic profile

Ok, let's step back. Even if you were able to resolve, doing an actual
installation of all the IU is impossible since there will be actions
that are platform specific that can't be successfully run (e.g. window
registry key setting on a linux box). 
>From a java world perspective when it comes to building, the only thing
that is necessary is to have access to the jars, however the jars in the
repos are not necessarily in a runnable form (e.g. they can be packed or
they can be in jar where they need to be a folder form) and they need to
be massaged. The code we introduced in M5
(org.eclipse.equinox.p2.repository.tools) goes over a set of
repositories and "massage" the artifacts and the resulting massaged
artifacts are then passed to PDE Build as a target. Again this work at
the artifact repo level and as such does not consider the metadata
dependencies (https://bugs.eclipse.org/bugs/show_bug.cgi?id=264267)
which is why it can be of help.

PaScaL

Inactive hide details for Thomas Hallgren ---02/10/2009 10:03:11 AM---I
want to create a target platform (or product) that can Thomas Hallgren
---02/10/2009 10:03:11 AM---I want to create a target platform (or
product) that can be used cross-platform. I'm not sure how ma



From:	
Thomas Hallgren <thomas@xxxxxxx>	

To:	
P2 developer discussions <p2-dev@xxxxxxxxxxx>	

Date:	
02/10/2009 10:03 AM	

Subject:	
Re: [p2-dev] Platform agnostic profile	
________________________________




I want to create a target platform (or product) that can be used
cross-platform. I'm not sure how massaging repositories can make that
happen. Is the PDE build removing platform constraints from the IU's
before installing them?

- thomas

Pascal Rapicault wrote: 

		In M5 we have released support for PDE build to use as a
target p2 repos and also fetch from p2 repos. These repos are massaged
by PDE to make the plug-in available in a "compilable" form. This is
probably what you are looking for.
		
		
		Inactive hide details for Thomas Hallgren ---02/10/2009
09:46:08 AM---I need it to create a target platform that can be used
foThomas Hallgren ---02/10/2009 09:46:08 AM---I need it to create a
target platform that can be used for building products that can run on
all pla
		
	
From:	
Thomas Hallgren <thomas@xxxxxxx> <mailto:thomas@xxxxxxx> 	
	
To:	
P2 developer discussions <p2-dev@xxxxxxxxxxx>
<mailto:p2-dev@xxxxxxxxxxx> 	
	
Date:	
02/10/2009 09:46 AM	
	
Subject:	
Re: [p2-dev] Platform agnostic profile	
________________________________

		
		
		
		I need it to create a target platform that can be used
for building products that can run on all platforms. It is essential to
us (and everyone else that creates similar products) that the platform
based discrimination is performed by OSGi at runtime and not at install
time.
		
		Regards,
		Thomas Hallgren
		
		Pascal Rapicault wrote: 

						It is not possible to
create such a profile. This would require changes into the slicer to
ignore the filters (should be straightforward) but the hardest part
would be in defining what is a valid solution since there could be
several singletons that would need to be enabled.
						What would you use this
profile for?
						
						
						Inactive hide details
for Thomas Hallgren ---02/10/2009 09:28:16 AM---I would like to create a
platform agnostic profile. I.e. Thomas Hallgren ---02/10/2009 09:28:16
AM---I would like to create a platform agnostic profile. I.e. a profile
that would accept IU's regardles 
	
From:	
Thomas Hallgren <thomas@xxxxxxx> <mailto:thomas@xxxxxxx> 	
	
To:	
P2 developer discussions <p2-dev@xxxxxxxxxxx>
<mailto:p2-dev@xxxxxxxxxxx> 	
	
Date:	
02/10/2009 09:28 AM	
	
Subject:	
[p2-dev] Platform agnostic profile	
________________________________

						
						
						
						I would like to create a
platform agnostic profile. I.e. a profile that 
						would accept IU's
regardless of platform filters. The analogy (which I 
						think is impossible at
present) would be to describe the current 
						delta-pack as a feature
and install it so that all it's bundles are 
						installed.
						
						Is it possible to create
such a profile? Can the PROP_ENVIRONMENT accept 
						wildcards?
						
						Regards,
						Thomas Hallgren
	
_______________________________________________
						p2-dev mailing list
						p2-dev@xxxxxxxxxxx
<mailto:p2-dev@xxxxxxxxxxx> 
	
https://dev.eclipse.org/mailman/listinfo/p2-dev
<https://dev.eclipse.org/mailman/listinfo/p2-dev> 
						
						
						
						
________________________________

						
	
_______________________________________________
						p2-dev mailing list
						p2-dev@xxxxxxxxxxx
<mailto:p2-dev@xxxxxxxxxxx> 
	
https://dev.eclipse.org/mailman/listinfo/p2-dev
<https://dev.eclipse.org/mailman/listinfo/p2-dev> 
						

		_______________________________________________
		p2-dev mailing list
		p2-dev@xxxxxxxxxxx <mailto:p2-dev@xxxxxxxxxxx> 
		https://dev.eclipse.org/mailman/listinfo/p2-dev
<https://dev.eclipse.org/mailman/listinfo/p2-dev> 
		
		
		
		
________________________________

		
		_______________________________________________
		p2-dev mailing list
		p2-dev@xxxxxxxxxxx <mailto:p2-dev@xxxxxxxxxxx> 
		https://dev.eclipse.org/mailman/listinfo/p2-dev
<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