From: Gokturk Yuksek <gokturk@gentoo.org>
To: gentoo-dev@lists.gentoo.org, pr@gentoo.org
Subject: Re: [gentoo-dev] News item: changed default bedup configuration file in >=app-backup/burp-2.0.0
Date: Wed, 19 Apr 2017 15:39:00 +0000 [thread overview]
Message-ID: <94a1248a-38d4-28ba-8b14-4a844cfad3b2@gentoo.org> (raw)
In-Reply-To: <e54d8c2c-61d9-1f81-37d6-5d96fe872f00@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
> Display-If-Installed: app-backup/burp
Wouldn't you wanna limit this to <2.0.54 ? Otherwise this will pop up
for the consumers of 2.0.54 as well.
> /etc/burp/burp.conf .
You have an extra '.' at the end.
> maintaining old Gentoo behaviour would needlessly complicate the
> code.
I think upstream using the new path is enough justification, do you
really need to justify it any further?
> If you want to keep using burp-server.conf with bedup, you can
> specify it on the command line:
>
> bedup -c /etc/burp/burp-server.conf
Maybe it's better to also provide a one-liner of 'mv' for people who
just want to upgrade to the new path.
Overall, my impression is that people handle conf file changes in
pkg_postinst() with REPLACING_VERSIONS rather than news items. How fatal
are the consequences of not updating the conf file path? Would the
program abort or misbehave?
- --
gokturk
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEv2SYNjDGGh+3Be4QhPgC5cCIzjMFAlj3hIoACgkQhPgC5cCI
zjObuQf/fu6L0fhJU/C2jW1D2th3xD9UaB2/1n/Ow/9dAYU71JnB+FFkzGdRxEW+
O4/dN9FiY46rnetAuA4JjFHq4HovBslwnxunPOwVLTOfjPUuKcHSN1yEwdxRUBQH
MQFvSSmDqJ9kzoohRz2W+5ZDTCrl0qmxIs8tVeOV5mazIP6X6QuSkOHI6UkgqkMt
xnFJDHfLwCwWL63yQV67fCh72b8UcMQRnVJxysBkUjzL0ppRSX/4ZI1g5CAVFSdk
phKoUZgIVMunCs0eWgj5H6pXSyvcklMcRib+pQHB65GPPpMKkde4LNoyx6O8Mxa/
xa8rSUmxq35c42JpncTjPdSj4bmJzg==
=Qvh/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-04-19 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 14:18 [gentoo-dev] News item: changed default bedup configuration file in >=app-backup/burp-2.0.0 Marek Szuba
2017-04-19 15:39 ` Gokturk Yuksek [this message]
2017-04-19 19:55 ` Amadeusz Żołnowski
2017-04-20 8:10 ` Marek Szuba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94a1248a-38d4-28ba-8b14-4a844cfad3b2@gentoo.org \
--to=gokturk@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox