I should have stated the question more clearly. I'm not very good a scripting, so how would I go about upgrading to 0.8.18 ? I need fairly comprehensive step by step instructions.

Thanks for any help.
Dan

Download all the files in ( http://taper.alienbase.nl/mirrors/pe...calibre/build/ ) , except calibre_pythondeps-13.37.0-i486.tar.bz2 AND calibre_pythondeps-13.37.0-i486.tar.bz2

Put then all into the same folder, enter a terminal, navigate to the folder, become root

Execute the script "./calibre.Slackbuild"

If any error happens and the build dont finish plx try to get some of the build log and copy in here

If everything turns to be good, as i think it will, use "upgradepkg /tmp/calibre*.txz" or "upgradepkg calibre*.txz"



The BUILD folder in alien repositorie is the formula that he uses to build the package he launchs every week. Its avaliable so everybody can see and learn how to build it thenselfs. If everything went fine and u did build the 0.8.18 version for your slackware-13.1_64bits, you can keep doing it by saving the folder you downloaded all the files from that BUILD and downloading and replacing just the calibre source code in it. Today ( its 2 AM of Friday here in Brazil ) the next version should be avaliable, the 0.9.19.

Alien REPO for more great packages: (http://taper.alienbase.nl/mirrors/pe...n/slackbuilds/)
Alien BLOG about Slackware, Life and everything (http://alien.slackbook.org/blog/)
Alien REPO RSS for updates and new packages ( http://connie.slackware.com/~alien/s.../ChangeLog.rss)

I know it has been a while since I started this, but I haven't had time to work on this project. I would like to thank everyone for their assistance. I now have Calibre 0.8.20 running. I shall now mark this thread solved.

Dan

There is a reason that I added these "calibre_pythondeps-13.37.0-i486.tar.bz2" and "calibre_pythondeps-13.37.0-i486.tar.bz2" files. They contain an "internal" pre-compiled python plus additional libraries which calibre needs (the python in Slackware is too old). Compiling these yourself will take a lot of time. Much more than compiling just the calibre source code.

So, because that "internal" python plus additional libraries do not change with every new version of calibre, it not needed to compile them every time. If the SlackBuild script finds a "calibre_pythondeps" tarball for your Slackware version and architecture, it will simply extract the binaries and add them to the calibre package. If such a tarball is not found during the build of the calibre package, then the SlackBuild script will have to compile python plus the additional libtraries and that takes a lot longer.

Your choice to use these tarballs with pre-compiled binaries. If you decide that you need to compile everything and do not trust my binaries, then you can still run the SlackBuild once. The SlackBuild will leave a tarball with the precompiled python binaries in the $TMP directory. You can move that tarball into the source directory and the next time, the SlackBuild script will use your own precompiled python binaries.

Eric

my bad

XD

Didnt know about those build details, but i did tested what i said before posting. I did take a while to finish...


Sorry Bob