-
-
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
Update noarch build #6250
Update noarch build #6250
Conversation
- noarch packages should only be build for specific TCVERSION, otherwise REQUIRED_MIN_DSM is not evaluated - noarch packages must now define `override ARCH=noarch` instead of `override ARCH=` - add all noarch packages to build-matrix
I can provide you assistance but I probably won't be able to look at this before Sunday? Maybe @mreid-tt can help? |
I'll take a closer look later tonight and perhaps suggest a better fix than the workaround presented. EDIT: @hgy59, I've taken the liberty of adding a commit to this PR (hope you don't mind) which should resolve the issue you were trying to workaround. Have not done much testing on it. |
Some thoughts for improvement:
|
It's too bad that the |
I will have a look, and guess we can evaluate the min/max dsm requirements in the prepare script. EDIT: |
Alas the dependeny list generation can't be optimized for interactive package build because there are additional packages evaluated to build (python, ffmpeg, video-driver). But maybe we could speedup the dependency-list generation by parsing the Makefile(s) instead of using make. |
Would there be a way to detect that a 7.2 build is needed when min_dsm is set? i.e. jellyfin |
@hgy59, I love the direction of the last change. Would this check for DSM 7.2 be on a per-package basis? So for example if Jellyfin had an external dependency on a .NET package and that package had a minimum of DSM 7.1 would it evaluate both packages and build for DSM 7.1 and DSM 7.2? |
Yes, if any package requires dsm 7.2 (i.e. currently jellyfin only) all packages that are built are built for dsm 7.2 too.
|
@hgy59, looks like things built well and as expected. The only suggestion I would have is perhaps the naming of the variables. |
I am happy with |
@mreid-tt all noarch packages needs an update. I have to push the remaining. Since you have an open PR for OwnCloud #6225, you will get a merge conflict. I can omit the update of spk/owncloud/Makefile. This will break the build of owncloud on the master branch and you will have to adjust override ARCH in your PR after updating with upstream when this redesign is integrated. |
I can push an update to the ownCloud PR to change the override ARCH in the Makefile once this PR is merged and then do a rebase. The PR is just about done, just needed feedback from you guys on the proposed migration strategy. EDIT: Be sure to revert the Jellyfin test before merging this PR. |
@mreid-tt and @hgy59 i'm guessing changes are still on-going. My short PR here didn't kicked-off the build as expected #6253 actual build: https://github.com/SynoCommunity/spksrc/actions/runs/11194152942/job/31120397567 EDIT: Note that this PR is zero urgent and can be used to test-out github-action work as you see fit. |
This reverts commit ebe8946.
- introduced to have build log files for noarch packages
One way or the other, I don't mind much as i won't have cycles to work on things for a week or two. So I'm ok at waiting a little longer so build fixes gets in. |
This reverts commit 2cfc738.
- SPK_NAME must not use variable
all issues fixed, ready to merge. BTW the dependency-list optimization will come in a future PR. |
LGTM |
* Update ownCloud to v10.15.0 * Refine service setup scripts * Fix backup validation * Fix upgrade check * Optimise initial ownCloud setup * Use MySQL for initial setup * Set noarch build (#6250)
Description
redesign of noarch build.
override ARCH=noarch
instead ofoverride ARCH=
Replacement for #6249.
Contains a bugfix for #6247 that removed all arch specific builds in github build action.
Checklist
all-supported
completed successfullyType of change