Thread: Plugin Removal
View Single Post
Old 04-25-2015, 07:00 PM   #3
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,745
Karma: 30237526
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by DiapDealer View Post
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.
@DiapDealer - Why couldn't the PI removal framework invoke an 'uninstall_cleanup' method within the PI (assuming it exists). That would put the onus on the PI to know about its dross files rather than the framework itself. Obviously the PI developers would have to add the uninstall_cleanup method to relevant PI's - at their convenience.

I'm blissfully ignorant of calibres PI framework - so "BetterRed, that's not the way calibre PI's work, or that's hard to do in python, etc" are acceptable answers.

BR
BetterRed is offline   Reply With Quote