OpenBSD manual page server

NAME

check-conflicts — verify conflicts between packages

SYNOPSIS

DESCRIPTION

check-conflicts is used to check a collection of packages for unregistered conflicts. A conflict is a file that belongs to two distinct packages. Common directories are not a problem.

By default, packages with the same stem (see packages-specs(7)) are registered to conflict. This can be changed to add or remove extra conflict registration with @option no-default-conflict or @conflict (see package-create(1)).

Conflicts between packages mean that a user can't have both packages installed at the same time. In some cases (same software, different version), this is expected, but the packages should be marked as conflicting, so that pkg_add(1) knows how to deal with it. In other cases, this is an oversight from the ports maintainer, and action should be taken to make sure both packages can be installed simultaneously. Conflicts also interact with dependencies, and sometimes a missing dependency will show up as an unregistered conflict. check-conflicts requires a set of packing-lists to operate, which it can obtain from the package itself, or from external sources.

Options are as follows:

-e

Check for extra logical conflicts, by adding supplementary formatted/unformatted manpages, as same name manpages under the same base directory will shadow one another.

-v

Be verbose

-d plist-dir

Scan directory plist-dir for packing-lists (see the description of PLIST_DB in bsd.port.mk(5)).

-p portsdir

Traverse the ports directory for packing-lists, using print-plist-all. More than one directory could be specified by delimiting them by colon, e.g.: /usr/ports/x11/kde:/usr/ports/x11/kde4.

If -d plist-dir is also used, traverse only the directories corresponding to the packages under plist-dir to figure out current pkgnames, and annotate those with a ‘’! in the report.

SEE ALSO

pkg_add(1), pkg_create(1), bsd.port.mk(5), packages-specs(7)