[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bird-users
Subject:    Re: Default config file name 1.6 vs. 2.0
From:       Eugene Crosser <crosser () average ! org>
Date:       2019-01-28 16:16:01
Message-ID: 6c334341-d5e1-71fb-5671-bdd3185a0787 () average ! org
[Download RAW message or body]

[Attachment #2 (multipart/mixed)]


On 1/28/19 4:18 PM, Ondrej Zajicek wrote:

>> I would like to suggest to change the default name of the configuratio=
n file for
>> bird version 2.0.

[...]

> Well, workaround would be to have config files in separate files and
> /etc/bird.conf just a symlink, which can be simply changed after packag=
e
> upgrade / downgrade.

When you are using automation for configuration and package management,
such approach complicates the process a lot. Instead of just "apt
install <new or old package>" automation tool would need a distribute a
script and execute it before/after upgrading the package. And it has to
be specific for this particular package. It is not insurmountable, it
just seriously complicates otherwise trivial job of replacing the package=
=2E

If changing the name upstream is not possible now, maybe a good
enough(?) solution would be to "strongly encourage" package maintainers
to specify different path for the config file? I am interested in a
debian (stretch) package myself.

Regards,

Eugene


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]