Rex Dieter <[EMAIL PROTECTED]> writes: > Understand that our motifivations are entirely different, as my primary > intention is to create a package that *administrators* install that > users merely "use".
I think I want this too. But, if the users want to install the software at home, how should they proceed? > My installer only looks in > %emacs_dir%\site-lisp > Program Files\Emacs\site-lisp I think it was confused by my existing emacs installation. I don't know how it could be however? I have no %emacs_dir% variable. I think it's a great way to do it. But should Program Files\Emacs\site-lisp be either Program Files\Emacs\setup\site-lisp or Program Files\Emacs\emacs21.3\site-lisp? Is this what makes it fail as shown above? > The latter being pretty much absolutely required (IMO), so that add-on > packages can have a known-ahead-of-time location to install lisp > packages and startup/inits in site-start.d. Will it work if users cannot write in Program Files\Emacs\site-lisp? -- Brian (remove the sport for mail) http://www.et.dtu.dk/staff/be/be.html
