=for :stopwords MailingList RWS subcontext =head1 NAME CPAN::Meta::History::Meta_1_2 - Version 1.2 metadata specification for META.yml =head1 PREFACE This is a historical copy of the version 1.2 specification for F files, copyright by Ken Williams and licensed under the same terms as Perl itself. Modifications from the original: =over =item * Various spelling corrections =item * Include list of valid licenses from L 0.2611 rather than linking to the module. =back =head1 SYNOPSIS --- #YAML:1.0 name: Module-Build abstract: Build and install Perl modules version: 0.20 author: - Ken Williams license: perl distribution_type: module requires: Config: 0 Cwd: 0 Data::Dumper: 0 ExtUtils::Install: 0 File::Basename: 0 File::Compare: 0 File::Copy: 0 File::Find: 0 File::Path: 0 File::Spec: 0 IO::File: 0 perl: 5.005_03 recommends: Archive::Tar: 1.00 ExtUtils::Install: 0.3 ExtUtils::ParseXS: 2.02 Pod::Text: 0 YAML: 0.35 build_requires: Test: 0 urls: license: http://dev.perl.org/licenses/ meta-spec: version: 1.2 url: http://module-build.sourceforge.net/META-spec-v1.2.html generated_by: Module::Build version 0.20 =head1 DESCRIPTION This document describes version 1.2 of the F specification. The F file describes important properties of contributed Perl distributions such as the ones found on CPAN. It is typically created by tools like Module::Build, Module::Install, and ExtUtils::MakeMaker. The fields in the F file are meant to be helpful for people maintaining module collections (like CPAN), for people writing installation tools (like CPAN.pm or CPANPLUS), or just for people who want to know some stuff about a distribution before downloading it and starting to install it. I, and the latest development version (which may include things that won't make it into the stable version can always be found at L.> =head1 FORMAT F files are written in the YAML format (see L). See the following links to learn why we chose YAML instead of, say, XML or Data::Dumper: =over 4 =item * Module::Build design plans L =item * Not keen on YAML L =item * META Concerns L =back =head1 TERMINOLOGY =over 4 =item distribution This is the primary object described by the F specification. In the context of this document it usually refers to a collection of modules, scripts, and/or documents that are distributed for other developers to use. =item module This refers to a reusable library of code typically contained in a single file. Currently, we primarily talk of perl modules, but this specification should be open enough to apply to other languages as well (ex. python, ruby). =back =head1 VERSION SPECIFICATIONS Some fields require a version specification (ex. L<"requires">, L<"recommends">, L<"build_requires">, etc.). This section details the version specifications that are currently supported. If a single version is listed, then that version is considered to be the minimum version supported. If 0 is given as the version number, then any version is supported. Additionally, for more complicated requirements, the specification supports a list of versions, each of which may be optionally preceded by a relational operator. Supported operators include E (less than), E= (less than or equal), E (greater than), E= (greater than or equal), == (equal), and != (not equal). If a list is given then it is evaluated from left to right so that any specifications in the list that conflict with a previous specification are overridden by the later. Examples: >= 1.2, != 1.5, < 2.0 Any version from version 1.2 onward, except version 1.5, that also precedes version 2.0. =head1 HEADER The first line of a F file should be a valid YAML document header like C<"--- #YAML:1.0">. =head1 FIELDS The rest of the F file is one big YAML mapping whose keys are described here. =head2 meta-spec Example: meta-spec: version: 1.2 url: http://module-build.sourceforge.net/META-spec-v1.2.html (Spec 1.1) [required] {URL} This field indicates the location of the version of the META.yml specification used. =head2 name Example: name: Module-Build (Spec 1.0) [required] {string} The name of the distribution which is often created by taking the "main module" in the distribution and changing "::" to "-". Sometimes it's completely different, however, as in the case of the libwww-perl distribution (see L). =head2 version Example: version: 0.20 (Spec 1.0) [required] {version} The version of the distribution to which the F file refers. =head2 abstract Example: abstract: Build and install Perl modules. (Spec 1.1) [required] {string} A short description of the purpose of the distribution. =head2 author Example: author: - Ken Williams (Spec 1.1) [required] {list of strings} A YAML sequence indicating the author(s) of the distribution. The preferred form is author-name . =head2 license Example: license: perl (Spec 1.0) [required] {string} The license under which this distribution may be used and redistributed. Must be one of the following licenses: =over 4 =item perl The distribution may be copied and redistributed under the same terms as perl itself (this is by far the most common licensing option for modules on CPAN). This is a dual license, in which the user may choose between either the GPL or the Artistic license. =item gpl The distribution is distributed under the terms of the Gnu General Public License (L). =item lgpl The distribution is distributed under the terms of the Gnu Lesser General Public License (L). =item artistic The distribution is licensed under the Artistic License, as specified by the Artistic file in the standard perl distribution. =item bsd The distribution is licensed under the BSD License (L). =item open_source The distribution is licensed under some other Open Source Initiative-approved license listed at L. =item unrestricted The distribution is licensed under a license that is B approved by L but that allows distribution without restrictions. =item restrictive The distribution may not be redistributed without special permission from the author and/or copyright holder. =back =head2 distribution_type Example: distribution_type: module (Spec 1.0) [optional] {string} What kind of stuff is contained in this distribution. Most things on CPAN are Cs (which can also mean a collection of modules), but some things are C