From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NvXPQ-0006ha-Q0 for garchives@archives.gentoo.org; Sat, 27 Mar 2010 14:54:44 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9C587E0917; Sat, 27 Mar 2010 14:54:43 +0000 (UTC) Received: from petteriraty.eu (host.petteriraty.eu [188.40.80.83]) by pigeon.gentoo.org (Postfix) with ESMTP id C1631E08FF for ; Sat, 27 Mar 2010 14:54:38 +0000 (UTC) Received: from [10.0.1.11] (qiw3.kyla.fi [82.130.46.203]) by petteriraty.eu (Postfix) with ESMTPSA id 210892A808 for ; Sat, 27 Mar 2010 14:54:38 +0000 (UTC) Message-ID: <4BAE1C33.6060604@gentoo.org> Date: Sat, 27 Mar 2010 16:54:43 +0200 From: =?UTF-8?B?UGV0dGVyaSBSw6R0eQ==?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.8.1.23) Gecko/20090916 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 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 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] RFC: changing ssl use flag descriptions and unify behavior X-Enigmail-Version: 1.0.1 OpenPGP: id=B8E4ECF0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig9D40E1DAA3AA320CE3AD7FF9" X-Archives-Salt: 949dd5d2-e7a5-4d9e-b052-12a121e48916 X-Archives-Hash: fb91ff64873f2dc6d21b83d6d442bde0 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9D40E1DAA3AA320CE3AD7FF9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable See this thread for background: http://archives.gentoo.org/gentoo-dev/msg_0673a33fe75961e510872fd2c1044ce= d.xml I think we should go through all the ssl use flag using packages and unify the use flag descriptions and behavior to the following standing policy (handed down probably): 1) packages always have the general ssl use flag to control whether to enable ssl at all 2) If the package supports multiple backends then there's use flags for gnutls, openssl or nss. EAPI 2 use defaults will be used to communicate upstream defaults if any. If they are all turned of select the default (ssl being on). No objections and I will open a tracker a week from now and let's see who joins up to go through packages and open bugs. Regards, Petteri --------------enig9D40E1DAA3AA320CE3AD7FF9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJLrhw2AAoJEPeUsk245OzwZnYP/0nlsKdQ/TXQO1Ar+T+gG6zS bIM1mJlCnFmYv9/pqk8jsuqDAXxaPwWj7X1/CWPdkC+y2KcHzkZl/yCDXtwCO4SO +8zE3c6oTsqqRdIIefHvndNerMRv9SqvTcsT9i7XRvxEM/C6UoJa8aAyX8ua5Mde OS1GwghNcEiWlPBoVkNHptFar3PUcuslDMl1+TGf0hZV18b7weVVFjFjmDS2VLPq JMQipSJPRwDZnzfBBaljcHbmGjjygCYP5an6nnHKhBX2PvRWPcoCCd2hyo4pylnc 8BBwpWN1m5BRf9k4HzRV5L5YFVCs0zrnTPlAIFYWrWK4ssRg26c2MnYqJ+cHIHRY EFIGlqyqgQHEs6EMjpcN72VbQnqPLQmy+dv2OycFnw5PPER5qlFDae+kryikknT+ Kgjqb4p+4Stw1V//2I6UCnOpTu6z1/xzyZGDToS+HVVAuA7k9XyCMGpsk+ZWdNlM KJG+BWoNE4O2NnrMa9l+ks3loCWo+QBztHqHzHarzVlEljYSHfRq0vO+BykbsXYm eSBlwk0qoNjTCKHhGr04nkFJufSHoUvjQbKpOj6G6/+hQTZtqhrjIGCpeJBp7epl KEoK4vvIrmdvzbr5HVxNGw9iLBOftAwzVpzHCilm245lowDYyle9KdT5kVsMURRV fgLfFLYhDWELLfQxGN9k =4I3o -----END PGP SIGNATURE----- --------------enig9D40E1DAA3AA320CE3AD7FF9--