Date: Wed, 27 Oct 2004 10:25:17 -0700 From: "Zoltan Frombach" <zoltan@frombach.com> To: "Kris Kennaway" <kris@obsecurity.org>, "Andre Guibert de Bruet" <andy@siliconlandmark.com>, "Ruben de Groot" <mail25@bzerk.org> Cc: freebsd-current@freebsd.org Subject: Re: Portupgrade -af question Message-ID: <001601c4bc49$ed540ec0$e201a8c0@p4> References: <BAY2-DAV100Bqhk6KR800012731@hotmail.com><20041027003640.K42571@alpha.siliconlandmark.com> <20041027140705.GA26376@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, Oct 26, 2004 at 10:35:16PM -0700, Zoltan Frombach typed:
>> 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
>
> You can omit step 8 by editing /usr/local/etc/pkgtools.conf. e.g.
>
> MAKE_ARGS = {
> 'lang/perl5.8' => 'WITH_THREADS=yes',
> }
In fact, I do have those compile options set in my
/usr/local/etc/pkgtools.conf file. But are you sure that portupgrade will
use those even when called with the -P flag ( eg: portupgrade -af -P )? If
it is true then of course step 8 can be eliminated. Can anyone confirm this?
Zoltan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001601c4bc49$ed540ec0$e201a8c0>