[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debian-emacs-policy



From: Rob Browning <rlb@cs.utexas.edu>
Subject: Re: debian-emacs-policy
Date: 13 Mar 1998 12:32:00 -0600

> >      I think it is better that debian-run-direcotires add 
> >      /usr/share/<emacs>/site-lisp/<package-name>/ to load-path 
> >      if /etc/<emacs>/site-start.d/NN<package-name>.el{,c} successfully loaded
> >       and /usr/share/<emacs>/site-lisp/<package-name>/ exists and is directory.
> > 
> > I agree.  This would, in some cases, simplify creating emacs add-on
> > packages quite a bit.
> 
> I don't think I want to do this.  I think I'd like to leave it
> completely up to the package maintainer to decide what should be added
> to the load path.
> 
> Consider, for example, a package that has all its files in
> /usr/share/<emacs>/site-lisp/<package-name>/lisp.  Why should
> /usr/share/<emacs>/site-lisp/<package-name>/ be in the load path?

Why don't decide which to be used for debian elisp add-on?

> Also a package might just load all it's code from the /etc/ file, so
> modifications to the load path would be superflouous.

Which elisp file should we set load-path for elisp-package?

/etc/<emacs>/site-start.d/NN<package>.el{,c} would not work
because debian-run-directories reset load-path after load it.

-- 
Fumitoshi UKAI / Debain JP Project


--
E-mail the word "unsubscribe" to debian-devel-request@lists.debian.org
TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to listmaster@lists.debian.org


Reply to: