Quote:
|
Originally Posted by heyjohn
- Is the calibre_postinstall thing just a validation/test script to see whether all the site-python bits were really installed? If so, it'll make more sense to put a python one-liner into the %post section of the .spec file.
|
calibre_postinstall does things like generate and install the FDI used by hal for device detection on Linux. It also sets up bash completion, and installs the desktop integration files (icons and .desktop). Take a look at post_install() in src/calibre/linux.py to see what it fully does. Some of it can be handled by the package manager.
Quote:
|
Originally Posted by heyjohn
- What are cherrypy, pyPdf, odfpy, and python-cssutils doing as part of this package? Are they modified versions, or taken straight from other projects? I already have them on my system, and do not want to overwrite my distro's versions. That's why I do this RPM thing and not binary installers...
|
They are part of the package because systems Windows does not provide a Linux like package manager. Also, distributing them this way avoids issues with the system package being out of date. Further it allows the building of the binary installer package. There should be no issue replacing them with the system package provided the versions are the same or compatible. Kovid has a tendency to require the latest and greatest.