head	1.5;
access;
symbols
	HORDE_1_2_7:1.1.2.27
	HORDE_1_2_6:1.1.2.27
	HORDE_1_2_5:1.1.2.27
	HORDE_1_2_4:1.1.2.25
	HORDE_1_2_3:1.1.2.25
	HORDE_1_2_2:1.1.2.24
	HORDE_1_2_1:1.1.2.23
	HORDE_1_2_0:1.1.2.22
	HORDE_1_2_0_pre14:1.1.2.24
	HORDE_1_2_0_pre13:1.1.2.20
	HORDE_1_2_0_pre11:1.1.2.19
	HORDE_1_3_2:1.3
	HORDE_1_2_0_pre10:1.1.2.15
	HORDE_1_3_1:1.3
	HORDE_1_2_0_pre9:1.1.2.13
	HORDE_1_2_0_pre8:1.1.2.13
	HORDE_1_2_0_pre6:1.1.2.12
	horde-dev-20000104:1.3
	HORDE_1_2_0_pre5:1.1.2.5
	STABLE_1_2:1.1.0.2;
locks; strict;
comment	@# @;


1.5
date	2000.05.22.11.13.13;	author rkrusty;	state dead;
branches;
next	1.4;

1.4
date	2000.02.15.07.48.38;	author rkrusty;	state Exp;
branches;
next	1.3;

1.3
date	99.10.26.11.16.25;	author rkrusty;	state Exp;
branches;
next	1.2;

1.2
date	99.10.15.02.59.28;	author rkrusty;	state Exp;
branches;
next	1.1;

1.1
date	99.10.10.16.52.40;	author rkrusty;	state dead;
branches
	1.1.2.1;
next	;

1.1.2.1
date	99.10.10.16.52.41;	author rkrusty;	state Exp;
branches;
next	1.1.2.2;

1.1.2.2
date	99.10.14.04.27.55;	author rkrusty;	state Exp;
branches;
next	1.1.2.3;

1.1.2.3
date	99.10.15.00.12.24;	author rkrusty;	state Exp;
branches;
next	1.1.2.4;

1.1.2.4
date	99.10.15.02.13.57;	author rkrusty;	state Exp;
branches;
next	1.1.2.5;

1.1.2.5
date	99.10.19.04.39.54;	author rkrusty;	state Exp;
branches;
next	1.1.2.6;

1.1.2.6
date	99.10.21.07.59.12;	author rkrusty;	state Exp;
branches;
next	1.1.2.7;

1.1.2.7
date	99.10.27.04.17.28;	author rkrusty;	state Exp;
branches;
next	1.1.2.8;

1.1.2.8
date	99.11.16.08.52.34;	author rkrusty;	state Exp;
branches;
next	1.1.2.9;

1.1.2.9
date	99.11.28.09.54.35;	author rkrusty;	state Exp;
branches;
next	1.1.2.10;

1.1.2.10
date	99.11.30.03.34.12;	author rkrusty;	state Exp;
branches;
next	1.1.2.11;

1.1.2.11
date	99.12.05.06.44.46;	author rkrusty;	state Exp;
branches;
next	1.1.2.12;

1.1.2.12
date	99.12.06.00.36.34;	author rkrusty;	state Exp;
branches;
next	1.1.2.13;

1.1.2.13
date	2000.01.21.03.36.23;	author rkrusty;	state Exp;
branches;
next	1.1.2.14;

1.1.2.14
date	2000.01.24.19.40.49;	author rkrusty;	state Exp;
branches;
next	1.1.2.15;

1.1.2.15
date	2000.01.25.05.48.17;	author rkrusty;	state Exp;
branches;
next	1.1.2.16;

1.1.2.16
date	2000.02.04.21.55.05;	author rkrusty;	state Exp;
branches;
next	1.1.2.17;

1.1.2.17
date	2000.02.04.22.34.50;	author rkrusty;	state Exp;
branches;
next	1.1.2.18;

1.1.2.18
date	2000.03.30.07.25.34;	author rkrusty;	state Exp;
branches;
next	1.1.2.19;

1.1.2.19
date	2000.04.01.03.30.42;	author rkrusty;	state Exp;
branches;
next	1.1.2.20;

1.1.2.20
date	2000.05.22.07.31.33;	author rkrusty;	state Exp;
branches;
next	1.1.2.21;

1.1.2.21
date	2000.07.16.10.46.08;	author rkrusty;	state Exp;
branches;
next	1.1.2.22;

1.1.2.22
date	2000.07.18.23.42.16;	author rkrusty;	state Exp;
branches;
next	1.1.2.23;

1.1.2.23
date	2000.09.05.08.43.25;	author rkrusty;	state Exp;
branches;
next	1.1.2.24;

1.1.2.24
date	2000.09.11.06.14.44;	author rkrusty;	state Exp;
branches;
next	1.1.2.25;

1.1.2.25
date	2000.09.21.09.47.13;	author rkrusty;	state Exp;
branches;
next	1.1.2.26;

1.1.2.26
date	2001.02.06.19.58.37;	author opal;	state Exp;
branches;
next	1.1.2.27;

1.1.2.27
date	2001.02.26.20.12.59;	author opal;	state Exp;
branches;
next	;


desc
@@


1.5
log
@[IEM] cleaning out the debian dir to prepare for the new stuff...nice clean
start. :)
@
text
@Template: horde/welcome
Type: note
Description: Welcome to the new HORDE setup program
 Please note that these options will only be asked of you the first time
 around and only new options will show during future upgrades.  
 .
 If you are upgrading currently and this is the first time your using
 the debconf version of the horde install we'll let you know this once.
 Your current horde.php file is getting backed up during the preinst
 process.  This will happen every time you upgrade even though you will
 never see this prompt again unless you have debconf set to prompt you
 for everything.  Also note that the horde.php file is now generated
 on the fly *everytime* you install or upgrade horde.  

Template: horde/debconf
Type: select
Choices: yes, no
Default: yes
Description: Use debconf to configure HORDE/IMP?
 You now must decide which method of configuration you wish to use.
 You can use an automatic method which will require you to answer some
 questions now and your config files will be generated (and re-generated
 in the future) based on your answers.  The alternative is the manual
 method which requires you to manually edit a configuration template
 (horde.php.in) and run the update-horde program to generate the 
 proper config files.

Template: horde/horderecheck
Type: select
Choices: yes, no
Default: yes
Description: Verify non-horde config files during upgrades/installs?
 Do you want the install/upgrade process to verify (and fix) other config files
 related to horde?  These would include Apache, php, and database
 config files and changes necessary for horde to work properly.
 ***NOTE*** Things will not work properly if you do not have things
 setup properly.  If you choose not to verify non-horde config files, please
 read the Debian.Install file in /usr/share/doc/horde

Template: horde/remove
Type: note
Description: You need to remove the lines in access.conf manually!
 HORDE is still a work in progress and do to that some of the 
 installation and removal pieces are not complete.  In order to complete
 the removal of HORDE from your system, you need to remove the lines
 refering to HORDE from your /etc/apache/access.conf file (or 
 /etc/apache-ssl/access.conf if your using Apache-SSL).  
 .
 NOTE: Apache will break if you do not do this!!!

Template: horde/horde_root_url
Type: string
Default: /horde
Description: What is the default url path for horde?
 When pointing your web browser to Horde, what is the directory pathing you
 will need for getting to horde?  As in http://localhost/horde where /horde
 would be what we are looking for.

Template: horde/horde_graphics_url
Type: string
Default: /horde/graphics
Description: What is the default url path for horde graphics?
 When pointing your web browser to Horde, what is the directory pathing you
 will need for getting to horde graphics?  As in http://localhost/horde/graphics
 where /horde/graphics would be what we are looking for.

Template: horde/faq_url
Type: string
Default: http://faq.horde.org/
Description: What is the url for the FAQ?
 By default this will point to the HORDE online faq.  If you want it to point
 somewhere else change it or leave it blank to not use this option.

Template: horde/horde_include_dir
Type: string
Default: ./templates
Description: What is the path to the templates directory?
 Where are all the html templates stored for horde?  Unless you have 
 changed this on purpose then leave it as is.

Template: horde/path_to_sendmail
Type: string
Default: /usr/sbin/sendmail
Description: What is the path to your sendmail program?
 Please put the path to the program you use to send mail with.

Template: horde/problem_reporting
Type: select
Choices: true, false
Default: false
Description: Use built in problem reporting feature?
 Horde has the ability to allow web surfers to send in problem reports via mail
 from the HORDE web interface. By saying yes to this option you are enabling
 you are enabling this ability.

Template: horde/problem_email
Type: string
Default: root@@localhost
Description: Where do you want problem reports sent to?

Template: horde/signup
Type: select
Choices: true, false
Default: false
Description: Do you want to use the Horde signup feature?
 This option allows users to fill out a form online to request a user account.
 The form is then sent to an email address which you will be able to configure.

Template: horde/signup_email
Type: string
Default: root@@localhost
Description: What email address do you want signups sent to?

Template: horde/database_type
Type: select
Choices: PostgreSQL, MySql
Default: PostgreSQL
Description: What type of container (database) are you going to use?
 Because HORDE uses phplib, we have the ability to support several different
 types of containers.  Currently this package only supports MySql and
 PostgreSQL but in the future will support others.

Template: horde/database_server
Type: string
Default: localhost
Description: What is the hostname where your database is running?
 If your database is on another machine besides the one that HORDE is running
 on then you need to change this value to the fully qualified domain name
 for that system.

Template: horde/webserver_type
Type: select
Choices: Apache, Apache-SSL, Both, Other
Default: Apache
Description: What type of Web Server are you running?
 By default HORDE supports any web server that php does.  This config process
 currently only supports Apache and Apache-SSL directly.  If you use another
 type you will have to handle the web ends manually.

Template: horde/database_name
Type: string
Default: horde
Description: What is the name of your HORDE database?
 By default this will be "horde".  This is where all the HORDE related database
 items will be setup and stored.  All other HORDE modules will most likely use
 this database as well.  If you are upgrading and you use a different database
 then you need to put it in here.

Template: horde/database_user
Type: string
Default: hordemgr
Description: What is your database username?
 What username will access the database for HORDE?  By default this is it's
 own user "hordemgr" so that permissions can be tightened down.

Template: horde/database_pass
Type: password
Default: hordemgr
Description: What is the password you wish to use for the database user
 Enter a password for the database user.  (type "none" for no passwrod)
 This is the password that will be used along with the
 database user name you have already supplied to connect to the database.

Template: horde/mysql_pass
Type: password
Description: What is your root mysql password?
 Enter the password for your root user to access the mysql account.
 This is most likely not the same password that your horde manager account
 will use.  

Template: horde/dbconfigured
Type: select
Choices: yes, no
Default: no
Description: Have you already configured your HORDE database?
 If you are upgrading or for any other reason have already configured your
 database for use with HORDE you'll want to set this to yes. 

Template: horde/restart
Type: select
Choices: webserver, database, both, none
Default: both
Description: Restart affected services (Webserver, Database or Both) after installation?
 This install has the ability to modify services such as your web server
 and your database server.  Please select whether you want either or
 all of the services to be restarted after an installation.

Template: horde/dblocal
Type: select
Choices: yes, no
Default: yes
Description: Is your database local?
 Currently this install process has the ability to configure a database that
 is on the local machine.  In the future it will be able to handle remote
 databases as well.  Is your database local?

Template: horde/installtype
Type: select
Choices: secure, generic, custom
Default: custom
Description: Type of install to use?
 There are 3 different types of installs you can choose from.  Each type
 has it's own set of criteria.  Secure choses the most secure options leaving
 system dependant options up to you.  Generic chooses the most common options
 and leaves system dependant options up to you.  And custom leaves everything
 up to you.
@


1.4
log
@[IEM] first round cleanup of debian package for -dev tree.  Bringing 1.2 stable
branch updates into 1.3-dev tree.
@
text
@@


1.3
log
@[IEM] migrating in changes from 2.2 tree
@
text
@d5 1
a5 3
 around and only new options will show during future upgrades.  If you
 need to change any of these options after installation, please look at
 /etc/horde/defaults.choices.
d9 1
a9 1
 Your current horde.php3 file is getting backed up during the preinst
d12 1
a12 1
 for everything.  Also note that the horde.php3 file is now generated
d15 14
a28 1
Template: horde/problem_reporting
d30 20
a49 6
Choices: true, false
Default: false
Description: Allow problem reporting?
 Horde has the ability to allow web surfers to send in problem reports via
 mail from the HORDE web interface.  By saying yes to this option you are
 enabling this ability.
d78 2
a79 2
 Where are all the html templates stored for horde?  Unless you have changed
 this on purpose then leave it as is.
d87 9
d112 1
a112 1
Description: What email address do you want signups sent to
d128 1
a128 1
 on then you need to chagne this value to the fully qualified domain name
d136 1
a136 1
 By default HORDE supports any web server that php3 does.  This config process
d161 9
d179 28
@


1.2
log
@[IEM] a few more tweaks related to the dev version compared to the pre ver.
@
text
@d99 1
a99 1
Choices: Apache, Apache-SSL, Other
@


1.1
log
@file templates was initially added on branch STABLE_1_2.
@
text
@d1 135
@


1.1.2.1
log
@[IEM] forgot 2 files
@
text
@a0 77
Template: horde/welcome
Type: note
Description: Welcome to the new HORDE setup program
 Please note that these options will only be asked of you the first time
 around and only new options will show during future upgrades.  If you
 need to change any of these options after installation, please look at
 /etc/horde/defaults.choices.
 .
 If you are upgrading currently and this is the first time your using
 the debconf version of the horde install we'll let you know this once.
 Your current defaults.php3 file is getting backed up during the preinst
 process.  This will happen every time you upgrade even though you will
 never see this prompt again unless you have debconf set to prompt you
 for everything.  Also note that the defaults.php3 file is now generated
 on the fly *everytime* you install or upgrade horde.  

Template: horde/problem_reporting
Type: select
Choices: yes, no
Default: yes
Description: Allow problem reporting?
 Horde has the ability to allow web surfers to send in problem reports via
 mail from the HORDE web interface.  By saying yes to this option you are
 enabling this ability.

Template: horde/root_url
Type: string
Default: /horde
Description: What is the default url path for horde?
 When pointing your web browser to Horde, what is the directory pathing you
 will need for getting to horde?  As in http://localhost/horde where /horde
 would be what we are looking for.

Template: horde/graphics_url
Type: string
Default: /horde/graphics
Description: What is the default url path for horde graphics?
 When pointing your web browser to Horde, what is the directory pathing you
 will need for getting to horde graphics?  As in http://localhost/horde/graphics
 where /horde/graphics would be what we are looking for.

Template: horde/faq_url
Type: string
Default: http://faq.horde.org/
Description: What is the url for the FAQ?
 By default this will point to the HORDE online faq.  If you want it to point
 somewhere else change it or leave it blank to not use this option.

Template: horde/horde_include_dir
Type: string
Default: ./templates
Description: What is the path to the templates directory?
 Where are all the html templates stored for horde?  Unless you have changed
 this on purpose then leave it as is.

Template: horde/path_to_sendmail
Type: string
Default: /usr/sbin/sendmail
Description: What is the path to your sendmail program?
 Please the path to the program you use to send mail with.

Template: horde/problem_email
Type: string
Default: root@@localhost
Description: Where do you want problem reports sent to?

Template: horde/signup
Type: boolean
Default: no
Description: Do you want to use the Horde signup feature?
 This option allows users to fill out a form online to request a user account.

Template: horde/signup_email
Type: string
Default: root@@localhost
Description: What email address do you want signups sent to

@


1.1.2.2
log
@[IEM] final touches to the debconf changes.  Now horde is tied into
debocnf so that one will have a one time config option (ala debconf)...now
to finish up the none install configure script that will interact with
debconf...

(2 weeks +/- away from Debian 2.2 freeze)
@
text
@d19 2
a20 2
Choices: true, false
Default: false
d60 1
a60 1
 Please put the path to the program you use to send mail with.
d68 2
a69 3
Type: select
Choices: true, false
Default: false
a71 1
 The form is then sent to an email address which you will be able to configure.
a76 56

Template: horde/database_type
Type: select
Choices: PostgreSQL, MySql
Default: PostgreSQL
Description: What type of container (database) are you going to use?
 Because HORDE uses phplib, we have the ability to support several different
 types of containers.  Currently this package only supports MySql and
 PostgreSQL but in the future will support others.

Template: horde/database_server
Type: string
Default: localhost
Description: What is the hostname where your database is running?
 If your database is on another machine besides the one that HORDE is running
 on then you need to chagne this value to the fully qualified domain name
 for that system.

Template: horde/webserver_type
Type: select
Choices: Apache, Apache-SSL, Other
Default: Apache
Description: What type of Web Server are you running?
 By default HORDE supports any web server that php3 does.  This config process
 currently only supports Apache and Apache-SSL directly.  If you use another
 type you will have to handle the web ends manually.

Template: horde/database_name
Type: string
Default: horde
Description: What is the name of your HORDE database?
 By default this will be "horde".  This is where all the HORDE related database
 items will be setup and stored.  All other HORDE modules will most likely use
 this database as well.  If you are upgrading and you use a different database
 then you need to put it in here.

Template: horde/database_user
Type: string
Default: hordemgr
Description: What is your database username?
 What username will access the database for HORDE?  By default this is it's
 own user "hordemgr" so that permissions can be tightened down.

Template: horde/database_pass
Type: password
Default: hordemgr
Description: What is the password you wish to use for the database user
 Enter a password for the database user.  (type "none" for no passwrod)

Template: horde/dbconfigured
Type: select
Choices: yes, no
Default: no
Description: Have you already configured your HORDE database?
 If you are upgrading or for any other reason have already configured your
 database for use with HORDE you'll want to set this to yes. 
@


1.1.2.3
log
@[IEM] more fixes to the debian build stuff.
      Also cleaning out final stuff from horde's default.php3.dist
@
text
@d26 1
a26 1
Template: horde/horde_root_url
d34 1
a34 1
Template: horde/horde_graphics_url
@


1.1.2.4
log
@[IEM] removing defaults.php3 since it's not being used and doesn't need
to be here anymore.
@
text
@d5 3
a7 1
 around and only new options will show during future upgrades.  
d11 1
a11 1
 Your current horde.php3 file is getting backed up during the preinst
d14 1
a14 1
 for everything.  Also note that the horde.php3 file is now generated
@


1.1.2.5
log
@[IEM] minor debian fixes dealing with debconf
@
text
@d97 1
a97 1
Choices: Apache, Apache-SSL, Both, Other
@


1.1.2.6
log
@[IEM] minor type cleanup for debian package stuff
@
text
@d15 9
a59 9
Template: horde/problem_reporting
Type: select
Choices: true, false
Default: false
Description: Do you want to use the HORDE problem reporting feature?
 Horde has the ability to allow web surfers to send in problem reports via
 mail from the HORDE web interface.  By saying yes to this option you are
 enabling this ability.

d76 1
a76 1
Description: What email address do you want signups sent to?
d92 1
a92 1
 on then you need to change this value to the fully qualified domain name
d133 1
@


1.1.2.7
log
@[IEM] committing final changes which fix all known issues with the debian
package (potato based)...should be happy for the freeze
@
text
@a14 11
Template: horde/remove
Type: note
Description: You need to remove the lines in access.conf manually!
 HORDE is still a work in progress and do to that some of the 
 installation and removal pieces are not complete.  In order to complete
 the removal of HORDE from your system, you need to remove the lines
 refering to HORDE from your /etc/apache/access.conf file (or 
 /etc/apache-ssl/access.conf if your using Apache-SSL).  
 .
 NOTE: Apache will break if you do not do this!!!

d42 2
a43 2
 Where are all the html templates stored for horde?  Unless you have 
 changed this on purpose then leave it as is.
d56 3
a58 3
 Horde has the ability to allow web surfers to send in problem reports
 via mail from the HORDE web interface.  By saying yes to this option 
 you are enabling this ability.
@


1.1.2.8
log
@[IEM] some more updates to the debconf stuff for debian packages
@
text
@d66 3
a68 3
Description: Use built in problem reporting feature?
 Horde has the ability to allow web surfers to send in problem reports via mail
 from the HORDE web interface. By saying yes to this option you are enabling
@


1.1.2.9
log
@[IEM] fixing several problems with debian packaging.  Creating templates for
      manual configuration instead of using debconf for those vi users out
      there.
@
text
@a25 11
Template: horde/autogen
Type: select
Choices: true, false
Default: true
Description: Do you want config files to be generated by debconf automatically?
 Using debconf we can automatically create all the necessary config files
 automatically during each upgrade/install.  This means that any changes you
 have made manually will be overwritten.  A backup copy of these files are
 always made prior to the upgrade but you will have to manually make any
 personal updates to the horde.php3.in template file.

@


1.1.2.10
log
@[IEM] more updates and bug fixes to the debian packaging...mostly typos
 and more fixes to mysql configuration pieces thanks to feedback.
@
text
@d27 3
a29 3
Type: boolean
Choices: yes, no
Default: yes
a146 9
 This is the password that will be used along with the
 database user name you have already supplied to connect to the database.

Template: horde/mysql_pass
Type: password
Description: What is your root mysql password?
 Enter the password for your root user to access the mysql account.
 This is most likely not the same password that your horde manager account
 will use.  
@


1.1.2.11
log
@[IEM] more debconf cleanup. Adding a update-horde script to rebuild config
files after modifying the templates.
@
text
@a14 13
Template: horde/configmethod
Type: select
Choices: auto, manual
Default: auto
Description: What method of configuration do you want?
 You now must decide which method of configuration you wish to use.
 You can use an automatic method which will require you to answer some
 questions now and your config files will be generated (and re-generated
 in the future) based on your answers.  The alternative is the manual
 method which requires you to manually edit a configuration template
 (horde.php3.in) and run the update-horde program to generate the 
 proper config files.

d26 11
d159 1
a159 1
Choices: no, yes
@


1.1.2.12
log
@[IEM] setting an option to not recheck non-horde config files during each
upgrade.
@
text
@a27 9
Template: horde/recheck
Type: boolean
Choices: yes, no
Default: yes
Description: Verify non-horde config files during upgrades?
 Do you want the upgrade process to verify (and fix) other config files
 related to horde?  These would include Apache, php3, and postgres 
 config files and changes necessary for horde to work properly.

@


1.1.2.13
log
@[IEM] more debian work...redoing postinst script including a better way
of doing things thanks to another debian guru...fixed up alot of other items
and added more documentation
@
text
@d32 3
a34 3
Description: Verify non-horde config files during upgrades/installs?
 Do you want the install/upgrade process to verify (and fix) other config files
 related to horde?  These would include Apache, php3, and database
a174 18

Template: horde/restart
Type: select
Choices: webserver, datagbase, both
Default: both
Description: Restart affected services (Webserver, Database or Both) after installation?
 This install has the ability to modify services such as your web server
 and your database server.  Please select whether you want either or
 all of the services to be restarted after an installation.

Template: horde/dblocal
Type: select
Choices: yes, no
Default: yes
Description: Is your database local?
 Currently this install process has the ability to configure a database that
 is on the local machine.  In the future it will be able to handle remote
 databases as well.  Is your database local?
@


1.1.2.14
log
@[IEM] typo fixes, cleanup, and whatnot for debian
@
text
@d178 1
a178 1
Choices: webserver, database, both
@


1.1.2.15
log
@[IEM] more tweaks...adding in more robust configuration options...working
on different types of install options (secure, normal, custom)  all for
debian.
@
text
@d15 1
a15 1
Template: horde/debconf
d17 3
a19 3
Choices: yes, no
Default: yes
Description: Use debconf to configure HORDE/IMP?
d178 1
a178 1
Choices: webserver, database, both, none
a192 11

Template: horde/installtype
Type: select
Choices: secure, generic, custom
Default: custom
Description: Type of install to use?
 There are 3 different types of installs you can choose from.  Each type
 has it's own set of criteria.  Secure choses the most secure options leaving
 system dependant options up to you.  Generic chooses the most common options
 and leaves system dependant options up to you.  And custom leaves everything
 up to you.
@


1.1.2.16
log
@[IEM] fixes for update-horde debian script
@
text
@d170 1
a170 1
Choices: yes, no
@


1.1.2.17
log
@[IEM] more fixes...mainly with the scripting of the configs
@
text
@d28 2
a29 2
Template: horde/horderecheck
Type: select
a35 3
 ***NOTE*** Things will not work properly if you do not have things
 setup properly.  If you choose not to verify non-horde config files, please
 read the Debian.Install file in /usr/share/doc/horde
@


1.1.2.18
log
@[IEM] minor tweak to fix a bug when the username the webserver is run as
isn't the default debian one
@
text
@a155 10
Template: horde/web_user
Type: string
Default: www-data
Description: What is the username that your web server runs as?
 What username do you use to run your webserver.  By default on Debian it
 is www-data, but some people like to change it.  We need this so that we
 can set the security on the HORDE files properly.  Since there is system
 configuration information stored in some files we need to only allow 
 the web server to view these files.

@


1.1.2.19
log
@[IEM] fixing configuration issues with php4.  Debian package now works with
php3 or php4.
@
text
@a206 9
Template: horde/phpversion
Type: select
Choices: php3, php4
Default: php3
Description: What version of PHP are you using?
 HORDE works with both php3 and php4 but the configuration of php differs
 for each version.  We need to know which version you plan on using 
 (especially since you can have both installed at the same time) with HORDE.

@


1.1.2.20
log
@[IEM] better handling of exim
@
text
@a225 11

Template: horde/eximconf
Type: note
Description: Note to EXIM users and possibly others...
 All mail sent from the Horde system modifies the sending user's name.
 With mail programs such as Exim, you must set the up the web user as 
 someone allowed to modify the senders name in mail headers.  We can 
 attempt to do this for you.  You must edit the /etc/exim.conf file
 and add "www-data" to the list of trusted users.  Failure to do this
 will cause all bounced messages sent by the Horde system to go to
 postmaster (or root) instead of the originating user.
@


1.1.2.21
log
@[IEM] some cleanup with the debconf pieces
@
text
@d20 2
a21 2
 You now must decide if you wish to use the automatic (debconf) method
 of configuration. The debconf method will require you to answer some
@


1.1.2.22
log
@[IEM] more debconf debian tweaks
@
text
@a13 5
 .
 You must have a database already setup locally and ready to go if you are
 going to have this program configure your database for you.  If you are
 not comfortable with this, you should tell the debconf process that your
 database is not local
a21 2
 (Depending on how you have debconf configured it could be anywhere from
 4 or 5 questions to twenty or more questions. )
d138 1
a138 4
 type you will have to handle the web ends manually.  If you chose one
 of the first three options, this install process will manage the configuration
 (or attempt to) of the Apache specific portions necessary to run horde 
 properly.  If you do not wish this to happen, please chose the Other option.
@


1.1.2.23
log
@[IEM] minor updates, typo fixes, etc for debian
@
text
@d180 1
a180 1
 Enter a password for the database user.  (type "none" for no password)
@


1.1.2.24
log
@[IEM] updating debian files..fixing typos in update-horde and other scripts
@
text
@a175 10
Template: horde/web_group
Type: string
Default: www-data
Description: What is the group that your web server runs as?
 What group do you use to run your webserver.  By default on Debian it
 is www-data, but some people like to change it.  We need this so that we
 can set the security on the HORDE files properly.  Since there is system
 configuration information stored in some files we need to only allow
 the web server to view these files.                   

@


1.1.2.25
log
@[IEM] updating debian stuff
@
text
@d20 15
d58 63
d235 11
@


1.1.2.26
log
@About to release debian version 1.2.4-1. Quite a lot of changes now.
@
text
@d13 1
a13 1
 on the fly *everytime* you install or upgrade horde.
d25 3
a27 3
 Do you want the install/upgrade process to verify (and fix) other config
 files related to horde?  These would include Apache, php3, exim, and
 database config files and changes necessary for horde to work properly.
d30 1
a30 1
 read the Debian.Install file in /usr/share/doc/horde.
d34 6
a39 4
Description: The HORDE remove script will try to remove all traces from
 the apache config, but only if you have told it to verify other config files
 related to horde. I you have not selected that you need to remove that config
 yourself.
d41 1
a41 3
 HORDE is still a work in progress and due to that some of the installation and
 removal pieces might not be complete. It will do what it can but sometimes it
 fails and then you have to unconfigure it yourself, else Apache will break!
d49 2
a50 2
 types of container databases. Currently this package only supports MySql and
 PostgreSQL.
d152 1
a152 1
Default: php4
d163 3
a165 4
 someone allowed to modify the senders name in mail headers.  We will
 attempt to do this for you if you have selected to verify (and fix) other
 config files. Otherwise you must edit the /etc/exim.conf file
 and add "www-data" to the list of trusted users. Failure to do this
@


1.1.2.27
log
@Major changes, next version of horde.
@
text
@d9 5
d17 2
a18 2
 not comfortable with this, you should tell the debconf process that you
 do not have any database.
d20 1
a20 1
Template: horde/webserver_type
d22 20
a41 9
Choices: Apache, Apache-SSL, Both, Other
Default: Apache
Description: What type of Web Server are you running?
 By default HORDE supports any web server that php3 does.  This config process
 currently only supports Apache and Apache-SSL directly.  If you use another
 type you will have to handle the web ends manually.  If you chose one
 of the first three options, this install process will manage the configuration
 (or attempt to) of the Apache specific portions necessary to run horde 
 properly.  If you do not wish this to happen, please chose the Other option.
d43 1
a43 1
Template: horde/databasemgr_type
d45 2
a46 2
Choices: PostgreSQL, MySql, none
Default: MySql
d52 1
a52 1
Template: horde/databasemgr_server
d60 12
d75 4
a78 4
Description: What name do you want for your HORDE database?
 By default this will be "horde". This is where all the HORDE related database
 items will be setup and stored. All other HORDE modules will most likely use
 this database as well. If you are upgrading and you use a different database
d88 20
d116 1
a116 11
Template: horde/dbmyadmin
Type: string
Default: root
Description: Enter the username of the administrator in the MySQL database.

Template: horde/dbpgadmin
Type: string
Default: postgres
Description: Enter the username of the administrator in the PostgreSQL database.

Template: horde/dbadmpass
d118 4
a121 4
Description: What is your admin database password?
 Enter the password for your database admin user to access the datbase.
 This is most likely NOT the same password that your horde manager account
 will use.
d130 39
@


