Today we (again) ran into the quota roof at TuxFamily cause the distribution packages keep growing. Manuel has solved this by asking nicely to get the quota increased, but that's a temporary solution really.
I'm thinking to rewrite some of the nightly linux builds and break out the data section. Instead I'm thinking to include a postinst script in the deb file that automatically downloads the data from SVN. However, this kind of breaks the way deb files usually function, so I'd like some comments on it.
The logic would be:
* Deb files includes everything except data (data being targets, textures, meshes etc)
* Deb file gets a hard dependency on "subversion"
* At postinstall it checks if /usr/share/makehuman/data/.svn exists
* If it does it cd:s to the install directory and does a SVN update
* Else it checks out the data directory from google code
Upside is
a) distribution binary shrinks by up to 90%
b) network load on tuxfamily decreases
c) users only download what they need
d) more or less transparent to users
Downsides
a) Deb files usually don't work this way, so it might be considered a bit ugly
b) First time installation will be significantly longer
c) network connection is required in order to install (although it'd be pretty difficult to get the nightly without it in the first place)
So... comments?