From fd712293b4b51f21324bcc5a8ea4aa3cc9352e19 Mon Sep 17 00:00:00 2001 From: idk Date: Sun, 19 Mar 2023 16:26:26 +0000 Subject: [PATCH] update I2P version --- docs/UPDATES.md | 38 +++++++++++++++------------------ i2pversion | 4 ++-- src/nsis/i2pbrowser-version.nsi | 2 +- 3 files changed, 20 insertions(+), 24 deletions(-) diff --git a/docs/UPDATES.md b/docs/UPDATES.md index 6f5b842..c2d6e79 100644 --- a/docs/UPDATES.md +++ b/docs/UPDATES.md @@ -2,28 +2,24 @@ Setting up an Update Server for an I2P Bundle ============================================= It is important to set up a signed update server so that people are able to -safely and anonymously update your I2P bundle. +safely and anonymously update your I2P bundle. There are two sort of "Levels" +to what you might do to provide updates to your users. Each of them requires the +generation of a [signed newsfeed](https://eyedeekay.github.io/Hopefully-Holistic-Guide-to-I2P-Dev-Build-Update-Hosting/), +which also serves as a way to provide information to your users about updates, +features, and security events. -The quick way: --------------- +This project, `i2p.firefox` a.k.a. the "I2P Easy Install Bundle" uses the "Executable" +update subtype, meaning that it capable of installing itself by executing code as the +user who runs the update, which is usually the main user of a Windows 10 or 11 PC. +This update subtype is highly flexible, but requires the creation of a "Scripted" using +something like `NSIS`, `wixl`, or custom code. Other update types include ZIP (used by +the core I2P product) and DMG(used by Mac OSX). -This process depends on my ability to push releases to github. If you are -forking, setting up a dev server, or taking over because I got hit by a bus, -you'll need to do it the complete way. +Static HTTP Update URL over I2P +=============================== -For as long as I am building updates, you will be able to mirror the jpackaged -Windows bundle by cloning the repository `https://github.com/eyedeekay/i2p` and -running the `make docker run` target in that repository. You can retrieve the -base32 address of your update server by viewing the log with -`docker logs eephttpd-jpackage | grep b32.i2p | tee eephttpd-address.md`. To -update the site, run `./update.site.sh` in that repository. +Bittorrent Update URL over I2P +============================== -Once you have cloned the repository and started the container with -`make docker run`, you can simply add `path/to/repo/update-site.sh` to your -`crontab` and it will update at an interval of your choosing. - -The complete way: ------------------ - -TODO: describe how to do it with less of the awesome fancy stuff I put together -to make it easier on myself to keep an update server going. \ No newline at end of file +[If you choose to do this, consider using zzzot to host your open tracker instead of a normal site](https://github.com/i2p/i2p.plugins.zzzot), +which you can obtain from [this I2P link](http://stats.i2p/i2p/plugins/zzzot.su3). \ No newline at end of file diff --git a/i2pversion b/i2pversion index 7a77dd6..0a44aa5 100644 --- a/i2pversion +++ b/i2pversion @@ -11,5 +11,5 @@ VERSIONMINOR=1 VERSIONBUILD=0 I2P_VERSION="$VERSIONMAJOR.$VERSIONMINOR.$VERSIONBUILD" export I2P_VERSION="$VERSIONMAJOR.$VERSIONMINOR.$VERSIONBUILD" -VERSION=i2p-2.1.0 -export VERSION=i2p-2.1.0 \ No newline at end of file +VERSION=i2p-2.2.0 +export VERSION=i2p-2.2.0 \ No newline at end of file diff --git a/src/nsis/i2pbrowser-version.nsi b/src/nsis/i2pbrowser-version.nsi index 6e2d3ce..a763e71 100644 --- a/src/nsis/i2pbrowser-version.nsi +++ b/src/nsis/i2pbrowser-version.nsi @@ -1,3 +1,3 @@ !define VERSIONMAJOR 2 -!define VERSIONMINOR 1 +!define VERSIONMINOR 2 !define VERSIONBUILD 0