Re: [tycho-dev] [discuss] tycho repository layout and metadata format

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

We need to know if *future* repository content changes can affect
resolution results. This I believe boils down to being able to tell if
IMatchExpression<IInstallableUnit> is guaranteed to match one and only
one installable unit or not. And even this may not be enough to handle
optional requirements.

--
Regards,
Igor

On 11-06-01 10:39 AM, Sievers, Jan wrote:
> > Heh. This was exactly my plan when I started to integrate p2 into
> > tycho few years back. I actually had working prototype that took
> > top-level features, calculated resolved dependency set and reported
> > on loose IUs. There was also a way to provide additional resolution
> > constrains to further lock down the resolution. I think this is the
> > right approach, but as I mentioned earlier, I am not positive this
> > is possible to implement in p2 3.6+.
>
> Hmm. I am not sure myself but Tobias told me this is related to
> slicer mode.
>
> What I understood is that in planner mode you can get those
> "dangling" requirements (required but not included, and thus possibly
> with version ranges), whereas in slicer mode you only get the
> (transitively) included bundles, and these always have perfect
> version matches.
>
> Maybe Tobias can comment?
>
> Regards, Jan