I am working on packaging a program which includes a very small subset of files from these packages.
From qt-examples, there are four files. From libqxt-devel, there are three files.
All of the files have been modified for use by the application.
I have done a search to see if these rpms are build requires for other packages: dnf repoquery --whatrequires qt-examples dnf repoquery --whatrequires libqxt-devel
In both cases I receive zero hits.
I'm thinking now that qt-examples doesn't really qualify as a "library". It is described as "Programming Examples for Qt" - which to me means the intent is to take what you need and modify. The intent was never that this be a "library".
In the case of libqxt-devel: http://dev.libqxt.org/libqxt/wiki/Home The website says: "This package is no longer maintained. Qxt will likely not work with newer Qt versions due to usage of internal api. We recommend that you pick out the parts you want instead of using the entire libqxt."
Which is exactly what the developer did.
Considering the above, I'm thinking no exception is required for the inclusion of these 7 files. Comments? I don't want to waste peoples time by going through the exception process if it isn't needed.
Thanks very much!
On Mon, 20 Apr 2015 10:55:34 -0700, Gerald B. Cox wrote:
I have done a search to see if these rpms are build requires for other packages: dnf repoquery --whatrequires qt-examples dnf repoquery --whatrequires libqxt-devel
In both cases I receive zero hits.
Just as a side-note, it's a faulty query. You need to query src.rpm repositories if you want to examine BuildRequires.
If you don't want to do that, examine dependencies on libqxt to get a first overview. Those likely are the result of a build dependency:
# repoquery --whatrequires libqxt clementine-0:1.2.3-4.fc22.x86_64 libqxt-devel-0:0.6.2-7.fc22.i686 libqxt-devel-0:0.6.2-7.fc22.x86_64 qlipper-0:2.0.1-5.fc22.x86_64 qterminal-0:0.6.0-1.fc22.x86_64 qterminal-0:0.6.0-2.fc22.x86_64 qutim-0:0.3.2-2.git.6f3a98a.fc21.i686 qutim-0:0.3.2-2.git.6f3a98a.fc21.x86_64 qutim-kde-0:0.3.2-2.git.6f3a98a.fc21.x86_64 qutim-quetzal-0:0.3.2-2.git.6f3a98a.fc21.x86_64 screengrab-0:1.2-1.fc22.x86_64 tepsonic-0:0.98.3-7.fc22.x86_64 yarock-0:0.9.67-3.fc22.x86_64
Here's a repoquery for BuildRequires:
# repoquery --archlist=src --whatrequires libqxt-devel --enablerepo=fedora-source cantata-0:1.4.1-2.fc22.src clementine-0:1.2.3-4.fc22.src qlipper-0:2.0.1-5.fc22.src qterminal-0:0.6.0-1.fc22.src qutim-0:0.3.2-2.git.6f3a98a.fc21.src screengrab-0:1.2-1.fc22.src tepsonic-0:0.98.3-7.fc22.src yarock-0:0.9.67-3.fc22.src
On Mon, Apr 20, 2015 at 1:51 PM, Michael Schwendt mschwendt@gmail.com wrote:
Just as a side-note, it's a faulty query. You need to query src.rpm repositories if you want to examine BuildRequires.
If you don't want to do that, examine dependencies on libqxt to get a first overview. Those likely are the result of a build dependency:
# repoquery --whatrequires libqxt
Here's a repoquery for BuildRequires:
# repoquery --archlist=src --whatrequires libqxt-devel --enablerepo=fedora-source
Michael, thanks for the correction. Had enabled src in the repo file for fedora and was using the command in conjunction dnf. dnf doesn't like the --archlist. Now I know.
That said, qt-examples still shows up with zero hits... and it doesn't have "lib" in the name, so I am think that "bundled libraries" does not apply here. Regarding libqxt, the recommendation from upstream I put above.
On Monday, 20 April 2015 at 23:47, Gerald B. Cox wrote:
On Mon, Apr 20, 2015 at 1:51 PM, Michael Schwendt mschwendt@gmail.com wrote:
Just as a side-note, it's a faulty query. You need to query src.rpm repositories if you want to examine BuildRequires.
If you don't want to do that, examine dependencies on libqxt to get a first overview. Those likely are the result of a build dependency:
# repoquery --whatrequires libqxt
Here's a repoquery for BuildRequires:
# repoquery --archlist=src --whatrequires libqxt-devel --enablerepo=fedora-source
Michael, thanks for the correction. Had enabled src in the repo file for fedora and was using the command in conjunction dnf. dnf doesn't like the --archlist. Now I know.
That said, qt-examples still shows up with zero hits... and it doesn't have "lib" in the name, so I am think that "bundled libraries" does not apply here. Regarding libqxt, the recommendation from upstream I put above.
I wouldn't take the "library" part from the guidelines so literarily. Any bundled code needs to be unbundled. Alternatively, an exception needs to be requested so that the bundling is tracked.
Regards, Dominik
packaging@lists.fedoraproject.org