|How do I contribute scripts to CPAN?
CPAN has a scripts repository at http://www.cpan.org/scripts/ and http://www.cpan.org/scripts/submitting.html will instruct you on how to go about contributing your scripts.
How to submit a script to CPAN
- Get a PAUSE ID;
this is required to upload files to CPAN.
- Create your script:
- It must be a single file, not compressed or archived. This
constraint will be relaxed in the future.
- Insert the appropriate POD sections, as outlined below.
(If you don't know what POD is, consult the `perlpod'
manpage). There is one mandatory section, and several
- The mandatory POD section is `SCRIPT CATEGORIES'. The
existence of this section informs PAUSE that this is a
script. The contents of this section indicate where the
script should be presented in the
categorized hierarchy; currently, you may specify up to
three categories for your script.
- The optional POD section `PREREQUISITES' contains a list
of modules which this script requires in order to
- The optional POD section `COREQUISITES' contains a list of
modules which this script would benefit from having
available, but which are not required.
- The optional POD section `OSNAMES' contains a list of
operating systems (as given in Perl's $^O variable) under
which this script will run.
- The contents of the optional POD section `README' will be
automatically extracted and displayed.
- You may wish to check your script's format against
- Upload your script to PAUSE.
- New script categories are not automatically created. If you
stipulate a SCRIPT CATEGORIES entry that does not exist, it will
be silently ignored. New categories are created via discussion on
the scripts mailing list.
Please join the list before posting to it, by sending an empty
Contents of POD sections
The data in the POD sections, outlined above, must be presented in a
machine-readable format. There are two ways to present the data:
The example script
contains COREQUISITES, OSNAMES, and SCRIPT CATEGORIES sections in the
first format, and a PREREQUISITES section in the second format.
- Unadorned, one item per line.
- Embedded in descriptive text, with the data appearing between
C< and >.
Improving the process
The scripts repository is still being refined. Please report and problems
or suggestions to
Last modified: Fri May 10 01:32:56 CEST 2002
|MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"|
|I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).|
|** The third rule of perl club is a statement of fact: pod is sexy.|
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||