Hi Eli,
On Wed, 25 Dec 2019, Eli Schwartz wrote:
> Are we discussing calibre itself, here, or the plugins? It's been
> previously agreed that calibre itself is mostly ready.
Indeed, unfortunately all the fixes in the py3 branch are not merged
into a released tarball, and I am not eager to try to create orig
tarballs myself from the git repo (I looked into it, but it seems a lot
of stuff is needed in addition).
> The debian package maintainer doesn't have the power to fix arbitrary
> user-installed plugins, hence why the community of *users* and plugin
> creators is working on porting them.
Indeed, and that is great!
> The "shortcomings", then, are mainly about the almost complete lack of
> plugin support (as of today).
Yes, that is the current situation.
> That being said, given Debian deletes the plugin installer from the
> menu, I'm not sure why Debian cares if plugins work.
Huuu???? Maybe you are using something else, but **my** calibre has it:
Preferences -> Plugins ... I can (and do!) install plugins, both from
files as well as from the directory. And do updates.
You probably mean that piece of patch:
--- calibre-debian.git.orig/src/calibre/gui2/actions/preferences.py
+++ calibre-debian.git/src/calibre/gui2/actions/preferences.py
@@ -30,8 +30,6 @@ class PreferencesAction(InterfaceAction)
pm.addAction(QIcon(I('config.png')), _('Preferences'),
self.do_config)
cm('welcome wizard', _('Run Welcome &wizard'),
icon='wizard.png', triggered=self.gui.run_wizard)
- cm('plugin updater', _('Get plugins to enhance calibre'),
- icon='plugins/plugin_updater.png', triggered=self.get_plugins)
if not DEBUG:
pm.addSeparator()
ACtually I have no idea what it is undoing, because in my preference
dialog I see and can update plugins, and grepping for get_plugins there
are indeed several places where it is used.
So bottomline, yes, Debian users *can* and *do* use plugins.
> value in sticking with python2 for as long as possible, lest you receive
Yes, that is what I tried over the last half year to keep Calibre at Py2
despite the cleanup action happening in Debian.
> whim. And so I exercised my whim and uploaded a python3 build of
> calibre, so that my users can choose whether to install it for python2
> or python3. I'll most likely leave it that way until calibre releases
> python3 support from beta.
Well, this is more or less what I did, too: The version in
unstable/testing was Py2, and in experimental I uploaded a Py3 version
so those who wanted to get rid of Py2 could use it already.
Didn't get any feedback at all, though.
So yes, I am with Eli in most points (besides the plugin installer ;-),
it would be better to keep Calibre at Py2 for as long as possible, but
if the Debian algorithms go for autoremoval, I have no other chance than
switching to the Py3 version build from the released sources.
It would be nice if Kovid could provide tarballs for the 4.99.N series
of pre-releases, though.
All the best
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
