[Slackbuilds-users] SlackBuilds-users Digest, Vol 147, Issue 7

[Richard Scott Smith]

> Date: Tue, 3 Jul 2018 12:14:37 -0700
> From: Larry Hajali <larryhaja at gmail.com>
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] qt5 is sorely in need of an update
> Message-ID:
>         <CAAZPBMgNKjveh4jtF7DOp0g1h1SeSuLBnJktPXRVwKTvPSDejQ at mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Tue, Jul 3, 2018 at 11:03 AM B Watson <yalhcru at gmail.com> wrote:
>
> > On 7/3/18, orbea at fredslev.dk <orbea at fredslev.dk> wrote:
> > >
> > > When programs I use will soon no longer support releases older than
> > > 5.9 I can not complain to them that it will no longer build in
> > > Slackware because by all means we should of updated literally years
> > > ago...
> >
> > You (or whoever) could submit a qt59 or qt5-new or something like that,
> > and the stuff that requires qt 5.9 or newer could list that as a dep.
> >
> > That, or if the old qt5 maintainer's OK with the change, rename the
> > existing qt5 to qt5-legacy and someone can submit a new qt5 build and
> > keep it up to date. Anything that won't build with the new qt5 has the
> > dep changed to qt5-legacy (more work that the previous option).
> >
> > Is the problem just that the maintainer's gone missing, or is he
> answering
> > emails and giving out a reason why he won't update the build?
> >
> I'm here and I did respond if you look at this email chain.
>
> Issue is that newer PyQt5 versions rely on a newer version of sip that
> comes with Slackware 14.2.  Last I remember someone was going to look at
> packaging a newer sip pacakge that can either replace or run alongside the
> stock sip package in Slackware 14.2.  I don't have time to investigate
> this.
>
> If the ultimate goal is to have a new version of qt5, than someone can
> create a package called qt59 or whatever to satisfy a dependency.  If
> someone does take over qt5 and upgrade then it would be up to them to make
> sure the dependencies work after the update.  Upgrading a package like qt5
> is a big ask as it is a big package itself to compile and there are
> multiple dependencies to test.
>
> --Larry
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> attachments/20180703/500f9ec5/attachment-0001.html>
>

First, thank you for your work on qt5.

+1 on moving qt 5.7 to legacy and making 5.9.x the current 14.2
Slackbuild.  I have been running into this issue for the last couple of
years.  Zoom is one of the biggest problems as I use it for work all the
time and it complains about qt5 being too old.  I live with it and people I
work with hate me for using Slackware because I have "issues".  I symlink,
I update nvidia drivers, I monkey with it until I've been able to get it to
work on one of my 4 Slackware systems.  My Intel graphics based systems are
a lost cause.

I don't even know what sip is, so I'm inclined to say I don't care about
it.  I like Slackware so much that I'm willing to work around most any
issues simply because Slackware so great.  I've used a lot of distros and
all of them piss me off more than Slackware.

For me, I'm speculating that updating qt5 would be less effort and
heartache than working around what's there now.

Has anyone used Alien Bob's Slackware current qt 5.9 install on Slackware
14.2?  If that works, and creates a few "issues" I don't care about, that
might be a worthy option.

scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180704/6533ecdd/attachment.html>