On Mon, Dec 21, 2009 at 1:25 AM, Dave Airlie <airl...@linux.ie> wrote: > > So I've changed libdrm_radeon API upsteram, I'd like to fixup Mesa 7.6 + > 7.7 branches to request the new API using a similiar patch I just > committed from Fabio. > > Reasoning is: > a) libdrm declares the ABI as unstable, so any distro shipping it already > has agreed to burden the hassle. if they ship the old libdrm_Radeon, > they'll just need to ship 2.4.17 libdrm. > b) if a distro has never shipped a libdrm_radeon, mesa ships all the code > necessary to do the non-kms/dri2 paths without it. So they won't be > affected. > > I'll do this tomorrow if nobody objects, the API changes are fairly > pickable.
Can you bump the version in the libdrm_radeon.pc file or have it just use @PACKAGE_VERSION@ like libdrm_intel? That should make it easier to enforce API changes. -- Dan ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
