Date: Mon, 14 Jul 2003 20:05:39 -0400 From: Mikhail Teterin <mi+mx@aldan.algebra.com> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: FreeBSD GNOME Users <gnome@freebsd.org> Subject: Re: minor patch for gconf Message-ID: <200307142005.39934@misha-mx.virtual-estates.net> In-Reply-To: <1058225812.299.100.camel@gyros> References: <200307141816.25067@misha-mx.virtual-estates.net> <200307141922.58178@misha-mx.virtual-estates.net> <1058225812.299.100.camel@gyros>
next in thread | previous in thread | raw e-mail | index | archive | help
=> I don't really use gconf (xmleditor dragged it in through the => gnomelibs), so I'm more interested in the "technicality", than in => getting anything done :-) Why would it not work? Seems to: =Because you'd have to edit gconf's configure to known about db4. Take a =lookg at patch-configure. I see. => I would think, it is imperative, that the bogus dependency is cut out => from the popular port. Unless I misunderstand you, this is a bug in => gconf, that the FreeBSD port of gconf better fixes, is not it? =It would be better to simply remove the db* dependency, and comment out =the checking code in configure (or break it). GConf has never used the =DB backend (only XML). This is exactly, what I was saying. Should I file a PR or will you, guys just do it? Yours, -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307142005.39934>