Date: Tue, 26 Oct 2004 22:35:16 -0700 From: "Zoltan Frombach" <tssajo@hotmail.com> To: "Andre Guibert de Bruet" <andy@siliconlandmark.com> Cc: freebsd-current@freebsd.org Subject: Re: Portupgrade -af question Message-ID: <BAY2-DAV9VApwOLZCHu00012752@hotmail.com> References: <BAY2-DAV100Bqhk6KR800012731@hotmail.com><BAY2-DAV18BYXifWoqF000128bb@hotmail.com> <20041027010516.Y42571@alpha.siliconlandmark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I was planning to recompile portupgrade manually first. But I didn't
know/remember that it was dependent on ruby. So here is what I'm gonna do
step by step:
1. cvsup src to 5.3-RELEASE (when it becomes available)
2. cvsup the ports tree to the latest skeleton - still using the 5.2 system
3. upgrade kernel + world (including the mergmaster step, of course)
I will follow the official updating guide step by step and very
carefully
4. double-check if ftp and http connection is still working with new kernel
5. recompile ruby manually
6. recompile portupgrade manually
7. portupgrade -af -P
8. recompile the few ports that needs special options and/or local patching
I believe this will work and will save a lot of time!
Thanks again for the help!!
Zoltan
----- Original Message -----
From: "Andre Guibert de Bruet" <andy@siliconlandmark.com>
To: "Zoltan Frombach" <tssajo@hotmail.com>
Cc: <freebsd-current@freebsd.org>
Sent: Tuesday, October 26, 2004 10:08 PM
Subject: Re: Portupgrade -af question
>
> 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/ >
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY2-DAV9VApwOLZCHu00012752>