On 09/12/2018 08:02 AM, David Cantrell wrote:
On Fri, Sep 07, 2018 at 01:18:28PM -0700, Karen Etheridge wrote:
On Fri, Sep 7, 2018 at 12:59 PM, Diab Jerius <djer...@cpan.org> wrote:
I see two options:
1. Create an empty package which gets indexed; or
2. Add an entry to the "provides" field mapping the distribution's
"package" name (App::pltvectors) to the script file.
Option 1 is correct -- create an App::pltvectors module which is indexable
and installable. However, it doesn't need to be an empty package -- not
only can it contain documentation for your script, but it could also
contain most of the functionality from the script as well, turning the
script into a wrapper that calls the module. That also allows others to
make use of the code in their own scripts.
It would also make it easier to write tests for your code - you'd be
able to load the module and call individual methods in it and check
their return values and side-effects instead of having to shell out to
the script a zillion times.
+1 to that as well!
