in reply to How to distribute complex perl based app

Add a module to CPAN that wraps up all the MICR stuff that you want to provide. Have it use various other helper modules that are bundled up in the same distribution:

xxx::MICR
xxx::MICR::Helper1
xxx::MICR::Helper2
xxx::MICR::Helper3

[download]

and provide the script to drive it in a Samples directory which may include other related stuff.

CPAN does have a scripts repository, but the less said about that the better - it's very much a fourth class citizen compared to the module repository.

Perl reduces RSI - it saves typing

Replies are listed 'Best First'.
Re^2: How to distribute complex perl based app
by leocharre (Priest) on Oct 07, 2008 at 01:15 UTC

    GrandFather, this is useful for set of perl modules/ a distro, with tests, etc.. the main focus are the modules and the functionality they provide.
    Your suggestion in useful. With something like CGI::Application, this kind of thing is useful.

    It makes sense and I've seen that done in distros.

    I think your explanation falls really short of addressing my concerns- however. Maybe I didn't do a good job in explaining myself.

    The scripts, helper data, config files, whatever.. these are not examples, these would be a good chunk of functional stuff. It's stuff that will be available system wide to all users, etc. They're production scripts/material.

    And a lot of it is not .pm material.

    The stuff really is more of a project- but the modules allow other programs/scripts/uis, to work with the same stuff.

    Maybe I should separate these things further.

[reply]

      Actually I really did mean to imply that you provide all the ancillary material in conjunction with a main module. It would be nice if the CPAN scripts repository were organised and maintained in the same fashion as the modules repository - that would be the ideal answer. But it's not, and failing that I think that a good solution is to provide your complete project keyed to a primary module.

      I don't think it matters that the scripts etc. are not examples. If they are useful to other people then CPAN is a good way to make them available and it is likely that people looking for the stuff you are working with will find it on CPAN by way of a well named module.

      Don't separate them further. Tie them all together into a single distribution.

      Perl reduces RSI - it saves typing
[reply]
        This is pretty much what I was doing. It's helpful to hear somebody else say suggest that! Thank you, this helps.
[reply]

In Section Seekers of Perl Wisdom