Date: Wed, 15 Sep 1999 21:34:17 -0500 From: "Scot W. Hetzel" <hetzels@westbend.net> To: <freebsd-bugs@FreeBSD.org> Subject: bin/13649: Conflict Checking for PKG_INSTALL tools (4.0-CURRENT) Message-ID: <039101beffeb$f9d90760$8dfee0d1@westbend.net> References: <199909090949.CAA89253@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The code in this PR is from the NetBSD pkg_install tools. All I did was
merge the changes between the FreeBSD & NetBSD pkg_install tools that would
allow our tools to perform port/package conflict checking.
Why have Conflict Checking for ports/packages?
Conflict checking allows a port maintainer to specify which
packages/ports conflict with the port that is currently being installed.
This can be based on:
1. port conflicts with an older version of itself
ex. foo-<=3.0
2. port conflicts with another port
3. port conflicts with old dependancies.
All the port maintainer needs to do is add the CONFLICTS variable to their
ports Makefile and specify the packages that conflicts with this
port/package. The CONFLICTS variable uses shell meta characters
[]*?<>,<=,>= ) to do pattern matching on conflicting ports.
Also, pkg_info -e has been changed to use shell meta characters, this allows
it to do pattern matching for installed packages.
>pkg_info -e cvsup-*
cvsup-mirror-1.0
cvsup-16.0
cvsup-bin-15.0
Scot
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?039101beffeb$f9d90760$8dfee0d1>