Interesting insight, Martin, good points, Alexander, I missed that post, that was the train of thought I was following as well. Are there any thoughts of integrating this to the main source tree or implementing something similar? Not having to deal with compiled packages is much tougher to maintain and streamline in production environments :) Thank you for your time, --Aris Lambrianidis Are there any thoughts of integrating On Jul 25, 2011, at 5:25 PM, Alexander V. Chernikov wrote:
On 25.07.2011 19:28, Martin Mares wrote:
Hello, world!\n
I was wondering whether an "include" general option could be implemented as to segment large BIRD configuration files to smaller parts, a lá BIND. This should be trivial to implement I suppose, and could really help with scripting and clarity. Actually I wrote about this several months ago: http://marc.info/?l=bird-users&m=130527511628462&w=2
Patch to 1.3.1: http://static.ipfw.ru/patches/bird_includes_20110513.diff
At the dawn of time, when we started thinking about BIRD configuration, we got the idea that if a config file were executable, it would be run and its output parsed -- this way, you could start e.g. with #!/usr/bin/m4 and have includes and macro processing.
Maybe it's too crazy, but still...
Have a nice fortnight