On 5 May 2010 00:09, Miklos Vajna <[email protected]> wrote:
> On Wed, Apr 21, 2010 at 07:11:20AM +1000, Russell Dickenson 
> <[email protected]> wrote:
>> I have recently had some minor difficulty with optional packages,
>> which are those which enhance an applications' functionality but are
>> not a definitive, runtime requirement. The best example of this is
>> codecs - particularly GStreamer, since this is a popular audio
>> framework. Most GStreamer plugin packages are not a requirement in
>> those FrugalBuilds for those applications which use GStreamer. However
>> if you don't have them installed and the application needs those to
>> provide specific functionality, the user of the application may be
>> confused as to why certain functions don't work; I know *I* get
>> confused. :) To make all GStreamer plugins a dependency of every app
>> that uses GStreamer leads to the installation of *many* packages, most
>> of which are not required.
>>
>> How can this problem be resolved? If plugins are not installed, the
>> user may get odd behaviour. If *all* plugins are installed, the user
>> has a lot of packages installed, most of which are not required.
>>
>> What options are available? IIRC Debian and Debian-based distributions
>> have optional dependencies, but I don't know what this means in
>> practice. If this has been discussed and resolved previously, sorry.
>
> Given that these plugins are installed by default (and I guess one who
> does not do a default install is a bit more advanced than the avarage),
> I don't think you need to add any gst plugin to depends. If you really
> want, you can add a README.Frugalware file that advices to install the
> necessary plugins for the given media type.


VMiklos,

That sounds like a reasonable solution. Thanks for your reply.


May you always be Frugal,

Russell Dickenson (AKA phayz)
_______________________________________________
Frugalware-devel mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-devel

Reply via email to