Krzysiek Pawlik kirjoitti:
> 
> This is done:
> 
>  * new hessian: hessian-3.0.20 and hessian-3.1.6
>  * version bump of mx4j* to version 3.0.2
> 
> New versions of hessian require >=JDK 1.5, so I had to raise the lowest 
> allowed JDK version for mx4j from 1.4 to 1.5.
> 
> Any idea how to test what packages would be affected by unmasking of new 
> mx4j?
> 
> Build everything in dev-java ? It would also catch all compile errors, 
> etc independent from mx4j - which is not relevant to this case.
> 

betelgeuse@pena ~/bin $ cat emergerdeps
#!/bin/bash
emerge -1 -a $(rdeps ${1} | egrep R?DEPEND | uniq | cut -f 3 -d ' ' | 
sed -e 's/^/=/' | uniq)
#echo $(rdeps ${1} | egrep R?DEPEND | uniq | cut -f 3 -d ' ' | sed -e 
's/^/=/' | uniq)
betelgeuse@pena ~/bin $ cat rdeps
#!/bin/bash
adjutrix -D /usr/portage --log-level silent --write-cache-dir 
/var/cache/paludis/metadata/ -r "${@}"

or whatever reverse dependency tool rocks your boat (like jeeves for 
instance)

Regards,
Petteri