From owner-freebsd-current@FreeBSD.ORG Mon Mar 17 17:39:52 2014 Return-Path: Delivered-To: current@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 DAEAF4D3; Mon, 17 Mar 2014 17:39:52 +0000 (UTC) Received: from secure.freebsdsolutions.net (secure.freebsdsolutions.net [69.55.234.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BC542134; Mon, 17 Mar 2014 17:39:52 +0000 (UTC) Received: from [10.10.1.198] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by secure.freebsdsolutions.net (8.14.4/8.14.4) with ESMTP id s2HHdhvC079614 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 17 Mar 2014 13:39:44 -0400 (EDT) (envelope-from lists@jnielsen.net) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: [HEADSUP] pkg 1.3.0 alpha1: Breath of fresh air from Kirov From: John Nielsen In-Reply-To: <20140317172130.GO90364@ithaqua.etoilebsd.net> Date: Mon, 17 Mar 2014 11:40:52 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <152DC71B-1208-46AD-9192-D45FBC938EB9@jnielsen.net> References: <20140317172130.GO90364@ithaqua.etoilebsd.net> To: Baptiste Daroussin X-Mailer: Apple Mail (2.1874) X-DCC-Etherboy-Metrics: ns1.jnielsen.net 1002; Body=4 Fuz1=4 Fuz2=4 X-Virus-Scanned: clamav-milter 0.97.8 at ns1.jnielsen.net X-Virus-Status: Clean Cc: ports@freebsd.org, stable@freebsd.org, FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Mar 2014 17:39:52 -0000 Looks great! Thanks as always for the work. I do have one question = (below). On Mar 17, 2014, at 11:21 AM, Baptiste Daroussin = wrote: > - Remove support for PACKAGESITE There are two cases where I still define PACKAGESITE in the environment, = specifically when building new jails or VM images. Can you suggest = alternatives? 1. Installing/bootstrapping the latest pkg from a specific source. Often = I build in an environment that is firewalled from the Internet at large = but I have a local repo. (And it's nice to know exactly what version = with which options I'm installing.) 2. Installing a package that includes a repo file for my local custom = repo. This is a chicken-and-egg problem for which PACKAGESITE was a nice = solution since there's no risk of a stale repo file being left = behind--either the package is installed (with the correct/current repo = file) or it isn't. JN