A different set of defaults for each platform

I intend to create a subdirectory with defaults for different platforms, and have configure pull in the right set according to what it detects you are running.

Rationale

The settings should default very differently for different set ups. For example:

• Everything is dependent on platform (Unix, Linux, Windows)
• On Windows you could be running apache or IIS
• On Windows Apache you could have an Apache install or a bundled/integrated mod_perl one supplied with IndigoPerl
• You could be running unix-emulation CygWin or native GnuWin32 for the bin utils

Rather than have the admin sit there and figure these out, I propose detect the configuration and if it is a known config, select the right profile to load as defaults.

Of course, if the admin has a LocalSite.cfg then they have already configured/customised so load that instead.

Implications

We need to create a directory for the profiles

e.g. either

• defaults/
  • platform._webserver_._utils_.default.cfg
  • Linux.Apache.Unix.default.cfg
  • Windows.Apache.ActiveStatePerl.CygWin.default.cfg
  • Windows.Apache.ActiveStatePerl.GnuWin32.default.cfg
  • IndigoPerlApache.IndigoPerl.CygWin.default.cfg
  • IndigoPerlApache.IndigoPerl.GnuWin32.default.cfg
  • Windows.IIS.ActiveStatePerl.CygWin.default.cfg
  • Windows.IIS.ActiveStatePerl.GnuWin32.default.cfg

• platform/
  • Linux /
  • Windows /
    • ActiveStatePerl.CygWin.default.cfg
    • ActiveStatePerl.GnuWin32.default.cfg
    • IndigoPerl.CygWin.default.cfg
    • IndigoPerl.GnuWin32.default.cfg
    • ActiveStatePerl.CygWin.default.cfg
    • ActiveStatePerl.GnuWin32.default.cfg

The advantage with the latter config is that we could check in binaries for those platforms

We could further split out Linux/Unix platforms.

Maybe I just want a TWikiFor IndigoPerl distro.

-- MartinCleaver - 04 Aug 2005