-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
luci.mk: include release in version number #7042
Conversation
WIthout having runtime tested it, it looks good to me so far. It will only change filenames for Makefiles that do declare PKG_REVISION, right? |
I've made the change to the luci.mk within the 23.05 SDK and it ran fine and produced IPK file with the desired filename. Yes, if |
I guess that @jow- meant that it shouldn't affect the bulk of packages that are not using PKG_VERSION at all and just rely on the automatic versioning. (REVISION was likely misspelling of VERSION, not RELEASE, I think...) The terminology in the PR is a bit confusing: the commit talks about "revision" but actually changes the handling of PKG_RELEASE. Please adjust. This whole issue concerns just a few packages... Makefiles using include luci.mk:
Normal Makefile:
Packages deviating from the default LuCI versioning:
|
Fixes issue mentioned in openwrt#7009 (comment) where the IPK filename doesn't contain release from the luci-app Makefile. Signed-off-by: Stan Grishin <stangri@melmac.ca>
Fixed in both commit message and PR.
Yes, like the previous code, it should only affect the version if the PKG_VERSION is set, otherwise it only uses PKG_SRC_VERSION.
That was the reason I was using the PKG_VERSION which also contained RELEASE in them in a few of the luci apps, now I can switch back to the same PKG_VERSION/PKG_RELEASE structure in luci apps as used in principal packages. |
Fixes issue mentioned in #7009 (comment) where the IPK filename doesn't contain release from the luci-app Makefile.