Bugzilla Bug 22869

Using constructs like "|| ( gimp-print gimp-print-cups )" as dependencies 
(see ghostscript-7.05.6-r2.ebuild) has strange side effects: 
If the dependency is not satisfied, which package is taken to satisfy it? 
I guess the first is taken, but this creates problems: for example I have 
gimp-print-cups installed but not gimp-print. Using the --deep flag I get: 
 
# emerge -uDp ghostscript 
 
These are the packages that I would merge, in order: 
 
Calculating dependencies ...done! 
[ebuild  N   ] net-print/foomatic-2.0.0 
[ebuild  N   ] dev-perl/Text-Balanced-1.95 
[ebuild  N   ] dev-perl/Parse-RecDescent-1.94 
[ebuild    UD] dev-db/mysql-3.23.56 [4.0.12] 
[ebuild    UD] app-text/tetex-1.0.7-r12 [2.0.2] 
[ebuild    UD] media-video/nvidia-kernel-1.0.4349-r2 [1.0.4363-r2] 
[ebuild    UD] media-video/nvidia-glx-1.0.4349 [1.0.4363] 
[ebuild  N   ] dev-perl/Data-Dumper-2.101 
[ebuild  N   ] dev-perl/Digest-MD5-2.24 
[ebuild  N   ] dev-perl/Inline-0.44 
[ebuild  N   ] dev-perl/Filter-1.29 
[ebuild  N   ] dev-perl/ExtUtils-F77-1.14-r1 
[ebuild  N   ] dev-perl/PDL-2.3.4 
[ebuild  N   ] media-libs/mpeg-lib-1.3.1-r1 
[ebuild  N   ] media-gfx/gimp-1.2.3-r3 
[ebuild  N   ] media-gfx/gimp-print-4.2.5 
 
this mean that during the recursive creation of the dependency tree gimp-print is taken 
as a dependency and its dependency subtree is considered. But I don't want gimp 
installed (BTW, gimp-print is also blocked by gimp-print-cups). 
 
I don't see a clear solution for this issue (I read bug #19937 and bug #21248 and 
was quite scared by them). Maybe a local use flag?

see comment on bug #19937 

this dep isn't needed anymore since the 4.3 series, so it will be fixed in next
gs version.

ghostscript-7.05.6-r3 now in portage ...