i2p.firefox/i2pversion

#! /usr/bin/env sh

JNA_VERSION=5.11.0
export JNA_VERSION=5.11.0
I2PFIREFOX_VERSION=0.0.26
export I2PFIREFOX_VERSION=0.0.26
# Comment this out to build from an alternate branch or
# the tip of the master branch.
VERSIONMAJOR=1
VERSIONMINOR=9
VERSIONBUILD=4
I2P_VERSION="$VERSIONMAJOR.$VERSIONMINOR.$VERSIONBUILD"
export I2P_VERSION="$VERSIONMAJOR.$VERSIONMINOR.$VERSIONBUILD"
VERSION=i2p-jpackage-1.9.4
export VERSION=i2p-jpackage-1.9.4
Make sure the build script enforces the use of a tagged, released version 2021-05-22 22:23:03 -04:00			`#! /usr/bin/env sh`

bump the version, use an updated JNA_VERSION 2022-05-17 15:12:39 -04:00			`JNA_VERSION=5.11.0`
use jsign 2022-05-17 16:12:43 -04:00			`export JNA_VERSION=5.11.0`
bump launcher lib again 2022-09-05 10:23:17 -04:00			`I2PFIREFOX_VERSION=0.0.26`
			`export I2PFIREFOX_VERSION=0.0.26`
re-add self-run of I2P.exe to save users a click, this needs testing but since I've got 3 VM's and 3 laptops on my desk right now I'm going to do it right now 2022-09-05 14:12:00 -04:00			`# Comment this out to build from an alternate branch or`
I think that might be a working UpdatePostProcessor, now to figure out how to register it 2021-07-01 18:20:16 -04:00			`# the tip of the master branch.`
i2pversion or i2pversion_overrides automatically sets version no matter what 2022-05-18 18:17:26 -04:00			`VERSIONMAJOR=1`
bump version 2022-08-28 13:58:32 -04:00			`VERSIONMINOR=9`
bump again 2022-09-05 14:19:35 -04:00			`VERSIONBUILD=4`
i2pversion or i2pversion_overrides automatically sets version no matter what 2022-05-18 18:17:26 -04:00			`I2P_VERSION="$VERSIONMAJOR.$VERSIONMINOR.$VERSIONBUILD"`
			`export I2P_VERSION="$VERSIONMAJOR.$VERSIONMINOR.$VERSIONBUILD"`
update version 2022-09-06 15:45:53 -04:00			`VERSION=i2p-jpackage-1.9.4`
			`export VERSION=i2p-jpackage-1.9.4`