> for total compatibility it seems like we should just use OSGi.
> from the we-need-something-like-maven/gem/ivy camp.
or else there wouldn't be such an upsurge in OSGi interest and adoption.
> that we implement the kitchen sink.
overlap, so we just assume they don't.
systems, then I think we would hit most use cases.
>>>>>> the runtime dependency expressions.
>>>>>> representation that can be returned by the search.
>>>> split packages as a necessity.
>>> On the split package front, however, it seems a little fuzzy to me.
>>> may return more than one instance that exports a given package.
>> or equal to it, I suppose.