Santiago Vila <[EMAIL PROTECTED]> wrote: > Peter S Galbraith wrote: > > Quick questions: > > > > debian-emacs-policy says: > > > > D) Each add-on package must declare relevant dependencies on other > > packages (including other add-on packages). Note that add-on > > packages should not depend on emacsen-common directly, but rather > > on either the virtual package "emacsen" (see below), or some > > appropriate combination of flavors (i.e. Depends: emacs20 | > > emacs19). In addition, any tools needed by the install/remove > > scripts must be listed as package dependencies. For example, > > many add-on packages will probably use make in the install > > script, so they need to add "Depends: make" to their control > > file. emacsen-common will make sure that the install/remove > > scripts are ordered to respect inter-add-on package dependencies. > > > > 1- So _can_ we depend directly on emacsen-common (Note that I wasn't > > doing that for a larger package that contained an Emacs mode, so I've > > learned something already). > > Yes, I think policy should allow such dependency for packages containing > some emacs bits but that are completely usable without the emacs bits > (i.e. they contain other functionality other than the emacs part). > > (gettext comes to mind :-).
I agree. > > 2- 'install' is in the package 'fileutils' and not 'make'. Is that what > > was meant here? > > It refers to the /usr/lib/emacsen-common/packages/install/<package> script, > provided by a <package> which uses emacsen-common infraestructure. Makes sense now that I re-read it. Thanks, Peter
