On 30 March 2014 21:28, Marc Glisse <marc.gli...@normalesup.org> wrote: > > Source: libboost1.55-dev > Followup-For: Bug #738538 > > > No, the -dev package is NOT multi-arch. > > Dear Maintainer, > > is there a particular obstruction to marking it as multi-arch? I was > surprised to notice that it wasn't, when that seemed the whole point of > splitting a -tools-dev package. Listing the files in this package, it > contains only the headers (not autogenerated, so common to all > platforms) and an example, which seems quite safe. (Most) other boost > -dev packages are in the same situation with an extra .a/.so pair which > is safe as well, so I don't think there is anything to do except pasting > the multi-arch line many times in the control file. The longest is > obviously building and checking that the resulting x86 and x86_64 (at > least) packages can be co-installed, and I can understand if you want to > wait for the next upstream release to do that. >
The problem is that dependencies of the suggested packages are not multiarched, e.g. one cannot co-install libboost-mpi-python1.55-dev. I guess, there is more benefit to allow libboost1.55-dev be multiarched:same (since it's ready), even if all suggests are not multiarch installable. The libboost1.55-dev package is coinstallable across bitness and endianess different systems. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
