Date: Thu, 24 Jul 2008 23:31:07 +0400 From: Boris Samorodov <bsam@ipt.ru> To: Derek Belrose <derekb@realgeeky.com> Cc: freebsd-questions@freebsd.org Subject: Re: Port Management on a larger scale Message-ID: <48237076@ipt.ru> In-Reply-To: <92B9E4E7-B8AB-41E6-952D-C24F6BD95F39@realgeeky.com> (Derek Belrose's message of "Tue\, 22 Jul 2008 00\:41\:46 -0400") References: <92B9E4E7-B8AB-41E6-952D-C24F6BD95F39@realgeeky.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Jul 2008 00:41:46 -0400 Derek Belrose wrote: > Sorry if this has been asked before, but I've inherited a fairly large > number of FreeBSD servers. All of them are running 6.3. > What is the recommended way of doing port management? Or if there > isn't a recommended way of updating ports on 10-15 servers, what do > people do? How do you handle port upgrades that deal with custom > compile configurations (such as exim with postgresql)? Do you build a > port on one system and install it as a package on all the others? > I come from a Slackware background, and in the past I would compile > the update on a test system then distribute and install to all the > other servers. You may take a look at ports-mgmt/tinderbox. It builds packages with custom configuration. Those packages may be installed by a "portupgrade -PP" command. We use a special 8-CURRENT tinderbox machine to build packages for 8-x, 7-x, 6-x FreeBSD versions. WBR -- bsam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48237076>