Hi, Cayetano Santos <[email protected]> writes:
> I see, but I still don’t see the benefit of tarballs over git repos > (except when the tarball includes something else), as this adds an extra > layer of complexity. In this case, for example, this added complexity > fails to disarchive mupdf, as in several other packages. This is > acceptable when tarballs provide a benefit, but otherwise ? I agree: in cases where tarballs don’t provide any benefit, better use ‘git-fetch’. Now, the “benefits” we’re talking about are primarily pre-built files embedded in the tarball and missing from the Git repo. The prime example is Autotools-generated tarballs, which contain generated code (./configure, Makefile.in, etc.). The long-term goal is to get rid of all this generated code. Currently there are many packages that we just cannot built without this (GCC, glibc, Binutils, to name the most obvious examples), but the live-bootstrap project is showing the way to address that. Ludo’.
