-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been aware of calibre upgrading to Qt5 and I have my own
system updated to work with it on Slackware 14.1. Right now
Slackware 14.1 and current cannot use the newer calibre due to the
sip package being too old. I was hoping Slackware
Dear List,
In libvpx's slackbuild the file `libvpx-v1.3.0/build-tmp/docs/html`
doesn't exist.
--- a/libvpx.SlackBuild 2014-08-03 06:40:23.0 -0300
+++ b/libvpx.SlackBuild 2015-04-02 20:12:54.0 -0300
@@ -103,7 +103,7 @@
| cut -f 1 -d : | xargs strip
Hi,
I've been aware of calibre upgrading to Qt5 and I have my own system
updated to work with it on Slackware 14.1. Right now Slackware 14.1 and
current cannot use the newer calibre due to the sip package being too old.
I was hoping Slackware current would update the sip package so that I could
* Larry Hajali larryh...@gmail.com wrote:
With that said, if the SBo community wants calibre to be updated
with the binary repackaging then I'm willing to give up maintaining
calibre.
I can only speak for myself but I think the way you maintain Calibre
is just fine.
Maybe the Calibre binary
On Thu, 2 Apr 2015, Larry Hajali wrote:
Hi,
I've been aware of calibre upgrading to Qt5 and I have my own system
updated to work with it on Slackware 14.1. Right now Slackware 14.1 and
current cannot use the newer calibre due to the sip package being too old.
I was hoping Slackware current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I built the new calibre a few month back on -current. It did require
me to update sip, but that wasnt the only thing that needs to be
updated. You also need to rebuild PyQt against the new sip, then QT5,
then PyQt5. Luckily the build scripts Pat
