Gotta disagree with you there.. a good Windows app won't use the
environment at all. Take a look at the environment of a typical Windows
server - the various services don't have any environment variables
related to them, it's all in the registry.
Writing something into HKEY_LOCAL_MACHINE\Software\PostgreSQL that says
where Postgres is installed would be reasonable.. at startup the Win32
code could simply read that variable from the registry and set it into
the environment so the rest of postgres can depend on it being in the
environment.
- Steve
-----Original Message-----
From: Merlin Moncure [mailto:merlin.moncure@rcsonline.com]
Sent: January 23, 2004 9:12 AM
To: Claudio Natoli
Cc: pgsql-hackers-win32
Subject: [pgsql-hackers-win32] Binary installer
Claudio Natoli wrote:
> > Clearly we will need an installer for a binary distribution.
The nullsoft installer is quite nice. Not sure about Microsoft .msi
packaging...I'm sure that's pretty easy to work with, too. The
installer should besides unzip, offer to run a few batch files (initdb,
etc), set up the environment, and offer set up the postmaster as a
service.
A good windows program has no internal dependencies on the registry.
Postgres is already set up to use the environment which is a more
flexible setup than the registry for servers.
Merlin
p.s.
Is there any way to keep mingw/msys from spamming console windows when
compiling? It's very irritating :(.
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly