Re: [p2-dev] Trying to make sense of agent, installer and director

["Torsten Schlabach" <TSchlabach@xxxxxxx>]

Hi!

Thanks, that explaination makes some sense.

> - the p2-installer can be directed to install anything by modifying  
> the installer.properties.

Well, I would have expected it to be able to install me an SDK if I use the default settings, but no luck.

I have downloaded the p2installer from Galileo 3.5RC3 on win32 and just lauched it.

Result:

> !SESSION 2009-06-04 19:14:49.062 >
> -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_13
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
> Command-line arguments:  -os win32 -ws win32 -arch x86
> 
> !ENTRY org.eclipse.equinox.p2.installer 4 0 2009-06-04 19:15:25.250
> !MESSAGE Installable unit not found: org.eclipse.sdk.ide

Shouldn't that work out of the box normally?

As you say, the UI has little options to set.

I also tried to install something using the agent.

There my problem was that it could not find certain required parts in any of its repositories.

Did anyone ever successfully install his / her SDK through P2?

I mean: Install from scratch. Not just install some additional features into an existing SDK which got installed by unpacking a ZIP file. Or do I suffer from a misunderstanding and the p2installer is not at all made for that?

Regards,
Torsten


-------- Original-Nachricht --------
> Datum: Thu, 4 Jun 2009 19:46:36 +0200
> Von: Henrik Lindberg <henrik.lindberg@xxxxxxxxxxxxxx>
> An: P2 developer discussions <p2-dev@xxxxxxxxxxx>
> Betreff: Re: [p2-dev] Trying to make sense of agent, installer and director

> In one respect, they are all the same (agent, installer, director) as  
> it is the same code beneath the surface.
> It is the UI and how you tell it what you want that differs.
> 
> Some small notes:
> - the 'director.app' is part of every SDK. There is also a separate  
> headless director.
> - the p2-installer can be directed to install anything by modifying  
> the installer.properties. It's UI is streamlined as it performs the  
> installs a particular way.
> 
> Henrik Lindberg
> henrik.lindberg@xxxxxxxxxxxxxx
> 
> 
> 
> On Jun 4, 2009, at 5:40 PM, Torsten Schlabach wrote:
> 
> > Hi all!
> >
> > I am currently trying to gain an understanding of how I will manage my
> > Eclipse SDK and Eclipse based product installations in the future.  
> > This
> > includes both RCP apps as well as possibly headless installations. I
> > understand p2 is what I want in the future, for a number of good  
> > reasons.
> >
> > Now I am trying to understand what's offered to me at
> >
> > http://download.eclipse.org/equinox/
> >
> > I think I am most interested in the sections
> >
> > Provisioning
> > Launchers
> >
> > What would be the difference between
> >
> > - A launcher for my platform
> > - An Equinox p2 agent
> > - An Equinox p2 installer
> > - The Equinox director which is not listed here at all, but I found it
> > on the Buckminster update site
> >
> > My guess was:
> >
> > - The agent can install arbitrary artifacts into arbitrary locations.
> > This is managed using some kind of profiles.
> > - The installer is a special purpose agent which can only install
> > Eclipse SDK?
> > - The director is the same as the agent, just it can run headless.
> > - After I will have installed by SDK for example, using either the  
> > agent
> > or the installer or the director, I will not yet have a launcher  
> > because
> > Launchers are not installable by using p2.
> >
> > Are my guesses about right?
> >
> > Regards,
> > Torsten
> >
> > _______________________________________________
> > 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