[Slackbuilds-users] qt5 is sorely in need of an update

[David Woodfall]

On Tuesday 3 July 2018 12:14,
Larry Hajali <larryhaja at gmail.com> put forth the proposition:
> 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.

I did say that I would look into a newer sip. Sorry, I just haven't
had time yet.

One option could be to download sip and install it but with it, and
all the references, renamed. I did this with the new pudb that
installed a custom urwid that didn't interfere with the stock, but
that was fairly simple because pudb is a small application compared
to PyQt5.  

I will try to get on to it ASAP

-Dave

--

How should I know if it works?  That's what beta testers are for.  I
only coded it.
  -- Attributed to Linus Torvalds, somewhere in a posting

                                                            .--.  oo
                                                           (____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'