Setting up a Development Server (3/4)

Posted on Posted in Technology Center

CVS

  • Install CVS via yum.
  • Setup the listening port.
  • Make sure the following lines exist in /etc/services

    cvspserver 2401/tcp

  • Create file named cvspserver under/etc/xinetd.dwith the following contents:

    service cvspserver
    {
    socket_type = stream
    protocol = tcp
    wait = no
    user = root
    server = /usr/bin/cvs
    server_args = –allow-root=/home/cvs pserver
    }

      • Make sure to set allow-root to correct cvs home.
      • Initialize the repository.

    cvs -d :local:/home/cvs init

    • Check if directory has appropriate permissions.

      chmod –R 775 /home/cvs
      chmod –R g+ws /home/cvs

    • Restart xinetd.d service.

      /etc/init.d/xinetd restart

  • Test CVS Connection.

Java (Reference: http://www.mksearch.mkdoc.org/howto/jpackage-sun-fc3/)

  • To add jpackage (prebuilt for RHEL4) repository to CentOS:

    cd /etc/yum.repos.d/
    wget http://www.jpackage.org/jpackage.repo
    vi jpackage.repo

  • Enable the rhel specific repository. Keep the others enabled as well.

    [jpackage-rhel]
    name=JPackage (free) for Red Hat Enterprise Linux $releasever
    mirrorlist=http://www.jpackage.org/jpackage_rhel-$releasever.txt
    failovermethod=priority
    gpgcheck=1
    gpgkey=http://www.jpackage.org/jpackage.asc
    enabled=1

  • These packages are signed with a GPG key so you will need to import the key
    ( as root ).

    rpm –import http://www.jpackage.org/jpackage.asc

  • Build non-free java packages. (http://www.jpackage.org/rebuilding.php)
      • First, you need a build tree in user home directory. This build tree should have the following structure:

        rpm
        |– BUILD
        |– RPMS
        | |– i386
        | |– i586
        | `– noarch
        |– SOURCES
        |– SPECS
        |– SRPMS
        `– tmp

      • Now you need to do some rpm configuration. A simple ~/.rpmmacros with the following contents should be enough:

    %_topdir %(echo ${HOME}/rpm)
    %_tmppath %{_topdir}/tmp

    %packager Allan Tan

    # Uncomment to have built RPMs land in RPMS/ instead of RPMS//
    #%_rpmfilename %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm

    • Upload the following files and copy to ~/rpm/SOURCES:

      jta-1_0_1B-classes.zip
      jta-1_0_1B-doc.zip
      jdk-1_5_0_06-linux-i586.bin

    • Download, verify and install the java-1.5.0-sun package from Jpackage, again ignore the warnings about users not existing.

      $ wget http://mirrors.sunsite.dk/jpackage/1.6/generic/non-free /SRPMS/java-1.5.0-sun-1.5.0.06-1jpp.nosrc.rpm
      $ rpm -K java-1.5.0-sun-1.5.0.06-1jpp.nosrc.rpm
      $ rpm -Uvh java-1.5.0-sun-1.5.0.06-1jpp.nosrc.rpm

    • Next try building the package to see what is needed from the Sun site.

      $ cd ~/rpms/specs/
      $ rpmbuild -ba java-1.5.0-sun.spec

    • Now you should be ready to install the java-1.5.0-sun-devel-1.5.0.06-1jpp.i586.rpm package that JTA depends on, and any dependencies.

      $ rpm -Uvh ~/rpms/rpms/i586/java-1.5.0-sun-1.5.0.06-1jpp.i586.rpm
      $ rpm -Uvh ~/rpms/rpms/i586/java-1.5.0-sun-devel-1.5.0.06-1jpp.i586.rpm

    • In case error occurred for libXp.so.6, you need to install xorg-x11-deprecated-libs.i386 via yum.
    • Now we can go back to the jta build instructions above and try again; this time there should not be any errors.

      $ cd ~/rpms/specs/
      $ rpmbuild -ba jta.spec

    • And now install jta.

      $ rpm -Uvh ~/rpms/rpms/noarch/jta-1.0.1-0.b.4jpp.noarch.rpm

       

      Continued… Setting up a Development Server (4/4)

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.