Hello, Yes I have seen this script already, but that would require for me to write out a script to install the package which is a little annoying to do so, this is something I plan to do when I remove the annoying proprietary Java service wrapper in onedev-oss package I have been working on (not yet pushed to the aur). I might merge -oss into the main onedev package later on if benqcooper agrees it is worth it. I have discussed how the entrypoint.sh script works with the OneDev developer already, it requires both the new binary and the old binary to patch, thus is not much different to using the JSW, just the JSW is distributed with the binaries. Thus I would rather save this for later when I work on the -oss version than worry about this now. Is there any way to reference files within the package from pre_upgrade hook? If not I might install onedev to a new location and then just patch it in the post_upgrade hook, and then delete the files after patching xD of course that would be very unconventional but it is how the codebase was written to function, even doing it the same way as it has been done for docker, the developers docker contains contain both the new update and the old version, and they patch the old with the new. Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev