en:developer:release_kits
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:developer:release_kits [2018/03/26 23:12] – [**create-installer**] kjdon | en:developer:release_kits [2023/03/13 01:46] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | |||
+ | |||
======Release Kits ====== | ======Release Kits ====== | ||
The Greenstone release kits automate the task of creating a releases of Greenstone2, | The Greenstone release kits automate the task of creating a releases of Greenstone2, | ||
Line 195: | Line 198: | ||
This target wraps the executable jar installer in a native linux executable, and puts it in a directory called // | This target wraps the executable jar installer in a native linux executable, and puts it in a directory called // | ||
+ | ====Differences between linux release kit and other release kits==== | ||
+ | ===Wrapped executable with bundled java installer === | ||
+ | The java installer for linux from the sun website is a self extracting executable - it does not have a gui installer interview process. Therefore, it was convenient to just create a regular tar with the same contents and ship that with the executable with bundled java. It is extracted into the temp directory on the user's machine when they execute the installer executable, whether java is found on their machine or not. Then, the installer jar is launched (using their java if they have it, otherwise the one in the temp directory). When the user hits ' |
en/developer/release_kits.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1