Re: Naming a module that extracts subsets of a Linux system

Hello NERDVANA,

maybe Linux::System::Reduce ? or ::Squeeze or ::Extract or ::Minify or ::Export (all these or needed for the wikisyntax ;)? Instead of System you can use the shorter OS or Sys

At the end I'd use Linux::OS::Export infact the main feature seems to be this one, then the minifying part is a corollary to be clarified in the sysnopsis of the documentation.

Sounds interesting anyway :)

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Comment on Re: Naming a module that extracts subsets of a Linux system Select or Download Code

Replies are listed 'Best First'.
Re^2: Naming a module that extracts subsets of a Linux system by NERDVANA (Priest) on Jan 15, 2025 at 11:30 UTC
I like the Export verb. Strong parallels to exporting subs from a module, which is very much like exporting binaries from a system image. Combined with Grandfather's 'Sys' observation, I'm liking `Sys::Export::Linux` or `Sys::Exporter::Linux`.	[reply] [d/l] [select]
Re^3: Naming a module that extracts subsets of a Linux system by cavac (Prior) on Jan 16, 2025 at 08:55 UTC
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', );` [download] 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. PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP Also check out my sisters artwork and my weekly webcomics	[reply] [d/l] [select]