Just keep adding .pm files to the lib directory of your skeleton build and .pl files to the script directory. The build process is smart enough to scan the lib directory and file all the modules stored there. They will be automatically added to your MANIFEST (the list of files that will get bundled into the tarball), when you run build manifest.
If you haven't seen it already, you might also want to check out, RFC: How to Release Modules on CPAN in 2011. It begins with a section that demystifies the contents of the project work area.
If you did check it out already, and asked this question because that essay wasn't clear, let me know (you can private message me) and I'll update the RFC - I think it needs a section anyway on tools for building the skeleton directory.
In reply to Re: How to create a distribution package with multiple class files
by ELISHEVA
in thread How to create a distribution package with multiple class files
by rmcgowan
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |