Should -dev and -dbg libary packages depend on ${Source-Version}?

I've noticed that it's not policy for shared libraries' libblah-dev and libblah-dbg packages to depend on libblah1 (=${Source-Version}) of the main library. I was bitten by this when I forgot to manually keep the dependancy up-to-date in debian/control, which allowed people to, say, install a new

It is ok to have a hardcoded Depends: libc6-dev ?

Hi. We have the shlibs mechanism for dependencies on shared libraries. This allows a package to be compiled under libc5, libc6, or whatever libc, and the right dependency info will be calculated automatically. However, there are some packages having a hardcoded dependency on libc6-dev, and it see

Re: FHS - transition

I wrote: >> A better way of handling this transition might be dpkg-divert. >> (I'm not _au fait_ with dpkg-divert's details, so I'm not sure how >> much it would need to be improved before it could be used like this.) >> Assuming dpkg-divert is (modified to be) capable of diverting whole >> directo