MobileRead Forums - View Single Post

NiLuJe · 08-02-2020, 01:26 AM

Not really, no, that'd be a waste of an awful lot of storage space/bandwidth: new snapshots automatically replace the previous ones.

The sources are tracked in a VCS, but the build scripts aren't really designed to build a pinned revision.

TL;DR: No

.

----

MRPI being broken is only the tip of the iceberg, so even with a previous MRPI version, you probably don't want to be running the current revisions of almost everything, because the issue lies in a dependency used by quite a lot of stuff.

I do test them locally before pushing them, but due to an unfortunate series of different issues, I caught one issue with the original local test builds, then tested the fix in a manner that bypassed MRPI on Kindle, and double-checked on Kobo, where the issue is not as obvious, but a different one was, and that one required pushing new builds online to fix... and that in turn broke MRPI ;p.

08-02-2020, 01:26 AM	#855
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Not really, no, that'd be a waste of an awful lot of storage space/bandwidth: new snapshots automatically replace the previous ones. The sources are tracked in a VCS, but the build scripts aren't really designed to build a pinned revision. TL;DR: No . ---- MRPI being broken is only the tip of the iceberg, so even with a previous MRPI version, you probably don't want to be running the current revisions of almost everything, because the issue lies in a dependency used by quite a lot of stuff. I do test them locally before pushing them, but due to an unfortunate series of different issues, I caught one issue with the original local test builds, then tested the fix in a manner that bypassed MRPI on Kindle, and double-checked on Kobo, where the issue is not as obvious, but a different one was, and that one required pushing new builds online to fix... and that in turn broke MRPI ;p.