Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Sep 2000 12:51:34 -0700 (PDT)
From:      asami@FreeBSD.org (Satoshi - Ports Wraith - Asami)
To:        jkh@FreeBSD.org, ports@FreeBSD.org, hetzels@westbend.net
Subject:   Re: PR ports/13649, ports/13650 (conflicts)
Message-ID:  <200009201951.e8KJpY771163@silvia.hip.berkeley.edu>
In-Reply-To: <200009200929.e8K9TEH67316@silvia.hip.berkeley.edu> (asami@FreeBSD.org)
References:  <200009192342.e8JNgMj64933@silvia.hip.berkeley.edu> <200009200929.e8K9TEH67316@silvia.hip.berkeley.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
 *  * Please review the following patch to pkg_install tools to add two
 *  * things: -C (conflicts) support and wildcard matching (also used for
 *  * conflict checking, but it will also enable users to do things like
 *  * "pkg_info -e 'emacs*'" to see which, if any, emacs ports are
 *  * installed).

Found another problem after running the entire package build through
it.  The "another version already installed" check is too strict.  The
following are cases it rejected where it shouldn't.

mule-2.3 / mule-common-2.3   (these two are designed to always work together)
tcl-8.0.5 / tcl-8.2.3        (these two are designed to not conflict)
docbook-241 / docbook-3.0    (ditto)

mule/mule-common is a bug, as the code should be looking at the wrong
hyphen (the last one delimits the version).  But I don't know why it's
even checking for different versions.  There are many ports that are
designed to work with different versions of itself.  Either we should
take this check away and leave them to CONFLICTS, or introduce another
variable (DOESNT_CONFLICT?) to explicitly state that there is no
conflict.

What do you guys think?

Satoshi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009201951.e8KJpY771163>