severity 608851 serious kthxbye On Mon, Jan 3, 2011 at 19:24:44 -0500, Yaroslav Halchenko wrote:
> Package: libsvm-dev > Version: 3.0-1 > Severity: normal > > > Since there is no libsvm3.0-dev, and multiple versions (e.g. 2.91 and 3.0) of > libsvm-dev could not be co-installed on the system, it really makes little to > no sense to carry additional versioned directory such as > /usr/include/libsvm-3.0 on top of libsvm includes directory. Or am I missing > something? > > Such include directories migration from one location to another might for no > good reason ruin builds of dependent packages which might remain > compatible with multiple versions of libsvm while not foreseeing a variety of > versioned directories coming with new major releases of libsvm. Partially it > accounts for FTBFS of pymvpa (#608844, CCed). > Same with libsvm-ruby (527491 last time around, 614651 now). There doesn't seem to be any reason for the versioned header directory, and without a pkg-config file this is just make-work for reverse dependencies. Please drop it. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
