Per-version templates #206
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…file based on the freeradius version
|
I like the idea. Hopefully it won't cause too much of a burden of maintenance. Also please be sure to document how a new set of templates can be added e.g. from the FreeRADIUS source when there is a new release that requires changes 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a work in progress PR for using templates per-version of FreeRADIUS.
The intent is to have templates in a folder structure, so that given a version say 3.0.16, we first look for a template for version 3.0.16, then for any 3.0.x version prior to 16 (so if we have say, 3.0.12 it will be used before 3.0), then 3.0, then 3.