From owner-freebsd-ports@FreeBSD.ORG Fri Oct 10 11:41:59 2003 Return-Path: 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 EF77016A4B3 for ; Fri, 10 Oct 2003 11:41:59 -0700 (PDT) Received: from mx2.fillmore-labs.com (lima.fillmore-labs.com [62.138.193.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14E0A43FB1 for ; Fri, 10 Oct 2003 11:41:57 -0700 (PDT) (envelope-from eikemeier@fillmore-labs.com) Received: from pd951aee5.dip.t-dialin.net ([217.81.174.229] helo=fillmore-labs.com ident=97yj6qtvu7fnh7l2) by mx2.fillmore-labs.com with asmtp (TLSv1:AES256-SHA:256) (Exim 4.24; FreeBSD 4.9) id 1A82D5-000P8C-Rw; Fri, 10 Oct 2003 20:41:56 +0200 Message-ID: <3F86FD71.5070109@fillmore-labs.com> Date: Fri, 10 Oct 2003 20:41:53 +0200 From: Oliver Eikemeier MIME-Version: 1.0 To: Thomas-Martin Seck References: <20031010183602.1664.qmail@laurel.tmseck.homedns.org> In-Reply-To: <20031010183602.1664.qmail@laurel.tmseck.homedns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: eikemeier@fillmore-labs.com User-Agent: KMail/1.5.9 Organization: Fillmore Labs GmbH X-Complaints-To: abuse@fillmore-labs.com cc: freebsd-ports@freebsd.org Subject: Re: ports that should use CONFLICTS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2003 18:42:00 -0000 Thomas-Martin Seck wrote: > * Will Andrews [gmane.os.freebsd.devel.ports]: > > >>On Fri, Oct 10, 2003 at 01:28:08PM -0400, Adam Weinberger wrote: >> >>>>>(10.10.2003 @ 1112 PST): Thomas-Martin Seck said, in 1.9K: << >>>> >>>>It seems that pkg_add should be tought to ignore unknown declarations in >>>>package files. >>> >>>What does that mean? >> >>I suspect he means it should be taught to ignore things like >>"@conflicts" if it does not recognize it. > > Right. > >>Noble idea, but we can't apply such a change retroactively. The >>best way to solve pkg_info conflicts is to force a newer version >>on them through sysutils/pkg_install. Unfortunately that hasn't >>been implemented yet, although it is trivial to do. > > I often wish that portmgr@ would deploy the kind of changes to the ports > system that imply that changes to the base system's pkg_*-tools have to > be made, _after_ these changes have propagated into the base system. For > instance: Teach pkg_* how to deal with @comment, MFC it into -STABLE, > wait for the next release and _then_ go ahead and implement the change > in the ports system. Yes, I know it's hard to hold one's breath for > probably six months or longer... The other way would be to make the > package handling tools in itself be part of the ports system. This will > of course create a "package bootstrapping" problem - how to install the > package manager package? We are working on it. sysutils/pkg_install is a first (small) step...