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 1OkjwD-00066x-Fq for garchives@archives.gentoo.org; Sun, 15 Aug 2010 20:36:13 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2BA4CE06EE; Sun, 15 Aug 2010 20:36:10 +0000 (UTC) Received: from mail-fx0-f53.google.com (mail-fx0-f53.google.com [209.85.161.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 336F7E0534 for ; Sun, 15 Aug 2010 20:36:01 +0000 (UTC) Received: by fxm15 with SMTP id 15so3377723fxm.40 for ; Sun, 15 Aug 2010 13:36:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:disposition-notification-to :mime-version:content-type:content-transfer-encoding:message-id; bh=1Fw6DCvYGLFIVhHf2jV72Xhb4d6i9f/wBdCJTJZwLdg=; b=D7ZVeAILPSRy+r7ECjvaFLxU3N8tgDEUCl11qf5GNHYbFMEcEqaSUDB83ZCfSIkAzv KfeVGI5XyO+3tyhpmpUhOD/EWYYyJW564LPMgwdQXjC6avGxqf/paGM5PLf2s3o/qjBT y737wZ75pFEiimPZ8tCJwlpe8R8cerGTnMndE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to :disposition-notification-to:mime-version:content-type :content-transfer-encoding:message-id; b=lBfDWPsdtir2QKeL6vmQaNIAC2l1tpO3zewTvsWsCdCeY9OyrrAZStjqZgN8Ijdg6C 0ynPN21lvJiTDIlrw6uIW6wPSsob/C9ZJozCuy8a+N1pIE6JYaZS6gPZzWoHS76B161p /aRWXYYn7x8g08HNe8e2434kpHLynKhDS4XlI= Received: by 10.223.118.211 with SMTP id w19mr4448627faq.19.1281904560512; Sun, 15 Aug 2010 13:36:00 -0700 (PDT) Received: from lebrodyl.localnet (azw111.neoplus.adsl.tpnet.pl [83.27.160.111]) by mx.google.com with ESMTPS id 10sm2127247fax.42.2010.08.15.13.35.58 (version=SSLv3 cipher=RC4-MD5); Sun, 15 Aug 2010 13:35:59 -0700 (PDT) From: Maciej Mrozowski To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Why (i.e. USE="openssl" instead of USE="ssl") Date: Sun, 15 Aug 2010 22:35:57 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.34-gentoo-r1; KDE/4.5.0; x86_64; ; ) References: <1281785177.6299.58.camel@lillen> <4C6681E3.2040006@gentoo.org> <1281803299.6299.69.camel@lillen> In-Reply-To: <1281803299.6299.69.camel@lillen> 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 Content-Type: multipart/signed; boundary="nextPart14408288.ncmnURfE8G"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201008152235.57639.reavertm@gmail.com> X-Archives-Salt: 3e514ee6-c846-4dfc-a44c-4abd51c5418a X-Archives-Hash: 385a3bb5403adeeea8ba0395962f38a5 --nextPart14408288.ncmnURfE8G Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Saturday 14 of August 2010 18:28:19 Peter Hjalmarsson wrote: > l=C3=B6r 2010-08-14 klockan 13:45 +0200 skrev Ch=C3=AD-Thanh Christopher = Nguy=E1=BB=85n: > > Peter Hjalmarsson schrieb: > > > This is about my beloved USE=3D"ssl". A bit long and ranty, but if you > > > want the consensus, just read the last part. > > >=20 > > >=20 > > > Today a new snapshot of gnash was uploaded where the old USE=3D"ssl" = was > > > renamed to USE=3D"openssl". > > >=20 > > > So yet another package where if you want ssl support you have to > > > _personally_ audit what function this useflag has (i.e. does it enable > > > ssl or tune the ssl implementation?). > > >=20 > > > So I wanted to figure it out, does gnash provide ssl itself and the > > > USE=3D"openssl" only tunes how it is implemented or does USE=3D"opens= sl" > > > enable ssl? > >=20 > > The USE flag was renamed after discussion with upstream. Gnash does not > > provide any SSL implementation itself and (when invoked as NPAPI plugin) > > uses the browser's facilities. Possibly I could make more explicit that > > users only interested in the plugin don't need it. > >=20 > >=20 > > Best regards, > > Ch=C3=AD-Thanh Christopher Nguy=E1=BB=85n >=20 > Well if that is the use of the use flag the description is to be honest > really bad. >=20 > And still, why openssl instead of ssl? Even if most people are out to > only get the plugin the meaning of use flag for the rest of the package > is still the same. So is there a special reson why upstream do want ssl > disabled for people only out to get the plugin (and why not EAPI=3D1 and > IUSE=3D"-ssl")? Because it won't work. Take a look at make.conf(5) manual page -=20 USE_ORDER=3D"env:pkg:conf:defaults:pkginternal:env.d" - USE defaults in pro= file=20 will override pkginternal (IUSE defaults in ebuild). That being said IUSE=3D"-foo" is no-op. Otherwise I agree with you wrt naming inconsistencies. I would also like to see some USE defaults from make.defaults moved to=20 package.use, and some package.use defaults moved to IUSE defaults (and some= =20 make.defaults dropped completely, like freaking python and perl USE flags -= =20 bug 250179) =2D-=20 regards MM --nextPart14408288.ncmnURfE8G Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkxoT60ACgkQFuHa/bHpVdshNQCfc3GtDM74Wb7BQfS4mi77/T1U nZQAnRVDknD4gA6yj+mgxzwYgw2Z20q8 =5aAH -----END PGP SIGNATURE----- --nextPart14408288.ncmnURfE8G--