Bug#537548: libafterimage/libafterbase API/ABI change

2009-07-20 Thread Julien BLACHE
Robert Luberda wrote: Hi, > I think it's too late for bumping the soname, so I prepared a patch for > aterm to make it build and work with the current libafterimage. I'm > going to make QA upload of it soon. Although it's nice and all for aterm, it doesn't help fix locally-built software, which

Bug#537548: libafterimage/libafterbase API/ABI change

2009-07-20 Thread Robert Luberda
Julien BLACHE writes: Hi, > > Upstream CVS log: > > Got rid of dpy global variable in libAfterBase and libAfterIMage for > good. Moved it into libAfterStep instead, as it incorporates screen > handling functionality. > > That is an API *and* ABI change for all three libraries, and that > w

Bug#537548: libafterimage/libafterbase API/ABI change

2009-07-20 Thread Julien BLACHE
Hi, Upstream CVS log: Got rid of dpy global variable in libAfterBase and libAfterIMage for good. Moved it into libAfterStep instead, as it incorporates screen handling functionality. That is an API *and* ABI change for all three libraries, and that warrants a soversion bump for all three l