unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* Why a site-lisp directory in /usr/local/share/emacs/22.0.50/
@ 2006-06-14 14:59 stefano.sabatini-lala
  2006-06-14 22:31 ` Tim X
  0 siblings, 1 reply; 3+ messages in thread
From: stefano.sabatini-lala @ 2006-06-14 14:59 UTC (permalink / raw)


I'm trying to figure out how the load-path is formed, and the
documentation isn't very clear.

The default load-path should consist initially only by the directories:

<prefix>/share/emacs/site-lisp
for all the not-flavour-specific libraries, and
<prefix>/share/emacs/<flavour>
for all the flavour-specific libraries.

<prefix> is the value of the variable "prefix" defined in the emacs
Makefile (usually /usr/local/ for a local install).

So I don't understand why there is a site-lisp directory:
/usr/local/share/emacs/22.0.50/site-lisp

(which is actually empty), in the default flavour libraries dir
(/usr/local/share/emacs/22.0.50).

Is it simply some backward-compatible-messy-thing (I can happily delete
it) or is something that actually makes sense?

Thanks.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Why a site-lisp directory in /usr/local/share/emacs/22.0.50/
  2006-06-14 14:59 Why a site-lisp directory in /usr/local/share/emacs/22.0.50/ stefano.sabatini-lala
@ 2006-06-14 22:31 ` Tim X
  2006-06-14 23:07   ` Kevin Rodgers
  0 siblings, 1 reply; 3+ messages in thread
From: Tim X @ 2006-06-14 22:31 UTC (permalink / raw)


stefano.sabatini-lala@poste.it writes:

> I'm trying to figure out how the load-path is formed, and the
> documentation isn't very clear.
>
> The default load-path should consist initially only by the directories:
>
> <prefix>/share/emacs/site-lisp
> for all the not-flavour-specific libraries, and
> <prefix>/share/emacs/<flavour>
> for all the flavour-specific libraries.
>
> <prefix> is the value of the variable "prefix" defined in the emacs
> Makefile (usually /usr/local/ for a local install).
>
> So I don't understand why there is a site-lisp directory:
> /usr/local/share/emacs/22.0.50/site-lisp
>
> (which is actually empty), in the default flavour libraries dir
> (/usr/local/share/emacs/22.0.50).
>
> Is it simply some backward-compatible-messy-thing (I can happily delete
> it) or is something that actually makes sense?
>
> Thanks.
>

I think its there so that you have an easy way of installing your own
(possibly not distro packaged) emacs add ons which are specific to the
version of emacs your running. This keeps or your local add-ons
apart from distro supplied ones. If your have a /usr/local partition,
it also means you can do a complete re-install of emacs (or even your
linux distro) without impacting on stuff you have added by hand. 

If you put stuff you have installed from tar balls etc within the same
directory hierarchy as the distro packaged emacs, you can get problems
when upgrading the distro version as many package systems will assume
once all the packaged stuff is removed, directories are empty. If they
are not, the package management scripts can fail or possibly get into
a "confused" state.

Tim
 
-- 
tcross (at) rapttech dot com dot au

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Why a site-lisp directory in /usr/local/share/emacs/22.0.50/
  2006-06-14 22:31 ` Tim X
@ 2006-06-14 23:07   ` Kevin Rodgers
  0 siblings, 0 replies; 3+ messages in thread
From: Kevin Rodgers @ 2006-06-14 23:07 UTC (permalink / raw)


Tim X wrote:
> I think its there so that you have an easy way of installing your own
> (possibly not distro packaged) emacs add ons which are specific to the
> version of emacs your running.

In particular, bug fixes and features from future versions.

-- 
Kevin

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-06-14 23:07 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-14 14:59 Why a site-lisp directory in /usr/local/share/emacs/22.0.50/ stefano.sabatini-lala
2006-06-14 22:31 ` Tim X
2006-06-14 23:07   ` Kevin Rodgers

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).