You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Building of indico wheels from the release sources is not possible.
The reason is the multiple calls to 'git' in the build scripts, i.e. the build scripts assume the build happens always in a git repository.
Describe the solution you'd like
Be able to build indico wheels from the sources.
Describe alternatives you've considered
There are two solutions: either to update build scripts or to include .git repository into the release tarballs. The second seems to be an easier solution.
Best regards,
Andrii
The text was updated successfully, but these errors were encountered:
We do not provide sdist/release tarballs... those are repo snapshots github always shows for a release (and AFAIK that can't be disabled), they are not something that people should use.
The supported ways of building/installing releases are:
the pre-built wheels from PyPI - this is what we recommend anyone who doesn't need to make modifications
built from a git checkout (ideally using a release tag like v3.1.1, or the release's branch such as 3.1.x)
actually, the repo snapshots are fine apart from some minor tweaks that disable any calls to 'git' commands.
I will have a look if one can make any sense out of that.
Is your feature request related to a problem? Please describe.
Building of indico wheels from the release sources is not possible.
The reason is the multiple calls to 'git' in the build scripts, i.e. the build scripts assume the build happens always in a git repository.
Describe the solution you'd like
Be able to build indico wheels from the sources.
Describe alternatives you've considered
There are two solutions: either to update build scripts or to include .git repository into the release tarballs. The second seems to be an easier solution.
Best regards,
Andrii
The text was updated successfully, but these errors were encountered: