From owner-freebsd-gnome@FreeBSD.ORG Thu Jun 24 04:56:14 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 4D08316A4CE for ; Thu, 24 Jun 2004 04:56:14 +0000 (GMT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70FDB43D41 for ; Thu, 24 Jun 2004 04:56:13 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) i5O4shA4003931; Thu, 24 Jun 2004 00:54:43 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: John Merryweather Cooper In-Reply-To: <20040624044920.GA12820@borgdemon.losaca.adelphia.net> References: <1088040025.91312.14.camel@shumai.marcuscom.com> <20040624030021.GA56728@borgdemon.losaca.adelphia.net> <1088049270.91312.19.camel@shumai.marcuscom.com> <20040624044920.GA12820@borgdemon.losaca.adelphia.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-05vGUeM5VduCfsKyb6zG" Organization: MarcusCom, Inc. Message-Id: <1088052939.91312.25.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 24 Jun 2004 00:55:39 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.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 04:56:14 -0000 --=-05vGUeM5VduCfsKyb6zG Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-06-24 at 00:49, John Merryweather Cooper wrote: > On Wed, Jun 23, 2004 at 11:54:30PM -0400, Joe Marcus Clarke wrote: > > On Wed, 2004-06-23 at 23:00, John Merryweather Cooper wrote: > > > 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, an= d let > > > > me know what you think. This is the new gconf policy I think we ne= ed 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 g= conf > > > > handling much more robust with respect to plists. > > > >=20 > > > > 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. > > > >=20 > > > > What are people's thoughts on this? Thanks. > > > >=20 > > > > Joe > > > >=20 > > > > --=20 > > > > PGP Key : http://www.marcuscom.com/pgp.asc > > >=20 > > > 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. > >=20 > > So far, there are only two (counting gconf) post-[de]install handlers > > that are being added the plists. I've written an omf.pl script (in my > > CVS repo) to handle automatically adding OMF handlers. I plan on doing > > the same for gconf. Given that, a pkg-install script might add more > > repo bloat that we need at this time. > >=20 > > > 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. > >=20 > > I don't think it will make gconf issues any harder to troubleshoot.=20 > > Like I said, it will "mask" the problem we see occasionally when a > > developer messes up one of the Makefiles, and schemas are not properly > > installed. > >=20 > > What gconf problems are you having? > >=20 > > Joe > >=20 > > >=20 > > > jmc > > >=20 > > --=20 > > PGP Key : http://www.marcuscom.com/pgp.asc >=20 > See attached patch to make comms/gfax into 0.6.0 (the gtk#) version. >=20 > Everything compiles and installs fine, but attempting to start gfax > gives errors about not being able to find two key values. I'd be > more specific, but I'm rebuilding GNOME right now and so my X is > unavailable to me. Well, this looks like a problem. From the gfax root Makefile: env GCONF_CONFIG_SOURCE=3D"" gconftool-2 --makefile-install-rule $(SCHEMA) This should probably be: GCONF_CONFIG_SOURCE=3D`gconftool-2 --get-default-source` gconftool-2 --makefile-install-rule $(SCHEMA) And of course, don't forget to install the schema file so you can remove the keys upon deinstall (something this application doesn't seem to do). Joe >=20 > jmc --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-05vGUeM5VduCfsKyb6zG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA2l7Kb2iPiv4Uz4cRAv9XAKCIe3qtW6CNniyC2WHCMyK31ATb2ACdHcUz ow/WNQMJ0jcFXGd0oQDSgVY= =XohZ -----END PGP SIGNATURE----- --=-05vGUeM5VduCfsKyb6zG--