20120221 special project building 389 directory from source - plembo/onemoretech GitHub Wiki

title: Special project: building 389 directory from source link: https://onemoretech.wordpress.com/2012/02/21/special-project-building-389-directory-from-source/ author: lembobro description: post_id: 2223 created: 2012/02/21 02:34:08 created_gmt: 2012/02/21 06:34:08 comment_status: closed post_name: special-project-building-389-directory-from-source status: publish post_type: post

Special project: building 389 directory from source

Wanted to try this because I really, really would like to deploy 389 directory with a more sensible file system layout than the standard LSB architecture. What I wouldn't do for a basic .zip installation package... ... like Sun did for DSEE before it was acquired. Doing the compile from source turned out to be easier than I thought it would be. I used the latest stable source for 389-ds-base, 1.2.9.9 as of this writing. I already had 389 directory for RHEL 6 installed, up and running from the developer's yum repository. The only additional pieces I had to install were the following rpms. mozldap mozldap-devel mozldap-tools libicu-devel icu pcre-devel Some other packages you might need that were already on my machine: nspr nspr-devel nss nss-tools nss-util nss-devel nss-util-devel svrcore svrcore-devel perl-Mozilla-LDAP db4 db4-devel db4-utils net-snmp cyrus-sasl cyrus-sasl-devel Then I did a

./configure --prefix=/opt/dirsrv

and a "make" and "make install". Found the setup-ds.pl script under /opt/dirsrv/sbin. Setting up a new instance called "localhost" created it under /opt/dirsrv/var/lib/dirsrv/slapd-localhost. Have not tested thoroughly yet, so I'm not sure what limitations there might be (can I get LDAPS working?). This was just the core directory server. Will leave mucking around with the console for later. A higher priority would be flattening the file system paths a bit to get "/opt/dirsrv/etc" rather than "/opt/dirsrv/etc/dirsrv", or "/opt/dirsrv/var/lib/dirsrv/slapd-localhost" to "/opt/dirsrv/var/slapd-localhost" or even "/opt/dirsrv/slapd-localhost" like I can do with DSEE. Ultimately I'd like to come up with a zip distribution of my own that I can deploy to any server I like. One of the challenges in doing something like that is understanding, in detail, all the dependencies that need to be in place.