From owner-freebsd-ports@FreeBSD.ORG Thu Sep 4 19:44:27 2003 Return-Path: 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 E270916A4BF for ; Thu, 4 Sep 2003 19:44:27 -0700 (PDT) Received: from gate.volant.org (gate.volant.org [207.111.218.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 598A543F85 for ; Thu, 4 Sep 2003 19:44:27 -0700 (PDT) (envelope-from patl+freebsd@volant.org) Received: from 64-144-229-193.client.dsl.net ([64.144.229.193] helo=[192.168.0.13]) by gate.volant.org with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 3.33 #1) id 19v6aA-000KB5-00; Thu, 04 Sep 2003 19:44:19 -0700 Date: Thu, 04 Sep 2003 19:44:17 -0700 From: Pat Lashley To: Roman Neuhauser , freebsd-ports Message-ID: <3615620000.1062729857@mccaffrey.phoenix.volant.org> In-Reply-To: <20030905023313.GG68249@freepuppy.bellavista.cz> References: <20030905023313.GG68249@freepuppy.bellavista.cz> X-Mailer: Mulberry/3.1.0b6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: ${INSTALL_COOKIE} and shared /usr/ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2003 02:44:28 -0000 --On Friday, September 05, 2003 04:33:13 +0200 Roman Neuhauser wrote: > Could ${INSTALL_COOKIE} include the hostname? If you do make install on > one box, and then want to install the port on another one that has the > /usr/ports tree nfs-mounted, it'll report that the port is already > installed. This is problematic with ports that have lots of runtime > dependencies, and I had recently quite some of this fun (finding all the > p5-* ports that needed to have the install cookie removed: my /usr/ports > is quite messy) with amavisd-new that I built and installed on one > system and then wanted to install it on another. If all of your systems have identical configurations, consider making packages on one system and installing from the package on others. If the systems have different sets of packages installed; or are different versions of the OS; then for safety you should completely re-build each port on each machine. In that case, I suggest setting WORKDIRPREFIX to some directory on local storage (i.e., not NFS-mounted) on each system. I'd also like to strongly recommend using portupgrade and portinstall. -Pat