From owner-freebsd-ports@FreeBSD.ORG Tue Jun 20 23:58:58 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E9D516A479; Tue, 20 Jun 2006 23:58:58 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1692443D48; Tue, 20 Jun 2006 23:58:57 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 61A20D80484; Tue, 20 Jun 2006 19:58:56 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by frontend3.internal (MEProxy); Tue, 20 Jun 2006 19:59:00 -0400 X-Sasl-enc: BB8cbnOIng4MdBnXoDFW7nbERHM+lHrSgdDztYelcEf6 1150847940 Received: from bb-87-81-140-128.ukonline.co.uk (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by mail.messagingengine.com (Postfix) with ESMTP id 17F8781E4; Tue, 20 Jun 2006 19:59:00 -0400 (EDT) From: RW To: freebsd-ports@freebsd.org, freebsd-questions@freebsd.org Date: Wed, 21 Jun 2006 00:58:53 +0100 User-Agent: KMail/1.9.3 References: <200606191251.k5JCpo7Y054704@app.auscert.org.au> <4496A85E.6040800@FreeBSD.org> In-Reply-To: <4496A85E.6040800@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606210058.54615.list-freebsd-2004@morbius.sent.com> Cc: Subject: Re: portupgrade confusing '-P' and '-p'? 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: Tue, 20 Jun 2006 23:58:58 -0000 On Monday 19 June 2006 14:36, Sergey Matveychuk wrote: > freebsd-questions@auscert.org.au wrote: > > Hi, > > > > I'm in the middle of configuring a repeatable jail installation with some > > ports - in a nutshell, I want to install from locally built packages, but > > if not available locally I want to build the port myself _and_ create a > > package for future repetition. To prevent remote fetching, I set the > > PKG_FETCH variable to /bin/false as recommended. Here's the part I found > > curious: > > I don't understand how you plan to build a port without of fetching of a > distfile? PKG_FETCH is for packages, not distfiles.