Hmm, for future proofing, it might be interesting to use a base/factory class like Sys::Exporter that then either automatically or manually selects the correct backend like Sys::Exporter::Linux and stuff. That way, it could also support cross-platform builds.
use Sys::Exporter; # Automatic detection/configuration my $exporter = Sys::Exporter->new(); # Prepare a cross-platform export my $exporter = Sys::Exporter->new( OS => 'FreeBSD', rootdir => '/mnt/freebsd', libtools => '/home/nerdvana/crossplatformldd', );
I'm not specific about a name, but putting the OS as the last element of the name instead the first makes sense to me.
In reply to Re^3: Naming a module that extracts subsets of a Linux system
by cavac
in thread Naming a module that extracts subsets of a Linux system
by NERDVANA
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |