Re: Debconf templates proofreading request
On Tue, May 06, 2003 at 07:26:04AM +0200, Christian Perrier wrote:
> Template: catalog/database_type
(This package name is too general :-()
> Type: select
> _Choices: PostgreSQL, MySql
> Default: MySql
> _Description: SQL server type
> URLs are stored in a database. This package currently supports
> MySQL but will support other SQL server software in the future.
I suggest:
Catalog stores URLs in a database. This package currently only supports
MySQL but will support other SQL server software in the future.
(Why is Postgres one of your choices if it is not supported?)
> Template: catalog/database_server
> Type: string
> _Default: localhost
> _Description: Database hostname
> If your database is hosted on another machine, please enter the fully
> qualified hostname of this system.
OK.
> Template: catalog/database_name
> Type: string
> _Default: catalog
> _Description: Catalog database name
> Default name is "catalog". This is the database where all the Catalog-related
> items will be setup and kept. All other Catalog modules will
> most likely use this database as well. If you already have a Catalog database,
> please enter its name here.
The default database name is "catalog". This is the database where all
Catalog-related data will be stored. Other Catalog modules will most likely
use this database as well. If you already have a Catalog database, please
enter its name here.
> Template: catalog/database_user
> Type: string
> _Default: catalogmgr
> _Description: Database username
> Which username will be used for accessing the Catalog database?
> Default is "catalogmgr" so that permissions can be tightened down.
What username should be used for accessing the Catalog database?
The default is "catalogmgr" so that access can be restricted.
Is it really necessary to ask this question at all?
> Template: catalog/database_pass
> Type: password
> _Default: catalogmgr
> _Description: Database user password
> Enter a password for the database user ("none" for no password).
> This password will be used for the previously entered database user.
What if your password is really "none"?
Is the postinst going to create this user if necessary? That isn't clear
from the description.
> Template: catalog/mysql_pass
> Type: password
> _Description: MySQL root password
> Enter the root password for your MySQL server. It is
> most likely different from the catalog manager account password.
OK.
> Template: catalog/dbconfigured
> Type: boolean
> Default: false
> _Description: Already configured Catalog database?
I think this should be "Already created ...?" rather than configured.
> If you are upgrading or, for any other reason, have already configured your
> database for use with Catalog, accept here.
OK (not great but I couldn't think of something better).
> Template: catalog/catalog_name
> Type: string
> _Default: url
> _Description: Catalog name
Description: Catalog table name
> The catalog name is also the SQL table name and must only be
> alphanumerical. Specifically, it may not contain underscore which is a
> reserved character for Catalog.
Is it necessary to ask this question at all? Why would a user want to
change the default? Is it 1% likely? 10%? 50%?
The catalog name is also the SQL table name and must only use
alphanumeric characters. Specifically, it may not contain underscores.
(I don't think you need to say why.)
> Template: catalog/conffilesconfigured
> Type: boolean
> Default: false
> _Description: Already configured Catalog config files?
> If you are upgrading or, for any other reason, have already configured your
> config files for use with Catalog, accept here.
That sounds like the dbconfigured question. Should you be asking these
questions if it's already been configured?
> Template: catalog/ask_for_purge
> Type: boolean
> Default: true
> _Description: Remove catalog data when pruging the package?
Typo: purging
> Do you want to drop the catalog database and user from the database
> server when the package will be purged?
Don't say 'drop', it's an SQL specific term.
Do you want to remove the Catalog database and user from the database
server when the Catalog package is purged?
Please help stamp out useless and trivial configuration questions.
HTH,
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
Reply to: