BSD is the only platform though that this applies to. All other platforms have either moved onto .NET Core or are already running newer versions of mono. So now at this point it creates a difficult situation where keeping the server targeting older libraries is hurting the other platforms.
SecureChannelFailure on FreeNAS
Posted 29 May 2018 - 09:01 PM
Directly from the mono site in it's section regarding BSD
It is typically recommended that BSD users NOT download the standard source tarball from the Mono download page and attempt to build/install it but use their ports system instead. The Mono ports typically contain platform specific patches which have either not been merged upstream or to work around idiosyncrasies in the system.
The port does seem to be regularly maintained with a minor update done on May 9. The build went from 126.96.36.199 to 188.8.131.52 on Jan 30. That doesn't give me much faith that 5.4 is around the corner since 5.4 was released in Oct 2017, a good 3 months before the port tree moved to 5.2.
Posted 29 May 2018 - 11:48 PM
Yea we have to move forward though. We do have a build developer that can potentially help with the 5.4 port, but we already have a lot for him to do as it is so I'm not sure it will happen in time for the next server release. We can give it a little while longer and then if it doesn't look like anyone in the BSD community is going to take on the 5.4 port, then we can have him do it.
Or by that time the .net core build process will be easier and friendlier and then we can just use that.
- Baenwort likes this
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users