View Single Post
Old 06-28-2022, 05:47 AM   #22
sherman
Guru
sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.sherman ought to be getting tired of karma fortunes by now.
 
Posts: 867
Karma: 2676800
Join Date: Aug 2008
Location: Taranaki - NZ
Device: Kobo Aura H2O, Kobo Forma
Quote:
Originally Posted by Deobulakenyo View Post
Thank you, sherman and xyclonei.

The problem is my ignorance. Thanks for all the help


BUT can you explain to me what and how the latest changes should be used? on my end, what I understand is that the github release page is still the original (initial one) nickelclock.

Are the changes supposed to be integrated (don't know if this is the proper term) to a new installer?

I do not understand what the build. artifact build means. Looking at the release pages, it is still v. 0.1.0 and was uploaded 13 hours ago.

BTW your (xyclonei) upload a few posts back work fine.
So, every time I push a change, a new KoboRoot.tgz is generated automatically, and these can be downloaded as an artifact (inside a NickelClock.zip file). These are used to test changes, and provided as a convenience so others do not have to compile the changes themselves. Artifacts are not intended for the general user. Consider them test builds.

When I am happy with the changes, I will make a new release, with an updated version (next will be 0.2.0), which will be available on the releases page.

Apologies for the confusion this caused.
sherman is offline   Reply With Quote