From 1123c7f43a886b1625a8cb10d1f124633b28f6fc Mon Sep 17 00:00:00 2001 From: "lpsolit%gmail.com" <> Date: Fri, 4 Apr 2008 11:48:24 +0000 Subject: Bug 390972: we shouldn't favor fink for os x - Patch by timeless r=Colin r=justdave --- docs/en/xml/installation.xml | 298 ++----------------------------------------- 1 file changed, 14 insertions(+), 284 deletions(-) (limited to 'docs/en') diff --git a/docs/en/xml/installation.xml b/docs/en/xml/installation.xml index 957f74bc3..0bdcd4562 100644 --- a/docs/en/xml/installation.xml +++ b/docs/en/xml/installation.xml @@ -1,5 +1,5 @@ - + Installing Bugzilla @@ -652,7 +652,6 @@ -
Configuration @@ -1318,7 +1317,6 @@ c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
-
Optional Additional Configuration @@ -1373,54 +1371,6 @@ c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
-
- Dependency Charts - - As well as the text-based dependency trees, Bugzilla also - supports a graphical view of dependency relationships, using a - package called 'dot'. - Exactly how this works is controlled by the 'webdotbase' parameter, - which can have one of three values: - - - - - - - A complete file path to the command 'dot' (part of - GraphViz) - will generate the graphs locally - - - - - A URL prefix pointing to an installation of the webdot package will - generate the graphs remotely - - - - - A blank value will disable dependency graphing. - - - - - - The easiest way to get this working is to install - GraphViz. If you - do that, you need to - enable - server-side image maps in Apache. - Alternatively, you could set up a webdot server, or use the AT&T - public webdot server. This is the default for the webdotbase param, - but it's often overloaded and slow. Note that AT&T's server - won't work - if Bugzilla is only accessible using HARTS. - Editor's note: What the heck is HARTS? Google doesn't know... - - -
-
The Whining Cron @@ -1485,229 +1435,7 @@ c:\perl\bin\perl.exe -xc:\bugzilla -wT "%s" %s
- -
- Patch Viewer - - - Patch Viewer is the engine behind Bugzilla's graphical display of - code patches. You can integrate this with copies of the - cvs, lxr and - bonsai tools if you have them, by giving - the locations of your installation of these tools in - editparams.cgi. - - - Patch Viewer also optionally will use the - cvs, diff and - interdiff - command-line utilities if they exist on the system. - Interdiff can be obtained from - . - If these programs are not in the system path, you can configure - their locations in localconfig. - - - -
- -
- RADIUS Authentication - - RADIUS authentication is a module for Bugzilla's plugin - authentication architecture. - Most caveats that apply to LDAP authentication apply to RADIUS - authentication as well. - - - Parameters required to use RADIUS Authentication: - - - - user_verify_class - - If you want to list RADIUS here, - make sure to have set up the other parameters listed below. - Unless you have other (working) authentication methods listed as - well, you may otherwise not be able to log back in to Bugzilla once - you log out. - If this happens to you, you will need to manually edit - data/params and set user_verify_class to - DB. - - - - - - RADIUS_server - - This parameter should be set to the name (and optionally the - port) of your RADIUS server. - - - - - - RADIUS_secret - - This parameter should be set to the RADIUS server's secret. - - - - - - RADIUS_email_suffix - - Bugzilla needs an e-mail address for each user account. - Therefore, it needs to determine the e-mail address corresponding - to a RADIUS user. - Bugzilla offers only a simple way to do this: it can concatenate - a suffix to the RADIUS user name to convert it into an e-mail - address. - You can specify this suffix in the RADIUS_email_suffix parameter. - - If this simple solution does not work for you, you'll - probably need to modify - Bugzilla/Auth/Verify/RADIUS.pm to match your - requirements. - - - - - -
- -
- LDAP Authentication - - LDAP authentication is a module for Bugzilla's plugin - authentication architecture. - - - - The existing authentication - scheme for Bugzilla uses email addresses as the primary user ID, and a - password to authenticate that user. All places within Bugzilla where - you need to deal with user ID (e.g assigning a bug) use the email - address. The LDAP authentication builds on top of this scheme, rather - than replacing it. The initial log in is done with a username and - password for the LDAP directory. Bugzilla tries to bind to LDAP using - those credentials, and if successful, try to map this account to a - Bugzilla account. If a LDAP mail attribute is defined, the value of this - attribute is used, otherwise emailsuffix parameter is appended to LDAP - username to form a full email address. If an account for this address - already exists in your Bugzilla system, it will log in to that account. - If no account for that email address exists, one is created at the time - of login. (In this case, Bugzilla will attempt to use the "displayName" - or "cn" attribute to determine the user's full name.) After - authentication, all other user-related tasks are still handled by email - address, not LDAP username. You still assign bugs by email address, query - on users by email address, etc. - - - - Because the Bugzilla account is not created until the first time - a user logs in, a user who has not yet logged is unknown to Bugzilla. - This means they cannot be used as an assignee or QA contact (default or - otherwise), added to any cc list, or any other such operation. One - possible workaround is the bugzilla_ldapsync.rb - script in the - contrib directory. Another possible solution is fixing - bug - 201069. - - - - Parameters required to use LDAP Authentication: - - - - user_verify_class - - If you want to list LDAP here, - make sure to have set up the other parameters listed below. - Unless you have other (working) authentication methods listed as - well, you may otherwise not be able to log back in to Bugzilla once - you log out. - If this happens to you, you will need to manually edit - data/params and set user_verify_class to - DB. - - - - - - LDAPserver - - This parameter should be set to the name (and optionally the - port) of your LDAP server. If no port is specified, it assumes - the default LDAP port of 389. - - Ex. ldap.company.com - or ldap.company.com:3268 - - You can also specify a LDAP URI, so as to use other - protocols, such as LDAPS or LDAPI. If port was not specified in - the URI, the default is either 389 or 636 for 'LDAP' and 'LDAPS' - schemes respectively. - - Ex. ldap://ldap.company.com, - ldaps://ldap.company.com or - ldapi://%2fvar%2flib%2fldap_sock - - - - - - LDAPbinddn [Optional] - - Some LDAP servers will not allow an anonymous bind to search - the directory. If this is the case with your configuration you - should set the LDAPbinddn parameter to the user account Bugzilla - should use instead of the anonymous bind. - - Ex. cn=default,cn=user:password - - - - - LDAPBaseDN - - The LDAPBaseDN parameter should be set to the location in - your LDAP tree that you would like to search for email addresses. - Your uids should be unique under the DN specified here. - - Ex. ou=People,o=Company - - - - - LDAPuidattribute - - The LDAPuidattribute parameter should be set to the attribute - which contains the unique UID of your users. The value retrieved - from this attribute will be used when attempting to bind as the - user to confirm their password. - - Ex. uid - - - - - LDAPmailattribute - - The LDAPmailattribute parameter should be the name of the - attribute which contains the email address your users will enter - into the Bugzilla login boxes. - - Ex. mail - - - - -
-
Serving Alternate Formats with the right MIME type @@ -1950,19 +1678,20 @@ C:\perl> ppm install <module name>
Libraries & Perl Modules on Mac OS X - Apple did not include the GD library with Mac OS X. Bugzilla + Apple does not include the GD library with Mac OS X. Bugzilla needs this for bug graphs. - You can install it using a program called - Fink, which is similar in nature to the CPAN installer, but installs - common GNU utilities. Fink is available from - . + You can use DarwinPorts () + or Fink (), both + of which are similar in nature to the CPAN installer, but install + common unix programs. - Follow the instructions for setting up Fink. Once it's installed, - you'll want to use it to install the gd2 package. + Follow the instructions for setting up DarwinPorts or Fink. + Once you have one installed, you'll want to use it to install the + gd2 package. - It will prompt you for a number of dependencies, type 'y' and hit + Fink will prompt you for a number of dependencies, type 'y' and hit enter to install all of the dependencies and then watch it work. You will then be able to use CPAN to install the GD Perl module. @@ -1983,9 +1712,10 @@ C:\perl> ppm install <module name> - Also available via Fink is expat. After using - fink to install the expat package you will be able to install - XML::Parser using CPAN. There is one caveat. Unlike recent versions of + Also available via DarwinPorts and Fink is + expat. After installing the expat package, you + will be able to install XML::Parser using CPAN. If you use fink, there + is one caveat. Unlike recent versions of the GD module, XML::Parser doesn't prompt for the location of the required libraries. When using CPAN, you will need to use the following command sequence: -- cgit v1.2.3-24-g4f1b