Difference between revisions of "Building FRANKLIN on CentOS 5"
(Adding Template:Article Footer, and Categories: Build, and CentOS) |
|||
Line 1: | Line 1: | ||
{{WIP}} | {{WIP}} | ||
− | + | == Introduction == | |
+ | |||
+ | Building Zimbra on any platform is really complex: there are many variables and places where things can go wrong. | ||
+ | |||
+ | == Getting the source == | ||
+ | |||
+ | There are two main ways to getting the Zimbra sources: | ||
+ | |||
+ | * Zimbra Community Builds (http://sourceforge.net/projects/zimbracommunity) | ||
+ | * Zimbra's official Perforce repositories | ||
+ | |||
+ | To download official Zimbra sources, first get proprietary Perforce client (free) from http://www.perforce.com/perforce/downloads/platform.html. Next create a temporary directory for the sources | ||
+ | |||
+ | $ mkdir /home/username/temp | ||
+ | |||
+ | Next do some linking to work around p4's default behaviour: | ||
+ | |||
+ | $ ln -s /home/username/temp /home/public | ||
+ | |||
+ | Then export some P4-related environment variables and do a full resync. This is required, because p4 is a proprietary program and it can't track changes for the public account. | ||
+ | |||
+ | $ export P4EDITOR=nano | ||
+ | $ export P4PORT=codes.zimbra.com:2666 | ||
+ | $ p4 -u public -P public1234 -c public-view sync -f //depot/zcs/FRANKLIN/... | ||
+ | |||
+ | Perforce should now start downloading the source code. | ||
+ | |||
{{Article Footer|unknown|4/28/2008}} | {{Article Footer|unknown|4/28/2008}} |
Revision as of 13:37, 1 December 2008
Introduction
Building Zimbra on any platform is really complex: there are many variables and places where things can go wrong.
Getting the source
There are two main ways to getting the Zimbra sources:
- Zimbra Community Builds (http://sourceforge.net/projects/zimbracommunity)
- Zimbra's official Perforce repositories
To download official Zimbra sources, first get proprietary Perforce client (free) from http://www.perforce.com/perforce/downloads/platform.html. Next create a temporary directory for the sources
$ mkdir /home/username/temp
Next do some linking to work around p4's default behaviour:
$ ln -s /home/username/temp /home/public
Then export some P4-related environment variables and do a full resync. This is required, because p4 is a proprietary program and it can't track changes for the public account.
$ export P4EDITOR=nano $ export P4PORT=codes.zimbra.com:2666 $ p4 -u public -P public1234 -c public-view sync -f //depot/zcs/FRANKLIN/...
Perforce should now start downloading the source code.