summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHavoc Pennington <hp@src.gnome.org>1999-07-22 20:15:16 +0000
committerHavoc Pennington <hp@src.gnome.org>1999-07-22 20:15:16 +0000
commit7c6fe0a88f4024261bdde8a6d2f888fbc3ac6b92 (patch)
tree8496d3317abcdc12a07f07286bb4b903a9181a0b
downloadgconf-7c6fe0a88f4024261bdde8a6d2f888fbc3ac6b92.tar.gz
import
-rw-r--r--AUTHORS0
-rw-r--r--COPYING481
-rw-r--r--ChangeLog0
-rw-r--r--Makefile.am1
-rw-r--r--NEWS0
-rw-r--r--README0
-rw-r--r--acconfig.h8
-rwxr-xr-xautogen.sh61
-rw-r--r--backends/Makefile.am10
-rw-r--r--backends/xml-backend.c64
-rw-r--r--configure.in38
-rw-r--r--doc/thoughts.txt231
-rw-r--r--gconf/GConf.idl9
-rw-r--r--gconf/GConfX.idl9
-rw-r--r--gconf/Makefile.am11
-rw-r--r--gconf/gconf-backend.c19
-rw-r--r--gconf/gconf-backend.h54
-rw-r--r--gconf/gconf-internals.c68
-rw-r--r--gconf/gconf-internals.h84
-rw-r--r--gconf/gconf.h37
-rw-r--r--po/ChangeLog0
-rw-r--r--po/POTFILES.in0
-rw-r--r--stamp.h.in0
23 files changed, 1185 insertions, 0 deletions
diff --git a/AUTHORS b/AUTHORS
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/AUTHORS
diff --git a/COPYING b/COPYING
new file mode 100644
index 00000000..eb685a5e
--- /dev/null
+++ b/COPYING
@@ -0,0 +1,481 @@
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1991 Free Software Foundation, Inc.
+ 675 Mass Ave, Cambridge, MA 02139, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the library GPL. It is
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Library General Public License, applies to some
+specially designated Free Software Foundation software, and to any
+other libraries whose authors decide to use it. You can use it for
+your libraries, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if
+you distribute copies of the library, or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link a program with the library, you must provide
+complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ Our method of protecting your rights has two steps: (1) copyright
+the library, and (2) offer you this license which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ Also, for each distributor's protection, we want to make certain
+that everyone understands that there is no warranty for this free
+library. If the library is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original
+version, so that any problems introduced by others will not reflect on
+the original authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that companies distributing free
+software will individually obtain patent licenses, thus in effect
+transforming the program into proprietary software. To prevent this,
+we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+ Most GNU software, including some libraries, is covered by the ordinary
+GNU General Public License, which was designed for utility programs. This
+license, the GNU Library General Public License, applies to certain
+designated libraries. This license is quite different from the ordinary
+one; be sure to read it in full, and don't assume that anything in it is
+the same as in the ordinary license.
+
+ The reason we have a separate public license for some libraries is that
+they blur the distinction we usually make between modifying or adding to a
+program and simply using it. Linking a program with a library, without
+changing the library, is in some sense simply using the library, and is
+analogous to running a utility program or application program. However, in
+a textual and legal sense, the linked executable is a combined work, a
+derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+ Because of this blurred distinction, using the ordinary General
+Public License for libraries did not effectively promote software
+sharing, because most developers did not use the libraries. We
+concluded that weaker conditions might promote sharing better.
+
+ However, unrestricted linking of non-free programs would deprive the
+users of those programs of all benefit from the free status of the
+libraries themselves. This Library General Public License is intended to
+permit developers of non-free programs to use free libraries, while
+preserving your freedom as a user of such programs to change the free
+libraries that are incorporated in them. (We have not seen how to achieve
+this as regards changes in header files, but we have achieved it as regards
+changes in the actual functions of the Library.) The hope is that this
+will lead to faster development of free libraries.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, while the latter only
+works together with the library.
+
+ Note that it is possible for a library to be covered by the ordinary
+General Public License rather than by this special one.
+
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library which
+contains a notice placed by the copyright holder or other authorized
+party saying it may be distributed under the terms of this Library
+General Public License (also called "this License"). Each licensee is
+addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also compile or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ c) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ d) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the source code distributed need not include anything that is normally
+distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Library General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ Appendix: How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the library's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Library General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Library General Public License for more details.
+
+ You should have received a copy of the GNU Library General Public
+ License along with this library; if not, write to the Free
+ Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
diff --git a/ChangeLog b/ChangeLog
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/ChangeLog
diff --git a/Makefile.am b/Makefile.am
new file mode 100644
index 00000000..2343c5ac
--- /dev/null
+++ b/Makefile.am
@@ -0,0 +1 @@
+SUBDIRS = gconf backends po intl
diff --git a/NEWS b/NEWS
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/NEWS
diff --git a/README b/README
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/README
diff --git a/acconfig.h b/acconfig.h
new file mode 100644
index 00000000..16d16922
--- /dev/null
+++ b/acconfig.h
@@ -0,0 +1,8 @@
+#undef PACKAGE
+#undef VERSION
+#undef HAVE_CATGETS
+#undef HAVE_GETTEXT
+#undef HAVE_LC_MESSAGES
+#undef HAVE_STPCPY
+#undef ENABLE_NLS
+
diff --git a/autogen.sh b/autogen.sh
new file mode 100755
index 00000000..062dbb6d
--- /dev/null
+++ b/autogen.sh
@@ -0,0 +1,61 @@
+#!/bin/sh
+# Run this to generate all the initial makefiles, etc.
+
+srcdir=`dirname $0`
+test -z "$srcdir" && srcdir=.
+
+ORIGDIR=`pwd`
+cd $srcdir
+PROJECT=GConf
+TEST_TYPE=-f
+FILE=gconf/gconf.h
+
+DIE=0
+
+(autoconf --version) < /dev/null > /dev/null 2>&1 || {
+ echo
+ echo "You must have autoconf installed to compile $PROJECT."
+ echo "Download the appropriate package for your distribution,"
+ echo "or get the source tarball at ftp://ftp.gnu.org/pub/gnu/"
+ DIE=1
+}
+
+(automake --version) < /dev/null > /dev/null 2>&1 || {
+ echo
+ echo "You must have automake installed to compile $PROJECT."
+ echo "Get ftp://sourceware.cygnus.com/pub/automake/automake-1.4.tar.gz"
+ echo "(or a newer version if it is available)"
+ DIE=1
+}
+
+if test "$DIE" -eq 1; then
+ exit 1
+fi
+
+test $TEST_TYPE $FILE || {
+ echo "You must run this script in the top-level $PROJECT directory"
+ exit 1
+}
+
+if test -z "$*"; then
+ echo "I am going to run ./configure with no arguments - if you wish "
+ echo "to pass any to it, please specify them on the $0 command line."
+fi
+
+case $CC in
+*xlc | *xlc\ * | *lcc | *lcc\ *) am_opt=--include-deps;;
+esac
+
+aclocal $ACLOCAL_FLAGS
+
+# optionally feature autoheader
+(autoheader --version) < /dev/null > /dev/null 2>&1 && autoheader
+
+automake -a $am_opt
+autoconf
+cd $ORIGDIR
+
+$srcdir/configure --enable-maintainer-mode "$@"
+
+echo
+echo "Now type 'make' to compile $PROJECT."
diff --git a/backends/Makefile.am b/backends/Makefile.am
new file mode 100644
index 00000000..101a59a5
--- /dev/null
+++ b/backends/Makefile.am
@@ -0,0 +1,10 @@
+INCLUDES= -I$(top_srcdir) $(GLIB_CFLAGS)
+
+lib_LTLIBRARIES = libgconfbackend-xml.la
+
+libgconfbackend_xml_la_SOURCES = \
+ xml-backend.c
+
+
+libgconfbackend_xml_la_LDFLAGS = -avoid-version
+libgconfbackend_xml_la_LIBADD = $(GLIB_CFLAGS)
diff --git a/backends/xml-backend.c b/backends/xml-backend.c
new file mode 100644
index 00000000..39931ef9
--- /dev/null
+++ b/backends/xml-backend.c
@@ -0,0 +1,64 @@
+
+/* GConf
+ * Copyright (C) 1999 Red Hat Inc.
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Library General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Library General Public License for more details.
+ *
+ * You should have received a copy of the GNU Library General Public
+ * License along with this library; if not, write to the
+ * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ * Boston, MA 02111-1307, USA.
+ */
+
+
+#include <gconf/gconf-backend.h>
+
+GConfBackend* init (void);
+void shutdown (GConfBackend* backend);
+
+GConfSource* resolve_address (GConfBackend* backend, const gchar* address);
+
+GConfValue* query_value (GConfSource* source, const gchar* key);
+
+static GConfBackendVTable xml_vtable = {
+ init,
+ shutdown,
+ resolve_address,
+ query_value
+};
+
+
+
+GConfBackend*
+init (void)
+{
+
+
+}
+
+void
+shutdown (GConfBackend* backend)
+{
+
+}
+
+GConfSource*
+resolve_address (GConfBackend* backend, const gchar* address)
+{
+
+}
+
+GConfValue*
+query_value (GConfSource* source, const gchar* key)
+{
+
+
+}
diff --git a/configure.in b/configure.in
new file mode 100644
index 00000000..8f2e856f
--- /dev/null
+++ b/configure.in
@@ -0,0 +1,38 @@
+AC_INIT(gconf/gconf.h)
+
+AM_CONFIG_HEADER(config.h)
+
+AM_INIT_AUTOMAKE(GConf, 0.1)
+
+AM_MAINTAINER_MODE
+
+AC_PROG_CC
+AC_ISC_POSIX
+AC_HEADER_STDC
+AC_ARG_PROGRAM
+AM_PROG_LIBTOOL
+
+AM_PATH_GLIB(1.2.0)
+GMODULE_CFLAGS=`glib-config --cflags gmodule`
+AC_SUBST(GMODULE_CFLAGS)
+GMODULE_LIBS=`glib-config --libs gmodule`
+AC_SUBST(GMODULE_LIBS)
+
+ALL_LINGUAS=""
+AM_GNU_GETTEXT
+
+CFLAGS="$CFLAGS -Wall"
+
+AC_SUBST(CFLAGS)
+AC_SUBST(CPPFLAGS)
+AC_SUBST(LDFLAGS)
+
+AC_OUTPUT([
+Makefile
+gconf/Makefile
+backends/Makefile
+intl/Makefile
+po/Makefile.in
+])
+
+
diff --git a/doc/thoughts.txt b/doc/thoughts.txt
new file mode 100644
index 00000000..ed6d8ff0
--- /dev/null
+++ b/doc/thoughts.txt
@@ -0,0 +1,231 @@
+
+GConf design notes
+==================
+
+Data Types
+===
+
+Must be able to store int, float, string. Also need a "record" or
+"struct" type, to store something like a printer; record has a fixed
+set of names and fixed types for the value at each name. There is
+also a list type.
+
+Should lists of lists be allowed? Probably so, since you can do this
+via a record type anyway (a record containing a list) so it may as
+well be allowed in a non-ugly way.
+
+Namespace
+===
+
+The namespace will be a filesystem-style hierarchical namespace. By
+convention, the first two "levels" of the namespace will be a vendor
+name and an application or module name. Subsequent levels are defined
+by applications.
+
+Config Sources
+===
+
+A config source is something like a URL. It has two parts: a "protocol"
+(backend), such as Berkeley DB, flat text file, Oracle, LDAP; and an
+"address", which is a backend-specific string sufficient to locate the
+particular config source. Could be a hostname, filename, directory
+name, whatever makes sense.
+
+Each config source can respond to queries for any /vendor/appname/key
+values, if only with "no value set."
+
+Sources can be read-only or read-write with respect to a given user.
+
+On the implementation side, backends will probably be implemented as
+loadable modules.
+
+Source Layering
+===
+
+Config sources can be layered in a search path. For example, you might
+configure your GConf to first check your user settings stored in flat
+files in ~/.gconf, then the systemwide Berkeley DB in /etc/gconf, then
+the network-wide LDAP configuration.
+
+System or network administrators can place a read-only config source
+at the beginning of your source search path. If the read-only source
+sets a value, then users can't modify it. (This is not intended to be
+a security measure, just a way to keep users from shooting themselves
+in the foot; you might lock IP addresses in place, for example, if
+users shouldn't be changing them.) Administrators can place a
+read-only source at the end of the source search path, to provide
+default values. User configuration is sandwiched between mandatory and
+default. For example, you might have:
+
+ /etc/gconf-mandatory:~/.gconf:/etc/gconf-defaults
+
+Layering is global; that is, you can't "mount" a layer only for a
+particular section of the namespace. However, layers can be "empty"
+except for a single namespace area; if a layer doesn't set a value for
+a given key or namespace area it's effectively nonexistent with
+respect to that key.
+
+There will be a master repository that stores metadata and information
+about the layers. Most likely this will be concealed by the API.
+
+Packages (debs/rpms) can also install a layer of defaults if they
+like, and uninstall the layer when the package is uninstalled.
+
+Notifier/Listener architecture
+===
+
+Apps should be able to register themselves as listeners for a given
+section of the namespace, to be notified whenever a config value in
+that namespace changes.
+
+A simple way to structure applications would listen for config
+changes; then when the app saves its own config, it gets a change
+notification back and updates itself. The app's internal config
+updating works as if an external tool or another instance of the app
+had changed the config; external changes are treated exactly the same
+as internal ones.
+
+This is the hardest thing to implement, it will require some kind of
+daemon and there are serious security and efficiency issues to work
+out. This is the main problem I'm not sure how to approach.
+
+We should have a nice GtkObject convenience layer to make it easy to
+implement this.
+
+Locking
+===
+
+Obviously the backends should have locking so multiple apps can edit
+the same key if needed.
+
+Key Metadata
+===
+
+Each key can be explicitly registered with the GConf system; on
+registration, a short and long description of the key's purpose should
+be stored. Also the key's type. It will then be an error to store the
+wrong type in that key. The description can be used in generic config
+tree browser/editor applications. This description of a key's type and
+purpose is called a "schema" or "template."
+
+Metadata will also include the time of the last change, and an
+arbitrary string identifying the software or person who made the
+change. Packages (deb/rpm) can use this to decide whether a key has
+been modified since the package was installed (by comparing the
+last modifier with their own modifier string).
+
+Comments
+===
+
+Administrators can attach comments to keys explaining what they
+changed and why, etc. if they like.
+
+
+Record Metadata
+===
+
+Record types are similarly pre-registered, along with descriptive
+metadata. Record types are referred to by name.
+
+Record types are stored in the namespace, just like other keys.
+Actually they are basically just a sub-namespace.
+
+Metadata Storage
+===
+
+Metadata is handled in source layers just like regular key-value
+pairs. That is, the first metadata found in a path takes precedence.
+
+Conventional Types
+===
+
+In addition to the primitive types, customary record types will be
+specified. For example, a record with four integers for an IP address.
+Some standard document will list the conventional types defined so
+far. The purpose of conventional types is compatibility, and so
+generic browser/editor apps can impose nice constraints on the value
+of the record members (such as 0-255 for each int in the IP address) -
+a Windows-style IP address entry box could be used.
+
+Conventional types will be ever-present and defined as global record
+types, since they aren't "owned" by any vendor or application.
+
+However, conventional types are only conventional; GConf itself isn't
+going to try to enforce their semantics or names.
+
+Iterators
+===
+
+You have to be able to iterate over everything: keys, appnames,
+vendors, record types, etc. in order to implement generic
+browser/editor applications
+
+Resource Limits
+===
+
+A configurable maximum value size should exist, to keep broken
+programs from bogging things down.
+
+"Fetch All Changes Since"
+===
+
+Clients should be able to fetch all entries with a mod time greater
+than a given time in a section of the namespace.
+
+Command line tool
+===
+
+A nice command line tool will be written to allow shell scripts to
+access config information. This is important for postinstalls and the
+like.
+
+So you'd say:
+
+gconf --set key value
+
+gconf --get key
+
+gconf --clear /vendor/appname/key
+
+gconf --list-sources
+
+etc., something like that
+
+The command line tool is also useful for writing a test suite.
+
+Change sets
+===
+
+This is primarily a matter of a convenient API. A change set will be
+an object that stores a series of changes to be made - key-value
+pairs.
+
+Change sets can be committed and reverted as a whole. So, you can
+build a change set as the user fiddles with a property box, then
+apply/revert it as they click the buttons.
+
+ACAP
+===
+
+I'm thinking ACAP will be a backend, I don't think it's the same thing
+as this tool. But maybe...
+
+
+
+What to do with gnome-config
+===
+
+gnome-config should remain unchanged for backward compatibility and
+stability; apps would gradually migrate to the new GConf API. I don't
+think it's feasible to implement gnome-config in terms of this more
+powerful system without breaking the more powerful system.
+But we'll see.
+
+
+
+
+
+
+
+
+
diff --git a/gconf/GConf.idl b/gconf/GConf.idl
new file mode 100644
index 00000000..dcc0b312
--- /dev/null
+++ b/gconf/GConf.idl
@@ -0,0 +1,9 @@
+
+interface Listener {
+ oneway void notify (in string value);
+
+};
+
+interface Notifier {
+ void add_listener(in string where, in Listener who);
+};
diff --git a/gconf/GConfX.idl b/gconf/GConfX.idl
new file mode 100644
index 00000000..dcc0b312
--- /dev/null
+++ b/gconf/GConfX.idl
@@ -0,0 +1,9 @@
+
+interface Listener {
+ oneway void notify (in string value);
+
+};
+
+interface Notifier {
+ void add_listener(in string where, in Listener who);
+};
diff --git a/gconf/Makefile.am b/gconf/Makefile.am
new file mode 100644
index 00000000..7d1032e2
--- /dev/null
+++ b/gconf/Makefile.am
@@ -0,0 +1,11 @@
+INCLUDES=-I$(top_srcdir) $(GLIB_CFLAGS) $(GMODULE_CFLAGS)
+
+bin_PROGRAMS = gconfd
+
+gconfd_SOURCES =
+ gconf-internals.c \
+ gconf-internals.h \
+ gconf-backend.h \
+ gconf-backend.c
+
+gconfd_LDADD = $(GLIB_LIBS) $(GMODULE_LIBS)
diff --git a/gconf/gconf-backend.c b/gconf/gconf-backend.c
new file mode 100644
index 00000000..48cddd44
--- /dev/null
+++ b/gconf/gconf-backend.c
@@ -0,0 +1,19 @@
+
+/* GConf
+ * Copyright (C) 1999 Red Hat Inc.
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Library General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Library General Public License for more details.
+ *
+ * You should have received a copy of the GNU Library General Public
+ * License along with this library; if not, write to the
+ * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ * Boston, MA 02111-1307, USA.
+ */
diff --git a/gconf/gconf-backend.h b/gconf/gconf-backend.h
new file mode 100644
index 00000000..cb595de5
--- /dev/null
+++ b/gconf/gconf-backend.h
@@ -0,0 +1,54 @@
+
+/* GConf
+ * Copyright (C) 1999 Red Hat Inc.
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Library General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Library General Public License for more details.
+ *
+ * You should have received a copy of the GNU Library General Public
+ * License along with this library; if not, write to the
+ * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ * Boston, MA 02111-1307, USA.
+ */
+
+#ifndef GCONF_GCONFBACKEND_H
+#define GCONF_GCONFBACKEND_H
+
+#include <gconf/gconf-internals.h>
+
+typedef struct _GConfBackendVTable GConfBackendVTable;
+
+struct _GConfBackendVTable {
+ GConfBackend* (* init) (void);
+ void (* shutdown) (GConfBackend* backend);
+
+ GConfSource* (* resolve_address) (GConfBackend* backend, const gchar* address);
+
+ GConfValue* (* query_value) (GConfSource* source, const gchar* key);
+};
+
+struct _GConfBackend {
+ guint refcount;
+ GConfBackendVTable* vtable;
+};
+
+/* Obtain the GConfBackend for this address, based on the first part of the
+ * address.
+ */
+GConfBackend* g_conf_get_backend(const gchar* address);
+
+/* Backends start with a refcount of 0, which is a bit weird for Gtk programmers
+ * but essential since you don't know from g_conf_backend_get() if you're the first
+ * to obtain the backend or if you got an already-cached backend.
+ */
+void g_conf_backend_ref(GConfBackend* backend);
+void g_conf_backend_unref(GConfBackend* backend);
+
+#endif
diff --git a/gconf/gconf-internals.c b/gconf/gconf-internals.c
new file mode 100644
index 00000000..433f72fc
--- /dev/null
+++ b/gconf/gconf-internals.c
@@ -0,0 +1,68 @@
+
+/* GConf
+ * Copyright (C) 1999 Red Hat Inc.
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Library General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Library General Public License for more details.
+ *
+ * You should have received a copy of the GNU Library General Public
+ * License along with this library; if not, write to the
+ * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ * Boston, MA 02111-1307, USA.
+ */
+
+GConfValue*
+g_conf_value_new(GConfValueType type)
+{
+ GConfValue* value;
+
+ value = g_new0(GConfValue, 1);
+
+ value->type = type;
+}
+
+void
+g_conf_value_destroy(GConfValue* value)
+{
+ g_return_if_fail(value != NULL);
+
+ if (value->type == G_CONF_VALUE_STRING &&
+ value->d.string_data != NULL)
+ g_free(value->d.string_data);
+
+ g_free(value);
+}
+
+void
+g_conf_value_set_int(GConfValue* value, gint the_int)
+{
+ g_return_if_fail(value != NULL);
+ g_return_if_fail(value->type == G_CONF_VALUE_INT);
+
+ value->d.int_data = the_int;
+}
+
+void
+g_conf_value_set_string(GConfValue* value, const gchar* the_str)
+{
+ g_return_if_fail(value != NULL);
+ g_return_if_fail(value->type == G_CONF_VALUE_STRING);
+
+ value->d.string_data = g_strdup(the_str);
+}
+
+void
+g_conf_value_set_float(GConfValue* value, gdouble the_float)
+{
+ g_return_if_fail(value != NULL);
+ g_return_if_fail(value->type == G_CONF_VALUE_FLOAT);
+
+ value->d.float_data = the_float;
+}
diff --git a/gconf/gconf-internals.h b/gconf/gconf-internals.h
new file mode 100644
index 00000000..d9f0e427
--- /dev/null
+++ b/gconf/gconf-internals.h
@@ -0,0 +1,84 @@
+
+/* GConf
+ * Copyright (C) 1999 Red Hat Inc.
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Library General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Library General Public License for more details.
+ *
+ * You should have received a copy of the GNU Library General Public
+ * License along with this library; if not, write to the
+ * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ * Boston, MA 02111-1307, USA.
+ */
+
+#ifndef GCONF_GCONFINTERNALS_H
+#define GCONF_GCONFINTERNALS_H
+
+#include <glib.h>
+
+typedef enum {
+ G_CONF_VALUE_INVALID,
+ G_CONF_VALUE_STRING,
+ G_CONF_VALUE_INT,
+ G_CONF_VALUE_FLOAT,
+ G_CONF_VALUE_LIST_OF_STRING,
+ G_CONF_VALUE_LIST_OF_INT,
+ G_CONF_VALUE_LIST_OF_FLOAT
+} GConfValueType;
+
+/*
+ * A GConfValue is used to pass configuration values around; it's
+ * pretty low-level, higher-level interface in gconf.h.
+ */
+
+typedef struct _GConfValue GConfValue;
+
+struct _GConfValue {
+ GConfValueType type;
+ union {
+ gchar* string_data;
+ gint int_data;
+ gdouble float_data;
+ GSList* list_data;
+ } d;
+};
+
+#define g_conf_value_string(x) ((x)->d.string_data)
+#define g_conf_value_int(x) ((x)->d.int_data)
+#define g_conf_value_float(x) ((x)->d.float_data)
+#define g_conf_value_list(x) ((x)->d.list_data)
+
+GConfValue* g_conf_value_new(GConfValueType type);
+void g_conf_value_destroy(GConfValue* value);
+
+void g_conf_value_set_int(GConfValue* value, gint the_int);
+void g_conf_value_set_string(GConfValue* value, const gchar* the_str);
+void g_conf_value_set_float(GConfValue* value, gdouble the_float);
+
+/* Sources are not interchangeable; different backend engines will return
+ * GConfSource with different private elements.
+ */
+
+typedef struct _GConfBackend GConfBackend;
+
+typedef struct _GConfSource GConfSource;
+
+struct _GConfSource {
+ gchar* backend_id;
+ GConfBackend* backend;
+};
+
+GConfSource* g_conf_resolve_address(const gchar* address);
+
+const gchar* g_conf_error (void);
+gboolean g_conf_error_pending (void);
+void g_conf_set_error (const gchar* str);
+
+#endif
diff --git a/gconf/gconf.h b/gconf/gconf.h
new file mode 100644
index 00000000..e6b151ec
--- /dev/null
+++ b/gconf/gconf.h
@@ -0,0 +1,37 @@
+
+/* GConf
+ * Copyright (C) 1999 Red Hat Inc.
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Library General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Library General Public License for more details.
+ *
+ * You should have received a copy of the GNU Library General Public
+ * License along with this library; if not, write to the
+ * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ * Boston, MA 02111-1307, USA.
+ */
+
+#ifndef GCONF_GCONF_H
+#define GCONF_GCONF_H
+
+#include <glib.h>
+
+/* A configuration engine (stack of config sources); normally there's
+ * just one of these on the system.
+ */
+struct _GConf GConf;
+
+struct _GConf {
+ gpointer dummy;
+};
+
+
+
+#endif
diff --git a/po/ChangeLog b/po/ChangeLog
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/po/ChangeLog
diff --git a/po/POTFILES.in b/po/POTFILES.in
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/po/POTFILES.in
diff --git a/stamp.h.in b/stamp.h.in
new file mode 100644
index 00000000..e69de29b
--- /dev/null
+++ b/stamp.h.in