Re: how can I prevent cdbs from stripping custom bytecode binaries?
On Wed, Apr 02, 2008 at 02:41:32PM +0200, Sven Luther wrote:
> Should we add this to the policy document ?
I've added a couple of lines about this to policy/chapter-progpack.xml
(and also removed the mention of lintian overrides, since it now
handles the case of ocaml bytecode executables).
The patch is attached, or I can commit it myself.
--
Eric Cooper e c c @ c m u . e d u
Index: chapter-progpack.xml
===================================================================
--- chapter-progpack.xml (revision 5413)
+++ chapter-progpack.xml (working copy)
@@ -75,10 +75,18 @@
</para>
<para>
- Bytecode programs which are compiled by <userinput>ocamlc -custom</userinput> must not be stripped. In particular, their package should be excluded from the <command>dh_strip</command> script. When compiled this way, an elf executable is generated containing the ocaml interpreter, and the bytecode of the program in a section which is removed when the program is stripped. For more information, see the bug <ulink url="http://bugs.debian.org/256900";>256900</ulink>. An override for the lintian warning is considered as acceptable in this situation.
+ Bytecode programs which are compiled by <userinput>ocamlc -custom</userinput> must not be stripped. In particular, their package should be excluded from the <command>dh_strip</command> script. When compiled this way, an elf executable is generated containing the ocaml interpreter, and the bytecode of the program in a section which is removed when the program is stripped. For more information, see the bug <ulink url="http://bugs.debian.org/256900";>256900</ulink>.
</para>
<para>
+When using <command>debhelper</command> directly,
+use the <option>--exclude</option> option to <command>dh_strip</command>
+to specify bytecode programs that should not be stripped.
+With <command>cdbs</command>,
+the variable <code>DEB_STRIP_EXCLUDE</code> should be used.
+</para>
+
+<para>
Bytecode programs should not be compiled for debugging, i.e. they should not
be compiled passing the <option>-g</option> option to
<command>ocamlc</command> (or <command>ocamlc.opt</command>).
Reply to: