On 06/03/16 10:53, Lowell Gilbert wrote:
Patrick Powell <[email protected]> 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.
When you do the 'pkg delete -f PortA' then it will also delete the
libraries installed by PortA.
if you do 'cd ...PortB; make install' and it will now install the files
that were in conflict,
but there are now some libraries installed by PortA which are missing.
I understand that this is on the outskirts of package/port management,
but there are times when
you want to install a test version of a utility which has only part of
the functionality of another port.
--
Patrick Powell Astart Technologies
[email protected] 1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting 858-874-6543 FAX 858-751-2435
Web: www.astart.com
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
