Hi! When I was thinking on the symlink puzzle, I ran into the question above. Let me explain: Suppose, that an updated version of audacious moves from /usr to /opt; and user does a "pacman -S audacious". In this case the installed audacious-plugins will be broken, because it thinks that audacious is installed to /usr. The dir change of audacious wasn't planned so audacious-plugins simply depends on audacious (with no version number), so audacious-plugins won't be updated. To avoid this, the package maintainer can do some ugly tricks only (conflicts, install_script/warn etc.). So it would be useful, if the maintainer somehow could record to the repo that there was a big change between audacious 2.0-1 and 2.0-2; so if user updates from a <=2.0-1 version to a >=2.0-2 version this will induce the update of audacious' depends (we can assume, that the updated version of audacious-plugins works fine with the updated audacious.). Or we can define a special ("major") version number, whose change indicates a "recursive" update. Bye, ngaba ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.