On 23 Jan 2014, at 17:24, Alan DeKok <aland@deployingradius.com> wrote:
Phil Mayers wrote:
And the dictionaries. Maybe a special comment:
# dict version=x.x
That's possible. The simplest thing is to update a special value in the dictionary files. It's awkward, but really only necessary for every release.
Probably easiest just to add a VERSION keyword and check it's value against RADIUS_VERSION any time it's found in a dictionary. Just adding VERSION to share/dictionary will solve most versioning issues.
The answer is probably "no that's crazy" but I don't suppose ABI / symbol versioning helps here?
Some. The issue is that we make changes to internal data structures. So the old libraries aren't really compatible with the new binaries. The typical library versioning approach isn't fine-grained enough. And symbol versioning doesn't deal with changes to data structures.
Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2