> Hello.
>
> I have re-read the logs for this bug from the beginning, and I see
> that I have been wrongly assuming (sorry!) that a Depends: emacsen-common in
> gettext would force the user to install some emacs flavour, but in fact
> emacsen-common just says:
>
> Depends: bsdmainutils
>
> Just in case I'm missing anything: Am I right that it's completely
> possible to install emacsen-common and not installing any emacs flavour?
>
> [ emacsen-common is a relatively small package. Making gettext to
> depend on it, even if you don't plan to use emacs po-mode at all,
> would not be such a tragedy ].
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).
2- 'install' is in the package 'fileutils' and not 'make'. Is that what
was meant here?
Peter
