View Single Post
Old 04-09-2022, 07:14 PM   #7
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
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
The JB hotfix has a weird history, that means it was never really supposed to see such a wide audience, which means it's not deployed as carefully as the other packages.

The TL;DR being that it's built from the 5.4.x JB tree, so when I said the main JB package, I meant that one (the one tagged "K5 JB" in the snapshots listing).

The actual source tree is public, but it's an old SVN repo with a complex layout, so you're better off looking at the actual package, as it's complete and already laid out properly, unlike the repo . This should be self-evident once you take an actual look at the build scripts, because they're all there, and they're responsible for piecing it all together.

(You might be encountering links to the Trac instance instead of the repo. The Trac instance is down because Python 3 shenanigans and lack of time to deal with it. The SVN repo is up, though).

Last edited by NiLuJe; 04-09-2022 at 07:22 PM.
NiLuJe is offline   Reply With Quote