Hi Jeff,
What I'm trying to achieve is a multiple-profile installation in the target
product.
We are using a maven based build system invoking p2-director application.
AFAIU to generate the config.ini I need a product configuration file. But
as I'm trying to create multiple Profiles I'm looking at a way to reuse the
config.ini and the bundles.info files generated when i create the
BaseProfile in first step.
The steps I'm trying are;
1. First materialize a BaseProfile (ProfileA) using a base.product
configuration file. This profile includes the minimal set of IUs installed.
I'm invoking director app with -destination {target.home}/{profile}. In
this step, a config.ini and a org.eclipse.equinox.simpleconfigurator/
bundles.info is generated under {target.home}/ProfileA.
2.Then I want to create a new Profile(ProfileB) which should include what I
installed in the BaseProfile + a set of new features.
At this point what I'm looking at is, reusing above created
bundles.infoand config.ini and try to invoke p2-director to install
the new features
into a new Profile without materializing it all over again using a
.product file.
Is this possible? Also in my case of multiple-profile installation, can
shared-configuration concept be useful?
Thanks,
Dileepa
On Sat, Feb 16, 2013 at 3:48 PM, Jeff MAURY <[email protected]> wrote:
> Can you tell us which customization you want to perform to the config.ini ?
>
> Jeff
>
> Le vendredi 15 février 2013, Dileepa Jayakody a écrit :
>
> Hi All,
>>
>> I know that when we give a .product configuration file with required
>> configurations to p2.director it will generate a config.ini file.
>> Is the only way to generate config.ini to provide a product configuration
>> file?
>> Can I pass the necessary configurations to be added to the config.ini
>> explicitly and pass a set of features as IUs to p2-director to install?
>>
>> Thanks,
>> Dileepa
>>
>> --
>> Dileepa Jayakody,
>> Software Engineer, WSO2 Inc.
>> Lean . Enterprise . Middleware
>>
>> Mobile : +94777-857616
>>
>
>
> --
> Jeff MAURY
>
>
> "Legacy code" often differs from its suggested alternative by actually
> working and scaling.
> - Bjarne Stroustrup
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.twitter.com/jeffmaury
>
> _______________________________________________
> p2-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/p2-dev
>
>
--
Dileepa Jayakody,
Software Engineer, WSO2 Inc.
Lean . Enterprise . Middleware
Mobile : +94777-857616
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
