On 9/29/09 6:47, Sahoo wrote:
Richard S. Hall wrote:
On 9/25/09 19:28, Sahoo wrote:
[Writing this email so that someone reading this later gets the
correct information. ]
I had a lengthy offline discussion with Richard and the conclusion
was because of the way Felix resolver is currently implemented,
bundle b1 will get package q from itself for Q1 irrespective of
installation order of b1 and b2 as long as b2 is in INSTALLED state.
Did I say that? Maybe I was confused, since I am not sure its true.
I think installation order is important since it is used for
priority. If we assume all bundles are INSTALLED and we are resolving
b1, p will be resolved to b1 since there is no other provider. For q,
however, there are two providers and the order of choice depends on
install order, since they are both version 1.0.
You mentioned that Felix starts with Export-Package list while
resolving a bundle, so it has to first decide whether bundle b1 will
export package q or not.
No, it is the opposite. When a bundle imports and exports the same
package, Felix always tries to resolve the import first (which may
resolve to itself). Sorry if I implied otherwise.
If what you are now saying is correct, then what is implementation
specific about this? What are the alternative ways of resolving those
packages?
Yes, as I mentioned when we talked. The spec doesn't mandate that the
impl should favor imports over exports of the same package. That is the
impl's choice. Some could, as you say, favor exports over imports of the
same package.
I think in that scenario, if you favored exports you'd always end up
with b1 being resolved to itself, but by favoring imports it ends up
being dependent on installation order for q.
-> richard
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
