path: root/doc/kommander/installation.docbook
diff options
Diffstat (limited to 'doc/kommander/installation.docbook')
1 files changed, 50 insertions, 0 deletions
diff --git a/doc/kommander/installation.docbook b/doc/kommander/installation.docbook
new file mode 100644
index 00000000..707df7a0
--- /dev/null
+++ b/doc/kommander/installation.docbook
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<appendix id="installation">
+<sect1 id="getting-kapp">
+<title>How to obtain &kommander;</title>
+<!-- This first entity contains boiler plate for applications that are
+part of KDE CVS. You should remove it if you are releasing your
+application -->
+<para>There is a dedicated homepage for &kommander; at <ulink url=""></ulink>.
+<sect1 id="requirements">
+List any special requirements for your application here. This should include:
+.Libraries or other software that is not included in kdesupport,
+kdelibs, or kdebase.
+.Hardware requirements like amount of RAM, disk space, graphics card
+capabilities, screen resolution, special expansion cards, etc.
+.Operating systems the app will run on. If your app is designed only for a
+specific OS, (you wrote a graphical LILO configurator for example) put this
+information here.
+&kommander; requires the latest version of &kde; 3.x series, currently 3.5.9. It might work with previous 3.5.x versions, but this was not tested throughfully.
+<!-- For a list of updates, you may refer to the application web site
+or the ChangeLog file, or ... -->
+<sect1 id="compilation">
+<title>Compilation and Installation</title>
+<!-- This entity contains the boilerplate text for standard -->
+<!-- compilation instructions. If your application requires any -->
+<!-- special handling, remove it, and replace with your own text. -->