Maintenance of the current radiusclient codebase
Alan, Thank you for the patches, but I'm confused. If the plan is to replace radiusclient completely within a few months with code that is currently being developed, why patch the current code with patches more than a year old? When you announced that you would be replacing radiusclient, I assumed that a separate maintainer for the old codebase would not be needed. Thank you again - Larry On Sat, Jul 09, 2011 at 11:34:47PM +0200, Alan DeKok wrote:
More patches.. From: Alex Massover <alex@jajah.com> To: FreeRadius developers mailing list <freeradius-devel@lists.freeradius.org> Date: Tue, 2 Mar 2010 17:39:15 +0200 Subject: RE: radiusclient thread-safety ....
freeradius developer/user identity wrote:
Thank you for the patches, but I'm confused. If the plan is to replace radiusclient completely within a few months with code that is currently being developed, why patch the current code with patches more than a year old?
For one, the patches are still useful. There are a lot of applications using the existing freeradius-client library. It will be a *long* time before those applications get re-written. So there's still a need for updated releases.
When you announced that you would be replacing radiusclient, I assumed that a separate maintainer for the old codebase would not be needed.
The new library is *not* BSD licensed. Parts of it may be in the future. But nothing is set in stone, due to commercial / legal issues. And those are largely out of my control. Having an updated freeradius-client library would be valuable. Alan DeKok.
participants (2)
-
Alan DeKok -
freeradius developer/user identity