| Re: [orbit-dev] EBR / Recipes Update |
This sounds like some good work, Gunnar. I hope to take a closer look soon, but thought in parallel I would ask some questions.
Does it literally have to be "one at a time"? I am think about when several packages that "go together" (such as Lucene).
I assume that when a bundle has some prereqs, those are still resolved from our current repositories? And that would be how we would
know a bundle was "completely" in Orbit.
None of this excludes the concept of having I-builds, S-builds and eventually R-builds, right? I would assume the "tiny repos" would be mirrored into the larger repos?
That is, we can still "increment" towards the final R-build repository, instead of everything going in the R-build, even if it was wrong the first build or two?
[I ask since R-builds are forever ... where as we I-builds and S-builds are temporary.]
I assume "moving to the new system" does not depend on this being done first, right? Though, it would be nice.
Any outlook on when this work would be done? (Does it eventually belong in Tycho?)
I think the thing that is blocking us now is having a place at Eclipse.org for the original artifacts to live.
Any progress or word on setting up an "original artifact database"? (Instead of pulling things live from maven. central).