On Thu, Oct 27, 2005 at 06:43:58PM -0400, Joey Hess wrote: > > Well, libXXX-ocaml is just a package on which dh_ocaml has nothing to > > do. If you like we can add a warning for this case, or, better a warning > > for all packages on which dh_ocaml has nothing to do. > Ok then the problem is someone who writes dh_ocaml -plibXXX-ocaml-dev in > their rules file.
It does what is supposed to (act on libXXX-ocaml-dev) and it also create substvar for libXXX-ocaml. What I can do to avoid the latter part is to store that info somewhere (a file in debian/ perhaps) and fill the substvar only when dh_ocaml is invoked on libXXX-ocaml. Such a behaviour is acceptable for me. Is it for you as well? Still, the causal requirement that dh_ocaml must be invoked first on the -dev part remains. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!-
signature.asc
Description: Digital signature
