[RFC] Policy for PKG_RELEASE bumps

[Adrian Schmutzler]

Hi,

> Looking at other distros (Debian [1], Fedora [2]), it appears to be common to
> reset the equivalent of PGK_RELEASE for every upstream version bump. In
> OpenWrt it appears to mean [3] "our version since the dawn of times"
> instead of "our version of this upstream release".

that's a misunderstanding.

PKG_RELEASE _is_ (/should be) reset for every upstream version bump, i.e. when PKG_VERSION or PKG_SOURCE_DATE are changed.
However, in that ref [3] I removed PKG_VERSION for those cases where _there is no upstream_, i.e. no PKG_SOURCE_URL was set.
The past has shown that "inventing" an upstream version where there is none is rather detrimental, as nobody will know which variable to bump.
So, in this case, and this case only, I removed the PKG_VERSION.

Best

Adrian 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20200810/155264ed/attachment.sig>