Quote:
Originally Posted by kovidgoyal
If you want a separate "dev" calibre and normal calibre, write a .bat file that launches the dev calibre like this
|
I have 4 scripts that choose different source hierarchies: one for calibre baseline and 3 for different kinds of development (normal, speculative, and store plugins). I also have 5 scripts that choose different libraries: production, small test (30 books with 25 bizarre custom columns), medium test (2000 books with 5 custom columns), large test (5,000 books with 3 custom columns), and huge test (20,000 books with 1 custom column). So, to run calibre, I first choose the source by running one script, then I choose the library and run calibre by running another script. The calibre portable .bat file in resources contains all the information necessary to set up these scripts.
Regarding the installer, I almost never run calibre other than from source so I don't care what calibre binary is installed. I run the installer from time to time because calibre source can depend on DLLs and other binary files in the binary version. My experience is that updating calibre binary once every month or so is sufficient, but there have been times where I must do it more often. There is no problem with updating the binary more often, but I am lazy.
If I really need to run a calibre binary, I do it in a virtual machine so I have full control over what it sees.