View Single Post
Old 08-17-2020, 12:01 PM   #11
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
@bru888: Firstly, while you claim to be a newbie, your post makes that statement questionable. You knew enough to wonder if the frequency of updates to the firmware would be an issue to the owner of calibre. That really suggests that you have seen that prompt a few times. Add that you know what the KoboTouchExtended driver is and have patched the firmware, that suggests that you have been around here a while, just never bothered to actually join and post.

Overall, to me at least, your request is very strange. Why on earth do you want calibre updated one last time? Why would you want the updates stopped? If what you think is that because the update has not been rolled out yet, that it won't be, then you are over-thinking things. Calibre usually gets updated every two weeks. That means that how soon after a firmware release the calibre support is received is really just a factor of timing. Unfortunately, for some reason there was no release last week. I haven't bothered to ask why as skipping a week isn't that uncommon. But, the emphasis at the moment is preparing for calibre v5 and there weren't that many changes in the main branch. Just one annoying one for us Kobo users.

And for the record, I have been maintaining the KoboTouch driver in calibre for a few years now. I have no intention of stopping that any time soon. I started doing this because the previous maintainer had moved to other things, and I wanted some changes (yes, purely selfish reasons). If I do have to stop for some reason, I think there are several people now who would be able to take over.

For calibre status, @PeterT has suggested a sticky. Honestly, I don't know if it would work any better than what is done now. Every time there is a new firmware release, there is a thread started to discuss it. I always make a post about the calibre status as soon as possible after the firmware is released. I am involved in the beta firmware group, and will have already prepared and tested the changes. Any apparent delay in my post is usually relate to timezones. Kobo likes to release the firmware when I am sleeping.

This has been happening for several years. Anyone who has been here for any time at all should have seen them. Anyone turning up new when there is a new firmware release, should be able to see the new release thread. I keep thinking that people would look there for the calibre status as well. But, it doesn't seem to happen, so I have no real belief that a sticky would help. I suppose it would give a place for people to point when a question like this is asked.

I have also thought of updating the warning message that calibre displays. Maybe add a statement to look in this forum for discussion of the firmware. But, it is already long and the evidence is that no one bothers to read it. Or panics even more when they do. If someone can come up with a clearer statement to replace the current one, I would be very happy.

I am not going to remove the warning. It is a matter of safety. There have been a few changes that would have caused problems, but, not for a long while. Luckily, Kobo keeps the database updates to a minimum and compatible across most releases. Most changes mean there is something we can take advantage of, but, do not change the current function.
davidfor is offline   Reply With Quote