| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
> Display-If-Installed: app-backup/burp |
| 5 |
|
| 6 |
Wouldn't you wanna limit this to <2.0.54 ? Otherwise this will pop up |
| 7 |
for the consumers of 2.0.54 as well. |
| 8 |
|
| 9 |
> /etc/burp/burp.conf . |
| 10 |
|
| 11 |
You have an extra '.' at the end. |
| 12 |
|
| 13 |
> maintaining old Gentoo behaviour would needlessly complicate the |
| 14 |
> code. |
| 15 |
|
| 16 |
I think upstream using the new path is enough justification, do you |
| 17 |
really need to justify it any further? |
| 18 |
|
| 19 |
> If you want to keep using burp-server.conf with bedup, you can |
| 20 |
> specify it on the command line: |
| 21 |
> |
| 22 |
> bedup -c /etc/burp/burp-server.conf |
| 23 |
|
| 24 |
Maybe it's better to also provide a one-liner of 'mv' for people who |
| 25 |
just want to upgrade to the new path. |
| 26 |
|
| 27 |
Overall, my impression is that people handle conf file changes in |
| 28 |
pkg_postinst() with REPLACING_VERSIONS rather than news items. How fatal |
| 29 |
are the consequences of not updating the conf file path? Would the |
| 30 |
program abort or misbehave? |
| 31 |
|
| 32 |
- -- |
| 33 |
gokturk |
| 34 |
|
| 35 |
-----BEGIN PGP SIGNATURE----- |
| 36 |
|
| 37 |
iQEzBAEBCgAdFiEEv2SYNjDGGh+3Be4QhPgC5cCIzjMFAlj3hIoACgkQhPgC5cCI |
| 38 |
zjObuQf/fu6L0fhJU/C2jW1D2th3xD9UaB2/1n/Ow/9dAYU71JnB+FFkzGdRxEW+ |
| 39 |
O4/dN9FiY46rnetAuA4JjFHq4HovBslwnxunPOwVLTOfjPUuKcHSN1yEwdxRUBQH |
| 40 |
MQFvSSmDqJ9kzoohRz2W+5ZDTCrl0qmxIs8tVeOV5mazIP6X6QuSkOHI6UkgqkMt |
| 41 |
xnFJDHfLwCwWL63yQV67fCh72b8UcMQRnVJxysBkUjzL0ppRSX/4ZI1g5CAVFSdk |
| 42 |
phKoUZgIVMunCs0eWgj5H6pXSyvcklMcRib+pQHB65GPPpMKkde4LNoyx6O8Mxa/ |
| 43 |
xa8rSUmxq35c42JpncTjPdSj4bmJzg== |
| 44 |
=Qvh/ |
| 45 |
-----END PGP SIGNATURE----- |
Archives