Quote:
Originally Posted by BobC
I see there is a zero byte __init__.py in the conversion folder but perhaps that is normal.
|
That's normal, Python needs an __init__.py file in a folder to tell it to treat the folder as part of a package. Doesn't matter if the file is empty, there just needs to be a file with that name. The only special __init__.py is the one at the top level of the plugin, that tells calibre what class to load as the plugin class.
Quote:
Originally Posted by BobC
A naive question from someone who doesn't really understand Git and similar but does the SQL stay in the repo in case you need to roll-back to a previous version ?
|
It stays in the previous versions. If you go to the repository (
https://github.com/jgoguen/calibre-kobo-driver/) you'll see above the list of files a drop-down that says "branch: master". Click that and choose "tags" and you'll see the list of tags, which represent a snapshot of the point in time that I released the tagged version. The sql folder won't be in the 'master' branch, but if it's needed for some reason you can always check out (or download) any tag to get each file as it was at that point in time.
Quote:
Originally Posted by BobC
When I built my copy I left the sql out as your recipe didn't call for it and AIUI it was used for manipulating tiles, not something needed in a conversion utility.
|
That's pretty much it, the SQL files were used to create the database triggers for hiding various tiles. Those are moved into the Kobo Utilities plugin now.