Show Posts
1
General Discussions / Patching on Linux and Mac OS X made simpler
« on: April 25, 2012, 05:33:20 pm »
The patches you release require Wine (a Windows emulator) to be run on Linux or Mac OS X, and I don't have it installed on my Mac, so I decided to write a simple script without external dependencies.
The outcome is the xdelta UNIX patcher, a script for all UNIX-compliant system (Linux, Mac OS X, BSD, etc), whose source code can be found on GitHub: https://github.com/kappa7194/xdelta-unix-patcher
This script is completely stand-alone, the only external commands it uses are wget or curl to download the source code of xdelta, but almost UNIX system out there has at least one of them.
At the moment its usage is quite simple: ./patch.sh OLD_FILE PATCH_FILE [ NEW_FILE ], however it can be adapted to you current Linux script, with the file names hard-coded into the script.
If the system where the patcher is run does not have a native xdelta executable installed (as a Debian Linux system can) the current version of the script has a drawback: it will download and build xdelta for every patch, because the executable it builds is saved in the patch's folder.
However, if you're interested in using it, I can modify the script to run off pre-compiled executables distributed with the patch.
The outcome is the xdelta UNIX patcher, a script for all UNIX-compliant system (Linux, Mac OS X, BSD, etc), whose source code can be found on GitHub: https://github.com/kappa7194/xdelta-unix-patcher
This script is completely stand-alone, the only external commands it uses are wget or curl to download the source code of xdelta, but almost UNIX system out there has at least one of them.
At the moment its usage is quite simple: ./patch.sh OLD_FILE PATCH_FILE [ NEW_FILE ], however it can be adapted to you current Linux script, with the file names hard-coded into the script.
If the system where the patcher is run does not have a native xdelta executable installed (as a Debian Linux system can) the current version of the script has a drawback: it will download and build xdelta for every patch, because the executable it builds is saved in the patch's folder.
However, if you're interested in using it, I can modify the script to run off pre-compiled executables distributed with the patch.