python-setuptools_scm
No description set
- Sources inherited from project devel:languages:python
- Devel package for openSUSE:Factory
-
26
derived packages
- Links to openSUSE:Factory / python-setuptools_scm
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:Maliku:python/python-setuptools_scm && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
no-generic-python.patch | 0000001142 1.12 KB | |
python-setuptools_scm.changes | 0000004925 4.81 KB | |
python-setuptools_scm.spec | 0000002303 2.25 KB | |
setuptools_scm-1.15.0.tar.gz | 0000023677 23.1 KB |
Revision 16 (latest revision is 87)
Jan Matejek (matejcik)
accepted
request 495767
from
Dominique Leuenberger (dimstar)
(revision 16)
For consideration - I know it is not optimal, if you find a better solution, please speak up. In essence, I'm trying to get rid of the (various) build cycles that accumulated in openSUSE:Factory (many hidden with the singlespec migration, something the bot seems not to have gotten correct) The issue here: if setuptools_scm requires git in the buildroot, then we get the cycle setuptools_scm -> git -> curl -> nghttp2 -> setuptools_scm git reqquires curl for the network access curl requires nghttp2 for http/2 access nghttp2 uses setuptools as build util. Gence, breaking at this very point seems to be the most beneficial - Do not buildrequire git: having git in the build root causes a build cycle over curl -> nghttp2 -> python-setuptoos_scm -> git. - Do not run the tests relying on git's presence.
Comments 0