Re: [Caml-list] [ANNOUNCE] otags reloaded 3.12.1 for OCaml 3.12.1
Le 20/01/2012 16:25, Hendrik Tews a écrit :
> a first version of the otags package is at
>
> http://mentors.debian.net/package/otags
>
> I would of course be glad if one of you could have a look at it.
It looks like a hostile takeover, and you cannot do that without the
maintainer's agreement unless the package is orphaned. Please keep
"Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>" as
maintainer, and put your name in the Uploaders field instead (and update
debian/changelog accordingly).
You obviously redid the packaging from scratch. Please have a look at
the diff with the current package and consider merging. In particular:
- respect the original formatting in debian/control
- keep the Vcs-* headers. If you don't use Git, I (or someone else)
will update the repository
- keep debian/gbp.conf
Moreover, I saw that the debian/ repository is also part of the upstream
tarball. Keep in mind that it is completely ignored by Debian tools with
the 3.0 (quilt) format (only the one from .debian.tar.gz is taken into
account), which is a good thing. The rationale is that the upstream
Debian packaging is (conceptually) not the same as the one officially in
Debian (or in another dpkg-based distribution), each might evolve
differently and comparing both might not even make sense. Please keep in
mind the separation between both (yes, this is kind of schizophrenia :)
I am usually against putting the debian/ directory directly inside the
"upstream" tarball... OT, when the package is really Debian-specific, I
consider it acceptable to make the package native (i.e. no upstream
tarball), but this is not the case of otags.
> I have not yet integrated the update-otags script for tagging
> /usr/lib/ocaml. This has to wait until otags does not crash any
> more because of bogus locations (see ocaml bug #5159).
Even if you remove update-otags, you should keep the prerm script to
clean up after an upgrade from Squeeze.
> 1. I would like to have a dependency on camlp4-extra requiring a
> version >= 3.12.1 _and_ << 3.13. How can I express this?
As Ralf said, "camlp4-extra (>= 3.12.1), camlp4-extra (< 3.13.)"... but
why do you want the "< 3.13" part?
> 2. From other ocaml packages I saw that ${F:OCamlInterpreter} is
> a dependency that expands into nothing if native compilation
> is used and into ocaml-base-nox if bytecode compilation is
> used.
>
> However, this magic does only seem to work with passing
> additional -V options to dh_gencontrol and requires there a
> fairly verbose rules file. Is this right?
Indeed, you need to pass the -V option to have ${F:OCamlInterpreter}
expanded.
> I am using now ${ocaml:Depends}, which worked in my tests,
> although I couldn't find this feature in the man page.
${ocaml:Depends} includes the interpreter if needed.
${F:OCamlInterpreter} dates back to when ${ocaml:Depends} did not exist
and I think should no longer be used.
Cheers,
--
Stéphane
Reply to: