Joshua Gargus wrote:
> Douglas Brebner wrote:
>> the numbered release images will be build from a set of specific
>> package releases and mantis submissions. (Think of these as branches
>> that should only receive fixes)
>> The latest mainline image will be built from the latest mainline
>> packages. (Fixes can be pulled and tested, then folded in but won't be
>> the main method of development).
>> Your own custom images can be built from whatever packages you like.
>> (can be a mix of specific release or latest)
>>
>> They'd all be built automatically from a build config for Kieths tool.
>>
>> Normal development would be done on a package basis, not a whole image
>> basis. The only exception would be for restructuring where the package
>> boundaries change.
>>
>> I think part of the problem is that some people are thinking in terms of
>> package development and others in terms of randomly messing with the
>> whole image.
>>   
>
> I'm thinking about both at the same time.  Packages are good, and
> Squeak development happens in Squeak images.  I believe that when
> someone goes to squeak.org, there should be an easy-to-find image that
> has the tools necessary to track current development.   That image may
> be built by Bob (why not?), and will have MC loaded (otherwise it
> couldn't track current development).
>
> The exact same packages as in this image (or a subset/superset/etc.)
> can be used to build other images using Bob.  I'm agreeing with you
> that "conveniently structured images built from packages is what
> Keith's build tool is for".
>
I think we're actually in violent agreement.

What I've been getting at is that some people seem to see the trunk repo
as a place to work on core packages with seperate build systems and
others see it as a place to hack on the big blob image old-style.