minor patch for gconf

Joe Marcus Clarke marcus at marcuscom.com
Mon Jul 14 16:37:13 PDT 2003


On Mon, 2003-07-14 at 19:22, Mikhail Teterin wrote:
> =On Mon, 2003-07-14 at 18:16, Mikhail Teterin wrote:
> => Hello!
> => 
> => Gconf does not really care, which db-backend it is going to use, it
> => seems. The following patch makes it accept anything, but default to
> => db41. If the user already has, say, db2 installed, there is no need
> => to drag in another version of db just for gconf, is there?
> =>
> => The patch relies on the ability to use regular expressions in the
> => LIB_DEPENDS lines, committed in March by kris. Should a particular
> => version of db be non-suitable for gconf, it is trivial to modify the
> => patch's regular expression. Thanks!
> 
> =Technically, this won't work, but that's okay.
> 
> 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.

> 
> ===>   gconf-1.0.9_3 depends on executable: gmake - found
> ===>   gconf-1.0.9_3 depends on file: /opt/libexec/libtool13/libtool - found
> ===>   gconf-1.0.9_3 depends on executable: pkg-config - found
> ===>   gconf-1.0.9_3 depends on shared library: guile.15 - found
> ===>   gconf-1.0.9_3 depends on shared library: db[0-9]+ - found
> ===>   gconf-1.0.9_3 depends on shared library: X11.6 - found
> ===>   gconf-1.0.9_3 depends on shared library: glib12.3 - found
> ===>   gconf-1.0.9_3 depends on shared library: gtk12.2 - found
> ===>   gconf-1.0.9_3 depends on shared library: xml.5 - found
> ===>   gconf-1.0.9_3 depends on shared library: ORBit.2 - found
> ===>   gconf-1.0.9_3 depends on shared library: oaf.0 - found
> ===>  Configuring for gconf-1.0.9_3
> [...]
> 
> =The DB backend isn't used by GConf anyway. You could simply hack
> =gconf's configure to remove DB detection altogether, and that would be
> =fine.
> 
> 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).

Joe

> 
> 	-mi
> 
> => ===================================================================
> => RCS file: /home/ncvs/ports/devel/gconf/Makefile,v
> => retrieving revision 1.38
> => diff -U2 -r1.38 Makefile
> => --- Makefile	12 Jun 2003 09:45:56 -0000	1.38
> => +++ Makefile	14 Jul 2003 22:15:53 -0000
> => @@ -19,5 +19,5 @@
> =>  
> =>  LIB_DEPENDS=	guile.15:${PORTSDIR}/lang/guile \
> => -		db3.3:${PORTSDIR}/databases/db3
> => +		db[0-9]+:${PORTSDIR}/databases/db41
> =>  
> =>  USE_BZIP2=	yes
> => 
> => 
> => _______________________________________________
> => freebsd-gnome at freebsd.org mailing list
> => http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> => To unsubscribe, send any mail to "freebsd-gnome-unsubscribe at freebsd.org"
> 
-- 
PGP Key : http://www.marcuscom.com/pgp.asc


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20030714/0dc1fe84/attachment.bin


More information about the freebsd-gnome mailing list