gnomemeeting amd portupgrade (was: Lots of core files with latest xscreensaver-gnome)

[Tom McLaughlin]

On Wed, 2004-05-05 at 01:26, Stacey Roberts wrote:
> Hi Kevin,
>    
> ----- Original Message -----
> From: "Kevin Oberman <oberman at es.net>"
> To: To Stacey Roberts
> Date: Mon, 03 May, 2004 20:21 BST
> Subject: Re: Lots of core files with latest xscreensaver-gnome
> 
> > > Date: Mon, 3 May 2004 20:14:02 +0100
> > > From: Stacey Roberts <stacey at vickiandstacey.com>
> > > Sender: owner-freebsd-gnome at freebsd.org
> > > 
> > > <massive snip>
> > > 
> > > Fair enough.., I'll make sure that X is off before the exercise for each ma=
> > > chine. 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?
> > > 
> > > <snip>
> > > 
> > > Hmm.., reading through the man pages here (from a *NON*-developer's perpect=
> > > ive), 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 t=
> > > here's a way to back out. But again, I stress that I'm not pretending to un=
> > > derstand 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.
> > 
> > Gnomemeeting should not be a problem in this regard. It has also been
> > pulled from the standard gnome2 meta-port, so building gnome2 won't even
> > try to build gnomemeeting.
> 
> Actually Kevin, running "portupgrade -u -a -f" *does* attempt to rebuild Gnomemeeting,
> which failed. The rebuild has kept on going though, which I-suppose-is-kinda-okay? My
> question is, what affect is this likely to have on the machine at the end of this (so
> far 30-odd hour) rebuild?

Gnomemeeting is being rebuilt because of the -a and -f.  I think Kevin's
post missed that you are doing a forced portupgrade on all ports and not
just the gnome2 port.  As for the effects on your system, should be
nothing.  Gnomemeeting will be skipped and no ports should fail since
noting should be dependent on it.  I had gnomemeeting installed on my
old box and the port was just routinely skipped during each portupgrade
and I had no ill side effects.

> I'm also curious as to why Gnomemeeting *was* a part of this, given the suggestion 
> (above) that it shouldn't.

Gnomemeeting was part of the gnome2 meta-port until the problems with
pwlib were reported.  Gnomemeeting requires pwlib to build and when
pwlib was marked as forbidden gnomemeeting could no longer build. 
Gnomemeeting was removed from the gnome2 meta-port because it's failure
to build would cause a failure with gnome2.

Tom

> 
> Thanks for the time.
> 
> Regards,
> 
> Stacey
> 
> > 
> > Unfortunately, I use GnomeMeeting, so I am hoping to get a chance to
> > work on getting pwlib and openh323 updated soon. (Not that I'll succeed,
> > but, if I can point out specific problems to Roger H, I'm hoping he can
> > point me in the right direction.)
> > -- 
> > R. Kevin Oberman, Network Engineer
> > Energy Sciences Network (ESnet)
> > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> > E-mail: oberman at es.net			Phone: +1 510 486-8634