From owner-freebsd-gnome@FreeBSD.ORG Thu Jun 24 03:00:10 2004 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 39F8A16A4CE for ; Thu, 24 Jun 2004 03:00:10 +0000 (GMT) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E46B543D4C for ; Thu, 24 Jun 2004 03:00:09 +0000 (GMT) (envelope-from johnmary@adelphia.net) Received: from 68-169-191-75.losaca.adelphia.net ([68.169.191.75]) by mta10.adelphia.netESMTP <20040624030009.PNBD12887.mta10.adelphia.net@68-169-191-75.losaca.adelphia.net>; Wed, 23 Jun 2004 23:00:09 -0400 Received: by 68-169-191-75.losaca.adelphia.net (Postfix, from userid 1001) id CB13B62DB; Wed, 23 Jun 2004 20:00:21 -0700 (PDT) Date: Wed, 23 Jun 2004 20:00:21 -0700 From: John Merryweather Cooper To: Joe Marcus Clarke Message-ID: <20040624030021.GA56728@borgdemon.losaca.adelphia.net> References: <1088040025.91312.14.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1088040025.91312.14.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.2.1i Phone: 1-509-338-9391 WWW-Home-Page: http://www.borgsdemons.com/ cc: FreeBSD GNOME Users Subject: Re: HEADS UP: New gconf key policy X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2004 03:00:10 -0000 On Wed, Jun 23, 2004 at 09:20:25PM -0400, Joe Marcus Clarke wrote: > Please take a look at the latest update to archivers/fileroller, and let > me know what you think. This is the new gconf policy I think we need to > adopt if we're to survive the upcoming gconf changes in GNOME 2.8 (it's > similar to the way we handle OMF files now). This will also make gconf > handling much more robust with respect to plists. > > The one downside I see with this is that we will miss Makefile bugs that > prevent proper schema installation. One way around that is to add a > pkg-install script to each port that installs gconf schemas, and do > gconf registration there. This may be more work than it's worth, > though. > > What are people's thoughts on this? Thanks. > > Joe > > -- > PGP Key : http://www.marcuscom.com/pgp.asc Well, there seems to be an increasing amount of post-install tasks in GNOME ports, so I think the idiom of using a pkg-install script for each port is a good one. Turning to a design issue, do you see the changes to gconf handling as making debugging of gconf-related issues easier or harder. I'm having a devil of a time wrestling an update of comms/gfax into working order because of gconf issues. jmc