Quote:
Originally Posted by madhatta
I'm sorry if it came across as insulting. It wasn't supposed to be, and I'd tried hard at my end to bend over backwards to make it clear how grateful I am for the existence of the plugin at all.
|
Well it was. As is this post, though maybe this time it would be better to say "condescending".
Quote:
|
But the model "get your OS from the OS people and your apps from the app people" is a Windows model of computer use, not a Linux model. Most people who use Linux stick fairly rigidly to the software that's distributed under the repository+indices+dependencies model because we know how many things start to break, and how balkanised and unsupportable our systems get, if we don't. This doesn't mean "only software distributed by the OS people", but it does mean "only software that's been built specifically for the environment provided by the version of the distro I'm choosing to run".
|
Great, I understand. But, there is a problem. Your distro version of calibre is broken. The plugin isn't broken. The plugin calls a calibre function and that didn't work. And the reason it didn't work is because the distro maintainers have broken it. They have decided to package a version of calibre that is built for Python 2.7 with Python 3.something. You shouldn't be surprised when it doesn't work properly. If anything, you should be surprised it works at all.
So great. I'll fix it. But, to fix it, I have to fix calibre and get it into your distro in a way that actually works. And still works in other distros and environments. And then I have to somehow get it out to your distro maintainers and then you have to do the update needed. Hopefully you aren't in a hurry to get the fix. And hopefully the distro maintainers don't break it in some other way.
Alternatively, I could change the plugin. That means I have to work out how to fix the problem that is happening on your specific distro and nowhere else. And it will mean adding code that is probably useless elsewhere. Code that as to be maintained. Code that has to be tested. Code that might break when your distro maintainers finally decide to package calibre properly. Do you really think that is a good idea?
For the rest of your post, I'll stand my statement that it is impossible to support all combinations of environments. It's impossible because no one has the resources or time to do it. We all have to choose where to spend what time and resources we have. I choose to make sure things work with the official calibre builds first. If I have time, and get decent reports, then I'll look at other environments, but, it won't be my priority. Especially if I know the official release will work in that environment.