On Wed, Apr 19, 2006 at 12:21:14AM +0100, Daniel Stone wrote: > > On the other side, how do we ensure that cursor themes aren't upgraded > > before the libraries that need to access them? I think having cursors > > conflict with or depend on a shared library (libxcursor1) to accomplish this > > would be a bad idea. > > > > We do have libxcursor1 in stable Depends: libx11-6 | xlibs, libx11-6 > > Depends: xfree86-common, and x11-common (unstable) Conflicts: > > xfree86-common; but this is only sufficient to force an upgrade of libx11-6, > > not of libxcursor1. > > > > So it looks like the only options are: conflict with old libxcursor1, depend > > on new libxcursor1, or ignore the problem. All of those options suck. > > Anyone have a better one? > > Unless I'm missing something, old libxcursor1 also searches in > /usr/share/icons, no? $ dpkg -x x/xcursor/libxcursor1_1.1.3-1_i386.deb /tmp/libxcursor $ strings /tmp/libxcursor/usr/lib/libXcursor.so.1|grep icons ~/.icons:/usr/share/icons:/usr/share/pixmaps:/usr/X11R6/lib/X11/icons $ Yes, apparently so. In that case, what is the source of this bug report on xcursor-themes? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature