Gentoo Wiki





This HOWTO describes how to install project-open, a Web-based ERP/Project Management software, on a Gentoo system. As ]po[ isn't in the portage tree, and depends on older versions of software, installation by following the ]po[ documentation can be confusing for first-timers. In this HOWTO it is assumed the reader has a fully-functional Gentoo system.

Use Windows.

Notice: comments and constructive criticism are welcome on the discussion and bugs page! __undefined__


The first step in installing [project-open] is downloading the compressed archive from SourceForge. Select the plus mark to expand the 3.1 branch downloads and download the file ProjectOpen- to your home folder.

Required Dependencies

]project-open[ requires the following packages, it is recommended to install these first. The requirements are taken from the ]po[ installation guide for 3.1, if installing 3.2 see its respective list.

For ]po[ 3.x

Installing Dependencies for 3.1


As of the time this document was written the latest version of PostgreSQL on portage was 8.0.9-r1, which isn't compatible with ]po[ 3.1, instead of using the standard emerge command, the version must be specified. __undefined__ Now we should change the password for postgre, the username (that should have been) created by portage for working with postgreSQL. __undefined__

If you get the error:

passwd: Authentication token manipulation error

You need to add a line of code to /etc/shadow. __undefined__ At the bottom add the following line of code


Now try setting the password again, it should work. If you have more things that you want to do with PostgreSQL check out HOWTO Configure Postgresql. It will go into more depth on configuring PostgreSQL, as this article only covers what's needed to get ]po[ working.


Installing CVS is easy, as the latest on portage is 1.12.12-r2 which fulfills the dependency version requirement. __undefined__


For AOLServer there is a choice, either use the binaries provided, or grab it from portage. This section will focus on the included binary, the next section covers installing AOLServer from portage. Choose the included binary if testing and debugging isn't an option.

Remember where that project-open.3-1-2-0-0.tgz tarball was saved? Now the files contained in this file need to be extracted. __undefined__ After this completes, there should be two more tarballs and a installation file

Since you are reading this guide, there is no need for INSTALL, project-open.3-1-2-0-0.tgz is the tarball containing all of the core files for ]po[, aolserver3.3oacs.tgz contains the AOLServer binaries that are distributed with ]po[. For these binaries to work they need to be in /usr/local. Remember for this example the user name that is doing the work is johnh, your user name may be different and should be replaced accordingly. __undefined__ Now that the binaries are now extracted, they should be tested to see if they work __undefined__ If a help menu is displayed then the binaries work.

AOLServer (from portage)

__undefined__ AOLServer is needed for it's TCL interpretation, which means the tcl USE flag must be used otherwise ]po[ won't work. The TCL language needs the threads USE flag as well. If these aren't in your make.conf, or you don't want them there, then lets add them to package.use. __undefined__

Now add the following line to package.use and save the file

dev-lang/tcl threads
www-servers/aolserver tcl

A quick check of portage reveals that AOLserver is masked as unstable so an block work around must be made in /etc/portage/package.keywords __undefined__

Now add the following line to package.keywords and save the file


After completing the above, AOLServer should merge correctly using emerge. __undefined__


Now that everything is emerged it should be started and added to the default runlevel. CVS isn't crutial to the opperation of ]po[ and thus is left out of the step, but may be included if desired. __undefined__

If any error occur when starting a process make sure that the second emerge command for postgreSQL was run othewise it won't have a database (or configuration files) to load.

Installing Dependencies for 3.2

See instructions of 3.1 for 3.2betas

Installing [project-open]

__undefined__ The first step in installing [project-open] is downloading the compressed archive from SourceForge. Select the plus mark to expand the 3.1 branch downloads and download the file ProjectOpen- to your home folder.

Configuring Database

With the files in place let's switch into the postgre user and check if postgreSQL is running or not. __undefined__ You should be greeted with the following (the first line of many)

This is psql 7.4.14, the PostgreSQL interactive terminal.

If so, then postgreSQL was installed. Now we can setup the user, database, and language for ]po[. __undefined__ Note that the last line switches the user back to the root, or what ever user you were previously.

Loading Sample Data (Recomended but Optional)

]project-open[ comes with two demo databases, ]projoect-consulting[ and ]project-translation[.


After selecting one of the two project databases to load switch to the projop user and load the files into the database. __undefined__ Now to check if the process was sucessfull we are going to do a SQL quere. __undefined__ For either demo the result should be 192. You can exit by typing \q

Custom Login

If you loaded a demo database, you will need to complete this step. Each project has its own login, and should have it's respective login loaded. __undefined__ The -f was used to force the overwriting of the file, do this with caution.

Retrieved from ""

Last modified: Fri, 05 Sep 2008 01:10:00 +0000 Hits: 13,824