On 2/15/06, Michael Sperber <sperber(a)informatik.uni-tuebingen.de> wrote:
Thanks for the info!
Sure! Thanks for the help.
Vin Shelton <acs(a)xemacs.org> writes:
> Here is the directory structure I want to support; under a common
> root, I want to have the following directories:
> PROBLEMS etc/ i586-pc-win32/ info/ lisp/ lock/
> COPYING PROBLEMS etc/ info/ lock/
> Installation README i586-pc-win32/ lisp/
> Do you need more detail, or is that sufficient?
No, that should work.
> Package path is
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.
Typically, the users would install in:
with the package directories common to the installed 21.4. and 21.5
kits. There would be an install kit for 21.4 and a separate install
kit for 21.5.
Here's how kit generation works:
1. I configure, build and install a 21.5 version of XEmacs.
2. I run InnoSetup, which takes the installed 21.5 tree and makes a
setup kit (essentially a fancy zip file).
3. User downloads the kit, runs the setup kit and decides where s/he
wants to install the kit. The root of the installation directory
defaults to C:\Program Files\XEmacs, but could be anywhere of the
Is this what you wanted to know?