Learn more about these different git repos.
Other Git URLs
Please allow direct download of project code in archive form for releases, versions and tags, so pagure-hosted projects can be easily packaged in Fedora using %forgemeta like with GitHub or GitLab, as requested by Matthew Miller here: https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/XJQG5V7SVTMDFNIQNJ2W5UM4C6JCWDWU/
See also: - https://fedoraproject.org/wiki/Forge-hosted_projects_packaging_automation - https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/thread/5K4CED5IBVTS567QJEYGUWLPBFYONDLN/ - https://pagure.io/packaging-committee/issue/719 - https://bugzilla.redhat.com/show_bug.cgi?id=1523779
Ideally: - archives are compressed with tar.xz - archives contain a topdir matching their name - archives do not contain .git and other git-specific metadata - the archive modification time matches the corresponding commit time - archive urls end with /archivename.tar.xz to make rpm happy - release archives are named project-release (and project is the same as in https://pagure.io/project/) - tag archives are named project-tag - commit archives are named project-commit
Releases can already be found at: https://releases.pagure.org/pagure/
For the feature to create tarball on demand from a commit or a tag, it's already being tracked in: https://pagure.io/pagure/issue/861
So I'm going to close this as duplicate :)
Thanks for filling it though, always appreciated!
Metadata Update from @pingou: - Issue close_status updated to: Duplicate
Pagure already allows manual release uploading but tagging a commit as a release commit should be sufficient to generate the corresponding release archive automatically without manual upload (as on GitLab)
Login to comment on this ticket.