- pre/post install paths (dev+test/prod)
- system paths configured once when Sys::Path is installed
- "Debian way" of handling configuration files
- automatic all files copying
- creating of empty folders (for state, log, etc. files)
The main reason for existence is to install files (configuration, templates, data files, ...) where FHS recommends and also to know where to put temporary files (like state, lock, cache, ...).
There are couple of stages that the CPAN distribution is going through. Development, smoke testing, pre install and install stage. In all of those it is good to know where our files are. :-P Before the final install the files are always inside the distribution folder, only after install the files are in the system folders. There for the Module::Build::SysPath requires a special module YouModuleName::SPc that gets overwritten with values from Sys::Path once installed.
There are, as always, couple of other ways how to store and work with non-perl modules files. Here are some that I'm aware of:
- storing data inside __DATA__ in .pm file
- storing files in the same folder as .pm files
- storing files in auto/ - File::ShareDir
- hardcoded system folders
- use Sys::Path paths directly
Everyone can choose.