As you can see, commit in URL[1] said that we can utilize buildsystem suffix and build quazip for both qt5 and qt4 Not sure if this change is available in 0.7.1, but it seems not hard to backport it. Some downstream application began to rely on changed name scheme. [1] - http://sourceforge.net/p/quazip/code/254
(In reply to Sergey Popov from comment #0) > backport it. Some downstream application began to rely on changed name > scheme. I'm not sure how to handle projects not supporting this scheme. Any idea?
(In reply to Justin Lecher from comment #1) > (In reply to Sergey Popov from comment #0) > > backport it. Some downstream application began to rely on changed name > > scheme. > > I'm not sure how to handle projects not supporting this scheme. Any idea? Reminder: it's upstream decision, so packages should migrate on this scheme sooner or later. We can make two ebuilds: 1) 0.7.1 with traditional REQUIRED_USE; 2) 0.7.1-r1 with new scheme And block dependencies like <dev-libs/quazip-0.7.1-r1 But, as naming of Qt4 version does not change, i wonder - how many packages depends on quazip built with USE="qt5" using old name? List of revdeps[1] are pretty short. So, we could deal with it without much delay. Other option would be pretty much the same, except we will roll out 0.7.1-r1 masked, carefully check all our revdeps and then - unmask it/set proper revdeps/patch them. [1] - https://qa-reports.gentoo.org/output/genrdeps/rindex/dev-libs/quazip
I worked on a multibuild bump for 0.7.2: https://github.com/gentoo/gentoo/pull/2636
Fixed in git by Andreas. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f0c1fce8a87ce8fefb1301a2015afb0d850dc079
By the way, we need to check all revdeps prior to stabilising this - at least some revdeps need patching to take into account the change.
