Re: Optional Package Dependencies for netscape-flash -> libflashsupport

Jim Ramsay wrote:
>> > This meets the following goals:
>> > 1) It makes it easy for "regular"
users to get netscape-flash with
>> > any additions required by any global USE flags
in exactly one step:
>> >  - emerge netscape-flash
>> So, in netscape-flash:
>> RDEPEND="
>>     ssl? ( foo/libflashsupport )
>>     pulseaudio? ( foo/libflashsupport )
>>     esd? ( foo/libflashsupport )
>>     oss? ( foo/libflashsupport )
>> "
>> and IUSE="ssl pulseaudio esd oss gnutls"
in libflashsupport (which, as
>> already said, has it's own ebuild)?
> 
> Yes, I considered this, it is option (2) in the
original post in this
> thread. However, I do not believe this is the best
solution.  Consider
> the case where:
>  - A user has 'ssl' disabled globally
>  - A user sees that netscape-flash now has 'ssl'
support, so he/she
> enables 'ssl' just for the netscape-flash ebuild.
>  - The ebuild would then install libflashsupport, but
do so without
> actually adding ssl support, which would be quite
frustrating to the
> user, and probably generate unnedded bug traffic.
> 
Well then the ebuild for libflashsupport should pull in ssl
iff the flag is
set; other packages do similar stuff. A usr who adds ssl to
package.use
will not be surprised to see the ssl package being pulled
in, so no bad
experience for the usr, and hopefully less bug reports.

I really *don't* like the option of a crippled install.
It's
counter-intuitive and is asking for trouble imo.

Thanks for adding shiny stuff to flash 


-- 
gentoo-devgentoo.org mailing list