If the port cannot be built if a certain port is already installed and the resulting package cannot coexist with the other package.
`CONFLICTS` check is done prior to the build stage and prior to the install stage.
+The values assigned to the `CONFLICTS*` variables are matched against the package base names and the full package names of all installed packages using file globbing rules.
+If the base name of the currently built package is matched by a `CONFLICTS*` pattern, this match is ignored.
+This allows to list all flavors of a port in a conflicts list, without being considered if the installed port matching this pattern is upgraded.
+For example, if git-lite is installed, `CONFLICTS_INSTALL=git git-lite` would allow to perform:
+[source,shell]
+....
+% make -C devel/git FLAVOR=lite all deinstall install
+....
+
+But the following command would report a conflict, since the package base name installed is `git-lite`, while `git` would be built, but cannot be installed in addition to `git-lite`:
+[source,shell]
+....
+% make -C devel/git FLAVOR=default all deinstall install
+....
+
The most common content of one of these variable is the package base of another port.
The package base is the package name without the appended version, it can be obtained by running `make -V PKGBASE`.