From owner-freebsd-ports@FreeBSD.ORG  Wed Aug 13 09:46:37 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0DF4FD56
 for <freebsd-ports@freebsd.org>; Wed, 13 Aug 2014 09:46:37 +0000 (UTC)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id AC8A32BB9
 for <freebsd-ports@freebsd.org>; Wed, 13 Aug 2014 09:46:36 +0000 (UTC)
Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251])
 (authenticated bits=0)
 by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s7D9jJlP016919
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-ports@freebsd.org>; Wed, 13 Aug 2014 10:45:19 +0100 (BST)
Date: Wed, 13 Aug 2014 10:45:18 +0100
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: freebsd-ports@freebsd.org
Subject: Ports, pkg's confusion on upgrades...
Message-ID: <52652ABEC925BB93CB8877CD@Mail-PC.tdx.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Wed, 13 Aug 2014 09:46:37 -0000


Hi,

We have a number of 10.x systems now - where we install packages (aka pkg 
install) some components, but other components we build from ports (as we 
need to add / remove options that the package gives you no choice over).

Initially 'pkg upgrade' wanted to replace the port versions with pkg 
versions (which include options we don't want, and would have pulled in a 
lot of other dependencies).

I seem to have fixed this by 'locking' them (i.e. pkg lock) - pkg upgrade 
doesn't want to touch them now, which is good.

But, 'pkg upgrade' still wants to pull in more packages than are installed 
- i.e. 'pkg upgrade' shows entries under "to be INSTALLED" as well as "to 
be UPGRADED".

'pkg info -a -d' displays the dependencies of all installed packages (none 
of which depend on the package it wants to install) - but I can't seem to 
find any way to get 'pkg upgrade' to tell me why it wants to install a new 
package (i.e. which *upgrade* is it doing that now requires the "to be 
INSTALLED" packages?)


-Karl