_   _ _
  | \ | | |_ ___  _ __
  |  \| | __/ _ \| '_ \
  | |\  | || (_) | |_) |
  |_| \_|\__\___/| .__/
                 |_|

             Network Top

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  HACKING
  =======

  Those who want to be always at the bleeding edge or even want to
  hack on the ntop sources can fetch the latest ntop source tree via
  rsync from a copy of the master repository. This copy is
  updated in regular intervals from the authors original CVS repository
  and can be used for easily keeping local modifications in a checked
  out tree while the master version is updated over time.

  This is the best way to get fresh ntop code. In fact, ntop source
  code is periodically cut to build a snapshot. Using rsync instead
  you can access pre-snapshot code as it is written, modified, improved.
  If you want to get the freshest ntop code first install the rsync
  package and then execute the following command:

  deri@> rsync -arvz jake.unipi.it::ntop-source-snapshot .


  If you want to hack on ntop, it will make you life easier
  to have the following packages installed:

  - GNU libtool 1.3.3 (ftp://ftp.gnu.org/pub/gnu/libtool-1.3.3.tar.gz)
  - GNU m4 1.4 (ftp://ftp.gnu.org/pub/gnu/m4-1.4.tar.gz)
  - GNU automake 1.4 (ftp://ftp.gnu.org/pub/gnu/automake-1.4.tar.gz)
  - GNU autoconf 2.13 (ftp://ftp.gnu.org/pub/gnu/autoconf-2.13.tar.gz)

  These should be available by ftp from ftp.gnu.org or any of the
  fine GNU mirrors. Beta software can be found at ftp://alpha.gnu.org.


  This means that you will need the usual GNU tools to build these in
  maintainer mode from the development tree. You can basically type

  ./autogen.sh

  [a simple shell script that basically does the following for you:

    libtoolize --copy --force
    aclocal
    autoheader
    automake --add-missing --gnu
    autoconf
    configure

  ]


  have fun!

  /luca && /rocco