On Sat, Nov 26, 2022 at 03:10:41PM +0100, Gert Doering wrote: > Instead of fully removing PORTS, keep "this is what you want to do for > porting OpenVPN to a new platform" section, and update the PLATFORMS > part to better reflect current status. > > Signed-off-by: Gert Doering <g...@greenie.muc.de> > --- > PORTS | 43 +++++++++++++++++++++++++------------------ > 1 file changed, 25 insertions(+), 18 deletions(-) > > diff --git a/PORTS b/PORTS > index ff76850d..b257c5d2 100644 > --- a/PORTS > +++ b/PORTS > @@ -11,20 +11,31 @@ Copyright (C) 2002-2022 OpenVPN Inc <sa...@openvpn.net> > > PLATFORM STATUS: > > - * Linux 2.2+ (supported) > - * Solaris (supported) > - * OpenBSD 3.0 (supported but pthreads are broken) > - * Max OS X Darwin > +Tier 1 platforms - actively tested for every source commit, across > +multiple operating system versions > + > + * Windows 7 and newer > + * Windows Server 2012 and newer > + * Linux 2.2+
Let's just use Linux. 2.2 is meaninglessly old at this point. > * FreeBSD > + * MacOS X macOS > + > +Tier 2 platforms - it worked at some point, but is not actively tested > +on "latest OS, latest OS libraries" so might break if larger changes > +are done on the platform side > + > + * OpenBSD > * NetBSD > - * Windows > - * 64 bit platforms -- I have heard reports that > - OpenVPN runs on Alpha Linux and FreeBSD. > - * ARM -- I have heard of at least one case > - where OpenVPN was successfully built and > - run on the ARM architecture. > + * DragonFly BSD > + * Solaris > + * AIX > + > +For underlying CPU architecture, everything 32 bit or 64 bit (Intel, AMD, > +ARM, PowerPC, SPARC*) should work fine. 16 bit Architectures are unlikely > +to work. > + > > -PORTING NOTES: > +PORTING GUIDELINE TO A NEW PLATFORM: > > * Make sure that OpenSSL will build on your > platform. Regards, -- Frank Lichtenheld _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
