From: Spam on
On Thu, 3 Dec 2009, Balwinder S Dheeman wrote:
> Append:
>
> BATCH=yes
>
> to your /etc/make.conf

Ouch! Thanks all who advised about BATCH ... I've killed the update, and
restarted with the BATCH parameter set ...

Cheers,
Rob
From: Stan Barr on
On 3 Dec 2009 16:43:02 GMT, Bob Eager <rde42(a)spamcop.net> wrote:
> On Thu, 03 Dec 2009 16:35:58 +0000, Stan Barr wrote:
>
>> On Wed, 2 Dec 2009 14:52:06 -0500, Spam(a)ControlQ.com <Spam(a)ControlQ.com>
>> wrote:
>>
>>> It seems that installed ports/packages must be recompiled/relinked. I
>>> have 680 installed packages, and each one is being systematically
>>> recompiled from the ports. This would be OK, were it not for the fact
>>> that some (not all) ports launch a curses based window manager (text
>>> based) to ask for configuration options, and the build freezes at that
>>> point, waiting for input. Its been running for 3 days, with no end in
>>> sight, and I have to constantly check to see if the port/package build
>>> requires input.
>>
>> Oh dear...I guess I'll have the same problem :-(
>
> Not if you set the environment variable BATCH first. Any value will do -
> even "NO"!
>
>
>

Thanks everyone for all the tips! All saved for when I get started.
I'll do the sparc first - no X and no graphics apps, got to be easier.

--
Cheers,
Stan Barr plan.b .at. dsl .dot. pipex .dot. com

The future was never like this!
From: Giorgos Keramidas on
On Wed, 2 Dec 2009 14:52:06 -0500, Spam(a)ControlQ.com wrote:
> It seems that installed ports/packages must be recompiled/relinked. I
> have 680 installed packages, and each one is being systematically
> recompiled from the ports. This would be OK, were it not for the fact
> that some (not all) ports launch a curses based window manager (text
> based) to ask for configuration options, and the build freezes at that
> point, waiting for input. Its been running for 3 days, with no end in
> sight, and I have to constantly check to see if the port/package build
> requires input.

This is the recommended way of upgrading across _major_ branches (6.X ->
7.0, 7.X -> 8.0, etc.). The fastest way to upgrade all packages is to
use pre-built packages from the CD-ROM and something like:

portupgrade -PP

Having said that, I prefer rebuilding the packages, because I like using
some non-default options in many of the ports.

From: Giorgos Keramidas on
On Thu, 03 Dec 2009 13:56:23 -0500, Lowell Gilbert <lgusenet(a)be-well.ilk.org> wrote:
>Tim Daneliuk <tundra(a)tundraware.com> writes:
>> OK, I'm officially confused. I have a production 7.2-Stable server.
>> I build new releases using csup and then recompiling the entire
>> source tree nightly (though I do not always/often install it later).
>> If I change my csup config to get the 8.0 source, recompile, and then
>> install them (which is how I migrated from 6.x to 7.x) am I then
>> going to have to recompile my entire installed base of ports as well?
>> I don't recall having to do this when I did the aforementioned 6.x to
>> 7.x upgrade. Oh, this is i386 in all cases...
>
> You don't need to do it immediately, but you'll need to update
> everything eventually (probably before you install new ports or update
> old ones). Otherwise, you'll end up with something linked to
> libraries from *both* the old and new version, and that won't work at
> all.

Very good point :)

From: Christoph Weber-Fahr on
Hello,

Spam(a)ControlQ.com wrote:

> It seems that installed ports/packages must be recompiled/relinked. I
> have 680 installed packages, and each one is being systematically
> recompiled from the ports. This would be OK, were it not for the fact
> that some (not all) ports launch a curses based window manager (text
> based) to ask for configuration options, and the build freezes at that
> point, waiting for input.

You are aware that this can be suppressed by the BATCH environment
variable?

furthermore, portupgrade also should suppress this accordingly.
What do you use for upgrading those ports?

Regards

Christoph Weber-Fahr