toltec icon indicating copy to clipboard operation
toltec copied to clipboard

Handle building KOReader

Open Eeems opened this issue 3 years ago • 7 comments

We may need to push out EBFs specific to the reMarkable outside the normal KOReader release cycle. In order to do that, it would be good to have reproducible builds instead of relying on their binary releases.

Eeems avatar Sep 21 '20 18:09 Eeems

What is EBF?

matteodelabre avatar Sep 23 '20 22:09 matteodelabre

Emergency Bug Fix.

Eeems avatar Sep 23 '20 22:09 Eeems

Gotcha. Thanks!

matteodelabre avatar Sep 23 '20 22:09 matteodelabre

No problem, I sometimes forget what abbreviations people are aware of outside my industry.

Eeems avatar Sep 23 '20 22:09 Eeems

Do we need this anymore? Or are we fine with just patching the built files like we have already?

Eeems avatar Jan 17 '21 04:01 Eeems

I think building from source should still be a target, since having less intermediates is better for security IMO. But I agree that this is low priority currently.

matteodelabre avatar Jan 17 '21 19:01 matteodelabre

patching the frontend is fine (the lua files) for keeping us up to date with KOReader nightly or even forward from KOReader and should work the majority of the time. we've only had to once modify koreader-base (to tell KOReader not to lock the input devices) which required actual code compilation. in a case like that - we'd have to wait for the monthly release or switch to using nightly to get those improvements.

raisjn avatar Jan 17 '21 19:01 raisjn