[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[RFR2] templates://webcalendar/{webcalendar.templates}

After comments by Kevin and Justin, please find attached the new
templates and control files.

I made the use of "single-user" and "multi-user" consistent. I
reverted the sentence about required stuff just like Justin
suggested. I also removed the "the" before "perfromance" as Kevin

If you send diffs, please send diffs against these files, not the
original ones.

Template: webcalendar/conf/db_persistent
Type: boolean
Default: false
_Description: Should WebCalendar use persistent connections?
 Using persistent connections can improve performance on heavily loaded
 websites by using a previously opened SQL connection.

Template: webcalendar/conf/use_http_auth
Type: boolean
Default: false
_Description: Use HTTP authentication?
 WebCalendar by default uses the database's webcal_user table for
 authenticating users. You can use HTTP authentication logins
 instead and use Apache to manage logins. This will still require adding
 the users to WebCalendar.

Template: webcalendar/conf/single_user_mode
Type: boolean
Default: false
_Description: Should WebCalendar be installed in single-user mode?
 WebCalendar can be installed in single-user mode or multi-user mode. If it
 is installed in single-user mode, no login will be required.
 Using the single-user mode is not recommended unless the software runs
 on a personal server protected by a firewall.

Template: webcalendar/conf/single_user_login
Type: string
_Description: Name of the WebCalendar user:
 If WebCalendar is installed in single-user mode, you need to specify
 the name of the user to connect as.

Template: webcalendar/status/debconf_managed
Type: boolean
Default: true
_Description: Manage settings.conf automatically?
 The configuration program for the package can manage the settings.conf
 file but you may prefer managing your settings yourself.

Template: webcalendar/note/admin_user
Type: note
_Description: Password change needed for the WebCalendar administrative user
 After installing the tables for the SQL database you will have access
 to WebCalendar using the standard administrative user. It is STRONGLY
 suggested that you change the password after logging in.
 The default login and password are 'admin:admin'.

Template: webcalendar/conf/httpd_conf
Type: multiselect
_Choices: apache2, apache, apache-ssl, apache-perl, other
Default: apache2
_Description: Web server to configure:
 Apache can be automatically configured to use WebCalendar by creating links in
 /etc/{apache-version}/conf.d/. Select all the versions of Apache you would
 like to automatically configure or 'other' if you don't use Apache or plan on
 configuring Apache yourself.

Template: webcalendar/conf/restart_webserver
Type: boolean
Default: false
_Description: Should ${webserver} be restarted?
 In order to activate the new configuration, ${webserver} has to be
 restarted. You can also restart ${webserver} by manually executing
 'invoke-rc.d ${webserver} restart'.

Template: webcalendar/store/webservers_to_be_restarted
Type: string
Description: Webservers to be restarted:
 (This is for internal use only)

Source: webcalendar
Section: web
Priority: optional
Maintainer: Elizabeth Bevilacqua <lyz@princessleia.com>
Uploaders: Rafael Laboissiere <rafael@debian.org>
Build-Depends: debhelper (>= 4.1.16), po-debconf, dpatch
Build-Depends-Indep: html2text
Standards-Version: 3.7.2
XS-Vcs-Svn: svn://svn.debian.org/svn/collab-maint/ext-maint/webcalendar/
XS-Vcs-Browser: http://svn.debian.org/wsvn/collab-maint/ext-maint/webcalendar/

Package: webcalendar
Architecture: all
Depends: ${misc:Depends}, libapache-mod-php4 | libapache2-mod-php4, php4-mysql | php4-pgsql, apache | apache2 | apache-ssl | apache-perl, ucf (>= 0.28), dbconfig-common
Suggests: php4-cli
Recommends: mysql-client | postgresql-client, mysql-server | postgresql
Description: PHP-Based multi-user calendar
 WebCalendar is a PHP-based calendar application that can be configured
 as a single-user calendar, a multi-user calendar for groups of users,
 or as an event calendar viewable by visitors. It requires either MySQL,
 PostgreSQL, Oracle, DB2, Interbase, or ODBC.

Attachment: signature.asc
Description: Digital signature

Reply to: