Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 1 Jul 2005 08:15:29 -0400
From:      Bart Silverstrim <bsilver@chrononomicon.com>
To:        Odhiambo Washington <wash@wananchi.com>
Cc:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: port rebuild question
Message-ID:  <54c46109bdfe0c4a094b12303a7268ce@chrononomicon.com>
In-Reply-To: <20050630134635.GM7287@ns2.wananchi.com>
References:  <7a5eb7b4b0a5274f6c82e716809d4bed@chrononomicon.com> <20050630134635.GM7287@ns2.wananchi.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Jun 30, 2005, at 9:46 AM, Odhiambo Washington wrote:

> * Bart Silverstrim <bsilver@chrononomicon.com> [20050630 15:58]: wrote:
>> Silly question...
>>
>> If I want to rebuild amavisd-new and ALL p5 ports that amavis uses (so
>> I can make sure they are seeing the upgraded PERL version properly),
>> would I just use "portupgrade -rR amavisd-new"?
>
> I'd do portupgrade -f amavisd-new

Isn't this just a force upgrade? Amavisd-new thinks it's the latest 
version, at amavisd-new-2.3.1,1.  Or would this do the rebuild?

Wait...duh...manpage says it will *also* do a rebuild.  Second 
question; should this be done just to amavisd-new or also to PERL?  And 
is there a way to get all the subsequent modules to rebuild that depend 
on PERL afterwards again, all the p5*?

I'm CCing this also to the list to try to get some further responses; 
I'm beginning to wonder if I've somehow become persona non-grata on it. 
  You're the only one who's tried suggesting something to help me out so 
far! :-)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54c46109bdfe0c4a094b12303a7268ce>