https://bugzilla.redhat.com/show_bug.cgi?id=955996 --- Comment #11 from Jeff Fearn <jfearn@xxxxxxxxxx> --- (In reply to Kevin Kofler from comment #10) > IMHO, a bundling exception for something as large as Qt is not realistic > either. How do you plan to maintain that fork? Upstream does most of that work. For security related issues the bundling rules specifically state how to structure spec files to make tracking bundled libraries easier for security response. > I see only 3 possibilities (with the reservation that I am not the one to > make the decision on bundling exceptions, the FPC is): > a) Upstream wkhtmltopdf gets their Qt changes upstreamed into upstream Qt. > b) Upstream finds a way to make wkhtmltopdf work without modifying the > entire Qt (maybe by forking selected 1 or 2 classes – the fewer classes, the > more likely it is to get a bundling exception in Fedora). > c) The package cannot go into Fedora (or only with all the features that > require a patched Qt disabled). wkhtmltopdf without the QT patches is already in fedora. FWIW you can't use that package to build PDFs for the fedora documentation, it just doesn't have the functionality required to be part of a publishing pipeline without the patches to QT. I'll make sure you get CC'd when the FPC ticket gets opened. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review