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
