[etoys-dev] Re: Merging Etoys

[K. K. Subramaniam]

On Saturday 20 February 2010 04:56:30 pm Bert Freudenberg wrote:
> What I meant to add is that this Etoys repo would hold all code currently
> in the Etoys image, just as the trunk repo holds all code in the trunk
> image. Ideally we'd add a configuration-based update mechanism just as in
> trunk so that we can easily load updates by pushing a button. Does that
> make the idea more clear?
The source code in Etoys packages are less than 8% of overall source code (35k 
out of 527k). Why not keep only the Etoys packages in the repo and compose an 
image on demand from the current trunk? Patches for trunk could go into Inbox 
while those for Etoys could go into tracker.

Is it possible to automatically harvest changesets in updates.list into mcz? 
Then we don't have to decide between cs or mcz right away. I don't know the 
history behind cs vs. mcz and don't intend to reawaken a flame war ;-).

Subbu