seen that steps have been approved I would immediately start with the
first 2 points.
1. download the source files
A. Where are the right sources, which branch should be used?
source files can be downloaded from the mercurial repository
using the following command:
hg clone
https://code.google.com/p/arsenalsuite/
The repository is composed of more than one branch. The branch
"default" contains the
latest stable versions of files, which means that we will use
the branch "default" to compile.
B. Prepare a folder structure
to keep my system clean, I use the following directory
structure:
~/buitd/arsenalsuite/hg_source - contains the source code
~/buitd/arsenalsuite/install - the result of the build
~/buitd/arsenalsuite/rpmbuild - the result of the
creation of rpm packages
C. Download the source
I use the following commands:
mkdir -p ~/build/arsenalsuite
cd ~/build/arsenalsuite
hg clone
https://code.google.com/p/arsenalsuite/ hg-
source
mkdir install
mkdir rpmbuild
2. prepare the environment
A. Installation of dependencies
postgresql
qt4
graphviz-devel
mercurial
mercurial-devel
xmpppy
qt-assistant-adp-devel
phonon-devel
ImageMagick-c++-devel
and certainly standard gcc make tools
libXScrnSaver-devel
qtwebkit-devel
qt-postgresql
B. Set the environment variable
Aren Villanueva wrote:
"It would be a good opportunity to ensure it works
outside of our specific build environments"
I agree with this statement
only such we have a couple of problems:
1. how to define the destination folder for
installation? such as --prefix=path_to_install ?
2. where to build rpm packages?
There is some truth here?
it will take time to complete this work ... but I want to do it well.
look forward to your comments.