Just for the community's benefit, here is a very quick summary of my CentOS environment, in case others want to try and replicate.
1. CentOS v6.4, x86_64, 'minimal server' install plus yum groupinstall of "Development tools" and "Ruby support".
2. The page https://github.com/Metaswitch/sprout/blob/dev/docs/Development.md, step 3,
lists a long sequence of Debian package dependencies. Their CentOS equivs look like this.
CentOS | Ubuntu
------------------|----------------------
ntp* : ntp
*** : build-essential
autoconf* : autoconf
scons : scons
pkgconfig* : pkg-config
libtool* : libtool
cloog-ppl : libcloog-ppl0
gdb* : gdb
gdb* : pstack
git* : git
git-svn : git-svn
n/a : dpkg-dev
n/a : devscripts
n/a : dh-make
python-setuptools : python-setuptools
*** : python-virtualenv
python-devel : python-dev
libcurl-devel : libcurl4-openssl-dev
mysql-devel : libmysqlclient-dev
gmp : libgmp10
gmp-devel : libgmp-dev
c-ares-devel : libc-ares-dev
ncurses-devel : ncurses-dev
libxml2-devel : libxml2-dev
libxslt-devel : libxslt1-dev
boost-devel : libboost-all-dev
<source>* : libzmq-dev
valgrind* : valgrind
libxml2 : libxml2-utils
rubygems* : rubygems
* already there
- no corresponding match
n/a Debian-specific
<source> installed from source
*** no native equivalent
As can be seen from the above list, there are some packages that do not have
a 'native' CentOS equivalent. Build-essentials is largely covered (eg we already
have most of the packages it lists installed) but for things like dpkg we need
to go to EPEL. The python-virtualenv is only available from EPEL.
I believe that installing dpkg and dpkg-devel on CentOS is perverse (and
indeed, the RPM notes that it is not quite natural) but I included it just
in case the build absolutely demanded it (although I have no intention of ever
knowingly calling a 'make deb' target on CentOS).
--k
1. CentOS v6.4, x86_64, 'minimal server' install plus yum groupinstall of "Development tools" and "Ruby support".
2. The page https://github.com/Metaswitch/sprout/blob/dev/docs/Development.md, step 3,
lists a long sequence of Debian package dependencies. Their CentOS equivs look like this.
CentOS | Ubuntu
------------------|----------------------
ntp* : ntp
*** : build-essential
autoconf* : autoconf
scons : scons
pkgconfig* : pkg-config
libtool* : libtool
cloog-ppl : libcloog-ppl0
gdb* : gdb
gdb* : pstack
git* : git
git-svn : git-svn
n/a : dpkg-dev
n/a : devscripts
n/a : dh-make
python-setuptools : python-setuptools
*** : python-virtualenv
python-devel : python-dev
libcurl-devel : libcurl4-openssl-dev
mysql-devel : libmysqlclient-dev
gmp : libgmp10
gmp-devel : libgmp-dev
c-ares-devel : libc-ares-dev
ncurses-devel : ncurses-dev
libxml2-devel : libxml2-dev
libxslt-devel : libxslt1-dev
boost-devel : libboost-all-dev
<source>* : libzmq-dev
valgrind* : valgrind
libxml2 : libxml2-utils
rubygems* : rubygems
* already there
- no corresponding match
n/a Debian-specific
<source> installed from source
*** no native equivalent
As can be seen from the above list, there are some packages that do not have
a 'native' CentOS equivalent. Build-essentials is largely covered (eg we already
have most of the packages it lists installed) but for things like dpkg we need
to go to EPEL. The python-virtualenv is only available from EPEL.
I believe that installing dpkg and dpkg-devel on CentOS is perverse (and
indeed, the RPM notes that it is not quite natural) but I included it just
in case the build absolutely demanded it (although I have no intention of ever
knowingly calling a 'make deb' target on CentOS).
--k
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
