|
Re: Migrating a Europa custom installer to Galileo P2 [message #132930 is a reply to message #132376] |
Fri, 12 June 2009 12:59 |
Henrik Lindberg Messages: 2509 Registered: July 2009 |
Senior Member |
|
|
Paul Webster wrote:
> Derek wrote:
>> Hi,
>>
>> We are starting to migrate our product from Europa to Galileo (we
>> missed out Ganymede).
>>
>> Our product consists of RCP, our plugins and a large collection of
>> files (executables, data file, etc) outside of the Eclipse install.
>>
>> For Europa, we wrote a custom InstallHandler that is invoked by the
>> update process and allows us to update the 'external' files. This is
>> working extremely well. We also use a similar facility to install
>> additional (optional) functionality from our update site - it installs
>> both the plugins and additional external files.
>>
>> We would like to do something similar with Galileo/P2:
>> - is this possible?
>> - are there any articles explaining how?
>> - any hints on where to start?
>>
The concepts you are looking for are called "install handlers" in p2 as
well (also refered to as "meta requirements") and it allows an
installable unit to declare requirements on units that must be installed
prior to running the rest of the installation.
The neat thing is that the "install handlers" are just regular
installable units and sort of gives the same result as if the user first
installed them, and then the rest of the installation - only that the
user sees it as one operation.
Secondly, when using p2 to install, it invokes touchpoint actions to
perform the actual install. To invoke custom actions you need to
implement at least a touchpoint action, but possibly also a custom
touchpoint if you need additional things not provided in say the native
touchpoint.
As a starting point, take a look at how some of the p2 native actions
are implemented - like unzip, copy, etc.
I know there are articles and examples being worked on for Galileo release.
Regards
- henrik
|
|
|
Powered by
FUDForum. Page generated in 0.01644 seconds