On Sun, 02 Apr 2006 18:33:59 +0100 Tom K <[EMAIL PROTECTED]> wrote: > Tor Krill wrote: > > Hi, > > > > I work on the Arch networkmanager package and have been doing so for > > quite some time. (We now actually have Arch support in the mainline > > version of it ;-) ) > > > > But this project has changed name not that long ago from > > GnomeNetworkManager to NetworkManager. To reflect that i now wanted > > to change the package name as well. > > > > I added: > > > > replaces=(gnome-network-manager) > > > > to my PKGBUILD and tried to upgrade on the command line. The problem > > that happens is that every file in the new package is said to > > conflict with the old package installed version of these. > > > > I had thought that pacman should either upgrade over the old > > version or inform me on uninstalling the old one first? PKGBUILD > > can be found here: > > http://www.krill.nu/arch/NetworkManager/cvs/PKGBUILD > > > > > As I understand it, replaces= doesn't work as you would think it > should. You need both of the following: > > conflicts=(gnome-network-manager) > provides=(gnome-network-manager) > > as well.
I'm pretty sure pacman doesn't work the way *you* think it should ;) replaces is only calculated when using -S. -U won't even look at replaces. Strictly speaking though, you probably want replaces, conflicts, and provides (provides is only really needed if things have dependencies on gnome-network-manager or people want to keep installing it with pacman -S gnome-network-manager even after the change). Each one handles its own case fairly well. > pacman will deduce from those entries that gnome-network-manager > should be removed before network manager is installed, and will > prompt the user to confirm the removal. Jason
signature.asc
Description: PGP signature
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
