From owner-freebsd-ports@FreeBSD.ORG Fri Aug 15 12:43:27 2014 Return-Path: Delivered-To: freebsd-ports@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 6BFCCECF for ; Fri, 15 Aug 2014 12:43:27 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 12A8C28DA for ; Fri, 15 Aug 2014 12:43:26 +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 s7FChORr094452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Aug 2014 13:43:24 +0100 (BST) Date: Fri, 15 Aug 2014 13:43:25 +0100 From: Karl Pielorz To: =?UTF-8?Q?=C5=81ukasz_W=C4=85sikowski?= , freebsd-ports@freebsd.org Subject: Re: Ports, pkg's confusion on upgrades... Message-ID: <2A69DCE1B30998B865D46192@Mail-PC.tdx.co.uk> In-Reply-To: <53EDE679.9050105@wasikowski.net> References: <52652ABEC925BB93CB8877CD@Mail-PC.tdx.co.uk> <53EDE679.9050105@wasikowski.net> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2014 12:43:27 -0000 --On 15 August 2014 12:52 +0200 =C5=81ukasz W=C4=85sikowski = =20 wrote: > You could solve this by using your own poudriere - create repos with > your own port's options and pkg upgrade everything. Your current > approach - mixing packages and ports - is not supported IIRC. Thanks for the suggestion - and I take your point about not mixing ports &=20 packages... Setting up our own pkg repo though sounds like a lot of work (all for the=20 sake of about probably 2 packages we need to change the options on) - I'd=20 guess there's no way of telling pkg to use 'our' repo for these 2-3=20 packages, and the main one for everything else? I suppose the other option is just ignore packages, and stick to ports?=20 (presuming ports will always be around :) I'd also still like to know if there's a way of getting 'pkg upgrade' to=20 spit out why it wants to install a 'new package' - when none of the current = packages have a dependency on it? This is going to happen at some point, even on a pkg only system (e.g. what = happens when pkg upgrade says it's going to install X11 [which nothing=20 currently 'depends' on] - but obviously some upgraded package does - you'd=20 really want to know what's going to cause X to be installed? -Karl