|Re: Managing available software sites [message #510531 is a reply to message #510226]
||Wed, 27 January 2010 18:19
| Paul Webster
Registered: July 2009
Konstantin Komissarchik wrote:|
> Thanks for your reply. I am interested in pursuing the p2.inf /
> touchpoint approach that you described, but I have not been able to
> figure out what to do with p2.inf file once I have it.
> Is there a command we can run after laying everything down that would
> apply stuff in a p2.inf file?
I haven't seen an application that could just run instructions, although
there might be a way to build something like that using the p2
provisional APIs ... I've never touched them myself.
> How do we make sure that p2 has a chance to process stuff in the dropins
> folder before we apply our p2.inf file? The removeRepository commands
> that we need to run have to apply after stuff in the dropins folder had
> made its contribution.
I think you might have to create a "distro feature" (or IU) that you
would only include when building the zipped distro and not publish to
your update sites.
The underhanded way to get it to work is to have your distro feature
actually include the p2.inf file (the p2 folks frowned at me, though :-)
Slap the distro feature in there when creating your dropins and away
you go. If you can make your distro feature depend on one of your
containing product/functionality features, then hopefully it won't have
any processing problems.
The downside is this feature shows up in the About dialog installed
software and features tabs. There's a way to just create the IU so that
it only shows up on the Installed Software tab, not the Features tab
(but you need to install using the director).
The full p2.inf I used that worked on 3.5.1 was:
> Is there any information you could point me to that would describe how
> to create distros in the "p2 way".
I haven't noticed an "assembling tutorial", sorry. I do know that the
director is the application that p2 uses to install features or build
complete applications from the command line.
If you are already creating update sites for your features, the director
can easily install them all into an SDK for you from the command line.
The example I used in testing (I had the EMF Update site in a local zip)
is to unzip an SDK target and then:
releng/eclipse/eclipse -application org.eclipse.equinox.p2.director \
-noSplash --launcher.suppressErrors -consoleLog \
-flavor tooling -p2.os linux -p2.ws gtk -p2.arch x86 \
-roaming -profile SDKProfile \
-repository jar:file:/tmp/sites/emf-xsd-Update-2.5.0.zip\!/ \
-destination target/eclipse \
My target/eclipse install is now the SDK + the EMF SDK. By fiddling
with the repositories (you can specify more than one) and the IUs you
can install a combination of things at once.
I hope that helps, good luck.
Powered by FUDForum
. Page generated in 0.02893 seconds