From owner-freebsd-gnome@FreeBSD.ORG Thu Jun 24 01:20:47 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 0E07F16A4CE for ; Thu, 24 Jun 2004 01:20:47 +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 8A0AD43D1F for ; Thu, 24 Jun 2004 01:20:46 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) i5O1JUIA002610 for ; Wed, 23 Jun 2004 21:19:30 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: FreeBSD GNOME Users Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-xFQ9weWJXKU9JWRxFJYq" Organization: MarcusCom, Inc. Message-Id: <1088040025.91312.14.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 23 Jun 2004 21:20:25 -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 Subject: 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 01:20:47 -0000 --=-xFQ9weWJXKU9JWRxFJYq Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-xFQ9weWJXKU9JWRxFJYq 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) iD8DBQBA2ixZb2iPiv4Uz4cRAkUhAJ9JXwqU/u6H7ZpGVdg38LQ3seEvFwCfUgER rT8YBEA/6H55iO/I34mPgow= =yI7L -----END PGP SIGNATURE----- --=-xFQ9weWJXKU9JWRxFJYq--