Difference between revisions of "Building FRANKLIN on CentOS 5"

(Adding Template:Article Footer, and Categories: Build, and CentOS)
Line 1: Line 1:
 
{{WIP}}
 
{{WIP}}
  
SHS
+
== 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:

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.


Verified Against: unknown Date Created: 4/28/2008
Article ID: https://wiki.zimbra.com/index.php?title=Building_FRANKLIN_on_CentOS_5 Date Modified: 2008-12-01



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »

Jump to: navigation, search