On Dec 11, 2006, at 6:46 AM, Rick wrote:
I like the fist break out that Jeremy proposed as I see there may be issues with keeping all this organized and lets give this a shot and see how well we manage it. After a while if we think things are going smooth start breaking out extensions on their own.
We need to break the extensions out upfront and not just reshuffle the tree, right? The tight build and distribution coupling between extensions and the kernel was what caused us problems and, IMO, we need to address that.
I do hope we can organize it to still allow building the latest in SVN TRUNK of all components so if we want to test how that all still hangs together it's possible without being too painful. The danger of going to long without catching incompatibilities I think is real too. Moving samples related to extensions to the extensions makes some sense, but I still think in the future we may want to offer some distribution artifact where they are bundled together and allow for a user to do a one shot download to play with them.
I agree with the "one shot" download if it is possible (probably organized by runtime type). By bunding samples for a specific extension with the latter, it would allow the extension to be released on its own, giving more flexibility. Samples that used multiple extensions would still be bundled under the separate samples directory.
Jim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
