[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#32229: [PROPOSED] libc-dev dependency in non-libc -dev packages



Package: debian-policy
Severity: wishlist

Most -dev packages currently hard-code a dependency on `libc6-dev', but for reasons of policy, not all architectures have that package (various other names include `libc6.1-dev' and `libc0.2-dev', which could expand to more if Debian ever branches into further systems that glibc is ported to), the other packages currently must provide `libc6-dev' to satisfy that dependency. I consider that ugly.

The packages also provide `libc-dev', but nothing in policy requires its use, I would like policy to require that -dev packages besides the -dev package provided by the glibc sources either recommend or depend on `libc-dev'.

Problems:

libc5-dev does provide libc-dev as well, but that package is not allowed to be installed on glibc2-based Debian systems, and libc5-altdev does not provide libc-dev. glibc should remain backward compatible for the forseeable future, so the name 'libc-dev' should be safe for quite some time (and if that ever changes, we will need to formulate a migration plan anyway).
--
Joel Klecker (aka Espy)                     <URL:http://web.espy.org/>
<URL:mailto:jk@espy.org>                  <URL:mailto:espy@debian.org>
Debian GNU/Linux PowerPC -- <URL:http://www.debian.org/ports/powerpc/>


Reply to: