There are three different variables to register a conflict
between packages and ports: CONFLICTS
,
CONFLICTS_INSTALL
and
CONFLICTS_BUILD
.
The conflict variables automatically set the variable
IGNORE
, which is more fully documented in
節 12.13, “Marking a Port Not Installable with
BROKEN
, FORBIDDEN
, or
IGNORE
”.
When removing one of several conflicting ports, it is
advisable to retain CONFLICTS
in
those other ports for a few months to cater for users who only
update once in a while.
If the package cannot coexist with other packages
(because of file conflicts, runtime incompatibilities, etc.),
list the other package names in
CONFLICTS_INSTALL
. Use
shell globs like *
and ?
here. Enumerate package names in there, not port names or
origins. Please make sure
that CONFLICTS_INSTALL
does not match this
port's package itself. Otherwise enforcing its installation
with FORCE_PKG_REGISTER
will no longer
work. CONFLICTS_INSTALL
check is done
after the build stage and prior to the install stage.
If the port cannot be built when other specific ports are
already installed, list the other port names in
CONFLICTS_BUILD
. Use
shell globs like *
and ?
here. Use package names, not port names or origins.
CONFLICTS_BUILD
check is done prior to the
build stage. Build conflicts are not recorded in the
resulting package.
If the port cannot be built if a certain port is already
installed and the resulting package cannot coexist with the
other package, list the other package name in
CONFLICTS
. use shell
globs like *
and ?
here.
Enumerate package names in there, not port names or
origins. Please make sure that
CONFLICTS
does not match this
port's package itself. Otherwise enforcing its installation
with FORCE_PKG_REGISTER
will no longer
work. CONFLICTS
check is done prior to the
build stage and prior to the install stage.
本文及其他文件,可由此下載: ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/。
若有 FreeBSD 方面疑問,請先閱讀
FreeBSD 相關文件,如不能解決的話,再洽詢
<questions@FreeBSD.org>。
關於本文件的問題,請洽詢
<doc@FreeBSD.org>。