[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Provisioning p2 with p2?

This is where I get lost, I understand that this might very well be
the case (I found the profile registry in the p2 agent, which I'm
using), but how would I go about to 'zip-up' my profile, which is done
with the eclipse SDK as John described, and ship it off to somewhere
else? Point being, I want my profile to be autonomous.

If I'm able to achieve this, would I still be able to use a second p2
agent to manage the now 'autonomous' system, as long as it's offline,
or are these set-ups mutually exclusive (i.e. is an externally
manageable autonomous system a contradiction in terms)?

Thanks,
Fredrik.

On Thu, Feb 26, 2009 at 00:16, Henrik Lindberg
<henrik.lindberg@xxxxxxxxxxxxxx> wrote:
> Hi,
> The profiles are stored in a ProfileRegistry - and the implementation used
> in p2 stores the profiles under  "engine". Snoop around under the "p2"
> directory in your stand alone Eclipse SDK installation, or under
> user.home/.p2 if you tried a SharedInstall.
>
> Henrik Lindberg
> henrik.lindberg@xxxxxxxxxxxxxx
>
>
>
> On Feb 25, 2009, at 4:47 PM, Fredrik Alströmer wrote:
>
>> 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? :)
>>
>> Thanks,
>> Fredrik.
>>
>> 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>
>>> To
>>> p2-dev@xxxxxxxxxxx
>>> cc
>>> Subject
>>> [p2-dev] Provisioning p2 with p2?
>>>
>>>
>>>
>>>
>>> Hi,
>>>
>>> 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?
>>>
>>> Thanks,
>>> Fredrik.
>>> _______________________________________________
>>> 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
>>>
>>>
>> _______________________________________________
>> 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
>