gnupg windows installer

[Jan-Oliver Wagner]

On Thu, Jan 04, 2001 at 11:46:56AM +0100, Jan-Oliver Wagner wrote:
> I am not sure why this all is a problem. Programs compiled
> with gcc under Windows seem to have no problem with paths:
> ls c:/gnupg/g*
> works as well as
> ls c:\gnupg\g*
> and
> ls c:\gnupg/g*
> 
> Seems that I must get into the gnupg source to learn more about
> the problem (fortunately gnupg is written in C, one of my preferred
> languages :-)

OK, what I found out is that

user at PASITHEA ~/project/gnupg/gnupg-cygwin
$ ./gpg.exe --homedir="D:\Programme\GnuPG" --help | grep Home
gpg: Please note that you don't have secure memory on this system
Home: D:\Programme\GnuPG

user at PASITHEA ~/project/gnupg/gnupg-cygwin
$ ./gpg.exe --homedir="D:\Programme\GnuPG"
gpg: Please note that you don't have secure memory on this system
gpg: D:\Programme\GnuPG/secring.gpg: keyring created
gpg: D:\Programme\GnuPG/pubring.gpg: keyring created
gpg: Go ahead and type your message ...

So Windows-style paths seem to work!
Found the hidden option --homedir in the source codes :-)

So, it is a problem of Registry reading ...
Sorry for the confusion.

Jan

-- 
Jan-Oliver Wagner               http://intevation.de/~jan/

Intevation GmbH	              	     http://intevation.de/
FreeGIS	                               http://freegis.org/