From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1DCDC139694 for ; Wed, 19 Apr 2017 15:39:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 024C3E0C3F; Wed, 19 Apr 2017 15:39:07 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B6A73E0C11 for ; Wed, 19 Apr 2017 15:39:06 +0000 (UTC) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3E42B209DB; Wed, 19 Apr 2017 11:39:06 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Wed, 19 Apr 2017 11:39:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=UkYyUZj2aG9UFm4UU4gbwNa/PhtLgBkkSdoecmeDw80=; b=VRvrlaNC 09x/3To7r+dEnsL8Vd233d3cuNhbLI2djyxtOUIq08lp1eruGSZuKZ5Yecn9CxOh 6SishOl/4EO+KD+0JV7b+GmfrG3KlPMZp4DEshS+lUz0IioQyyKWfg6rWCejBl7V vp2bhwvXaMPvXKq4wvlj6GwJmuI4Jx3lmtPpHUoiBrvwX6owVsxdM21xB467QO/h /UPDxzaAXMteS1UMEfA/FKu96ttJQodTJS1X6jWkaZNqkZEtF6bWHR9+slqLseTX iIO4/LO0SV85IBikF+PZYem4k6v7TcaWZdzD6JgQGGNImF/wQIlUVz/ZD94pFA2c NjhD1VrNjpYS/w== X-ME-Sender: X-Sasl-enc: 2pZphV7nAMyXBnFuyy33Gsi8xz2WP3IX6pt+jDjacW/2 1492616345 Received: from [127.0.0.1] (atlantic850.dedicatedpanel.com [85.25.103.69]) by mail.messagingengine.com (Postfix) with ESMTPA id C10DB2478D; Wed, 19 Apr 2017 11:39:04 -0400 (EDT) From: Gokturk Yuksek Subject: Re: [gentoo-dev] News item: changed default bedup configuration file in >=app-backup/burp-2.0.0 To: gentoo-dev@lists.gentoo.org, pr@gentoo.org References: Message-ID: <94a1248a-38d4-28ba-8b14-4a844cfad3b2@gentoo.org> Date: Wed, 19 Apr 2017 15:39:00 +0000 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 66862cb4-2437-4845-b12d-41c72cf2110b X-Archives-Hash: 8a91c1a70e5f8de06a295652f6eef95f -----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-----