[Pkg-ocaml-maint-commits] r5632 - in /trunk/packages/ocaml/trunk/debian/policy: chapter-generalities.xml chapter-libpack.xml ocaml_packaging_policy.xml
gildor at users.alioth.debian.org
gildor at users.alioth.debian.org
Tue May 13 18:46:29 UTC 2008
Author: gildor
Date: Tue May 13 18:46:29 2008
New Revision: 5632
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/?sc=1&rev=5632
Log:
* Update section on camlp4 in the policy
Modified:
trunk/packages/ocaml/trunk/debian/policy/chapter-generalities.xml
trunk/packages/ocaml/trunk/debian/policy/chapter-libpack.xml
trunk/packages/ocaml/trunk/debian/policy/ocaml_packaging_policy.xml
Modified: trunk/packages/ocaml/trunk/debian/policy/chapter-generalities.xml
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocaml/trunk/debian/policy/chapter-generalities.xml?rev=5632&op=diff
==============================================================================
--- trunk/packages/ocaml/trunk/debian/policy/chapter-generalities.xml (original)
+++ trunk/packages/ocaml/trunk/debian/policy/chapter-generalities.xml Tue May 13 18:46:29 2008
@@ -230,9 +230,6 @@
<listitem><para>bytecode object files (<filename>*.cmo</filename>)</para></listitem>
<listitem><para>native object files (<filename>*.cmx</filename>)</para></listitem>
<listitem><para>configuration files for handling libraries with <filename>ocamlfind</filename> (<filename>META</filename>)</para></listitem>
- <!-- ZACK: do we really need to differentiate them? They are plain
- objects or library after all ... -->
- <!--<listitem><para>&camlp4; related files (<filename>*.cm[ao]</filename>)</para></listitem>-->
</itemizedlist>
</para>
</section>
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=5632&op=diff
==============================================================================
--- trunk/packages/ocaml/trunk/debian/policy/chapter-libpack.xml (original)
+++ trunk/packages/ocaml/trunk/debian/policy/chapter-libpack.xml Tue May 13 18:46:29 2008
@@ -244,33 +244,47 @@
-->
<section id="camlp4-path">
- <title>&camlp4;</title>
- <para>
- Actually, &camlp4; extensions are stored in
- <filename>&ocaml-sys-dir;/camlp4/</filename>. In order to do something
- cleaner, &ocaml-force; proposes to put this files in their own directory, even in their
- own package. It is not mandatory, but it could ease a lot by avoiding
- name clashes.
- </para>
-
- <para>
- You just have to consider a &camlp4; file just as a standard library, except that you
- prefix them with <varname>-syntax</varname>. For example: the syntax
- extension coming with <application>libokey-ocaml-dev</application> should be stored
- in <filename>&ocaml-sys-dir;/okey-syntax/</filename>, the package
- containing it should be called <application>libokey-syntax-ocaml-dev</application>.
- </para>
-
- <para>
- It is recommended to use <filename>META</filename> to specify how to handle this
- extension.
- </para>
-
- <para>
- All definition is taken from previous text considering syntax extension as a standalone
- library.
- </para>
-
+ <title>&camlp4;/&camlp5;</title>
+
+ <para> Actually, &camlp4; extensions should be processed just as standard
+ OCaml library. The META file distributed with this syntax extension
+ should follow the
+ <ulink url="http://cocan.org/osr/meta_files_for_packages_containing_syntax_extensions">
+ OSR: META files for packages containing syntax extensions</ulink>. In
+ particular, the syntax extension should be contained in a <varname>syntax</varname> sub
+ packages.
+ </para>
+
+ <para>
+ The naming convention of the package is to use the same naming as with
+ standard package, replacing <varname>-ocaml-</varname> by the syntax
+ extension name, <varname>-camlp4-</varname>.
+ </para>
+
+ <para>
+ If a package contains at the same time syntax extension and library, it
+ is up to the maintainer to choose the most relevant name for the package.
+ Whatever the name chosen for the package, the other name should be a
+ <varname>Provide</varname> of the package.
+ </para>
+
+ <para>
+ For example, consider the package <application>sexplib310</application>.
+ It provides a syntax extension and a library, which is the runtime support
+ of the additional function generated by the syntax extension. Since the most
+ common use of <application>sexplib310</application> is through its syntax
+ extension, the package is name
+ <application>libsexplib-camlp4-dev</application> and it also provide
+ <application>libsexplib-ocaml-dev</application>.
+ </para>
+
+ <para>
+ &camlp5; is an alternate pretty-printer and preprocessor for OCaml
+ (which is compatible with pre-3.10.0 version). Syntax extension are
+ handled through exactly the same scheme as for &camlp4; except that
+ package name use <varname>-camlp5-</varname> rather than
+ <varname>-camlp4-</varname>.
+ </para>
</section>
<section id="documentation">
Modified: trunk/packages/ocaml/trunk/debian/policy/ocaml_packaging_policy.xml
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocaml/trunk/debian/policy/ocaml_packaging_policy.xml?rev=5632&op=diff
==============================================================================
--- trunk/packages/ocaml/trunk/debian/policy/ocaml_packaging_policy.xml (original)
+++ trunk/packages/ocaml/trunk/debian/policy/ocaml_packaging_policy.xml Tue May 13 18:46:29 2008
@@ -18,7 +18,8 @@
<!ENTITY ocamlopt "<application>ocamlopt</application>">
<!ENTITY ocamldoc "<application>ocamldoc</application>">
<!ENTITY ocamlfind "<application>ocamlfind</application>">
-<!ENTITY camlp4 "<application>CamlP4</application>">
+<!ENTITY camlp4 "<application>Camlp4</application>">
+<!ENTITY camlp5 "<application>Camlp5</application>">
<!ENTITY debian-name "Debian">
<!ENTITY authors SYSTEM "authors.xml">
<!ENTITY legal SYSTEM "legal.xml">
More information about the Pkg-ocaml-maint-commits
mailing list