It's all about re-thinking what rosapps is. Initially it was supposed to be a place for various "app"lications. Right now it turned out to become a kind of a trashcan, where stuff unapplicable for trunk goes. Since this is wrong, it's perfectly fine to "force" devs to build with rosapps (and rostests, if they are interested in thorough testing) module.
Otherwise, with make/make all, we again end up with rudimentary rosapps.
Also there will be some kind of "unmaintained" module (undecided yet - discussions are welcome) where some stuff from rosapps is going to be moved (which is not currently maintained, and not interesting for devs).
WBR, Aleksey.
On Mar 9, 2007, at 2:38 AM, Ged Murphy wrote:
Upon thinking about this, I'm not sure it's such a good idea with respect to usermode stability as it will get less testing now from non-included apps.
This would allow us to have the best of both world. Many of the tests we run at application level rely on the apps which have just been moved being easily accessable. If these are gone, I suspect less feedback will be collected about the status of usermode.
Ged.