<!DOCTYPE html>
<html data-lt-installed="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;">
Dear all,<br>
<br>
First, sorry in advance for this long message. It probably contains
over simplified statement about packaging (but I have an excuse: I
am a packager newbie!).<br>
<br>
Since version 6.0.0-1 the camitk source package is build using qt6.
The package libqtpropertybrowser6 and libqtpropertybrowser-dev are
therefore built using qt6.<br>
libqtpropertybrowser5 is the version available in Debian stable.
Debian unstable and Debian testing provides the Qt6 version.<br>
<br>
As you noticed, the vendor copy in the camitk source package is not
the currently official version of qtpropertybrowser. As explained in
sdk/libraries/qtpropertybrowser/README.CAMITK:<br>
<blockquote type="cite">
<div
style="color: #383a42;background-color: #fafafa;font-family: 'JetBrains Mono','Droid Sans Mono', 'monospace', monospace, 'Droid Sans Fallback', 'Droid Sans Mono', monospace;font-weight: normal;font-size: 18px;line-height: 24px;white-space: pre;"><div><span
style="color: #383a42;">CamiTK started to use Qt Property Browser way back in </span><span
style="color: #986801;">2010</span><span style="color: #383a42;">, when it was part of the Qt Solutions component</span></div><div><span
style="color: #383a42;">released under the BSD Licence.</span></div>
<div><span style="color: #383a42;">- Qt Solutions archive where first moved to gitlab</span></div><div><span
style="color: #383a42;"> For qtpropertybrowser on gitlab, see:</span></div><div><span
style="color: #383a42;"> https:</span><span
style="color: #a0a1a7;font-style: italic;">//github.com/qtproject/qt-solutions/tree/master/qtpropertybrowser/src</span></div>
<div><span style="color: #383a42;">- It was then took over again by the Qt Company Ltd.</span></div><div><span
style="color: #383a42;"> For qtpropertybrowser the Qt Company see:</span></div><div><span
style="color: #383a42;"> https:</span><span
style="color: #a0a1a7;font-style: italic;">//code.qt.io/cgit/qt/qttools.git/tree/src/shared/qtpropertybrowser</span></div>
<div><span style="color: #383a42;">The CamiTK team tries to keep in sync with both projects (at least of the bug fixes),
but we did our own migration to Qt</span><span style="color: #986801;">5</span><span
style="color: #383a42;"> and our modification and bug fixing.</span></div></div>
</blockquote>
<br>
The migration to Qt6 was also performed on the same vendor code.<br>
FYI, we noticed a renewed activity in the upstream source at
code.qt.io since circa 2023. The vendor copy was not updated that
much at all.<br>
<br>
From what I understand, nextpnr also uses a forked version from the
original qt-solutions (see 3rdparty/QtPropertyBrowser/README.md
[1]).<br>
<br>
Moreover, the CamiTK development team (upstream) is considering
removing this dependency and using an in-house specialized solution
in the near future.<br>
This removal is underway but not performed yet.<br>
Knowing that there were no reverse dependencies on
libqtpropertybrowser6 we were also considering removing both
libqtpropertybrowser6 and libqtpropertybrowser-dev packages.<br>
If I remembered well, the gazebo package was at some stage dependent
on these packages but it is no longer the case.<br>
<br>
Finally, to answer your question: yes, it might be a good idea to
have an independent package for QtPropertyBrowser based on the
code.qt.io corresponding subdirectory [2].<br>
It seems to be updated regularly by the people at qt.io.<br>
I don't know if there any other vendor distribution of
QtPropertyBrowser in other Debian packages (or if there is a way to
check this)<br>
<br>
Note nevertheless that the class ObjectController (a very useful
tool used in CamiTK to automatically create a GUI from the Qt
property system) was initially part of the original
QtPropertyBrowser examples. I could not find the ObjectController
example source code in the current repository.<br>
If nextpnr is also using the ObjectController "magic" class, then it
won't help to have a separate package.<br>
<br>
The other thing to consider is the licence. The current source code
in src/shared/qtpropertybrowser [2] has a complex
SPDX-License-Identifier:<br>
LicenseRef-Qt-Commercial OR LGPL-3.0-only OR GPL-2.0-only OR
GPL-3.0-only<br>
(so I suppose it is ok but not 100% sure).<br>
<br>
Best regards,<br>
Emmanuel<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://salsa.debian.org/electronics-team/nextpnr/-/tree/2ab3a896bdfe3ee1539c32ce963e277648b325c6/3rdparty/QtPropertyBrowser">https://salsa.debian.org/electronics-team/nextpnr/-/tree/2ab3a896bdfe3ee1539c32ce963e277648b325c6/3rdparty/QtPropertyBrowser</a><br>
[2]
<a class="moz-txt-link-freetext" href="https://code.qt.io/cgit/qt/qttools.git/tree/src/shared/qtpropertybrowser">https://code.qt.io/cgit/qt/qttools.git/tree/src/shared/qtpropertybrowser</a>
or the github clone at
<a class="moz-txt-link-freetext" href="https://github.com/qt/qttools/tree/a7527f64886f628fc0f2657798d199400df01ce3/src/shared/qtpropertybrowser">https://github.com/qt/qttools/tree/a7527f64886f628fc0f2657798d199400df01ce3/src/shared/qtpropertybrowser</a><br>
<br>
<div class="moz-cite-prefix">On 22/07/2026 17:03, Simon Richter
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:44af2ef0-7afd-417e-8fee-0fac58215913@debian.org">Hi,
<br>
<br>
The libqtpropertybrowser5 package is currently provided from a
vendored copy in the camitk package.
<br>
<br>
In nextpnr, we have another vendored copy, but we're already using
qt6, so we cannot use the one from camitk.
<br>
<br>
I'm not sure where upstream is at this point, but I suspect there
are more copies. Does it make sense to try to unify them?
<br>
<br>
Simon
<br>
<br>
_______________________________________________
<br>
Debian-med-packaging mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Debian-med-packaging@alioth-lists.debian.net">Debian-med-packaging@alioth-lists.debian.net</a>
<br>
<a class="moz-txt-link-freetext" href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging</a>
<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
</body>
<lt-container></lt-container>
</html>