slapt-src doesn't detect package conflicts

[GJones]

Today I installed the dump package via slapt-src, and discovered to my consternation that it overwrote an existing binary (/usr/bin/restore). Does spkg have any way of detecting conflicts like this, so that stuff from SBO doesn't make a mess of my system?

[gapan]

No. spkg has nothing like that and it shouldn't. Packages having common files are very usual and having common files is not a conflict by itself. You should just make sure you read the README before installing anything from SBo. In this case it clearly says:

CONFLICT: The restore application conflicts with the tar package.

On installing this dump package "/usr/sbin/restore" will be overwritten.

Should you remove the dump package, you may note that this file will not be
deleted because it is "shared" with the tar package. You may opt to reinstall
the stock tar package after uninstalling the dump package.

[thenktor]

Does spkg have any way of detecting conflicts like this

Features like this usually make me hate rpm based distributions. They are bugging me much too often about dependencies, conflicts, ...

[mimosa]

So in a situation like this, what is the best way to go about it? Just go ahead and install? What about if you decide to remove the package later? Just go ahead and remove, ignoring any complaints? Will there even be any, taking this particular case as an example?

I can't recall anything like this happening to me, but it's bound to one day

[gapan]

In this case, if you remove the dump package, just reinstall the tar package as it says in the README.

[GJones]

Ah... I guess I'll have to get used to reading the READMEs for Slackbuilds. Probably a good habit anyway.