SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just noticed that Calibre 3.0.0 has been released, and in trying to build it, I have found that it has a couple of new dependencies. First, regex is now an external prerequisite as is no longer bundled in the source package, and Calibre 3 will not run without it. Second is msgpack-python, which may be optional (maybe not) because while it squawks about not finding module msgpack during the install phase of the SBo script, it still starts up ok and I am able to read Ebooks, though I have not had a chance to go through and test all the options that may use that module. In other words, I saw no squawks running calibre from a terminal window. Usual disclaimer here, YMMV.
Thanks. Actually sad that it's easier to install that way, but sometimes, just sometimes, practicality beats purity. This is one of those times.
Yeah, but where is the fun in that?
I'll look into updating my own calibre.SlackBuild for this new 3.x release. Sounds like fun. Glad Kovid is still using Python2 though... less effort for me.
Ho Ho .. Ok - that's true. I have installed this release, albeit from the site recommended way. It works. The application looks ever so slightly slicker. The new content server by way of web is very nice. Allows one to read a book inside the browser, even in offline mode. Makes sharing of books REALLY easy.
Ho Ho .. Ok - that's true. I have installed this release, albeit from the site recommended way. It works. The application looks ever so slightly slicker. The new content server by way of web is very nice. Allows one to read a book inside the browser, even in offline mode. Makes sharing of books REALLY easy.
I guess that Kovid "borrowed" the concept of the new contentserver with the capability to read the book in your browser, from the alternative contentserver COPS: http://blog.slucas.fr/en/oss/calibre-opds-php-server
The old Calibre contentserver was taxing my hardware, looked ugly and that's why I switched to COPS a long time ago - slick, responsive and with the capability to read your books inside the browser.
I have a SlackBuild ready for calibre-3 and once I have a free VM to compile a package I will have a look at this new feature. But I am probably not going back, my COPS server is perfect: FBReader on Android understands the OPDS URL and shows me a proper library on my tablet where I can download the books I want to read.. wherever I am.
Having an issue with your slackbuild: https://pastebin.com/N6bF0Xge (Been lax with updates. I've got Calibre 3.0 installed, but was trying to package 3.5.)
Here's an updated SlackBuild that will package 3.5.0 from the binary installer:
Code:
#!/usr/bin/env bash
# This will package the latest version of Calibre for Slackware. Run it
# as root. It will download Calibre, package it, and give you a correctly-
# named, ready-to-install Slackware package in /tmp.
set -e
VERSION=$(wget -O - -o /dev/null http://status.calibre-ebook.com/latest)
TMP=${TMP:-/tmp}
PKG=$TMP/package-calibre
BUILD=1dc
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
rm -rf "$PKG"
rm -rf $"TMP/calibre-installer-cache"
mkdir -p "$PKG/usr/share"
mkdir -p "$PKG/usr/bin"
wget -nv -O- https://download.calibre-ebook.com/linux-installer.py | python -c "import sys; main=lambda:sys.stderr.write('Download failed\n'); exec(sys.stdin.read()); main(install_dir='$PKG/opt', isolated=True)"
LD_LIBRARY_PATH="$PKG/opt/calibre/lib" "$PKG/opt/calibre/bin/calibre_postinstall" --root="$PKG/usr"
for symlink in $(find "$PKG/usr/bin" -maxdepth 1 -type l)
do
(
cd "$PKG/usr/bin"
ln -sf "/opt/calibre/$(basename "$symlink")" .
)
done
cd "$PKG"
/sbin/makepkg -l y -c n "$TMP/calibre-$VERSION-$ARCH-${BUILD}.txz"
On my system (binary NVidia drivers, -current, ktown), It won't launch on OpenBox, and I could only get it to launch on Xfce by setting QT_SCALE_FACTOR=1 before launching it.
Here's an updated SlackBuild that will package 3.5.0 from the binary installer:
On my system (binary NVidia drivers, -current, ktown), It won't launch on OpenBox, and I could only get it to launch on Xfce by setting QT_SCALE_FACTOR=1 before launching it.
Awesome, thanks! Should've specified I'm on 14.2. Loaded just fine for me, no variable setting needed.
On my system (binary NVidia drivers, -current, ktown), It won't launch on OpenBox, and I could only get it to launch on Xfce by setting QT_SCALE_FACTOR=1 before launching it.
Okay, I finally figured out the magic sauce that KDE (5) adds to get the upstream Calibre builds to work:
Code:
export QT_AUTO_SCREEN_SCALE_FACTOR=0
After adding this, it works in OpenBox and i3. Whereas before, I was getting the error described here:
After reading the documentation on this option, I'm wondering if the problem might be unique to my setup (my monitor is a TV that definitely doesn't give the correct EDID values):
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.