-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
tc.mk: Force two (2x) digits for version #4219
Conversation
|
Please remove TC_FIRMWARE DSM 6 development guide:
|
After deleting TC_FIRMWARE the INFO file generation can be adjusted for backward compatibility like this (pseudo code)
|
Thnx! It's exactly what I was wondering about yesterday when I left the PR for review. I'll make the necessary adjustments. |
Have a look at the code I've pushed (untested yet)... There is still this part which confuses me and that I believe it may not be needed anymore or algo needs to be revisited:
|
@publicarray , @ymartin59 and @hgy59 I've reviewed the code and currently testing. I've reworked the A quick run provided the following over
Versus the same run on
Versus the same run on
|
@th0ma7 Just want to say thank you and good work on cleaning up the Makefiles with the recent PRs. Excellent work 👍 I haven't been following the toolchains much. Why are geminilake-6.2 and purley-6.2 removed here? |
Reason is simple: This was to "fake" a 6.2 build for theses two arches as none of them ever existed as "6.2" DSM version and where never published online. But, with the current versioning fix you can now build a 6.2.2 or 6.2.3 package and final version will be showed as 6.2-BUILD# which will vary depending of its origin. And the best of that is that it follows Synology's guidelines (thnx to @hgy59 and @ymartin59 for pointers on this). |
I think we can remove
|
@th0ma7 Thanks that explains it :) |
Sorry one more I'd like to have addresed: (let me know if a sperate PR is preferred and I can make one)
|
Sorry to ask @hgy59 @ymartin59 @publicarray but re-requesting review after this other round of testing after new changes...
|
@@ -84,7 +84,6 @@ $(WORK_DIR)/INFO: | |||
$(create_target_dir) | |||
@$(MSG) "Creating INFO file for $(SPK_NAME)" | |||
@echo package=\"$(SPK_NAME)\" > $@ | |||
@echo thirdparty=\"yes\" >> $@ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm just wondering do we support older DSM versions, like really old 3.x or even 4.x where this could still be used?
If not I'm very happy removing it completely
Thanks for the quick updates @th0ma7 👌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't believe we will ever be releasing any DSM 3.x or 4.x spk ever. That's why I removed it entirely, further more as we lost all old packages during the web server migration. Presumably similar hooks will disappear for DSM5 once DSM7 comes in.
@th0ma7 Do I understand there is no longer need to extend spkrepo to support minor version numbering "a.b.c"? |
That's my expectation. To be confirmed with the new set of |
* tc.mk: Force two (2x) digits for version * spk.mk: Remove TC_FIRMWARE variable and force firmware for < 6.1 * common.mk: Use latest for apollolake, geminilake and purley * spk.mk: Use @publicarray proposal to manage <=6.1 DSM version * spksrc.spk.mk: remove thirdparty as not used in DSM 5.0 or newer * spksrc.spk.mk: startable is deprecatade > DSM-6.1, use ctl_stop
Motivation: Relates to recent PR #4200 where @hgy59 noticed that the version number must be always two (2x) digits.
Linked issues: N/A
Checklist
all-supported
completed successfullyAddition to current PR
geminilake-6.2
andpureley-6.2
as now superseeded with this fix using 6.2.2 & 6.2.3 toolchainsstartable
flag for DSM-6.1+ versionsfirmware
flag for DSM-6.1+ versionsthirdparty
flag as deprecated since DSM-5.0