Currently the rpmbuild.sh script is producing tarballs by just using git archive, which means the tarballs include everything committed to
git. But our release tarballs are created by python setup.py sdist
which uses different rules to decide what to include.
To keep things consistent, we should use python setup.py sdist for the
development builds too. This will help catch missing entries in
MANIFEST.in, for example #33.
Currently the rpmbuild.sh script is producing tarballs by just using
git archive, which means the tarballs include everything committed togit. But our release tarballs are created by
python setup.py sdistwhich uses different rules to decide what to include.
To keep things consistent, we should use
python setup.py sdistfor thedevelopment builds too. This will help catch missing entries in
MANIFEST.in, for example #33.