Just a thought - but why not build the tarball with sdist rather than rm -rf'ing the .git folder? Thanks, Kiall On 12/05/2012 11:40 AM, Alan Pevec wrote: > This is a simplified version of what our rpm build tools do: >> >> $ git clone git://github.com/openstack/**nova.git<http://github.com/openstack/nova.git> >> > Hmm, rpmbuild from git? > It works fine from a released tarball e.g. > $ wget https://launchpad.net/nova/**grizzly/grizzly-1/+download/** > nova-2013.1%7Eg1.tar.gz<https://launchpad.net/nova/grizzly/grizzly-1/+download/nova-2013.1%7Eg1.tar.gz> > $ tar zxf nova-2013.1~g1.tar.gz > $ cd nova-2013.1/ > $ sed -i "/setup_requires=\['**setuptools_git/d" setup.py > $ find build -name migrate.cfg > build/lib/nova/db/sqlalchemy/**migrate_repo/migrate.cfg > build/lib/nova/virt/baremetal/**db/sqlalchemy/migrate_repo/**migrate.cfg > $ grep migrate.cfg nova.egg-info/SOURCES.txt > nova/db/sqlalchemy/migrate_**repo/migrate.cfg > nova/virt/baremetal/db/**sqlalchemy/migrate_repo/**migrate.cfg > > > Yes, it works fine from the tarball because it's generated using setuptools_git and it contains the nova.egg-info with the full filelist. However, we want to have build projects that track the branches directly from git for development branches for example. -Ionuț ______________________________**_________________ OpenStack-dev mailing list OpenStack-dev at lists.openstack.**org <OpenStack-dev at lists.openstack.org> http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-dev<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121205/063dab6e/attachment.html>