Re: Portupgrade -af question

> On Wed, Oct 27, 2004 at 10:32:12AM -0700, Kris Kennaway typed:
>> On Wed, Oct 27, 2004 at 10:26:49AM -0700, Zoltan Frombach wrote:
>>
>> > >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 )?
>>
>> Such environment variables have no effect on pkg_add (i.e. portupgrade
>> -P), because the package has already been compiled and its build
>> options were set at that time.
>
> Yes. Wouldn't it be a nice feature for "portupgrade -P" to install the
> port
> instead of the package if any non-defaults were defined in pkgtools.conf?
>
> (I guess now's the time for me to learn some ruby)

This would be awesome!

On the other hand, I also use some custom local patches for some of my ports
when I build them. In those cases I just place my additional patch files
into the port's 'files' directory (inside the ports tree). It works, but
only if I compile these ports locally, of course. I don't believe that
portupgrade can detect these extra patch files when using the -P option...
So I just keep a list of these locally patched ports installed on my system
(fortunately, there are only a few of these) and I will re-compile them one
by one issuing 'portugrade -f portname' commands right AFTER
'portupgrade -af -P' has completed. IMO, there is just no other way to take
care of these locally patched ports. And since I have to do this anyway,
might as well do the same with all the ports that have custom options in my
pkgtools.conf file... For now I have to anyway. Unless you quickly hack
portupgrade's source code in ruby. ;-)

BTW, cvsup'ing the ports tree sometime wipes out my custom patches from the
ports tree, too. I can live with it, because it only happens when the same
file is being patched with an 'official' patch by the port maintener. Then
that patch oreplaces my custom patch. This is another thing I must watch out
for when I cvsup'ing my ports skeleton... I can live with it, though.

Zoltan