Hi, On Mon, Sep 26, 2016 at 01:44:32AM +0200, Michael Biebl wrote: > Am 26.09.2016 um 01:28 schrieb Sebastian Reichel: > > I wonder if libvala-XY-dev should be named libvala-dev with the > > next version increase, though. This should make binnmu based > > transitions possible for valabind. > > Would a Provides: libvala-dev be sufficient?
As long as it's guaranteed, that there is only one package providing libvala-dev it might work. It would be a problem if libvala-0.34-dev and libvala-0.36-dev (numbers are just examples) are both available and providing libvala-dev. Then it's unclear which build-dependency should be pulled. That could be worked around by creating a transition-style libvala-dev package, that depends on libvala-xy-dev. > I think it makes some sense to include the API version in > libvala-XY-dev. After all, the version is encoded in > libvala-XY.pc and /usr/include/vala-XY. > > Would we need to provide an unversioned libvala.pc as well? No. valabind checks which libvala-xy it has to build against based on the valac version: https://sources.debian.net/src/valabind/0.10.0-1/getvv/ valadoc has a list of supported libvala versions, that it can build against: https://sources.debian.net/src/valadoc/0.30.0~git20160518-1/configure.ac/#L83 -- Sebastian
signature.asc
Description: PGP signature
