electron-userland
How to disable auto-update for RPM and DEB?
Hey all,
I'd like to disable auto-update for RPM and DEB builds, and rely on my own purpose built apt/yum repos.
Is there an easy way to do this using the electron-builder config file?
Currently I'm doing a check at runtime, but I'd way prefer to disable it at build time if possible.
Thanks for any help!
The assets are automatically generated, any it should be possible to deactivate it in a few manners, but there's no config property for it specifically.
Easiest route, use afterPack hook and just delete the app-update.yml from linux-unpacked/resources directory.
How are you doing it at runtime? (Purely curious)
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Adding auto-update files for deb is a beta feature, it says so in the logs. How come a beta feature has been activated by default with no discernable way to deactivate it ?
The afterPack route will not work as the app-update.yml file is added AFTER afterPack is executed.
We have had to resort to getting apt to delete the file in Linux_x86_64/package/post-install.sh
Adding auto-update files for deb is a beta feature, it says so in the logs. How come a beta feature has been activated by default with no discernable way to deactivate it ?
I second that ; It add a lot of time - for nothing - to the CI pipelines, for all builds!
It add a lot of time - for nothing - to the CI pipelines, for all builds!
This is almost certainly incorrect and likely is confusing with another portion of the build process. The "Adding auto-update file" step for rom/deb/fpm is literally writing a 1-line text file in resources dir.
Anyhow, I'm updating the config logic to allow cascading overrides of publish (e.g. deb.publish should override linux.publish which can override root .publish). Set it null for a specific target, and no auto-update file will be configured for it.