Default config file name 1.6 vs. 2.0

[Eugene Crosser]

Hello,

I would like to suggest to change the default name of the configuration file for
bird version 2.0.

The two bird versions cannot use the same file because of syntax change. And
some of us distribute the file via configuration management tools (like ansible
etc.). This makes upgrade path rather difficult and unnecessarily error-prone:
you need to synchronize exchange of the version of the configuration file with
upgrade (or downgrade! That can be necessary too!) of the bird package.

Whereas if different versions used different files, you could distribute both
files with you configuration management tool in advance, and then gradually
upgrade the package, with easy rollback if things do not go well.

Even if configuration management is not used, it is still more convenient to be
able to start one or the other version of the daemon without the need to specify
alternative configuration, or replacing the file.

Thanks for consideration!

Eugene

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20190126/0ac2568b/attachment.sig>