https://bugzilla.redhat.com/show_bug.cgi?id=2156091
--- Comment #4 from Antonio T. sagitter <trpost(a)rocketmail.com> ---
(In reply to Sandro Mani from comment #1)
Just a quick suggestion for future-proofness / analogy with other Qt
libraries: I'd call the base package qwtplot3d and then the subpackage
qwtplot3d-qt6, which then allows you to add say qwtplot3d-qt7 without
renaming the source repo or requiring an additional source repo. BTW, there
appears to be no BR: qwt-qt6-devel or equivalent?
I have re-named this package as qwtplot3d-qt
Probably, a Qt5 sub-package could obsolete the `qwtplot3d-qt5` rpm
(In reply to Vasiliy Glazov from comment #2)
5. Change
%autosetup -n qwtplot3d-%{commit} -N
%patch0 -p1 -b .backup
to
%autosetup -p1 -n qwtplot3d-%{commit} -N
I prefer to use the %%patch command apart.
Let me work better to this package
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2156091