From de36ba96a7d328655885e7bf6fed08cf06faecb6 Mon Sep 17 00:00:00 2001 From: Enrico Tassi Date: Fri, 2 Nov 2007 14:16:23 +0000 Subject: [PATCH] finisced configuration section --- matita/help/C/sec_install.xml | 30 +++++++++++++++++++----------- 1 file changed, 19 insertions(+), 11 deletions(-) diff --git a/matita/help/C/sec_install.xml b/matita/help/C/sec_install.xml index 4d50db4e6..7dc37937b 100644 --- a/matita/help/C/sec_install.xml +++ b/matita/help/C/sec_install.xml @@ -389,11 +389,24 @@ Configuring &appname; - The file matita.conf.xml... - &TODO; + The configuration file is divided in four sections. The user and + matita ones are self explicative and does not need user + intervention. Here we report a sample snippet for these two + sections. The remaining db and getter sections will be explained in + details later. + + + $(HOME) + $(USER) + +
+ $(user.home)/.matita + /usr/share/matita/ + $(user.name) +
+]]>
- - The db and the getter sections &appname; needs to store/fetch data and metadata. Data is essentially composed of XML files, metadata is a set of tuples for a relational @@ -414,8 +427,7 @@ How to configure the databases. - - The getter + The getter Consider the following snippet and the URI cic:/matita/foo/bar.con. If &appname; @@ -456,9 +468,7 @@ writing when &appname; is started in system mode (used to publish user developments in the library space). - - - The db + The db The database subsystem has three fron ends: library, user and legacy. The latter is the only optional one. Every query is done on @@ -485,8 +495,6 @@ a password (or none) and the name of the front end to which it is attached. - -
-- 2.39.2