From owner-freebsd-ports@FreeBSD.ORG Wed Jan 23 11:56:22 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 001FD16A418 for ; Wed, 23 Jan 2008 11:56:21 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from be-well.ilk.org (dsl092-078-145.bos1.dsl.speakeasy.net [66.92.78.145]) by mx1.freebsd.org (Postfix) with ESMTP id A83B213C44B for ; Wed, 23 Jan 2008 11:56:21 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from Lowell-Desk.lan (Lowell-Desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id 5736328430; Wed, 23 Jan 2008 06:56:18 -0500 (EST) Received: by Lowell-Desk.lan (Postfix, from userid 1147) id 73E4F1CC74; Wed, 23 Jan 2008 06:56:17 -0500 (EST) To: hans@lambermont.dyndns.org (Hans Lambermont) References: <20080122151037.316850@gmx.net> <20080122184553.GD30918@leia.lambermont.dyndns.org> From: Lowell Gilbert Date: Wed, 23 Jan 2008 06:56:17 -0500 In-Reply-To: <20080122184553.GD30918@leia.lambermont.dyndns.org> (Hans Lambermont's message of "Tue\, 22 Jan 2008 19\:45\:53 +0100") Message-ID: <44wsq0wyam.fsf@Lowell-Desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: c.mm@gmx.net, freebsd-ports@freebsd.org Subject: Re: create ports from list 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: Wed, 23 Jan 2008 11:56:22 -0000 hans@lambermont.dyndns.org (Hans Lambermont) writes: > c.mm@gmx.net wrote: > >> I have a server with round about 200 installed Ports. I need >> to setup a second server with the same, but slightly newer, >> ports recompiled from source. >> >> Is there an easy way to crate a port list > > Use the Root and Leaf sections from 'portmaster -l' > (ports-mgmt/portmaster) and skip the Trunk and Branch sections. Or just take the output from pkg_info directly; portmaster will figure out the dependencies on its own, so including the non-leaf ports is no problem. The other tools (e.g., portupgrade) will do the same thing. >> with compile options > > I try to use ports.conf (ports-mgmt/portconf) for this, but it does not > include the OPTIONS framework (/var/db/ports/*/options) . > > Maybe someone else can help further on this point, and Seems like a one-liner of a shell script. Maybe something like; # cd /usr/ports; for portname in `cat /path/to/port/list` ; do (cd $portname; make config) ; done (untested) >> and feed a build command on the second server with it? > > on this one as well. (I use my own script portsinstall.sh for this, it > uses a list like x11/xorg x11/kde3 devel/glib20 ...) My one-liner assumes a similar list. A brute force approach is to feed the whole list into portinstall (or portmaster, etc.).