From owner-freebsd-gnome@FreeBSD.ORG Fri Aug 29 14:32:34 2003 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFC5616A4C0 for ; Fri, 29 Aug 2003 14:32:34 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA93443FD7 for ; Fri, 29 Aug 2003 14:32:33 -0700 (PDT) (envelope-from mdonadio@comcast.net) Received: from comcast.net (pcp01403617pcs.radnor01.pa.comcast.net[68.81.79.105]) by comcast.net (rwcrmhc11) with SMTP id <2003082921323301300asen8e> (Authid: mdonadio); Fri, 29 Aug 2003 21:32:33 +0000 Message-ID: <3F4FC68A.BEE0199@comcast.net> Date: Fri, 29 Aug 2003 17:32:58 -0400 From: Matthew Donadio X-Mailer: Mozilla 4.79 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Joe Marcus Clarke References: <3F4F9156.7AEAB897@comcast.net> <1062179702.47188.28.camel@shumai.marcuscom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-gnome@freebsd.org Subject: Re: Gnome 2.4 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: m.p.donadio@ieee.org List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2003 21:32:35 -0000 Joe Marcus Clarke wrote: > There haven't been any GNOME > components removed, only moved. That is, bonobo-activation will be part > of libbonobo, stickynotes_applet will be part of gnomeapplets2, and > themus and fontilus will be part of gnomecontrolcenter2. Ah, this makes sense now. > > For those of us who track the ports tree, should there be any headaches > > that we should be aware of, or will a cvsup and porupgrade be > > sufficient? > > I'm still working on that. I don't want to have to hunt down all the > ports that depend on, say, atk, and bump their PORTREVISIONS (though, if > people think I should, I will). > > What I'm considering now is the following recipe: > ... That looks cool. I was thinking of config issues that would result in logging into a wonked desktop. I just had a thought. How is nautilus-cd-burner implemented? If it uses the CAM layer, then there probably needs to be something mentioned in a README since atapicam isn't in the GENERIC kernconf file. -- Matthew Donadio (m.p.donadio@ieee.org)