summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorStefan Walter <stefw@src.gnome.org>2007-05-18 19:47:51 +0000
committerStefan Walter <stefw@src.gnome.org>2007-05-18 19:47:51 +0000
commitcd53523ae6adc035e3d03a425a3daed81d32d401 (patch)
tree043d9a7e22edb031709eea559ac5a15d4848298d /HACKING
parentec8bbbaf7005587449163793a46bcdd83aed0aa9 (diff)
downloadgnome-keyring-cd53523ae6adc035e3d03a425a3daed81d32d401.tar.gz
Pass make distcheck Add myself as an author Update info files about
* tests/Makefile.am: * Makefile.am: Pass make distcheck * AUTHORS: Add myself as an author * HACKING: Update info files about gnome-keyring svn path=/trunk/; revision=611
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING27
1 files changed, 27 insertions, 0 deletions
diff --git a/HACKING b/HACKING
new file mode 100644
index 00000000..6cfc18c6
--- /dev/null
+++ b/HACKING
@@ -0,0 +1,27 @@
+
+HACKING GNOME KEYRING
+
+Patches should be submitted to bugzilla:
+http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-keyring
+
+Gnome Keyring is made up of several distinct parts working on concert with
+each other. These parts generally live in different directories:
+
+cryptoki
+ The PKCS#11 provider code
+
+daemon
+ The main daemon startup code and gnome-keyring password protocol operations.
+
+keyrings
+ Code that manages the user's password keyrings
+
+library
+ The gnome-keyring library for accessing passwords and secrets.
+
+tests
+ Test tools and unit tests.
+
+ui
+ Prompting the user, asking for passwords.
+