From owner-freebsd-ports@FreeBSD.ORG  Mon Jun 21 09:58:26 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id BB79B16A4CE; Mon, 21 Jun 2004 09:58:26 +0000 (GMT)
Received: from fillmore.dyndns.org (port-212-202-50-15.dynamic.qsc.de
	[212.202.50.15])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 733A543D48; Mon, 21 Jun 2004 09:58:26 +0000 (GMT)
	(envelope-from eikemeier@fillmore-labs.com)
Received: from [172.16.0.13] (helo=localhost)
	by fillmore.dyndns.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.34 (FreeBSD))
	id 1BcLZG-000K4V-Kb; Mon, 21 Jun 2004 11:58:25 +0200
Date: Mon, 21 Jun 2004 11:58:28 +0200
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
To: Volker Stolz <vs@FreeBSD.org>
From: Oliver Eikemeier <eikemeier@fillmore-labs.com>
In-Reply-To: <20040621070848.GA78206@i2.informatik.rwth-aachen.de>
Message-Id: <8B8F1627-C369-11D8-9250-00039312D914@fillmore-labs.com>
Content-Transfer-Encoding: 7bit
User-Agent: KMail/1.5.9
cc: Anish Mistry <mistry.7@osu.edu>
cc: ports@FreeBSD.org
cc: lewiz@fajita.org
cc: lars.eggert@gmx.net
Subject: Re: Freevo port (TESTING REQUIRED).
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jun 2004 09:58:26 -0000

Volker Stolz wrote:

> [...]
> Please check if this could be encoded in the dependencies somehow...it 
> might
> be possible to (ab)use CONFLICTS for this, but that might be over the 
> top.

I would strongly advise against using CONFLICTS as a kind of 
(anti-)dependency.
If you require certain version of a package, use pkg-req or pkg-install 
for
that, possibly calling pkg_info. Or we could cook some new dependency
scheme up, although this might take some time.

One reason for that is that I might integrate a file database into the 
pkg_*
tools, completely ignoring CONFLICTS. I might not have the time to really
finish this project, but at least this example might show why it's not a
good idea to abuse CONFLICTS for something else than conflicting files.

> [...]
> Please also consider using OPTIONS.

IMHO OPTIONS is not ready for production, I would wait until the bugs are
resolved. Just my 2 cents, YMMV.

-Oliver