Date: Wed, 27 Oct 2004 01:08:52 -0400 (EDT) From: Andre Guibert de Bruet <andy@siliconlandmark.com> To: Zoltan Frombach <tssajo@hotmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Portupgrade -af question Message-ID: <20041027010516.Y42571@alpha.siliconlandmark.com> In-Reply-To: <BAY2-DAV18BYXifWoqF000128bb@hotmail.com> References: <BAY2-DAV100Bqhk6KR800012731@hotmail.com> <BAY2-DAV18BYXifWoqF000128bb@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Oct 2004, Zoltan Frombach wrote: > Thank you for your prompt reply! All of the mentioned conditions are true in > my case, so I guess this is the way I'm gonna go. I have a few ports that I > compile with custom command line options, but I can always re-compile those > later just by issuing individual portupgrade -f portname commands. My main > point is to shorten the downtime this server must suffer at the > "upgradathon". ;-) Just as a word of caution, when jumping between versions of FreeBSD, you should upgrade ruby and portupgrade manually first and then performing the portupgrade on all ports. This isn't documented, but I've run into instances where some changes to the base system broke ruby... Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041027010516.Y42571>