The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

This is an adoptable module. It has no maintainer and no support.

The Pod::SpeakIt::MacSpeech module

This is the README for the Pod::SpeakIt::MacSpeech Perl module. You're probably looking at this because you don't know where else to find what you're looking for. Read this once and you might never have to read one again for any Perl module.

Documentation

To read about Pod::SpeakIt::MacSpeech, look at the embedded documentation in the module itself. Inside the distribution, you can format it with perldoc:

        % perldoc lib/Pod/SpeakIt/MacSpeech.pm

If you have already installed the module, you can specify the module name instead of the file location:

        % perldoc Pod::SpeakIt::MacSpeech

You can read the documentation and inspect the meta data on one of the CPAN web interfaces, such as CPAN Search or MetaCPAN:

The standard module documentation has example uses in the SYNOPSIS section, but you can also look in the examples/ directory (if it's there), or look at the test files in t/.

Installation

You can install this module with a CPAN client, which will resolve and install the dependencies:

        % cpan Pod::SpeakIt::MacSpeech
        % cpanm Pod::SpeakIt::MacSpeech

You can also install directly from the distribution directory, which will also install the dependencies:

        % cpan .
        % cpanm .

You could install just this module manually:

        % perl Makefile.PL
        % make
        % make test
        % make install

You probably don't want to do that unless you're fiddling with the module and only want to run the tests without installing anything.

Source location

The meta data, such as the source repository and bug tracker, is in Makefile.PL or the META.* files it creates. You can find that on those CPAN web interfaces, but you can also look at files directly in the source repository:

Getting help

This is an abandoned module. It's looking for a maintainer and that might be you. Other than that you are on your own.

You should have received a LICENSE file, but the license is also noted in the module files. About the only thing you can't do is pretend that you wrote code that you didn't.

Good luck!

Enjoy,

brian d foy, bdfoy@cpan.org