View Single Post
Old 10-13-2020, 12:27 AM   #5
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
I don't see any need for pkg_resources entry points, especially since calibre doesn't currently use setuptools or pkg_resources (though its dependencies might).

Furthermore, calibre is still not in site-packages (we would need to figure out a way to get upstream tinycss/odfpy to not be broken, and fork templite properly I suppose. css_selectors is custom code that could I suppose be turned into a generic library. polyglot can be phased out)

IMO it should be entirely sufficient to have calibre pick up plugins first, from e.g. /usr/share/calibre/plugins/

As for whether people would package plugins... I might update my current fanficfare CLI package to provide a calibre plugin too. Perhaps I'd package other plugins too, but not DeDRM software.
eschwartz is offline   Reply With Quote