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 1NvXFs-0005Xu-Be for garchives@archives.gentoo.org; Sat, 27 Mar 2010 14:44:52 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1CE79E07FD; Sat, 27 Mar 2010 14:44:49 +0000 (UTC) Received: from petteriraty.eu (host.petteriraty.eu [188.40.80.83]) by pigeon.gentoo.org (Postfix) with ESMTP id 9BC68E07A7 for ; Sat, 27 Mar 2010 14:44:41 +0000 (UTC) Received: from [10.0.1.11] (qiw3.kyla.fi [82.130.46.203]) by petteriraty.eu (Postfix) with ESMTPSA id E795F2A808 for ; Sat, 27 Mar 2010 14:44:40 +0000 (UTC) Message-ID: <4BAE19DE.70206@gentoo.org> Date: Sat, 27 Mar 2010 16:44:46 +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: Re: [gentoo-dev] when to use a function and an implementation use flag. References: <1269455454.31227.12.camel@lillen> In-Reply-To: <1269455454.31227.12.camel@lillen> X-Enigmail-Version: 1.0.1 OpenPGP: id=B8E4ECF0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig15892F77C0973808E3AA7FF3" X-Archives-Salt: 726598ed-25b0-4aa0-8b5a-9c39b492ac33 X-Archives-Hash: 0101af709ca8d751b4765685007b6d39 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig15892F77C0973808E3AA7FF3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 03/24/2010 08:30 PM, Peter Hjalmarsson wrote: > For qemu-kvm the problem is that there is only one implementation (i.e.= > gnutls), and if I want to have ssl support I have to enable gnutls for > this package. In this case the ebuild should have only ssl use flag. > When I wrote a bug about this I got a rather short reply from maintaine= r > about pointing me to the policy about this. Where did he point you to? > So I have a question: > Is there no policy about this? The policy is that USE=3D"ssl" controls whether to enable ssl support in general. Then the specific use flags like gnutls and openssl control what implementation to use if the package supports multiple. USE=3D"ssl" --> should always give you ssl support > If there is could someone please point me towards it and also it in tha= t > case may be time to update the gentoo development guide. >=20 > [1] > http://devmanual.gentoo.org/general-concepts/use-flags/index.html#confl= icting-use-flags >=20 If you read the example code you see what I said is already done in the example code. Opened a bug for qemu-kvm: http://bugs.gentoo.org/show_bug.cgi?id=3D311627 Opened a bug for repoman: http://bugs.gentoo.org/show_bug.cgi?id=3D311629 Regards, Petteri --------------enig15892F77C0973808E3AA7FF3 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/ iQIcBAEBCAAGBQJLrhnhAAoJEPeUsk245Ozwf5oQAKNY7EavS4BWeVSVvhRUl1xq 7MD6rs79jTELyhGaOQn7BA5m/wcnUl+dJONDHyCW/z76Pb+lhFo3p2/ewKbv3hjt zU8RskTZ5RL3vG92E2OLe+jGm7UWB4lb7SfMWgcJ0nAuEmmlbi4pLK03rijrkiGC 2iKAD48lNDN1EXsA8nBOhP2bFcEOvTr7rFQnP+LtY6ibYCSllfZNDs0gcZge6kXT r6pYvkCNxrYgNl97EXTp55Ed7Qia32yIkn8NjVLKIfT5fIX7yOewIuFZGqA90MpK CLfyxft6brNRw2H2z+YZJT6aJc774PduBf0udm1FGi0Gw5ALeNWHLdZV1libR4zu nU0BX3JTsgHOVf5K0Nl9EFnmHX/vpYtOIFBbpOA+XoPgz+5JUw/3NHvLZJUYyFbD PKdcscT6OhO+8Ri3g/S+lGRyPU6uKOZJwkUBkpNtleCkahRb3pJ7nIZMDeJgX5sY vWXcpiIZ/0cnm/1q8URAfRDMwjWybgBoKvgx6q7eIAMw+Fq/NHVj8MmZKaswU4WO I8vpAOXFt9u7Q8pcwc0iM1X1VnYRa5jbskf703MdD1pElLX6o+JpLwaHhoBTihYF CIQ+optXWK+6PoaZ3ime30C9kLJjL5OhbMVWQnW4ma5QBPOPBR7PL+kORuSPKkWo StrqwYJEJbz8q1Xiig2Y =54+1 -----END PGP SIGNATURE----- --------------enig15892F77C0973808E3AA7FF3--