Hi, On Wed, Mar 16, 2022 at 10:29:37AM +0100, Frank Lichtenheld wrote: > > As discussed on IRC, we need to build with the new security-fixed 1.1.1n > > release, and vcpkg port is not there yet. Somewhat annoying, we should > > find a better way to decouple "build" and "openvpn main repo" commits... > > We could always move the whole contrib/vcpkg-ports directory to a separate > repository, right? Or is there a strong technical reason why this should be > in the main repository?
Just for the sake of the archives - this is what we discussed in the
meeting yesterday, and the plan is
- "building openvpn should be possible from the openvpn repo, without
any extra submodules either way" - but will give the person building
the vcpkg default packages (like, 1.1.1m yesterday)
- "for release building", we add whatever is needed to the openvpn-build
repo, to do "take openvpn repo, add vcpkg port overlays for newer
versions etc." and build from there
so this patch will go away again, in the not so distant future.
(Thanks, Lev, for all the work on this)
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
