Hi,
there is a slight inconsistency in packaging compared to other nextcloud-release packages, adding overhead to build management and version tracking, which in reality means I will just lose track of the app until something breaks, instead of having our build system notify me about application updates.
Most applications in nextcloud-release, such as calendar, contacts, deck, forms, impersonate, notify_push, twofactor_nextcloud_notification use the following scheme for downloads:
${APPNAME}-v${VERSION}.tar.gz
where version is the actual version string.
This means one would expect twofactor_admin version 4.5.0 to be available under
https://github.com/nextcloud-releases/twofactor_admin/releases/download/v4.5.0/twofactor_admin-v4.5.0.tar.gz
but it is actually available under:
https://github.com/nextcloud-releases/twofactor_admin/releases/download/v4.5.0/twofactor_admin.tar.gz
It would be nice if this could be fixed.
If backward compability is needed, one can probably just provide the archive under both URLs.
Hi,
there is a slight inconsistency in packaging compared to other nextcloud-release packages, adding overhead to build management and version tracking, which in reality means I will just lose track of the app until something breaks, instead of having our build system notify me about application updates.
Most applications in nextcloud-release, such as calendar, contacts, deck, forms, impersonate, notify_push, twofactor_nextcloud_notification use the following scheme for downloads:
${APPNAME}-v${VERSION}.tar.gzwhere version is the actual version string.
This means one would expect twofactor_admin version 4.5.0 to be available under
https://github.com/nextcloud-releases/twofactor_admin/releases/download/v4.5.0/twofactor_admin-v4.5.0.tar.gz
but it is actually available under:
https://github.com/nextcloud-releases/twofactor_admin/releases/download/v4.5.0/twofactor_admin.tar.gz
It would be nice if this could be fixed.
If backward compability is needed, one can probably just provide the archive under both URLs.