[med-svn] r5850 - trunk/packages/ensembl/ensembl/57/debian

[Steffen Möller]

Author: moeller
Date: 2011-02-01 23:18:41 +0000 (Tue, 01 Feb 2011)
New Revision: 5850

Modified:
   trunk/packages/ensembl/ensembl/57/debian/ensembl.templates
Log:
Extension of writing. Helping lintian.


Modified: trunk/packages/ensembl/ensembl/57/debian/ensembl.templates
===================================================================
--- trunk/packages/ensembl/ensembl/57/debian/ensembl.templates	2011-02-01 21:42:16 UTC (rev 5849)
+++ trunk/packages/ensembl/ensembl/57/debian/ensembl.templates	2011-02-01 23:18:41 UTC (rev 5850)
@@ -1,54 +1,90 @@
 Template: ensembl/port
 Default: 80
 Type: string
-_Description: Port that Apache will listen on.
+_Description: Port that Apache will listen on:
+ Ensembl presents itself to the user via 
+ a web server. When there are multiple
+ web pages on the same server, it is not
+ unlikely that Ensembl should have a different
+ than the default port 80.
 
 Template: ensembl/webuserdbhost
 Default: localhost
 Type: string
-_Description: MySQL server for web user db.
+_Description: MySQL server for web user db:
+ The local installation of Ensembl needs a 
+ MySQL Database server to store user-associated
+ data. Please specify the hostname of the
+ server here. Enter it in the same way
+ that you would use to log into that machine
+ when using it manually from the server and
+ test that you have all the right access
+ permissions.
 
 Template: ensembl/webuserdbport
 Default: 3306
 Type: string
-_Description: MySQL port for web user db.
+_Description: MySQL port for web user db:
+ The port of the local MySQL database.
 
 Template: ensembl/webuserdbname
 Default: ensembl
 Type: string
-_Description: MySQL database name for web user db.
+_Description: MySQL database name for web user db:
+ The local database to store user associated
+ data for Ensembl shall have a name.
 
 Template: ensembl/webuserdbuser
 Default: ensembl
 Type: string
-_Description: MySQL username for web user db.
+_Description: MySQL username for web user db:
+ The username under which the database can be
+ accessed.
 
 Template: ensembl/webuserdbpwd
 Default: ensembl
 Type: string
-_Description: MySQL password for web user db.
+_Description: MySQL password for web user db:
+ The password with which to access the local
+ Ensembl database.
 
 Template: ensembl/webuserdbexistyn
 Default: false
 Type: boolean
-_Description: True if the web user db already exists.
+_Description: Does web user db already exist?
+ When installing Ensembl, the local database may
+ already exist, e.g. from a previous installation.
+ .
+ True if the web user db already exists.
 
 Template: ensembl/webuserdbkeepyn
 Default: true
 Type: boolean
-_Description: True if the web user db already exists and should be kept.
+_Description: If existing, should the web user db be kept?
+ When there is a previous installation of the local
+ database to support the web interface, one may argue if that
+ should be overridden during an update.
+ .
+ True if the web user db already exists and should be kept:
 
 Template: ensembl/mysqladminuser
 Default: root
 Type: string
-_Description: MySQL admin user for creating the web user db if it doesn't exist.
+_Description: MySQL admin user for creating the web user db if it doesn't exist:
+ When a new database shall be created, one needs a user with the
+ permissions to perform so.
 
 Template: ensembl/mysqladminpwd
 Default: 
 Type: password
-_Description: MySQL admin password for creating the web user db if it doesn't exist.
+_Description: MySQL admin password for creating the web user db if it doesn't exist:
+ The user with the right to create a new database most likely has a password.
 
 Template: ensembl/webuserdbkeeptablesyn
 Default: true
 Type: boolean
-_Description: True if the web user db already exists and the data in it should be kept.
+_Description: Shall the data in web user db be kept by package update?
+ When the database is available, the remaining question is how to perform with
+ already existing tables.
+ .
+ True if the web user db already exists and the data in it should be kept: