On Wed, Jul 07, 2010 at 12:57:19PM +0200, Agustin Martin wrote:
> > > lisp stuff in a package whose main use is not Emacs should be used if
> > > an emacsen package is installed and ignored otherwise. There is nothing
> > > wrong
> > > with that. Even if /var/lib/emacsen-common/installed-flavors w
Ian Jackson wrote:
> Rob Browning writes ("Re: RFC: relaxation of debian-emacs-policy dependency
> requirements"):
> > If the package doesn't need to use any of the emacsen-common build
> > infrastructure (doesn't need to byte-compile for each flavor, etc.),
> > then it doesn't need to have any
On Tue, Jul 06, 2010 at 10:46:57PM -0500, Rob Browning wrote:
> Ian Jackson writes:
>
> > Rob Browning writes ("RFC: relaxation of debian-emacs-policy dependency
> > requirements"):
> >> After some investigation, it looks like we might be able to change
> >> policy to just require add-on package
On Tue, Jul 06, 2010 at 10:54:33PM -0500, Rob Browning wrote:
> Agustin Martin writes:
>
> > On Tue, Jul 06, 2010 at 11:51:06AM +0100, Ian Jackson wrote:
>
> >> Why should a package which happens to also ship some elisp need to
> >> depend on any Emacs package at all ? What will go wrong if the
Rob Browning writes ("Re: RFC: relaxation of debian-emacs-policy dependency
requirements"):
> If the package doesn't need to use any of the emacsen-common build
> infrastructure (doesn't need to byte-compile for each flavor, etc.),
> then it doesn't need to have any emacsen-related dependencies --
5 matches
Mail list logo
