From owner-freebsd-questions@FreeBSD.ORG Wed Mar 7 01:45:06 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D432A106566B for ; Wed, 7 Mar 2012 01:45:06 +0000 (UTC) (envelope-from freebsd-questions@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 4DFB98FC16 for ; Wed, 7 Mar 2012 01:45:06 +0000 (UTC) Received: from mail.unitedinsong.com.au (bell.herveybayaustralia.com.au [192.168.0.40]) by mail.unitedinsong.com.au (Postfix) with ESMTP id 033045C28 for ; Wed, 7 Mar 2012 11:58:28 +1000 (EST) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 346F05C22 for ; Wed, 7 Mar 2012 11:58:28 +1000 (EST) Message-ID: <4F56BC66.5000908@herveybayaustralia.com.au> Date: Wed, 07 Mar 2012 11:39:50 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4F547C59.1040604@bananmonarki.se> <4F548571.1050203@gmail.com> <4F54ED12.1090409@bananmonarki.se> <20120305175551.ae24b6f0.freebsd@edvax.de> <4F564B17.1010700@bananmonarki.se> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: port to package amd64 to i386 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2012 01:45:06 -0000 On 03/07/12 04:13, Adam Vande More wrote: > On Tue, Mar 6, 2012 at 11:36 AM, Bernt Hansson wrote: > >> Again, a "problem" is that packages can only be generated >>> if the port has been installed >>> >> Why is that. I hope you can educate me on that. >> > Because a package is the result of what is installed. It essentially works > somewhat like Debian's checkinstall by keeping track of what's installed by > the installation script, then using the info of what's installed to build > the package. I'm not exactly sure how "make package" works internally, but > it wouldn't surprise me if it's almost the same as "pkg_create -b". From what I understand of ports (as a maintainer) that is the case; plus some other bits and pieces for checking, verification, and cleanup.