Skip to content

Navigation Menu

Sign in
Sign up

Create package workflow #22

007revad started this conversation in General
Oct 14, 2025 · 1 comments · 1 reply
Discussion options

@PeterSuh-Q3
After unpacking your ScriptNotify Samplepackage-x86_64-1.0.0-7.2.spk and my ScriptNotify-x86_64-1.0.0-7.2.spk I see they have a lot of extra files in the scripts folder.

Instead of just these 4 files that in the synology/scripts:

postinst
postuninst
preinst
preuninst

there are also these extra files which I assume are added by the GitHub Action?

_presets.docker
_substitute
postinst.docker
postupgrade
postupgrade.docker
preuninst.docker
preupgrade
preupgrade.docker
start-stop-status
start-stop-status.docker
_elevate
_presets

But my real question is why are these 5 from my package different to yours?

_presets.docker
_substitute
postinst.docker
_elevate
_presets

Is it because your yml file used tomgrv/synology-package-builder@v2.1.0 and mine used tomgrv/synology-package-builder@v1.3.0 ?

You must be logged in to vote

Replies: 1 comment 1 reply

Comment options

That seems likely.

I also built both v1.3.0 and v2.1.0 separately,
and found that v2.1.0 had more lines of script improvements.

For more details, please contact @tomgrv directly.

I'll also rebuild my SynoSmartInfo package using v2.1.0.
Perhaps this will allow me to include the automatic update detection feature that @gioxx wanted.

You must be logged in to vote
1 reply
Comment options

In the meantime, I was playing around with a dedicated GitHub repo to see if GitHub Pages could somehow simulate an alternative source (like SynoCommunity & Co.) to allow automatic package updates. Everything seems OK, but when I go to add the additional source on DSM 7.3, it goes to a blank page.
On DSM 7.2, on the other hand, it correctly detects packages.json, but it doesn't read the details contained within it properly and therefore doesn't allow me to install/update your package automatically.

I hope to be able to spend a little more time researching the problem and - possibly - the solution without going through Docker containers and the like, I was hoping to be able to do everything in an easier way (precisely, via GitHub directly, the easiest thing to automate as much as possible).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /