From owner-freebsd-questions@freebsd.org Mon Aug 13 13:53:51 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9160E10734AB for ; Mon, 13 Aug 2018 13:53:51 +0000 (UTC) (envelope-from Norman.Gray@glasgow.ac.uk) Received: from plockton.cent.gla.ac.uk (plockton.cent.gla.ac.uk [130.209.16.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 31B167A93A for ; Mon, 13 Aug 2018 13:53:50 +0000 (UTC) (envelope-from Norman.Gray@glasgow.ac.uk) Received: from cas07.campus.gla.ac.uk ([130.209.14.164]) by plockton.cent.gla.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1fpDHy-0001iz-4V; Mon, 13 Aug 2018 14:53:42 +0100 Received: from [130.209.45.140] (130.209.45.140) by cas07.campus.gla.ac.uk (130.209.14.164) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 13 Aug 2018 14:53:41 +0100 From: Norman Gray To: wes Frazier CC: Subject: Re: Resolving package conflicts (pkg set -o?) Date: Mon, 13 Aug 2018 14:53:41 +0100 X-Mailer: MailMate (1.11.3r5509) Message-ID: <9734C9CF-6AB1-4D78-AB92-5827B3C168CA@glasgow.ac.uk> In-Reply-To: References: <03EF2AAC-B928-4B82-BB14-3AF4C009E5E5@astro.gla.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [130.209.45.140] X-ClientProxiedBy: cas07.campus.gla.ac.uk (130.209.14.164) To cas07.campus.gla.ac.uk (130.209.14.164) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 13:53:51 -0000 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 slapd daemon. 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 being present. This clearly isn't a trivial issue, but I hope there's a best practice recommendable. Best wishes, Norman -- Norman Gray : https://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK