This repository tracks repository configuration files (like .gitignore), which is good practice.
Unfortunately, these .gitignore files are also part of the release tarballs (which have nothing to do with a git-repository, apart from accidentally being created from one).
This is kind of problematic, as downstream projects that might want to ignore completely different things will also inherit these .gitignore files.
E.g. for Debian (and Ubuntu, and ...), the source tarballs are imported verbatim into a packaging (git) repository. However, Debian does not do development of LibAAF (or whatever) since this is the job of the upstream developers, and is much more concerned about reproducible build processes and the like. As such we actually are interested to see all the build artifacts when doing a git status.
The solution is simple:
please exclude all repository configuration from the release tarballs.
This repository tracks repository configuration files (like
.gitignore), which is good practice.Unfortunately, these
.gitignorefiles are also part of the release tarballs (which have nothing to do with a git-repository, apart from accidentally being created from one).This is kind of problematic, as downstream projects that might want to ignore completely different things will also inherit these
.gitignorefiles.E.g. for Debian (and Ubuntu, and ...), the source tarballs are imported verbatim into a packaging (git) repository. However, Debian does not do development of LibAAF (or whatever) since this is the job of the upstream developers, and is much more concerned about reproducible build processes and the like. As such we actually are interested to see all the build artifacts when doing a
git status.The solution is simple: please exclude all repository configuration from the release tarballs.