[opensuse-factory] Packman libxine makes libzypp install PulseAudio, it's problem?
libxine1 package from Packman requires "esound". Smart just installs the package esound, but libzypp (YaST PM) installs pulseaudio-esound-compat. Both options are correct, but pulseaudio-esound-compat makes libzypp to also install "libpulse0", "libpulsecore4" and "pulseaudio". pulseaudio recommends "alsa-plugins-pulse", and YaST PM by default also installs it (I don't see any options to use or not recommends/suggests, or any sepecial icon to see clearly which automatic deps are optional). libflashsupport supplements flash-player & pluseaudio, and so is also installed. So, with every pulseaudio related package installed... is pulseaudio going to be used for all applications (even if they use ALSA API)? PulseAudio was supposed to be used only with Gnome, not with KDE. I don't know exactly how things where patched to detect Gnome vs KDE... but I would not be surprised if the install of alsa-plugins-pulse would mean that PulseAudio is used for everything. Since a LOT of people is going to install libxine1 from Packman... If it's a problem, the best solution I can think of is Packman removing "/usr/lib64/xine/plugins/1.22/xineplug_ao_out_esd.so" from the libxine1 package and putting it in a libxine1-esd package like it does with arts. But should be done fast to be ready for thursday. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, On Tuesday, June 17, 2008 at 17:04:03, Christian Morales Vega wrote:
But should be done fast to be ready for thursday.
This is not the proper communication channel for anything related to packman. They are their own project and you have to tell them. http://212.112.227.138/cgi-bin/mailman/listinfo/packman Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Jun 17, 2008 at 05:04:03PM +0200, Christian Morales Vega wrote:
(I don't see any options to use or not recommends/suggests, or any sepecial icon to see clearly which automatic deps are optional).
If you're in the UI, select "Package Groups" as filter and then select "Recommended packages" from the list. All of those packages are optional. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, 2008-06-17 at 17:04 +0200, Christian Morales Vega wrote:
libxine1 package from Packman requires "esound". Smart just installs the package esound, but libzypp (YaST PM) installs pulseaudio-esound-compat. Both options are correct, but pulseaudio-esound-compat makes libzypp to also install "libpulse0", "libpulsecore4" and "pulseaudio". pulseaudio recommends "alsa-plugins-pulse", and YaST PM by default also installs it (I don't see any options to use or not recommends/suggests, or any sepecial icon to see clearly which automatic deps are optional). libflashsupport supplements flash-player & pluseaudio, and so is also installed. So, with every pulseaudio related package installed... is pulseaudio going to be used for all applications (even if they use ALSA API)?
PulseAudio was supposed to be used only with Gnome, not with KDE. I don't know exactly how things where patched to detect Gnome vs KDE... but I would not be surprised if the install of alsa-plugins-pulse would mean that PulseAudio is used for everything. Since a LOT of people is going to install libxine1 from Packman...
Its a simple provides issue - pulse-esound-compat and esound both
provide /usr/bin/esd or esound.
With zypper you can zypper install -n esound which should only look at
the name and prevent this. You should also file a packman bug about the
requires.
-JP
--
JP Rosevear
Its a simple provides issue - pulse-esound-compat and esound both provide /usr/bin/esd or esound. Yes. And the provides is correct. Eveything is correct at really. What I'm worried about is about KDE users installing alsa-plugins-pulse without knowing and starting to have sound
With zypper you can zypper install -n esound which should only look at the name and prevent this. You should also file a packman bug about the requires. I asked for the esd xine plugin separation to his own package. Even if
2008/6/17 JP Rosevear
On Tue, 2008-06-17 at 18:45 +0200, Christian Morales Vega wrote:
Its a simple provides issue - pulse-esound-compat and esound both provide /usr/bin/esd or esound. Yes. And the provides is correct. Eveything is correct at really. What I'm worried about is about KDE users installing alsa-plugins-pulse without knowing and starting to have sound
2008/6/17 JP Rosevear
: problems. But since the "PulseAudio works in Gnome but not in KDE" thing looks like black magic (i.e. I don't know how has been implemented) I wanted a confirmation to know for sure if install alsa-plugins-pulse means PulseAudio is used for everything (I'm not sure about how to test this).
no, not really, alsa-plugins-pulse installs /etc/alsa-pulse.conf, which is used in GNOME because we add this: export ALSA_CONFIG_PATH=/etc/alsa-pulse.conf to the startup scripts. So, if you don't use GNOME, alsa should be using PA, if not, it just works as normal (it uses the config in /usr/share/alsa/alsa.conf).
With zypper you can zypper install -n esound which should only look at the name and prevent this. You should also file a packman bug about the requires. I asked for the esd xine plugin separation to his own package. Even if there is no PulseAudio problem makes sense to remove a Gnome only plugin from a generic package.
yes, it's probably the best thing to do, since on non-GNOME, you don't
need esound at all, and installing pulseaudio-compat-esound will force
you to activate PA if you want esound-based apps to work
--
Rodrigo Moya
On Thu, 2008-06-19 at 11:52 +0200, Rodrigo Moya wrote:
On Tue, 2008-06-17 at 18:45 +0200, Christian Morales Vega wrote:
Its a simple provides issue - pulse-esound-compat and esound both provide /usr/bin/esd or esound. Yes. And the provides is correct. Eveything is correct at really. What I'm worried about is about KDE users installing alsa-plugins-pulse without knowing and starting to have sound
2008/6/17 JP Rosevear
: problems. But since the "PulseAudio works in Gnome but not in KDE" thing looks like black magic (i.e. I don't know how has been implemented) I wanted a confirmation to know for sure if install alsa-plugins-pulse means PulseAudio is used for everything (I'm not sure about how to test this). no, not really, alsa-plugins-pulse installs /etc/alsa-pulse.conf, which is used in GNOME because we add this:
export ALSA_CONFIG_PATH=/etc/alsa-pulse.conf
to the startup scripts. So, if you don't use GNOME, alsa should be using PA, if not, it just works as normal (it uses the config in /usr/share/alsa/alsa.conf).
sorry, this is 'if YOU USE GNOME, alsa should be using PA, if not, ....'
--
Rodrigo Moya
participants (5)
-
Christian Morales Vega
-
Henne Vogelsang
-
JP Rosevear
-
Michael Schroeder
-
Rodrigo Moya