On Mon, Jan 1, 2007 at 23:26:30 +0100, Daniel Baumann wrote: > > Why? dpatch.make(7) says: > > Using dpatch.make is rather straightforward: one has to include > > the file in debian/rules, change the appropriate targets to depend on > > patch and unpatch, and that is all it takes. > > In fact, in /usr/share/dpatch/dpatch.make, the patch target depends on > > patch-stamp. > > excately. patch depends on patch-stamp, so why not call patch-stamp > directly? ;) > I think I disagree with this, patch-stamp is an implementation detail. > > Another question. The Debian OCaml Policy (section 2.2) says: > > > > A bytecode package must build-depend-indep on ocaml-nox-3.09.2 (or > > ocaml-3.09.2 if the program either uses the Graphics or the LablTk > > module). The current version number of OCaml should not be hardcoded > > into the build-dependency (this is a deviation from a practice which > > used be recommended but is depreciated now). Of course, if it is > > necessary to ensure that the version of OCaml has a certain value then > > version constraints can be used. However, this should be justified by > > the requirements of the compilation of the program. > > > > This is not clear to me. It says I should build-depend-indep on > > ocaml-nox-3.09.2. However, wouldn't this mean "hardcoding the current > > version number of OCaml into the build-dependency"? > > Currently, I just have "Build-Depends-Indep: ocaml-nox". > > some packages do have a versioned depends, such as "ocaml-nox (>= > 3.09.2)", but the ocaml policy says to have a "ocaml-nox-3.09.2" > depends. ocaml-nox-3.09.2 is a virtual package provided by the current > ocaml-nox package. > I think this might be a bug in the ocaml packaging policy. A build-dep on ocaml-nox is fine, I think, but if this is a bytecode program (which I don't know, I haven't looked at the package yet) it needs to have a runtime dependency on the current ocaml-base (or ocaml-base-nox) package (ocaml-base-nox-3.09.2 at the moment). I don't think there is a reason to hardcode the ocaml version number in the build dependencies. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature