[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [AUCTeX-devel] Usage of install.el
From: |
Ralf Angeli |
Subject: |
Re: [AUCTeX-devel] Usage of install.el |
Date: |
Sat, 24 Feb 2007 17:37:29 +0100 |
User-agent: |
Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.93 (gnu/linux) |
* Frank Küster (2007-02-24) writes:
> Ralf Angeli <address@hidden> wrote:
>
>> As far as I can see the intent is to extract a tar ball at a target
>> location, e.g. site-lisp, and then compile everything in place. My
>> thoughts about this are a bit ambiguous. On the one hand this
>> enforces the notion of a package keeping everything in one place.
>> This way it will also be easier to update or remove a package. On the
>> other hand this might leave some unwanted cruft in the target
>> location, e.g. distribution files like INSTALL or README. (Of course,
>> those might not be necessary anymore once something like install.el is
>> established.) And e.g. an info file might have to be copied to a
>> directory where the standalone info reader can find it nevertheless.
>
> Please also keep in mind people who want to create distribution packages
> (deb or rpm or similar):
>
> - Installation will be done in a temporary directory, before packing it
> up in the deb/rpm
As far as I understood Stefan in
<mid:address@hidden> that's supported.
> - Compilation will most probably be done at the time the deb/rpm is
> unpacked (otherwise we'd need one auctex package for each emacs flavor
> we ship, that could be xemacs21, emacs21, emacs22 and emacs-snapshot
> in Debian lenny).
Compilation is handled by install.el. You just have to call the
respective function when installing the package. (I have to check if
this works in batch mode, though.)
--
Ralf