Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#16805 - [amsn] Make farsight2 an optional dependency
Attached to Project:
Community Packages
Opened by Sergio Tridente (TioDuke) - Friday, 23 October 2009, 16:03 GMT
Last edited by Dan Griffiths (Ghost1227) - Sunday, 01 November 2009, 20:21 GMT
Opened by Sergio Tridente (TioDuke) - Friday, 23 October 2009, 16:03 GMT
Last edited by Dan Griffiths (Ghost1227) - Sunday, 01 November 2009, 20:21 GMT
|
DetailsDescription:
I'd like to request farsight2 being made an optional dependency. Here are the reasons why I think it could be useful: - farsight2 is needed only if the user wants to make use of the VideoConferencing feature. It is not needed for simple webcam sharing or audio-clip sending (the latter requires another additional package which, in fact, is not listed in amsn's dependency list - not even as optional). - farsight2 pulls out a series of dependencies on its own: gstreamer0.10-base-plugins, gstreamer0.10-base, gstreamer0.10-python and libnice. It also has two other optional dependencies: gstreamer0.10-good and gstreamer0.10-bad, and without them, the VideoConferencing feature does not work. - And even with all these dependencies installed (mandatory and optional), it might still not work on ALSA. As stated in amsn's wiki: "The configuration of the sound card for input and output will be added to aMSN UI soon, you will need to be patient in case you don't have one audio device and use alsa. You could however try running the command 'gstreamer-properties' from a Terminal and if that works, then configure your audio devices from there, and it should then work properly. If that command doesn't exist for you, or you are using mac or windows, then just be patient." Additional info: * package version(s) 0.98.1-1 * config and/or log files etc. Steps to reproduce: |
This task depends upon