You are not logged in.
Is there a way for pacman and/or yaourt to continue installing the remaining packages if one can't be installed for whatever reason (i.e. like a conflict)? Of course it would skip any other packages that depended on it, but it's annoying if I have a script setup to install packages and it stops midway, even though I'd rather have everything other than the conflicting package installed.
Offline
pacman stops because it wants you to decide what to do.
yaourt? No idea, I never use it.
Offline
The problem is I have a script that installs a bunch of packages for me. I'd rather have the script do most of the work instead of none of the work.
Last edited by gsingh93 (2015-01-24 21:41:25)
Offline
Maybe remove the problem package(s) from the bunch and install them separately.
Offline
Yea, that's what I'll have to do if I can't find a way to make pacman continue.
Offline
Is there a way for pacman and/or yaourt to continue installing the remaining packages if one can't be installed for whatever reason (i.e. like a conflict)? Of course it would skip any other packages that depended on it, but it's annoying if I have a script setup to install packages and it stops midway, even though I'd rather have everything other than the conflicting package installed.
So, package X requires package Y, but package Y can't be installed because some of its files are present in the filesystem (for example). Now, you are suggesting that pacman skip package Y? This doesn't sound too smart.
Packages from [core], [extra] or [community] won't give you installation issues. Packages built from the AUR is a different story, but you shouldn't install them blindly anyways. If the offending package(s) is your own -- fix them.
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline