On 2020/02/29 07:27, Landry Breuil wrote:
> On Thu, Feb 27, 2020 at 08:48:55AM +0100, Rafael Sadowski wrote:
> > On Thu Feb 27, 2020 at 08:35:41AM +0100, Landry Breuil wrote:
> > > On Thu, Feb 27, 2020 at 07:59:32AM +0100, Rafael Sadowski wrote:
> > > > Hi All
> > > >
> > > > After truly hard work, I am excited to write this email. The
> > > > following diff contains the 3 ports which are all dependent on each
> > > > other.
> > > >
> > > > - devel/py-sip
> > > > - x11/py-qt5
> > > > - x11/qt5
> > > >
> > > > Almost all consumers fixed. For some you will find patches on
> > > > ports@, for some, private maintainer emails are out. math/octave is not
> > > > happy now but maybe an update helps. I'll take care of this monster.
> > > >
> > > > What's the news?
> > > >
> > > > - Most of the work was done in qtbase.
> > > > - The qtbase port comes with vulkan and zstd support by default enabled.
> > > > I hope this will works fine with !{amd64,i386} arches.
> > > > - s/c++11/c++17/
> > > > - Qtdoc (docs) is broken again, I think I am not that bad again and can
> > > > be fixed later.
> > > > - Bump all shred lib and cleanup SHARED_LIBS.
> > > > - Many cleaning jobs in the Makefiles.
> > > > - New py-qt5/pkg/PFRAG.python3. Could the py- wizards take a look at
> > > > this.
> > >
> > > can you explain why ? the MODPY_COMMENT bit should achieve the same in
> > > the current port.. unless i missed something ?
> >
> > I can't, this works for me. I'm not the py-{port} expert maybe there is
> > a smarter/cleaner way to do it.
>
> tried simplifying things to avoid the PFRAG.python3 & PLIST churn, but
> the resulting pyqt5 seems broken:
>
> [18:33] c64:~/mystuff/x11/py-qt5/ $python3
> >>> from PyQt5 import QtCore
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> ModuleNotFoundError: No module named 'PyQt5.sip'
Looks like the py-qt5 diff misses "--sip-module PyQt5.sip --no-tools" or
whatever
it was that's needed..
