I think you're misunderstanding the packaging guidelines. The case you're referring to is for when two packages for the same program (or library or whatever) exist, one for the fixed versions and one for building from VCS. In that case, per guidelines, the VCS package should conflict and provide the base package as it offers the same functionality, but is slightly different.
In the case here, this package has nothing to do with the spot client, and it's not really clear to me why it contains /usr/bin/spot
. Plus there's also a 'spot-client' package this one is also in conflict with due to the overlapping filename.
Since 'afdko' is the package going against the convention here — providing a binary with a filename with no connection to the package — I'd put the conflict here, or rather rename the binary if possible, i.e. it's not called from somewhere else.
Pinned Comments
alerque commented on 2020-03-04 09:16 (UTC)
PSA: I've started hosting this and all its dependencies as prebuilt packages in my repository for those that want to install them using
pacman
without messing around with building from the AUR.