There is a missing dependency when attempting to update x11-libs/libXrandr-1.2.1 to x11-libs/libXrandr-1.3.1. This update requires package >x11-proto/randrproto-1.3 to be on the system. When I attempted this update on a system with x11-proto/randrproto-1.2.1 installed, emerge did not pull x11-proto/randrproto-1.3 into the dependency list, and thus failed with the following error: ... checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for RANDR... configure: error: Package requirements (x11 randrproto >= 1.3 xext xextproto xrender renderproto) were not met: Requested 'randrproto >= 1.3' but version of RandrProto is 1.2.1 ... Sure enough, running emerge -1 '>x11-proto/randrproto-1.3' allowed the subsequent x11-libs/libXrandr update to succeed. Therefore, x11-libs/libXrandr-1.3.1 (and possibly earlier versions) needs to have >x11-proto/randrproto-1.3 as a dependency.
randrproto-1.3.0 has been stable since 2009, and the last 1.2* version has been removed from the portage tree more than 1.5 years ago. I'm not convinced that it makes much sense to keep dependencies for that.
Although it won't affect people who upgrade with any frequency, it is a bug. If Xrandr 1.4 comes out, are you saying we shouldn't modify its dependency to be >=randrproto-1.4 also?
configure.ac uses the following logic to determine minimum randrproto version: RANDR_VERSION=[`echo $VERSION | sed 's/^\([0-9][0-9]*\.[0-9][0-9]*\).*$/\1/'`] Maybe this could be reproduced with versionator.eclass so it is done for all future versions.
Added the versioned dependency to libXrandr. Thanks.
