> I agree and I cuss pacman every once in a while for it. It
> is more restrictive
> and it does a very good job. I just wish it was smart enough
> to:
> 
> if diff pkg1/file.x pkg2/file.x; then
>   install the darn thing
> fi
> 
> But.. then you screw up (or complicate) the package manager
> database regarding
> who owns what on the system. I think this is where other
> package managers are
> smarter than pacman. Their package databases seem to be able
> to do this on the
> fly while pacman doesn't. Because in the above example, you
> would need to expand
> it to:
> 
> if diff pkg1/file.x pkg2/file.x; then
>   install the darn thing
>   update_pkgmgr_db(pkg2/file.x, owned by pkg2)
>   update_pkgmgr_db(pkg1/file.x, owned by pkg2)
> fi

Oh, boy. I could say something now in defense for why the Slackware packaging system never required dependency checking.... :)

There is no database, no Central Headquarters. Just tgz packages....

Slackware installs the dam*ed thing and expects the user to know better. Yeah, not all users pay attention, but the package tools do pay attention to what gets removed. When two packages have installed the same file the package tools do not argue and leaves the files untouched during the removal process.

Oh never mind. I'll start a distro war soon!

Darrell