RangeDependenciesAnalysed
From APIDesign
(Difference between revisions)
JaroslavTulach (Talk | contribs)
(New page: When analysing dependencies it can be easily proven that RangeDependencies (as used by OSGi) are too flexible and may lead to NP-Complete problems. However recently I start...)
Next diff →
Revision as of 12:10, 7 January 2012
When analysing dependencies it can be easily proven that RangeDependencies (as used by OSGi) are too flexible and may lead to NP-Complete problems. However recently I started to ask following question - it is known that LibraryReExportIsNPComplete and that the problem can be fixed by generating so called complete repositories. Can't the same trick be applied to repositories using RangeDependencies as well?
My current feeling is that it can. This page is my attempt to formalize the feeling to something more material.
Follow
