[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [p2-dev] P2 default fragment requirements
|
This redundancy is a glitch of time that has never been fixed, but its
presence has no impact on the provisioning operations.
This could likely be fixed by changing the metadata generator to not
generate this additional entry and it would most likely have no impact
on the install operation since the Slicer and the Projector consider the
requirements from the fragments. That said, this may have an unforeseen
impact on other components of p2 or usage of the metadata done by other
tools.
The fact is that people have (without knowing) relied on this spurious
requirement and now changing it may have unforeseen consequences.
On 27/02/2014 11:57 AM, Vladimir Prus wrote:
Hi,
I'm looking at http://wiki.eclipse.org/Equinox/p2/Setting_Start_Levels
and it mentions that default fragment
is added to all IUs, and in particular it contains this:
<hostRequirements size='1'>
<required namespace='org.eclipse.equinox.p2.eclipse.type'
name='bundle' range='0.0.0' multiple='true' greedy='false'/>
</hostRequirements>
<requires size='1'>
<required namespace='org.eclipse.equinox.p2.eclipse.type'
name='bundle' range='0.0.0' multiple='true' greedy='false'/>
</requires>
What exactly is the role of the 'requires' element? It is rather board
requirements already, and then this fragment
is added to every other IU, so effectively every bundle IU has a
requirement that can be satisfied by any other
bundle IU, and the practical impact of this is rather unclear to me.
Unrelatedly, looking at
http://wiki.eclipse.org/Equinox/p2/P2_Fragments is seems that
'fragments' is used in completely
different way there? What is the current primary meaning?
Thanks in advance,
