Re: AUCTeX configuration, hardwiring etc...

David Kastrup <[email protected]> writes:

> Hi folks, I have decided that we won't need all those special options
> after all.  Really none of them.
>
> Why?  Because we can make do by just making everything relative to
> lispdir, then using
>
> make install-el # installs in ${lispdir}/preview
> make lispdir=that install-elc
> make lispdir=whatever install-startup
>
> The only problem is that the startup file needs to do something like
>
> (defvar TeX-lisp-directory
>         (if (file-directory-p
>               (expand-file-name "auctex" (file-name-directory load-file-name)))
>             (expand-file-name "auctex" (file-name-directory load-file-name))
>            @lisplispdir@))
>
> Which is sick.  So maybe we need something like
> --with-package-lispdir[=auctex]
>
> as a configure option that will hardcode
>
>       (expand-file-name "auctex" (file-name-directory load-file-name))
> into @lisplispdir@
>
> Sigh.

Ok, still in "think!" mode.  How about having the startup file
carrying

(defvar TeX-lisp-directory
   (expand-file-name @lispextralispdir@
     (file-name-directory load-file-name)))

Then we have an option --with-extralispdir[=auctex] to configure.
Extra means "outside of load-path" with a bit of fantasy.  If the
filename is absolute (which is fine for deb and RPM), the
load-file-name has no effect.  If it is relative (for stuff like
XEmacs packages or when rolling a prepackaged Emacs that is installed
into unknown territory), one can use "." to get the same directory as
the startup file (which gets placed in lispdir).

Does this sound like a good scheme?

Uwe, I don't know why I did not see your posting from 0207, maybe I
have skipped over it and accidentally removed it or whatever.  It has
Dejavu all over it for a different reason: I seem to remember that we
had pretty much the same discussion previously and code was placed
into the autoconf stuff.  Maybe it was in the preview-latex version
and got overwritten again by the AUCTeX variant.  Anyhow, the only
sensible thing to place stuff in by default is site-packages.  It has
_always_ been the case that defaults for autoconf are for site-wide
installation (corresponding to a prefix of /usr/local/ commonly): it
is customary to be able to do make as a normal user, and then install
with sudo make install or similar.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum