From owner-freebsd-ports@FreeBSD.ORG Fri Jul 20 17:12:04 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E46A106564A for ; Fri, 20 Jul 2012 17:12:04 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id DADA28FC0C for ; Fri, 20 Jul 2012 17:12:03 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so1248018vcb.13 for ; Fri, 20 Jul 2012 10:12:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=E1CK9pQkkQvUWDFms0qReS0quiD2IGkNKZ+Xc2FvKKw=; b=PzBM6elr/IWJKjn/YuxubEdfRBnSvCN23ECR04Z91ffkoCgT3uNeeiJXvVIPVCkX2D fytH7YKaz2MDRqKAr0LFvyAQg8meppidVhU5dFPpoEgLw3iluLBTqRyQLo3NgiFo3hr2 slQD7krTqL18WRn8qQb7S1Znq5XDeEIXZIGsZY6GzWXE21ZwTBkTnAzGEee4vPjt3/+D 7v6rfPjAogwbUuKtOwGrQD76B4wsQ62mOkIQ6uG0px9IkS1hbuJMMPkt0rR/+CvmXAQ2 OsrFKhzwJwHsavzNuu/4vxRO+wEOnIZAUWghByi6af5S30kgx76M1yiV89pdtaYoj0+w mCEg== MIME-Version: 1.0 Received: by 10.52.72.44 with SMTP id a12mr4500006vdv.124.1342804322941; Fri, 20 Jul 2012 10:12:02 -0700 (PDT) Received: by 10.58.145.10 with HTTP; Fri, 20 Jul 2012 10:12:02 -0700 (PDT) In-Reply-To: <50098EEF.8040801@shatow.net> References: <50098EEF.8040801@shatow.net> Date: Fri, 20 Jul 2012 20:12:02 +0300 Message-ID: From: Kimmo Paasiala To: Reko Turja Content-Type: text/plain; charset=UTF-8 Cc: freebsd-ports@freebsd.org, Bryan Drewery Subject: Re: How to remove erroneous deps from pkgng X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2012 17:12:04 -0000 On Fri, Jul 20, 2012 at 8:01 PM, Bryan Drewery wrote: > On 7/20/2012 11:57 AM, Reko Turja wrote: >> I'm testing out the pkgng system and somehow a port managed to pull >> devel/pkg-config into one low level port polluting whole db. "pkg check" >> just wants to install the annoying thing. Is there any way to get rid of >> that erroneous dependency? > > Which port is pulling it in? > >> >> In production system, these kind of errors should be somehow >> correctable, especially if pkgng is to be used with ports as well. > > If the port defines invalid dependencies, it's not pkgng's problem, it's > the port. > >> >> -Reko >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > > -- > Regards, > Bryan Drewery > bdrewery@freenode/EFNet > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" I think this is the effect of "recursive dependencies". If port B directly depends on port C and A directly depends on B, then port A has both ports B and C as its dependencies. Replace C with devel/pkg-config and you get the picture. The port devel/pkg-config is used in many ports, there's no harm in installing it.