x11-libs/fox-1.0.49 (current stable) is not modular X ready. 1.0.53 is ported, bug unsupported upstream (see Bug 145046 Comment #18 and following) and is not worth the stabilization hassle. So, I'd suggest removing fox-1.0.* and the couple of ebuilds that depend on it: dev-python/fxpy-1.0.5 dev-python/fxpy-1.0.5-r1 dev-ruby/fxruby-1.0.25 dev-ruby/fxruby-1.0.29-r1 dev-python/fxpy should be removed completely, 1.0.5 states >=x11-libs/fox-1.0.17 but it plain won't compile w/ >=1.2 (the deps were fixed in -r1). Nothing depends on this package, no upstream update since 2003. dev-ruby/fxruby-1.2.2 is already stable, so 1.0.x is not needed any more anyway.
Looks like mabi picked up fox stuff recently, re-assigning.
dev-ruby/fxruby-1.0* are gone.
*** Bug 79849 has been marked as a duplicate of this bug. ***
Another two, that needs to get the axe are =x11-misc/pathfinder-1.0.53 and =app-editors/adie-1.0.53 depending on fox-1.0.53 [...] -done-
(In reply to comment #4) > Another two, that needs to get the axe are > =x11-misc/pathfinder-1.0.53 and > =app-editors/adie-1.0.53 depending on fox-1.0.53 Well, there apparently may be others, because those two above specify dependencies in a broken ("ranged") way, so won't ever get caught by pquery (nor do those dependencies work as expected). Sigh.
dev-util/reswrap-1.0.4 needs to die as well...
@python - can you please mask/kill dev-python/fxpy?
dev-python/fxpy killed.
