[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Why is the director needed during install?
- From: Thomas Hallgren <thomas@xxxxxxx>
- Date: Thu, 24 Sep 2009 17:12:47 +0200
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
That was interesting news.
My use-case is that I first aggregate a repository. The result of the
aggregation is always a P2 repository. Seems to me, it would be
beneficial if the aggregator could resolve this issue so that the
resulting P2 repository is complete.
How would I do that? I guess I would start by looking for the partial
IU's. But then what?
On 09/24/2009 04:45 PM, Pascal Rapicault wrote:
This dependency is from the eclipse touchpoint to the publisher. It is
necessary in order to generate the complete IUs for the bundles being
installed from the legacy update sites (becasue when we are generating
metadata for UM site we don't pull down all the bundles, but just the
The code is written this way so we can honor the fact that the dependency
on the publisher is optional. For example if you know you only contact p2