On Friday, January 18, 2002, at 10:41 AM, David R. Morrison wrote:
> First, are you making the built-in /usr/bin/emacs part of this system?
> Will add-ons automatically get byte-compiled for it?
That would be tough to do cleanly. In order for a given emacs binary to
hook into the emacsen-common s
In the debian system, all of the flavors of emacs are made to depend on
this emacsen-common package, and they all "Provide: emacsen". This
includes xemacs. In the fink world, it might hopefully also include
the Aqua version of emacs. After all, if I want to use an emacs addon,
I probably want t
>Thanks! Just trying to absorb all of this! It looks like a very elegant
>solution.
>
>I have a few questions.
>
>First, are you making the built-in /usr/bin/emacs part of this system?
>Will add-ons automatically get byte-compiled for it?
>
>Second, do you anticipate that all of fink's emacs pac
Christian Swinehart <[EMAIL PROTECTED]> wrote:
> The solution that the debian project has settled on is to use the
> emacsen-common package which handles byte-compiling for all installed
> copies of emacs. So far I've converted the emacs20 and emacs21 packages
> to work with it (and I would pr
The solution that the debian project has settled on is to use the
emacsen-common package which handles byte-compiling for all installed
copies of emacs. So far I've converted the emacs20 and emacs21 packages
to work with it (and I would presume that getting xemacs to consult it
as well wouldn'
My pari-gp package uses emacs to byte-compile a .el file during installation.
To implement this properly in fink, I have to be sure that the result will
be the same if the package is installed on different machines.
I was using BuildDepends: emacs, but Max got me to change that to
BuildDepends:
