Thread: Plugin Removal
View Single Post
Old 04-25-2015, 06:18 PM   #2
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,643
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Calibre doesn't know all the pecifics about plugin configuration and/or support files. Only the plugin itself would know all the details necessary to remove itself entirely. I suppose it wouldn't be impossible to create a cleanup framework that calibre could run at plugin removal time, but it would still be entirely up to the plugin developer to provide a valid manifest for that cleanup routine. Sounds like a lot of work for something that couldn't really be enforced anyway.

Don't get me wrong, I'm not opposed to a cleanup option, I'm just not sure it could be accomplished short of calibre monitoring every run of every plugin to record any files that might get created by plugins.

Last edited by DiapDealer; 04-25-2015 at 06:38 PM.
DiapDealer is offline   Reply With Quote