search

pgaskin / NickelMenu

The easiest way to launch scripts, change settings, and run actions on Kobo e-readers.
https://pgaskin.net/NickelMenu
MIT License
591 stars 32 forks source link

Log the exact version at init #22

Closed NiLuJe closed 4 years ago

NiLuJe commented 4 years ago

Might come in handy one day, because I know quite a few people extremely averse to updating stuff ^^.

e.g.,

May 13 17:57:13 nickel: (NickelMenu) version: v0.0.3-2-g043dfb3 (src/init.c:24)
May 13 17:57:13 nickel: (NickelMenu) init: creating failsafe (src/init.c:25)
pgaskin commented 4 years ago

^ A note about branch deletion and squash/merge: I've settled on using squash commits and deleting branches for small changes which are tracked in a PR. For larger changes, I'll use rebasing unless a merge commit would be more suitable.

NiLuJe commented 4 years ago

:+1:

(You'll notice I've been reusing a "disposable" topical branch named "misc" for trivial stuff. I'll keep meatier features in named branches on my end).

NiLuJe commented 4 years ago

@geek1011: Complete sidebar: I'll be including NM in the KOReader/Plato OCP packages, unless you have an objection to that ;).

pgaskin commented 4 years ago

@NiLuJe: Sounds good. One question: how are you planning to deal with updates?

NiLuJe commented 4 years ago

I try to rebuild those ASAP on any new Plato/KOReader release, and/or any significant KFMon changes (i.e., it's actually always picking up a KFMon git build).

So, I'll just add NM to the list of stuff that might require a rebuild ;).

EDIT: In practice, that means either using the latest release via the GitHub API, or using a local build like for KFMon.

pgaskin commented 4 years ago

OK.

EDIT: In practice, that means either using the latest release via the GitHub API, or using a local build like for KFMon.

Note that you can link directly to the latest release with https://github.com/geek1011/NickelMenu/releases/latest/download/KoboRoot.tgz.