From: Maciej Mrozowski <reavertm@gmail.com>
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 [thread overview]
Message-ID: <201008152235.57639.reavertm@gmail.com> (raw)
In-Reply-To: <1281803299.6299.69.camel@lillen>
[-- Attachment #1: Type: Text/Plain, Size: 2149 bytes --]
On Saturday 14 of August 2010 18:28:19 Peter Hjalmarsson wrote:
> lör 2010-08-14 klockan 13:45 +0200 skrev Chí-Thanh Christopher Nguyễn:
> > Peter Hjalmarsson schrieb:
> > > This is about my beloved USE="ssl". A bit long and ranty, but if you
> > > want the consensus, just read the last part.
> > >
> > >
> > > Today a new snapshot of gnash was uploaded where the old USE="ssl" was
> > > renamed to USE="openssl".
> > >
> > > 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?).
> > >
> > > So I wanted to figure it out, does gnash provide ssl itself and the
> > > USE="openssl" only tunes how it is implemented or does USE="openssl"
> > > enable ssl?
> >
> > 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.
> >
> >
> > Best regards,
> > Chí-Thanh Christopher Nguyễn
>
> Well if that is the use of the use flag the description is to be honest
> really bad.
>
> 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=1 and
> IUSE="-ssl")?
Because it won't work. Take a look at make.conf(5) manual page -
USE_ORDER="env:pkg:conf:defaults:pkginternal:env.d" - USE defaults in profile
will override pkginternal (IUSE defaults in ebuild).
That being said IUSE="-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
package.use, and some package.use defaults moved to IUSE defaults (and some
make.defaults dropped completely, like freaking python and perl USE flags -
bug 250179)
--
regards
MM
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-15 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 11:26 [gentoo-dev] Why (i.e. USE="openssl" instead of USE="ssl") Peter Hjalmarsson
2010-08-14 11:45 ` Chí-Thanh Christopher Nguyễn
2010-08-14 16:28 ` [gentoo-dev] " Peter Hjalmarsson
2010-08-15 20:35 ` Maciej Mrozowski [this message]
2010-08-14 12:14 ` [gentoo-dev] " Samuli Suominen
2010-08-14 16:29 ` [gentoo-dev] " Peter Hjalmarsson
2010-08-15 21:48 ` Gilles Dartiguelongue
2010-08-16 12:07 ` Peter Volkov
2010-08-16 16:11 ` Gilles Dartiguelongue
2010-08-16 17:45 ` Mike Frysinger
2010-09-26 17:14 ` Petteri Räty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201008152235.57639.reavertm@gmail.com \
--to=reavertm@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox