"James R. Van Zandt" <[EMAIL PROTECTED]> wrote: > Frank Küster writes: > >> Why does this package have a Pre-depends on Emacs at all? It doesn't >> even have a preinst script. > > Policy says > > Sometimes, a package requires another package to be installed _and_ > configured before it can be installed. In this case, you must specify > a `Pre-Depends' entry for the package. > > Installation of emacspeak involves byte-compiling many .el files using > each installed version of emacs. Doesn't this require that emacs be > installed and configured?
I don't think so, I think a Depends would be sufficient: ,---- Policy 7.2 ---- | Depends | This declares an absolute dependency. A package will not be | configured unless all of the packages listed in its Depends field | have been correctly configured. | | [...] | | The Depends field should also be used if the postinst, prerm or | postrm scripts require the package to be present in order to | run. Note, however, that the postrm cannot rely on any | non-essential packages to be present during the purge phase. `---- As far as I can see, emacs is only called in postinst, and if emacspeak depends on emacs, emacspeak's postinst will not be run unless emacs is working. A pre-depends would only be needed if the preinst script would need an other package (or if the unpacking itself depends on some particular version of the involved commands, like dpkg). Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
