Hi, On Mon, Jun 07, 2021 at 10:34:36AM +0300, Lev Stipakov wrote: > 3) do nothing and have those ports as part of openvpn repo. vcpkg > supports "ports-overlay" , so > I see nothing wrong or "hacky" with this approach. I see you point > about having dependencies build scripts > as part of openvpn repo. However in this case script is fairly trivial > and mostly consists of boilerplate code: > > https://github.com/lstipakov/openvpn/blob/dco180521/contrib/vcpkg-ports/pkcs11-helper/portfile.cmake > > To my understanding this part of openvpn is fairly static, so I don't > expect much maintenance burden for it, if any. In any case I > volunteer to take care of it.
For now, this sounds like the easiest way forward...
> 4) submit pkcs11-helper and ovpn-dco-win ports to vcpkg upstream and
> then remove those from openvpn.
... and when the dust has settled, move here...
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
