[RFC] Policy for PKG_RELEASE bumps

Paul Spooren mail at aparcar.org
Tue Aug 18 05:10:44 EDT 2020


On 17.08.20 20:55, Florian Eckert wrote:
> Hi team,
>
>> * When anything inside the packages ipk file changes
>>     Includes patch and so called "cosmetic" changes outside the
>> Makefile, e.g. replace tabs with spaces.
>
>
> PKG_VERSION:
> This is the upstream version of the Project and this is the upstream 
> version we build.
>
> PKG_RELEASE:
> This is the change we are making on the part of OpenWrt and should be 
> counted up with every change.
> No matter what is changed.
> It is not the same package anymore.
> And if we change the PKG_VERSION and use a new upstream version, the 
> PKG_RELEASE number will be set to 1.
>
ACK

> I've always done it this way until now?
>
> This would avoid the tedious asking `Can you please bump the 
> PKG_RELEASE number?`
> The advantage is if there is a policy and everybody knows the workflow.
>
> Now I don't know whether to count it up or not.
> Also you can not estimate if it is a big or small change.
> See my P/R [1] to add tabs to rc.common help output.
>
It's binary, if the package checksum changes, it's a PKG_RELEASE bump.
>
> Best regards
>
Paul
>
> [1] https://github.com/openwrt/openwrt/pull/3246



More information about the openwrt-devel mailing list