From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:50920) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hOGtx-0003y3-Sm for guix-patches@gnu.org; Wed, 08 May 2019 03:22:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hOGtu-0002Pz-NL for guix-patches@gnu.org; Wed, 08 May 2019 03:22:05 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:46702) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hOGtu-0002Pk-Jt for guix-patches@gnu.org; Wed, 08 May 2019 03:22:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hOGtu-0005b0-FJ for guix-patches@gnu.org; Wed, 08 May 2019 03:22:02 -0400 Subject: bug#35544: [PATCH] services: dovecot: Rename auth-verbose-passwords?. Resent-To: guix-patches@gnu.org Resent-Message-ID: References: <20190503091039.12424-1-mail@cbaines.net> <87r29a5pt1.fsf@gnu.org> From: Christopher Baines In-reply-to: <87r29a5pt1.fsf@gnu.org> Date: Wed, 08 May 2019 08:21:01 +0100 Message-ID: <877eb1o1ia.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 35544-done@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > Christopher Baines skribis: > >> * gnu/services/mail.scm (dovecot-configuration)[auth-verbose-passwords?]: >> Rename to auth-verbose-passwords, and change the type to a string, as th= is >> parameter can take one of three string values. >> * doc/guix.texi (Dovecot service): Update the corresponding documentatio= n. > > I don=E2=80=99t use the Dovecot service but this LGTM. Great, I've pushed this now. > The question is whether it=E2=80=99s OK to break the API. I=E2=80=99d sa= y that with > proper documentation it probably is. Thoughts? > > Longer-term we=E2=80=99ll need a way to gracefully handle deprecation for= this > kind of change, probably at the level of the =E2=80=98define-record-type*= =E2=80=99 > kitchen sink. Yeah, I'm uncertain. For long running systems, it's probably good to update the packages, without having to adjust the service configuration for changes like this. If there was a "stable" channel to track, which didn't include updates to services, but did include important package updates, then that may be useful. Also, just making the errors relating to service configuration may be more impactful than adding extra deprecation support. Thanks, Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAlzSg11fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9Xf03g/8DWhkXDeS5nXmx+dl4NOBtBB1EZxe3J+/pSACdWvlvMw1Cua6RDD5sNqn LbRJsdubSu28dINTYwsmL9NYwhrf5GoUngEHe8Czhj6tG9IK5Z7OL1fuMx05osyc r9WzQT9zbw80bICWR55sUXFAAfZrWkS/qLGbMCU+VKIF2V0okhNWOV6iC7Guhq3j /6jQ4mxtEc6rlDvIa6ZW99OLHLJBv5c8xlUyzC7VKk8i9Nku2Z+tfrOxRckAXdXs YIJZZww3lavigb1nNFV5osych+Z9g8tTWmtvK82cd8JYtCDrRQ2xhANuSWaGciBd 5lLmuzS838ZhQ3lzDPs6vGNTB4Q3We4jyShzw5TmGGl4enHzGsTK9+4qTdEH15wq U1+X09mKNfPOWmNgNpcpLki0dg6cYPG+jMwOVq9VEf67keWvJD09gQ5fxPiVKvxP WBN2nEbFOpIZpLEFqtmxXIld45zYyLqPxgL1Lqwq/siOJi9gABoI72AqzcXh3lpu gyowuz5PF3BfmhhZqqnB2pdgF+Y1PRppNCgL/2AJphk0yz4FjHgnjTi1TawFeOHV 3026fGfabgxSheIVoIxvOLoAxUgqqbXBqcxoH0pTsuFLz6MaO8T2QOlDoXZuQq0K KbL5Hep+5HVnjtkrGDTDBBlhrdmAkGtZaRfzOtl0eSu92t3PE2w= =MeM7 -----END PGP SIGNATURE----- --=-=-=--