I'm not keen on the separation between where I specify the repo
to use and where I specify what to include from that repo (and the
absence of authoring support for that latter). Because of that
separation, goodness knows if what think I contribute will really
come from my repo and not some other repo.
That is the case with b3 though. The guarantee is only as strong as what version requirement you put in the aggrcon file. If you specify an exact version in the aggrcon and another p2 repo has exactly the same version the bundle may be pulled from that repo instead.
I also wonder too if the two different implementations
(resolution algorithms) use to build the repositories really do
actually produce the same repositories? E.g., when I contribute
Oomph, I do not contribute the http client bundles (as an
example). I do it that way so that I don't contribute conflicting
or older versions of those things. But what stops the Tycho
resolution mechanism from grabbing potentially older the ones from
the Oomph repository anyway? Nothing I think...
The b3 implementation does not stop this case either. b3 does not limit itself to pulling from your p2 repo what you put in the aggrcon, it just guarantees that the output repo will have at least what you do specify.
The Planning Council ought to speak out and the simrel
participant opinions (if any one has one!), ought to be considered
too.
I have just joined the planning council, we have a meeting on Wednesday so I'll make sure this comes up (although I expect it would have anyway :-)
Jonah
