[PATCH 19.07 4/4] treewide: mark selected packages nonshared

[Adrian Schmutzler]

> -----Original Message-----
> From: Giovanni Giacobbi [mailto:giovanni at giacobbi.net]
> Sent: Freitag, 9. Juli 2021 09:37
> To: Adrian Schmutzler <mail at adrianschmutzler.de>; 'Paul Spooren'
> <mail at aparcar.org>; 'Petr Štetiar' <ynezz at true.cz>; openwrt-
> devel at lists.openwrt.org
> Cc: 'Hannu Nyman' <hannu.nyman at iki.fi>
> Subject: Re: [PATCH 19.07 4/4] treewide: mark selected packages nonshared
> 
> On 04/07/2021 14:46, Adrian Schmutzler wrote:
> >>>    PKG_NAME:=json-c
> >>>    PKG_VERSION:=0.12.1
> >>> -PKG_RELEASE:=3.1
> >>> +PKG_RELEASE:=3.2
> >> I've never seen a non integer release, is there a special reason for this?
> > I've also used this as standard scheme for changes in stable branches. The
> advantage is that you immediately see up to which version the changes are
> shared with master, and when it starts to deviate.
> 
> What would you do then if the upstream version is bumped, but the
> patchset/Makefile would still differ between the master and branch? In this

I'd have to think about that.

But changing PKG_VERSION or PKG_SOURCE_DATE is rare in release branches. 

Best

Adrian

> case, you bump PKG_VERSION to 0.12.2, but if you restart the PKG_RELEASE
> from 1 for both the branch and the master you end up with two different
> "0.12.2-1" packages in let's say 21.02 and 19.07.
> 
-------------- 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/20210709/3a049cb3/attachment.sig>