Author: zack
Date: Wed May 16 11:23:53 2007
New Revision: 3759

URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/?sc=1&rev=3759
Log:
describe deps from -dev to shared lib packages and mention the binNMU safety 
issue

Modified:
    trunk/packages/ocaml/trunk/debian/changelog
    trunk/packages/ocaml/trunk/debian/policy/chapter-libpack.xml

Modified: trunk/packages/ocaml/trunk/debian/changelog
URL: 
http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocaml/trunk/debian/changelog?rev=3759&op=diff
==============================================================================
--- trunk/packages/ocaml/trunk/debian/changelog (original)
+++ trunk/packages/ocaml/trunk/debian/changelog Wed May 16 11:23:53 2007
@@ -14,8 +14,10 @@
     - mandate the compilation of *.cm[ao] with debugging information for
       libraries and forbid it for bytecode programs
     - update the Vcs-Svn info to the latest PTS documentation
-
- -- Stefano Zacchiroli <[EMAIL PROTECTED]>  Wed, 16 May 2007 13:09:25 +0200
+    - describe dependencies from a -dev package to its companion shared stub
+      package (if any) and suggest the usage of ${binary:Version}
+
+ -- Stefano Zacchiroli <[EMAIL PROTECTED]>  Wed, 16 May 2007 13:22:23 +0200
 
 ocaml (3.09.3-1) experimental; urgency=low
 

Modified: trunk/packages/ocaml/trunk/debian/policy/chapter-libpack.xml
URL: 
http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocaml/trunk/debian/policy/chapter-libpack.xml?rev=3759&op=diff
==============================================================================
--- trunk/packages/ocaml/trunk/debian/policy/chapter-libpack.xml (original)
+++ trunk/packages/ocaml/trunk/debian/policy/chapter-libpack.xml Wed May 16 
11:23:53 2007
@@ -17,6 +17,41 @@
                 <para>
                     <filename>libxxx-ocaml-dev</filename> should provide the 
rest of the library package, in fact anything needed to develop programs using 
the library. If the library uses other libraries or C libraries, this package 
should depend on them.
                 </para>
+               <para>
+
+                 <filename>libxxx-ocaml-dev</filename> should depend on its
+                 companion <filename>libxxx-ocaml</filename> package (if any).
+                 The reason is that at compile time the &ocaml-name; compiler
+                 will try to load the shared library stubs, aborting the
+                 compilation in case of failure. Hence the development package
+                 is useless if the corresponding stub package is missing. To
+                 ensure compatibility the dependency among the two packages
+                 should be strictly versioned. In order for the resulting
+                 packages to be <ulink
+                   url="http://wiki.debian.org/binNMU";>binNMU safe</ulink> this
+                 requirement states that the dependency should make use of a
+                 <code>${binary:Version}</code> substitution variable.
+
+                 <example>
+                   <title>Dependency from a -dev package to its companion share
+                     library stub package (if any), from the
+                     <application>pcre-ocaml</application> package</title>
+                   <programlisting>
+  Package: libpcre-ocaml
+  Architecture: any
+  Section: libs
+  Depends: ocaml-base-nox-${F:OCamlABI}, ${shlibs:Depends}, ${misc:Depends}
+  ...
+
+  Package: libpcre-ocaml-dev
+  Architecture: any
+  Section: libdevel
+  Depends: ocaml-nox-${F:OCamlABI}, libpcre3-dev (>= 4.5), 
<emphasis>libpcre-ocaml (= ${binary:Version})</emphasis>, ocaml-findlib (>= 
1.1), ${misc:Depends}
+  ...
+                   </programlisting>
+                 </example>
+
+               </para>
                <para>
                  <filename>libxxx-ocaml-dev</filename> packages should be in 
<code>Section: libdevel</code>
                </para>


_______________________________________________
Pkg-ocaml-maint-commits mailing list
Pkg-ocaml-maint-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-ocaml-maint-commits

Reply via email to