Resolving package conflicts (pkg set -o?)
norman.gray at glasgow.ac.uk
Mon Aug 13 13:53:51 UTC 2018
Wez and all, hello.
On 13 Aug 2018, at 14:09, wes Frazier wrote:
> I am curious about this too. I am currently living with a conflict
> between lang/chicken and lang/mono over the 'csi' binary; and I would
> appreciate knowing what the proper solution is.
Also, I think there are two distinguishable problems here:
1. Two packages install incompatible programs with the same name; eg,
Wez's case of chicken and mono both having a binary called 'csi', and
the two 'csi' programs have nothing to do with one another.
2. Two packages install 'the same' program built different ways; eg,
my case of openldap-client and openldap-sasl-client both installing a
Since the two packages in case 2 install software built with different
options, there will be at least some cases where the installed programs
_aren't_ functionally 'the same', so perhaps these cases aren't as
distinct as they appear at first.
Case 1 could be partly handled by installing with a prefix, thus
chicken-csi and mono-csi. However, that would only work for packages
where there isn't a dependency which depends on particular programs
This clearly isn't a trivial issue, but I hope there's a best practice
Norman Gray : https://nxg.me.uk
SUPA School of Physics and Astronomy, University of Glasgow, UK
More information about the freebsd-questions