Open Stack

On Tue, Dec 04 2012, Sascha Peilicke wrote:

> We are building RPM packages from release tarballs (such as [1]), which
> of course don't include the .git directory. Therefore the setuptools_git
> approach can't do its magic, thus our package builds get wrong results.
> Having OpenStack components rely on setuptools_git at build time means
> we have to distribute the whole git repository along with the source
> code tarball. Of course this makes no sense, since it would increase the
> size of release tarballs dramatically and won't get shipped in
> distributions anyway.Therefore, we (and potentially other distribution
> vendors) would have to track these files manually in our RPM spec files.
> Some reviews have already been opened on the topic (admittedly before we
> discovered the real issue). Given the different outcome of each review
> it seems that not everybody is aware that setuptools_git is used or of
> what it does.

FWIW, the Debian packaging team is hit by this problem too, and also
have problems with version computing which relies on git¹. They would
also been happy to see a solution to this problem.

¹  https://review.openstack.org/#/c/16547/

-- 
Julien Danjou
-- Free Software hacker & freelance
-- http://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121204/e358b857/attachment.pgp>