During packaging I noticed that the release tarballs (from https://github.com/kensanata/bitlbee-mastodon/tags) seem to be just point-in-time snapshots of the git tree, and do not contain a configure binary.
Is this intentional? Running autotools during the build process is of course possible, but always a bit fraught as the build process might use a different autotools version than the source maintainer, leading to inconsistencies in the generated files.
During packaging I noticed that the release tarballs (from https://github.com/kensanata/bitlbee-mastodon/tags) seem to be just point-in-time snapshots of the git tree, and do not contain a
configurebinary. Is this intentional? Running autotools during the build process is of course possible, but always a bit fraught as the build process might use a different autotools version than the source maintainer, leading to inconsistencies in the generated files.