On Sun, 29 Nov 2009 12:16:15 -0800
Paul Hoffman wrote:
> At 12:50 AM + 11/29/09, Frank Shute wrote:
> >You don't mention what command you are using to upgrade your
> >ports/packages.
>
> Sorry: portupgrade -aPPR
Packages for a release are built against the ports tree that's
distributed with
On Sun, Nov 29, 2009 at 12:16:15PM -0800, Paul Hoffman wrote:
>
> At 12:50 AM + 11/29/09, Frank Shute wrote:
>
> >You don't mention what command you are using to upgrade your
> >ports/packages.
>
> Sorry: portupgrade -aPPR
My opinion is that you shouldn't use packages and compile from source
On Sun, 29 Nov 2009, Boris Samorodov wrote:
On Sun, 29 Nov 2009 12:16:15 -0800 Paul Hoffman wrote:
So, I have now done a long, painful
portrupgrade -a', having it stop regularly to prompt me for
configuration settings.
I'm sure portupgrade has an option to do a recursive configure
before act
On Sun, 29 Nov 2009 12:16:15 -0800 Paul Hoffman wrote:
> So, I have now done a long, painful
> portrupgrade -a', having it stop regularly to prompt me for
> configuration settings.
I'm sure portupgrade has an option to do a recursive configure
before actual upgrade. If it doesn't you may look at
At 12:50 AM + 11/29/09, Frank Shute wrote:
>You don't mention what command you are using to upgrade your
>ports/packages.
Sorry: portupgrade -aPPR
>You do realise that you don't have to upgrade your ports if you go
>from 7.1 to 7.2. You can do but don't have to.
No, I didn't realize that. Th
On Fri, Nov 27, 2009 at 07:47:03PM -0800, Paul Hoffman wrote:
>
> Greetings again. I used freebsd-update to upgrade a system from 7.1
> to 7.2. The main upgrade went fine, but upgrading the ports had huge
> problems. It could not find most (but not all) of the packages to
> upgrade. A typical part