I don't think we want a config file for the no-gconf case; embedded people

2006-05-12  Elijah Newren  <newren gmail com>

	* configure.in: I don't think we want a config file for the
	no-gconf case; embedded people would prefer hard-coding things
	into the binary
	(http://mail.gnome.org/archives/metacity-devel-list/2006-May/msg00010.html)
This commit is contained in:
Elijah Newren 2006-05-12 17:46:53 +00:00 committed by Elijah Newren
parent 9f21db5366
commit 34cb1840cf
2 changed files with 9 additions and 5 deletions

View File

@ -1,3 +1,10 @@
2006-05-12 Elijah Newren <newren gmail com>
* configure.in: I don't think we want a config file for the
no-gconf case; embedded people would prefer hard-coding things
into the binary
(http://mail.gnome.org/archives/metacity-devel-list/2006-May/msg00010.html)
2006-04-25 Elijah Newren <newren gmail com>
* HACKING: Clarify that gnome-common is needed now that autogen.sh

View File

@ -483,11 +483,8 @@ AC_OUTPUT
if test x$enable_gconf = xno; then
echo "*** WARNING WARNING WARNING WARNING WARNING"
echo "*** Building without GConf"
echo "*** This means there's no way to change prefs except"
echo "*** hacking source code, at least for now."
echo "*** Also, some prefs may have broken defaults."
echo "*** Patches needed for a simple no-gconf config file."
echo "*** Building without GConf. This means there's no"
echo "*** way to change prefs except hacking source code."
echo "*** This is intended for embedded systems etc., not for normal use."
fi