Am Jan 22, 2007 um 17:45 schrieb Joshua N Pritikin:
On Mon, Jan 22, 2007 at 05:33:42PM +0100, Bert Freudenberg wrote:
Am Jan 22, 2007 um 15:09 schrieb Marco Pesenti Gritti:
Etoys git keeps growing in size because of the etoys.image.gz
history.
How can we solve this? Maybe download the image at some build stage
rather than checking it in git?
Alternatively, we might switch to a more general SCM, like
subversion. The problem would just not exist there.
I don't understand. Why do you expect subversion to be better?
Because subversion does not download all versions since the beginning
of time, when you actually only need the latest one to build.
Is etoys.image.gz generated from source code?
Not quite. In Smalltalk you "program" by directly manipulating a live
world of objects - classes, methods, instances, UI elements, etc. A
snapshot of this world is saved as "image" on disk and simply resumed
(in contrast to other OO systems which recreate all objects on each
run).
If so, why do you need to store its history? Why not store it
outside of GIT?
Well, the etoys image is where most development happens for the etoys
activity. So there are almost daily changes to it. It's correct that
we do not need the history for it, at least not for producing diffs
or merging etc.
Putting the image (and the example projects) in a different place
would make sense - hence my inquiry for a subversion repository.
- Bert -
_______________________________________________
Sugar mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/sugar
