Hi, just a version bump. Sven
Created attachment 23802 [details] prokyon3-0.9.2.ebuild
regarding bug #27254, I think it's better to exclude mysql from the DEPEND. Sure, you have to merge mysql anyway becaus QT needs it for mysql-support but why having a dependency of the qt mysql-plugin in the prokyon3-ebuild? The ebuild checks if qt is compiled with mysql and that's in my eyes enough. The way it is now, with mysql-dependency, only confuses users....
That depends in which order portage will emerge the packages if mysql nor qt are installed and mysql is not in USE. When portage will emerge mysql first, mysql will be added to USE according to use.defaults and this will lead to qt being compiled with mysql support. I'm currently testing if it will have an effect on the order if mysql is in DEPEND or is not in DEPEND in prokyon3.
doing USE=-mysql emerge -ep prokyon3 with mysql in DEPEND in prokyon3 will lead to result: > [ebuild N ] dev-db/mysql-4.0.17 > [lines removed] > [ebuild N ] x11-libs/qt-3.2.3-r1 > [ebuild N ] media-sound/prokyon3-0.9.2 doing USE=-mysql emerge -ep prokyon3 without mysql in DEPEND in prokyon3 will lead to result: > [lines removed] > [ebuild N ] x11-libs/qt-3.2.3-r1 > [ebuild N ] media-sound/prokyon3-0.9.2 So in my opinion having mysql as a dependency in prokyon3 does make a lot of sense to me.
If in your example mysql is added to the USE-flags after emerging it you're right. Then a DEPEND on mysql if good for prokyon3. I haven't thought about this.
in portage. thanks.