Re: HEADS UP: Slightly more robust Python Requires generated by RPM
On 31. 10. 21 19:21, Gordon Messmer wrote:
> (it doesn't even use git snapshot, but upstream release tarball).
In my opinion, calling it an "upstream release tarball" implies intent that is
not in evidence. GitHub's release tarballs are a side-effect of declaring a
release for a project that can't be disabled (last time I looked). For any
project whose release process is more complex than simply tarring up the git
repo (for example, any project that includes sub-modules in their intentional
release archive), GitHub's automatic archive isn't a suitable substitute for
the archive that developers intentionally publish.
I've made a mistake when mentioning "upstream release tarball" because
I've
mistaken it with another package (sqlalchemy). It is not relevant here.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok