From owner-freebsd-stable@FreeBSD.ORG Thu Jan 16 15:59:16 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EEED497; Thu, 16 Jan 2014 15:59:15 +0000 (UTC) Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A720A1967; Thu, 16 Jan 2014 15:59:15 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id j17so3122512oag.18 for ; Thu, 16 Jan 2014 07:59:14 -0800 (PST) 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=UNyIYpqnZinw5q91j3DRWuAGFAAQ9klEjJWvqy5xqYg=; b=jRHarNdg3P2lMbEouNQhdZjpPrA4vN1f6Jn13CoxAVmyCxlP7ftDdb8DwCz44+13Sk GSTPaQbepDkS+9jJbHJNqsRLn6siTUGHmlDps7UcrB+0FgnOgOrSRoUkPpgAHaUDG0Qf CpGljC0Ilg1Go/8sHLZb2cAvAvTfmveWcJbukEPM73aWu1N9htxppnjwXFZX4KNEnuY1 zfBuq5/dt9oaQgHgy7heslrpKUTgRL05J3Bx/PYe0pmtWrHnJJ6CafnmbLy8c9b3+N8k bLBQAIOKsQScHH1EGj1BmBWPNUF5mbTWqNjD8ALR/8qiqGEoiNu3xsddsjINncq4T4W8 cWgQ== MIME-Version: 1.0 X-Received: by 10.182.29.33 with SMTP id g1mr7678267obh.59.1389887954828; Thu, 16 Jan 2014 07:59:14 -0800 (PST) Received: by 10.76.132.9 with HTTP; Thu, 16 Jan 2014 07:59:14 -0800 (PST) In-Reply-To: References: Date: Thu, 16 Jan 2014 07:59:14 -0800 Message-ID: Subject: Re: FreeBSD 10.0-RC4 pkg upgrade QT conflict From: Freddie Cash To: CeDeROM Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Stable , freebsd-ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 15:59:16 -0000 On Thu, Jan 16, 2014 at 5:26 AM, CeDeROM wrote: > I have solved this issue with "pkg delete -xf qt4-; pkg upgrade" - all > packages now match binary release, no more conflicts. > > I guess it was produced by compiling+installing some stuff from ports, > which introduced some inconsistency, even though "WITH_PKGNG=3Dyes" was s= et > in /etc/make.conf... > =E2=80=8BThe inconsistency comes when you use a different ports tree (diffe= rent versions of things in the tree) than what was used to compile the binary packages; or from selecting non-default OPTIONS when using the ports tree. If you only use binary packages, there's no inconsistencies, as everything is build at the same time, using the same ports tree and OPTIONS. If you only use the ports tree to compile things, there's no inconsistencies as everything is compiled (and kept up-to-date via portmaster) using the same ports tree and OPTIONS.=E2=80=8B When you mix the two, inconsistencies abound. Different ports tree lead to different versions and/or differenet OPTIONS selected etc. If you want to custom compile some ports, then using something like ports-mgmt/poudriere to bulk build binary packages based on a local ports tree is best. That gives you the ease of upgrade/install of binary packages, with the customisability of the ports tree, without any inconsistencies. =E2=80=8BI used to be a die-hard ports tree user, customising every port an= d tailoring everything to the machine. Since pkg was released as stable, though, I've compiled fewer and fewer ports. My home desktop runs PC-BSD using only binary packages, and the last 2 servers I've installed at work have used only binary packages. They really have come a long way ...=E2=80= =8B --=20 Freddie Cash fjwcash@gmail.com