How to handle conflicts

h2 · 2011-02-16 15:32:25

Hi everyone,

I am still kind of new to Arch and pacman (I use yaourt for AUR). One of the pleasant surprises with Arch was that it works really well with OSS. I really dislike alsa, and am happy to do without it.

Now the problem is that some apps (e.g. chromium) don't cope with OSS, so I wanted to install libsalsa, which of course conflicts with alsa-lib.

How do I go about replacing alsa-lib with libsalsa? yaourt doesn't want to do it, since other packages require alsa-lib.

What's the usual way of "Remove Package A, install Package B, transfer all dependencies from Package A to B", I couldn't really tell from reading the man. On BSD this way quite simple, or I could at least force the removal of Package A, without removing anything else.

Thank you for your help.

Inxsible · 2011-02-16 15:57:15

man pacman

Look for force options and -d options to use with -R

But, be warned, that you do this at your own risk as forcing uninstalls - or in other words removing packages without dependency checks is bad mojo.

However, if you simply want to switch dependencies, i think simply installing the new package should do it for you.

wonder · 2011-02-16 16:03:38

https://bbs.archlinux.org/viewtopic.php?id=56373

h2 · 2011-02-16 16:50:39

Inxsible wrote:

man pacman
Look for force options and -d options to use with -R
But, be warned, that you do this at your own risk as forcing uninstalls - or in other words removing packages without dependency checks is bad mojo.
However, if you simply want to switch dependencies, i think simply installing the new package should do it for you.

Ok, so there is nothing like a replace operation? What happens if uninstall something with -Rd, install a replacement that provides the stuff and then upgrade packages depending on the original. Wont they want the original back? How do you do this in general, shouldn't there be a mechanism for this?

For the current case I used -Rd and it works, but it doesn't feel too well. Also the version of libsalsa seems to be outdated and not working as replacement for alsa-lib, chromium gives me some symbol-errors. So I will revert to alsa-lib for now and hope for the future...

@ wonder: I don't think thats related, I am talking about "official" conflicts between packages, not error because a file would be overwriten.

Thanks for your help.

tomk · 2011-02-16 17:45:13

h2 - from pacman's perspective, chromium etc depend on alsa-lib, so if you want the packaging all correct, you would need to rebuild chromium etc against libsalsa. I'm not sure what you mean by "official" conflicts - libsalsa is in the aur, so it's not an official package.

If you have a link to a more recent version of libsalsa, you should give it to the maintainer of the libsalsa package in the aur. Seems to me he has built the current stable release.

h2 · 2011-02-17 11:07:43

tomk wrote:

h2 - from pacman's perspective, chromium etc depend on alsa-lib, so if you want the packaging all correct, you would need to rebuild chromium etc against libsalsa. I'm not sure what you mean by "official" conflicts - libsalsa is in the aur, so it's not an official package.
If you have a link to a more recent version of libsalsa, you should give it to the maintainer of the libsalsa package in the aur. Seems to me he has built the current stable release.

Ah, ok. Well it still needs some rethinking on my point. Anyway, I found a better solution with alsa-plugins and
http://www.opensound.com/wiki/index.php … _Emulation

So I don't need libsalsa at all.

Arch Linux

#1 2011-02-16 15:32:25

How to handle conflicts

#2 2011-02-16 15:57:15

Re: How to handle conflicts

#3 2011-02-16 16:03:38

Re: How to handle conflicts

#4 2011-02-16 16:50:39

Re: How to handle conflicts

#5 2011-02-16 17:45:13

Re: How to handle conflicts

#6 2011-02-17 11:07:43

Re: How to handle conflicts

Board footer