Quote:
Originally Posted by BetterRed
@WoSch - why do you want the library to be located outside the Calibre Portable folder?
The reason to put the library inside the Calibre Portable folder is that by doing so the software is no longer subject to the vagaries of Windows drive letter assignment - it can use paths that are relative to its location.
Otherwise the only way I can re-suggest is to put a symbolic link with a relative destination path into the Calibre Portable folder- but understand that a move or rename of the destination will break the symbolic link.
@eschwartz - does PA still do a Portable Calibre, couldn't see it in their directory. Sigil's there, but it's a bit long in the tooth.
BR
|
PA.com has
never done a portable calibre, on the grounds that they would have to push updates every week and they don't feel up to that.
There is, however, a development version here:
http://portableapps.com/node/20518
It relies on unpacking Kovid's calibre-portable.exe in order to install/update.
I would prefer the PA.com dev build, since it integrates into the PortableApps launcher, and uses their powerful infrastructure for updating the configuration files to match changing drive letters (as well as $TMP redirection and registry cleanup, although calibre doesn't really bother the registry much).
It is more robust for libraries stored in arbitrary locations (which is to say, you can use them).