GIT version size

Could someone explain why Xonotic from git is almost 10 times larger then stable releases? I know that there are many other things that are required for build but they don't use so much space. The most of space is taken by pure data which is models, and textures. Is it the matter of compression or there are simply files that are merged together in original release?

I don't have much disk space and I am wondering what do I need for maps creation. Do I this large data directory from git or the .zip'ed one is enough?

How did you measure the git's size? If you looked at the total size of the entire xonotic directory, you have to roughly divide this by two because git hosts the entire history of the project in its directories, and that includes a copy of the files that sit outside of git's own directories. So, my xonotic dir is 11GB, excluding the git directories brings that down to 6.1GB.

There's a huge gain from converting textures from .tga to .jpeg and/or .dds. Apparently, tga files alone total to 4.3GB of space.

I don't know if nexcompat is part of the release, but that's worth 500MB as well.

Here's some stats on filetypes on all default git directories in .xonotic (plus mediasource, hence the .rar files are project files in mediasource for example)

Code:

.tga 4393.3M .zip 245.5M .rar 201.9M .wav 196.7M .pk3 148.6M .ogg 132.2M .psd 118.7M .jpg 95.2M .png 63.9M .7z 49.1M .blend 48.4M .map 38.3M .md3 35.7M .ttf 32.0M .iqm 30.5M .dll 26.8M .ase 25.0M .xcf 18.3M .dpm 15.7M .max 14.1M .dylib 13.1M

Without mediasource:

Code:

.tga 4377.0M .wav 191.7M .ogg 132.2M .pk3 113.2M .jpg 94.8M .png 46.7M .map 38.3M .md3 35.7M .ttf 32.0M .iqm 30.5M .dll 26.8M .ase 25.0M .dpm 15.7M .dylib 13.1M

Edit: for the record, I grabbed this awk script from stackexchange and modified it a bit. Dirty stuff ahead:
find . \( -name '.git' -o -path './data.old' -o -path './mediasource' \) -prune -o -type f -printf "%f %s\n" | awk '{sub(/.*\./,"",$1);count[$1]+=$2} END{for (var in count) print "."var"\t" sprintf("%.1fM",count[var]/1024/1024);}' | sort -t$'\t' -k 2 -h -r


EDIT2: You don't need git for map creation. And in git, I'm guessing netradiant doesn't need anything outside of the map repo. Downloading that alone takes 5 GB of disk space in total.

The git version has 11 GB, while the 0.6 stable zip, has less than 1 GB. Is the compression of zip so high that it's 5 GB after unpacking or I have missed something?

I said above that tga files take up 4.3GB of the 6GB in xonotic data. Those tga files are converted to jpeg (quality 97 for rgb, 99 for alpha) for releases, I think that's where most of the volume gets slashed.

Ok. So I need tga files, for textures. Thanks.

No, you don't need these. All the resources necessary for mapping should be in the 0.6 release and the netradiant package. If you want to use resources from a git clone, I think you only need to clone the map repository. You don't need tga files for mapping, jpeg files are fine too. All I'm saying is that the size difference from git to releas is not due to missing files, but to better compression of textures.

Yo man. Tga keeps everything legit. Jpg and dds (worse!) puts in artifacts my man. If you don't like git, don't run with the gazells. Feast with the bison.

Slow lane bro!

@maxyan
Xonotic-latest-mappingsupport.zip and Xonotic-latest.zip from http://beta.xonotic.org/autobuild/ should be enough for mapping.

@ RuckaRuckaAli
Amusing but irrelevant mapping just use images, it does not re-use them. thus lossy or not don't matter (aside from teh dds case that simply does not work as not netradiant or q3map2 knows how to read those)