[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] Publisher question, feature requirements
- From: Thomas Hallgren <thomas@xxxxxxx>
- Date: Wed, 14 Apr 2010 10:51:57 +0200
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199) Gecko/20100330 Fedora/3.0.4-1.fc12 Lightning/1.0b1 Thunderbird/3.0.4
There are two ways of adding a feature reference in a feature. It can be
either 'included' or 'required'. My interpretation has always been:
'included' features will be installed when the parent feature is installed.
'required' features serves as a prerequisite. They will not get
installed. Instead, an error will be generated if they are not present.
Is that a correct interpretation?
If it is, then shouldn't this be reflected by the 'greedy' status of the
IRequirement? From the wiki:
"When a requirement is marked greedy (greediness flag on a requirement),
installable units satisfying the requirements are added to the solution,
whereas IU satisfying non greedy requirements should be added to the
solution by another requirement. By default all requirements are greedy."
To me, that sounds like a 1-1 correspondance to the 'includes' versus
The reason I ask is that I cannot find any indication that this is
considered in the publisher FeaturesAction. I'm not sure that my
interpretation is correct so I thought I'd ask here before I file a bug.