[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cross-project-issues-dev] dependencies, build and P2
- From: Thomas Hallgren <thomas@xxxxxxx>
- Date: Sun, 19 Dec 2010 10:40:03 +0100
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:22.214.171.124) Gecko/20101103 Fedora/1.0-0.33.b2pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.6
I'm also questioning the use of feature requirements. I can see one (somewhat far fetched) use of it and that is when
all bundle inter-dependencies are expressed as packages rather than bundles. By adding feature requirements, one can
encourage that those packages are provided by certain bundles. I say encourage because there's no way to guarantee that
this actually happens when other bundles also provide the same packages.
In the old days, a feature requirement was interpreted as 'non-greedy', i.e. the thing had to be present in the install
in order to install your feature but there would be no attempt to install it. Unless they were met, the installation
would fail immediately. For some reason that interpretation is no longer valid. The feature requirements are greedy so
their role is IMO very questionable.
On 2010-12-19 10:29, Gunnar Wagenknecht wrote:
Am 19.12.2010 09:19, schrieb Eike Stepper:
I see that there are plugin and feature dependencies possible. Would
you say that the plugin dependcies are a relict from times before p2?
Frankly, I'm constantly asking myself the same question. They definitely
existed before p2. As far as I remember the old update manager used
those dependencies. p2 should't need them as it is capable of collecting
all the dependencies by using the meta-data produced from the bundle