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.
for me the Slackware and SBo combination offers a good compromise. We have Slackware as a stable, conservative and very well tested base, combined with very recent and actively updated third party software.
how long does it take to compile qt5 with 8 cores. I know.
you try it.
Hi Drakeo, I gather you have a problem with building qt5 from SlackBuilds.org?
If you are running Slackware 14.1, use qt5-5.5.1. This has not changed since November 2015.
If you are running Slackware 14.2, use qt5-5.7.1. This has not changed since February 2017.
If you are running -current, you are a beta tester. If you don't like being a beta tester, please go back to 14.2, where qt5 has been stable for 471 days.
Thanks for the feedback!
I have no issue with qt5. love kde5 great tool if Pat does not go that way or Bob's latest blob far from stable. Will seek another distro. been slack since 2004.
love the KDE team donate to them. none of them shoved qt 5 into slackware throats.
I like it how it works now. We get to have a nice stable base system (Slackware) while still getting the latest and greatest applications (SBo).
I disagree ask what part of cmake and qt in slackware work. Ton of work. try it out. take simple screen recorder use qt5 to build it I have builds for it. compile qt5 ok have fun fixing things.
YES! The scripts at slackbuilds.org are all tested by the admins.
They use a full installation of Slackware. Not including stuff from the /extra or /pasture directories.
You say "nope".
I would like that you explain which SlackBuild scripts on SBO are not working on a full installation of Slackware 14.2 (or on whatever version they are targeting).
Why are they not working in your opinion?
The SBo admins will test ZERO scripts on slackware-current when they are QA testing.
So, considering that qjackctl recomends itself to "provides a simple GUI dialog for setting several JACK daemon parameters" it is really and really need of compiling that huge crap which include even the Chromium and has tons of sensible dependencies...
Yeah, sure! But, last time when I compiled the Qt5, was about 6 hours in a Phenom x4 9650 at 2.3GHz, 8GB RAM, and mechanical hard drives.
Excuse me, but SBO started to look really ridiculous.
You guys forget that not all people buy annually a $5000 computer just to toy with your builds...
Last edited by Darth Vader; 05-26-2018 at 08:10 AM.
YES! The scripts at slackbuilds.org are all tested by the admins.
They use a full installation of Slackware. Not including stuff from the /extra or /pasture directories.
Yeah, man! BUT the users does not use clean full installations, because they install other packages, some even SBO generated.
THEN, it is safely to assume that the packages are built in "dirty" systems by the SBO users, so depending on what the user already installed, the build may or may not pick particular features.
Long story short, I believe that the SBO scripts never generate the same packages, because the particular conditions where the packages are built.
AND, how SBO lacks the support for build-dependencies and it is unable to check and tune them, it is safely to assume that this endeavor is a failed design from start.
Last edited by Darth Vader; 05-26-2018 at 08:07 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.