[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Provisioning p2 with p2?
- From: Fredrik Alströmer <roe@xxxxxxx>
- Date: Wed, 25 Feb 2009 16:47:10 +0100
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=bAYerl+z+Ppo9ZS15L5FZ+C4Sfi3uspBQIBcPx0ER5AEyIZtI2oUlj6lb9aU5HeePc H7xqbOKzf0yiBuMcjHI+Ud6AILHlNx7WoXWVUDZLIO+46TYBXPBn3ktp8v15dFw8nt/O MGudSjVc18ihzoBdifTEkhjGjbCgF1pWBuNek=
Excellent, that's what I wanted to hear... Now I only need to figure
out how to do this... ;)
For the second part, that's what I meant, I was just curious whether
an external p2 system (which is creating the profile) is actually able
to convey information to the profile about IUs being installed and so
on. I wasn't able to find a meta data repository (i.e. a description
of the installed IUs) - only an artifact repository - in the profile I
installed into, how does the p2 instance within the created profile
know what it contains? Or does it simply backtrack and look for
matching IUs to the artifacts?
Or am I simply missing some magic here? :)
On Wed, Feb 25, 2009 at 15:01, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:
> Absolutely, p2 can and does do that. In fact our Eclipse project builds run
> exactly in this way - p2 ant tasks are used to create a profile, into which
> the platform or Eclipse SDK is provisioned. The result is then zipped up and
> delivered on our downloads page. Also, once you have installed the platform
> (which includes p2), p2 will manage and be able to upgrade that (including
> itself). p2 can manage a system that is not currently running, or it can
> manage a system that it is currently running inside of.
> What you read about who touches what might have been taken out of context.
> What that means is that if the user unzips stuff manually into
> eclipse/plugins or eclipse/dropins, then it is the user's responsibility to
> "manage" those plugins manually at the file system level (upgrade it, remove
> it, etc). p2 won't touch them. Things that have been provisioned into
> eclipse/plugins or elsewhere by p2 via the user interface or command line
> tools shouldn't be manually edited/removed at the file system level by the
> end user (just like you don't manually move/delete DLL's from Windows apps
> and expect them to continue working).
> Fredrik Alströmer <roe@xxxxxxx>
> Sent by: p2-dev-bounces@xxxxxxxxxxx
> 02/25/2009 08:38 AM
> Please respond to
> P2 developer discussions <p2-dev@xxxxxxxxxxx>
> [p2-dev] Provisioning p2 with p2?
> I think I read somewhere that, whatever is managed by p2 you shouldn't
> touch, and whatever you manage p2 won't touch. This makes perfect
> sense, however there's one thing that's not completely clear to me. Is
> it one of the purposes of p2 to be able to create a new profile (using
> p2, that is, like with the p2 agent), install p2 into that profile,
> and then let it manage itself?
> p2-dev mailing list
> p2-dev mailing list