GIRA/Physical-Etoys — comment on commit 8da8f9922c35619efa74c54113e844264586c22d
File:  line 0
By RichoM:

Ok, I removed the image from the repository. I like the idea of having a
script download an official image and install the required packages
automatically. I'm concerned about two things, though:
1) the Physical Etoys package modifies the Etoys system in various places
(see the package extensions) and it could be dangerous to always use an up
to date image (although it would highlight errors sooner, which is a good
thing).
2) the loading of code in Etoys is awfully slow.

In any case, this is not a big deal right now. We can worry about it later.

2011/12/13 Sverin Lemaignan <
reply@reply.github.com
>

> > Well, that image is not actually supposed to change much, really. I have
> it as a helpful way of starting with a clean image with a few helpful
> packages and preferences. But I haven't though of the size, and I guess it
> will make things *really* slow... maybe I should just upload it somewhere
> else.
>
> Well main issue is that, every time we change a single line in the
> image, the repo grows of 30 MB... (that's not a Git specific issue...
> every system would have such troubles with binary blobs. Git makes it
> a bit worse, though, because it does (by design) not allow to treat
> binary blobs as specific objects whose verions are not tracked).
>
> I'll investigate the option to download a fresh image from the
> official repo (via a Python script, for instance, to ensure it's cross
> platform) and apply the changes via a script (much like the Level
> Playing Script :
> http://installer.pbworks.com/w/page/19997714/LevelPlayingField )
>
> Cheers,
> Sverin
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/GIRA/Physical-Etoys/commit/8da8f9922c35619efa74c54113e844264586c22d#commitcomment-789530
>