You are not logged in.
I'm doing a package for gamin - a fam replacement for GNOME users, which uses inotify kernel backend (less memory usage, faster, etc.). Gamin replaces fam providing same functionality. So:
...
conflicts=fam
provides=fam
...
Installing my gamin package gives:
[root@HAL:gamin]# pacman -A gamin-0.0.26-1.pkg.tar.gz
loading package data... done.
:: gamin conflicts with fam. Remove fam? [Y/n] y
error: this will break the following dependencies:
fam: is required by gnome-vfs
install aborted.
...so the only option is to actually go
pacman -Rd fam
pacman -A gamin-0.0.26-1.pkg.tar.gz
So - I think that if package A provides B, than B should be skipped from dependency-break checking.
MDK
Open Source Software Operations/Nokia
michael.kostrzewa (at) nokia.com
Offline
just remove the "conflicts" and leave a "provides=(fam)" ... that should handle it all nicely... unless gamin provides the same binarys as fam.... *shrug*
Offline
It provides the same binaries... (libfam) that's why I put fam in conflicts in the first place. You can't have two of them installed.
MDK
Open Source Software Operations/Nokia
michael.kostrzewa (at) nokia.com
Offline
hmmm, the only thing I can say is this: conflicts like that should be handled in a complicated manner... it makes sense to me considering things that depend on fam are built for fam....not some fam replacement....
I dunno if it works, but can you do "-Ad" or "-Sd" and remove fam.... I dunno
Offline