Date: Thu, 11 Oct 2007 06:15:19 +0000 From: "Aryeh Friedman" <aryeh.friedman@gmail.com> To: "Bill Stwalley" <stwalley2004@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: best way to update ports Message-ID: <bef9a7920710102315s24d22ec8l44efab8c63e09886@mail.gmail.com> In-Reply-To: <687f2b920710102251i4b3b3bf8uadcae71dc407881@mail.gmail.com> References: <687f2b920710102233ve746e2auece74d1e95486e73@mail.gmail.com> <bef9a7920710102241l4cda1cbcn542ba752fc1d5f51@mail.gmail.com> <687f2b920710102251i4b3b3bf8uadcae71dc407881@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> yeah, in that situation nfs mount will be easy. > > My servers are in different cities, and the ports are installed with > different options on different servers, for example, some postfix use unix > login accounts, some postfix use courier authentication with mysql database. > So unfortunately I can't share the same ports among them. In a simelar situation I did this by setting up a centeral cvsup mirror (allows you to maintain patches between cvsupdates [i.e. if the file does not differ rcs stamp will not clobber it]). So you always have the most upto date to build against. I am not sure on how to handle the manual security patches on there first application but once applied until the effect files are updated you will not have to reapply the patches.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bef9a7920710102315s24d22ec8l44efab8c63e09886>