Hi,
I have another idea that might simplify the mess of dealing with
PKG_RELEASE handling.
1. we use AUTORELEASE for all packages in master
2. when creating a release branch, all PKG_RELEASE lines are changed to
something like 22.03-1
3. we write a script that can automatically edit a series of local
commits and for each commit:
- figures out affected packages
- edits each affected makefile to bump PKG_RELEASE
- adds a Updated-Packages: <...> tag to indicate which packages it
has changed (or 'none' if no packages were affected)
4. we ask people submitting patches via email or PR to not update
PKG_RELEASE themselves anymore
5. we make the server side enforce the presence of the
"Updated-Packages" tag for release branches and packages, just like
Signed-off-by.
That way, dealing with PKG_RELEASE becomes a matter of simply running
one command before doing git push.
What do you think?
- Felix
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
