Re: [AC21.5] Fix EMACSPACKAGEPATH
Vin Shelton <acs(a)xemacs.org> writes:
On 2/15/06, Michael Sperber
<sperber(a)informatik.uni-tuebingen.de> wrote:
> No, that should work.
> > [Installation]
> > Package path is
"~\\.xemacs;;e:\\XEmacs\\site-packages;e:\\XEmacs\\xemacs-packages".
>
> This is your build setting, though, right? (I.e. not what's set in
> the install kit.) What are the settings of the various
> configure-<xxx> variables for the install kit?
I'm not sure I understand the question. The installation kit will be
*built* on my machine with those settings, but will be installed
somewhere of the user's choosing. I want to build the kits on my
machine but enable the users to install them wherever they choose.
Yeah, but it seems you're compiling your own private package path into
the executable, which might surprise users. (And via the now obsolete
package-path setting, too.) Is that necessary?
It would still be helpful to know what the various configure-<...>
variables are set to in an XEmacs that's installed from the Windows
installer.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla