For background here, this bug is about permitting the splitting of the architecture-independent headers for a library into a separate -headers package rather than requiring (which the current Policy wording implies) that they be in the usually architecture-dependent -dev package.
"Kevin B. McCarty" <[email protected]> writes: > Chris Waters wrote: >> I would rather see that last sentence modified slightly to allow a >> little more flexibility. Perhaps changing "placed in" to "placed in or >> installed by". Or something along those lines. > Hmm, how about this? (I can't quite see how to keep it to a single > sentence of reasonable length.) > "If there are development files associated to a shared library, the > source package needs to generate a binary development package called > librarynamesoversion-dev, or if you prefer only to support one > development version at a time, libraryname-dev. Installing the > development package must result in installation of all the development > files." > This change would leave the door open for development files to be split > up into separate packages as needed, as long as lib<whatever>-dev > depends upon all of them, either directly or indirectly. This looks good to me. Here's proposed wording. Objections or seconds? diff --git a/policy.sgml b/policy.sgml index 720150d..1e134bb 100644 --- a/policy.sgml +++ b/policy.sgml @@ -5163,11 +5163,20 @@ Replaces: mail-transport-agent <heading>Development files</heading> <p> - The development files associated to a shared library need to be - placed in a package called - <package><var>libraryname</var><var>soversion</var>-dev</package>, + If there are development files associated with a shared library, + the source package needs to generate a binary development package + named <package><var>libraryname</var><var>soversion</var>-dev</package>, or if you prefer only to support one development version at a - time, <package><var>libraryname</var>-dev</package>. + time, <package><var>libraryname</var>-dev</package>. Installing + the development package must result in installation of all the + development files necessary for compiling programs against that + shared library.<footnote> + This wording allows the development files to be split into + several packages, such as a separate architecture-independent + <package><var>libraryname</var>-headers</package>, provided that + the development package depends on all the required additional + packages. + </footnote> </p> <p> -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
