> > > get from an update site (e.g. Europa's update site).
> > Sure! Again, we may have been talking about two different
> To me, the driving use-case is what we provide to Europa.
> If we follow the Callisto model, we'd provide one feature for every
> then other projects could "require" (not 'include') that
> feature for improved
> update manager operation. Is that still the right model?
Some projects seem to have followed that model while
others (e.g., the Eclipse project) just included the third party bundles
in their regular features. Honests I've not thought about this alot
to have an opinion one way or the other.
> And, again following the Calliso model, Europa's
update site is simply a
> combination/copy of individual project's update sites ... so, that's
> why I figured we in Orbit would have one too.
Right. I was looking at that as an implementation
detail. That is, without the 3.3 PDE Target Provisioning support
for adding things from update sites directly to your target platform (that
work has not yet begun btw), it is unclear who would go to an *Orbit* update
site. Certainly people with the Europa release would want to update
Orbit bundles but they would go to the Europe update site. Don't
get me wrong, I'm all for having an update site but also observe that a)
its going to be a pain to manage all the features and b) the site will
be largely useless given the client side infrastructure we have today.