Lots of core files with latest xscreensaver-gnome

[Stacey Roberts]

Hi Adam,
   Thanks for the time..,

----- Original Message -----
From: "Adam Weinberger <adamw at freebsd.org>"
To: To Stacey Roberts
Date: Mon, 03 May, 2004 19:45 BST
Subject: Re: Lots of core files with latest xscreensaver-gnome

> >> (05.03.2004 @ 1344 PST): Stacey Roberts said, in 3.6K: <<
> > Hi Adam,
> > 
> > ----- Original Message -----
> > From: "Adam Weinberger <adamw at FreeBSD.org>"
> > To: To Stacey Roberts
> > Date: Mon, 03 May, 2004 17:54 BST
> > Subject: Re: Lots of core files with latest xscreensaver-gnome
> > 
> > > Clear out everything in /usr/local/lib/compat/pkg and the run:
> > > 
> > > portupgrade -u -a -f
> > > 
> > > That will rebuild everything. After you clear out
> > > /usr/local/lib/compat/pkg, nothing will run until you complete the
> > > portupgrade.
> > 
> > Thanks for the reply.
> > 
> > As nothing (presumably this refers to X-related apps) will run in between "rm -rf'ing /usr/local/lib/compat/pkg/*" and the portupgrade cmd, is it best then, to ensure that no-one is logged in on X during this exercise?
> > 
> > If anything I'll be looking to run this overnight.
> > 
> > Thanks again, Adam.
> > 
> > Regards,
> > 
> > Stacey
> >> end of "Re: Lots of core files with latest xscreensaver-gnome" from Stacey Roberts <<
> 
> That's probably the safest behaviour, yes. It's not that *nothing* will
> run, but after you delete the stuff in .../pkg, a whole bunch of things
> will be missing libraries.

Fair enough.., I'll make sure that X is off before the exercise for each machine. I don't suppose you'd be able to let me know what kind of time-frame I could expect in terms of round-trip completion, would you?

> 
> I hope that someday they'll make -u a default argument to
> portupgrade(1).

Hmm.., reading through the man pages here (from a *NON*-developer's perpective), I guess I could see why the "-u" switch isn't default, just in case *something* fails during the install / registration stages I suppose. Then there's a way to back out. But again, I stress that I'm not pretending to understand that stuff.

On that note though.., see as on all my systems gnomemeeting is un-portupgradeable (openh323-1.12.0_3 is forbidden: http://people.freebsd.org/~eik/portaudit/27c331d5-64c7-11d8-80e3-0020ed76ef5a.html), what are the chances of gnomemeeting being in this state causing problems? I guess I'll find out later tonight, but its good to be prepared.


Thanks again, Adam.

Regards,

Stacey

> 
> # Adam
> 
> 
> --
> Adam Weinberger
> adamw at magnesium.net || adamw at FreeBSD.org
> adamw at vectors.cx    ||   adamw at gnome.org
> http://www.vectors.cx

-- 
Stacey Roberts
B. Sc (HONS) Computer Science

Web: www.vickiandstacey.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 466 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20040503/b8d38aeb/attachment.bin