It's not a workaround - it is a real fix as suggested by gconf documentation and it's used by linux distros (see debian[1] and gentoo[2]).
[1] http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gconf/debian/gconf2.postinst?revision=31302&view=markup [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/gnome2-utils.eclass?diff_format=s&revision=1.31&view=markup On Mon, Aug 5, 2013 at 9:40 PM, Torfinn Ingolfsen <tin...@gmail.com> wrote: > On Sun, Aug 4, 2013 at 8:42 PM, Marcin Wisnicki > <mwisnicki+free...@gmail.com> wrote: >> I guess bsd.gnome.mk should be smart enough to `killall -HUP gconfd-2` >> at package post-install when port uses gconf (has GCONF_SCHEMAS). >> Please file a PR against gnome ports. > > Are you sure that this way (killall -HUP ...) is the correct fix? > It seems like a workaround (instead of a real fix) to me, based on the > discussion in the two bugs I listed in my previous message. > Also, pkill -HUP gconfd-2 didn't work for me, I had to kill the > gconfd-2 process totally. > HTH > -- > Regards, > Torfinn Ingolfsen _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
