View Single Post
Old 03-07-2021, 08:04 PM   #12
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,144
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by PeterT View Post
I think the issue that Jon is referring to is that many maintainers are adamant in sticking to certain versions of libraries that calibre uses, resulting in builds that are quite often crippled or broken in some subtle manner.

One issue I found yesterday on trying the flatpack version on my chromebook yesterday is that when I ran calibre in debug mode, I was told the log file was being written to /tmp/{some file name}, which did not exist.
Yes exactly. The problem is that you cannot always rely on the repository for the software to work or be the current version. Heck, a lot of people ended up with some Calibre 5 beta from their repository instead of the correct version. There were a number of posts on MR about this. So do you really want to rely on your repository when it most likely will not work?
JSWolf is offline   Reply With Quote