[Request] Qt 5.x in /testing or /extra for Slackware 14.1
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.
[Request] Qt 5.x in /testing or /extra for Slackware 14.1
Qt 4.x is EOL soon and many projects migrating or planning to migrate on Qt5. So, i think that it would be a good choice to add Qt5 into -current branch for including Qt5 to Slackware 14.1.
Qt4 and Qt5 might be non-conflicting, if Qt5 to use a bit modified SlackBuild from Qt4
# Link the shared libraries into /usr/lib:
( cd $PKG/usr/lib${LIBDIRSUFFIX}
for file in qt5/lib/*.so* ; do
ln -sf $file .
done
)
Code:
mkdir -p $PKG/usr/lib${LIBDIRSUFFIX}/pkgconfig
( cd $PKG/usr/lib${LIBDIRSUFFIX}/qt5/lib/pkgconfig
for file in *.pc ; do
( cd $PKG/usr/lib${LIBDIRSUFFIX}/pkgconfig ; ln -sf /usr/lib${LIBDIRSUFFIX}/qt5/lib/pkgconfig/$file . )
done
)
One of the big changes for Qt5 is support for gstreamer 1.0. Unfortunately neither Clementine or KDE support this ATM (although I suspect KDE will with the v5.0 release to match Qt). I don't remember which one but there is at least one alternative browser which requires gstreamer 1.0.
I know Qt4 included Qt3 support (I could find only two things which actually used it- the 'make xconfig' for kernel configuration, and K3b.. and the latest git of k3b dropped this dependency).
All in all, it will take some time for everything to migrate in this direction.
To be honest, I can't think of an application that requires qt5 at the moment, so it sounds more like a cool new technology that can live in a SlackBuild until stable software starts coming out that uses it.
Since Slackware has only python2.7, it will be pretty hard to compile PyQt against python3.
Eric
I know... but since we're talking about a pipe dream for Slack. 15 Most modern distros have already switched to Python 3. I'm not real sure of the advantages/dependencies of sticking with Python 2. I would do it myself except it's a huge chain (Qt, Python3, sip, PyQt, KDE...).
Python 3 is essentially a different language than 2. It is not easy to switch from 2 to 3. Similarly is C++ to Java. We can install the other in additional.
I'm not aware of many (if any) direct dependencies on python2 in Slackware.
KDE has an indirect dependency on python but the version depends on that which was used to compile PyQt.
I just came across this problem again today trying to install Openshot. Requires pygoocanvas which requires pycairo which requires python3. (and, no, the py2cairo is not sufficient).
bash-4.2# python setup.py
Error: Python >= (3, 0) is required
Most everything is migrating towards python3. I also need it for the kxstudio plugins.
Ubuntu already employs it.
And, Qt5 and python3 would be a natural together.
I'm not aware of many (if any) direct dependencies on python2 in Slackware.
Possibly not many requires Python 2, but absolutely nothing (in slackware-current) requires Python 3. So why should 3 replace 2? BTW, I know at least hplip depends on Python 2.
Quote:
Originally Posted by jon lee
I just came across this problem again today trying to install Openshot. Requires pygoocanvas which requires pycairo which requires python3. (and, no, the py2cairo is not sufficient).
bash-4.2# python setup.py
Error: Python >= (3, 0) is required
I've never heard of Openshot. Why should its dependency added to slackware? -- Just downloaded the latest source (openshot-1.4.3). The README says it requires Python 2.5+, and it's Python source is incompatible with Python 3.
Quote:
Originally Posted by jon lee
Most everything is migrating towards python3.
Yes. Your wording is precise -- "is migrating", not "has migrated".
AFAIK, e.g. the physics community is far from ready for Python 3. Some fundamental softwares are even just matured on Python 2. So, what's the exact meaning of "everything" here?
Quote:
Originally Posted by jon lee
I also need it for the kxstudio plugins.
You are free to install your dependencies.
Quote:
Originally Posted by jon lee
Ubuntu already employs it.
Slackware does not have to be the same as Ubuntu. The former will never be a re-branded redistribution of Debian.
I'm not aware of many (if any) direct dependencies on python2 in Slackware.
KDE has an indirect dependency on python but the version depends on that which was used to compile PyQt.
I just came across this problem again today trying to install Openshot. Requires pygoocanvas which requires pycairo which requires python3. (and, no, the py2cairo is not sufficient).
bash-4.2# python setup.py
Error: Python >= (3, 0) is required
Most everything is migrating towards python3. I also need it for the kxstudio plugins.
Ubuntu already employs it.
And, Qt5 and python3 would be a natural together.
Next time, check SlackBuilds.org first. They have a SlackBuild for OpenShot 1.4.3 on Slackware 14.0, including all the required dependencies. Building OpenShot on Slackware 14.0 using sbopkg would be dead easy.
And remember - Slackware's tools do not require Python 3. And the fact that there is no Python 3 SlackBuild on slackbuilds.org is a good indication that nobody has found a need for Python 3 yet (or a tool that requires Python 3)...
And remember - Slackware's tools do not require Python 3. And the fact that there is no Python 3 SlackBuild on slackbuilds.org is a good indication that nobody has found a need for Python 3 yet (or a tool that requires Python 3)...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.