Hi, On Tue, Nov 23, 2021 at 01:39:16PM +0200, Lev Stipakov wrote: > > Can our installer use "custom locations", like "install all our software > > to "d:\mystuff\openvpn\"? > Yes.
OK.
> > In that case, built-in paths won't work well (as was pointed out in the PR,
> > to my dismay).
>
> We could use something like C:\Windows\System32\SSL ?
We could, but then "special openssl.cnf for openvpn" might get in the
way of "special openssl.cnf for someone else's OpenSSL binary", so maybe
not such a good idea...
> One could install Windows to a different drive, but the first line of defence
> could be a path defined by env variables.
>
> > > 2) use env variables for openvpn and openvpn-gui ?
> >
> > I think that this might be the most flexible and robust approach.
>
> On startup we could read the installation path from
> HKLM\SOFTWARE\OpenVPN and assume
> something like <installation-path>\ssl\openssl.cnf ?
To me, this feels like the least annoying way forward... and then we can
also stop worrying about any future changes on the vcpkg side (even if
they accept the PR now, they might rebuild their build script, breaking
things again).
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
