This document describes how to port Krang to a new platform. You'll
need to port Krang if you want to run Krang on a platform which isn't
supported. See the installation instructions
for the list of supported platforms.

If Krang failed to build, or test failures reveal that something
wasn't built right you need to make changes to your Platform.pm. One
possibility is to choose a base class from among the other supported
platforms. For example, when porting Krang to Mandrake Linux it might
be reasonable to start with this:

use base 'Redhat9::Platform';

In place of this line:

use base 'Krang::Platform';

Now your build process will mimic that of another platform.

Failing that, you'll need to start overriding methods in
Krang::Platform to adjust Krang's build process. For example, let's
say Apache::DBI won't build on your platform without /usr/local/bin
first in the path. You could add an overridden build_perl_module() to
your Platform.pm:

Each platform is allowed to have its own README file. This file is
copied into binary distributions for that platform. For an example,
take a look at platform/Redhat7_3/README.Redhat7_3. This file is a
good place to describe any platform-specific setup needed to get Krang
working.

When you're done porting Krang, commit your work to CVS or send a
patch to the Krang developer mailing-list. Remember to add the
platform to the supported platform list in docs/ops_install.pod.