From 866e3204cee593817850f5e5c23a0bcf7af9c591 Mon Sep 17 00:00:00 2001
From: Stef Walter <stefw@gnome.org>
Date: Tue, 5 Feb 2013 11:50:16 +0100
Subject: Add documentation about contributing to p11-kit

---
 doc/p11-kit-notes.xml | 48 ------------------------------------------------
 1 file changed, 48 deletions(-)
 delete mode 100644 doc/p11-kit-notes.xml

(limited to 'doc/p11-kit-notes.xml')

diff --git a/doc/p11-kit-notes.xml b/doc/p11-kit-notes.xml
deleted file mode 100644
index 02a3288..0000000
--- a/doc/p11-kit-notes.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
-]>
-<chapter xml:id="config">
-	<title>Developer and Packager Notes</title>
-
-	<section id="notes-paths">
-		<title>Using pkg-config to determine paths</title>
-
-		<para>Developers or packagers of PKCS#11 modules need to install various
-		files into specific locations so that p11-kit will recognize and load the
-		module correctly.</para>
-
-		<para>You should use <literal>pkg-config</literal> as described below
-		to determine configuration paths. p11-kit installs a
-		<literal>pkg-config</literal> file called <literal>p11-kit-1.pc</literal>.
-		This file contains all the information about the various paths that p11-kit
-		looks for files at.</para>
-
-		<section id="notes-paths-config">
-			<title>Path to place module configuration</title>
-
-			<para>As described in the <link linkend="config-module">module configuration</link>
-			documentation, each PKCS#11 module should install a config file describing
-			that module. These config files should be installed to a specific directory which
-			can be determined by running:</para>
-
-			<programlisting>
-$ <command>pkg-config p11-kit-1 --variable p11_module_configs</command>
-/usr/share/p11-kit/modules</programlisting>
-		</section>
-
-		<section id="notes-paths-modules">
-			<title>Default path for modules with relative paths</title>
-
-			<para>If a <link linkend="config-module">module configuration</link>
-			contains a relative path in its <literal>module:</literal> setting,
-			then that module will be loaded from the default module path. This
-			path can be determined by running:</para>
-
-			<programlisting>
-$ <command>pkg-config p11-kit-1 --variable p11_module_path</command>
-/usr/lib64/pkcs11</programlisting>
-		</section>
-
-	</section>
-
-</chapter>
-- 
cgit v1.1