Hello! First of all sorry for the late review, but the currently ongoing transition is not helping.
You might want to consider suscribing to pkg-kde-talk@a-l.d.n (CCed), it's a *very low* traffic mailing list in which we coordinate some stuff. OK, looking at the package: - I know I'm late, but python-pyside2 and python3-pyside3 are definitely not a good idea. Any packager could just use them as a build dependency and install *tons* of useless MB of packages to build a package that just needs qtbase. It would not surprise me if it's final installed size would exceed 1GB, without considering dependencies. We do not have a qt5-dev package for exactly this reason and time proved us to be right as many came in asking for it. Please consider removing this meta packages in your next upload. - Looking at https://buildd.debian.org/status/package.php?p=pyside2 you might want to limit the qtwebengine5-dev to the archs in which it builts. If pyside2 build system works like pyqt then the related packages will not get built on those archs. Yes, this needs an arch list in the related binary packages too. - Looking at debian/control pyside2-tools seems to ship pyside2-uic, but python[3]-pyside2uic too. This is confusing :-/ I think that's all, thanks for it! -- Programming is really just the mundane aspect of expressing a solution to a problem. There are talents that are specifically related to actually coding, but the real issue is being able to grasp problems and devise solutions that are detailed enough to actually be coded. John Carmack answers on Slashdot, http://slashdot.org/games/99/10/15/1012230.shtml Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.