Date: Fri, 03 Jun 2016 13:53:36 -0400 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: Patrick Powell <papowell@astart.com> Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org>, freebsd-pkg@freebsd.org Subject: Re: how do you force make install to overwrite conflicting files from another port? Message-ID: <44poryi2fz.fsf@lowell-desk.lan> In-Reply-To: <5b020f89-8f29-5c52-e3de-6c067019b7e9@astart.com> (Patrick Powell's message of "Fri, 3 Jun 2016 08:26:25 -0700") References: <5b020f89-8f29-5c52-e3de-6c067019b7e9@astart.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Patrick Powell <papowell@astart.com> writes: > Suppose that you have a portA which is a dependency of a lot of other ports. > > You also have a portB which is a replacement/update/upgrade for portA. > > PortB provides replacements for the executables generated/supplied by > PortA but for various reasons you still want to use some of PortA > installed items such as libraries, etc. > > I tried doing the following: > > # pkg install PortA > # cd /usr/ports/xxx/PortB > # make install > > Installing PortB... > pkg-static: PortB conflicts with PortA (installs files into the same > place). Problematic file: /usr/local/bin/utilityl > *** Error code 70 > > Is there an option, or a way similar to using 'make > FORCE_PGK_REGISTER=YES install' > to force overwriting the conflicting files? Not directly, no. The way to do it straight from the ports tree is to remove the "PortA" *first* (with "pkg delete -f"), and then install "PortB". You end up losing the dependency information that PortA had formerly had, but things will work. Upgrade tools (pkg, portmaster, portupgrade, at least) have a "-o" option that fixes up the dependency information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44poryi2fz.fsf>