| CPAN::Meta::History::Meta_1_4 - Version 1.4 metadata specification for META.yml |
CPAN::Meta::History::Meta_1_4 - Version 1.4 metadata specification for META.yml
This is a historical copy of the version 1.4 specification for META.yml files, copyright by Ken Williams and licensed under the same terms as Perl itself.
Modifications from the original:
--- #YAML:1.0 name: Module-Build abstract: Build and install Perl modules version: 0.20 author: - Ken Williams <kwilliams@cpan.org> 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 resources: license: http://dev.perl.org/licenses/ meta-spec: version: 1.4 url: http://module-build.sourceforge.net/META-spec-v1.3.html generated_by: Module::Build version 0.20
This document describes version 1.4 of the META.yml specification.
The META.yml 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 META.yml 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.
Note: The latest stable version of this specification can always be found at http://module-build.sourceforge.net/META-spec-current.html, and the latest development version (which may include things that won't make it into the stable version) can always be found at http://module-build.sourceforge.net/META-spec-blead.html.
META.yml files are written in the YAML format (see http://www.yaml.org/).
See the following links to learn why we chose YAML instead of, say, XML or Data::Dumper:
Class-Container, libwww-perl, or DBI.
Class::Container,
LWP::Simple, or DBD::File.
The first line of a META.yml file should be a valid YAML document
header like "--- #YAML:1.0".
The rest of the META.yml file is one big YAML mapping whose keys are described here.
Example:
meta-spec: version: 1.4 url: http://module-build.sourceforge.net/META-spec-v1.3.html
(Spec 1.1) [required] {URL} This field indicates the location of the version of the META.yml specification used.
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 http://search.cpan.org/dist/libwww-perl/).
Example:
version: 0.20
(Spec 1.0) [required] {version} The version of the distribution to which the META.yml file refers.
Example:
abstract: Build and install Perl modules.
(Spec 1.1) [required] {string} A short description of the purpose of the distribution.
Example:
author:
- Ken Williams <kwilliams@cpan.org>
(Spec 1.1) [required] {list of strings} A YAML sequence indicating the author(s) of the
distribution. The preferred form is author-name <email-address>.
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:
Example:
distribution_type: module
(Spec 1.0) [optional] {string} What kind of stuff is contained in this
distribution. Most things on CPAN are modules (which can also mean
a collection of modules), but some things are scripts.
Unfortunately this field is basically meaningless, since many distributions are hybrids of several kinds of things, or some new thing, or subjectively different in focus depending on who's using them. Tools like Module::Build and MakeMaker will likely stop generating this field.
Example:
requires:
Data::Dumper: 0
File::Find: 1.03
(Spec 1.0) [optional] {map} A YAML mapping indicating the Perl prerequisites this distribution requires for proper operation. The keys are the names of the prerequisites (module names or 'perl'), and the values are version specifications as described in VERSION SPECIFICATIONS.
Example:
recommends:
Data::Dumper: 0
File::Find: 1.03
(Spec 1.0) [optional] {map} A YAML mapping indicating the Perl prerequisites this distribution recommends for enhanced operation. The keys are the names of the prerequisites (module names or 'perl'), and the values are version specifications as described in VERSION SPECIFICATIONS.
ALTERNATIVE: It may be desirable to present to the user which features depend on which modules so they can make an informed decision about which recommended modules to install.
Example:
optional_features:
foo:
description: Provides the ability to blah.
requires:
Data::Dumper: 0
File::Find: 1.03
(Spec 1.1) [optional] {map} A YAML mapping of names for optional features which are made available when its requirements are met. For each feature a description is provided along with any of requires, build_requires, and conflicts, which have the same meaning in this subcontext as described elsewhere in this document.
Example:
build_requires:
Data::Dumper: 0
File::Find: 1.03
(Spec 1.0) [optional] {map} A YAML mapping indicating the Perl prerequisites required for building and/or testing of this distribution. The keys are the names of the prerequisites (module names or 'perl'), and the values are version specifications as described in VERSION SPECIFICATIONS. These dependencies are not required after the distribution is installed.
Example:
configure_requires:
Module::Build: 0.2809
Data::Dumper: 0
File::Find: 1.03
(Spec 1.4) [optional] {map} A YAML mapping indicating the Perl prerequisites required before configuring this distribution. The keys are the names of the prerequisites (module names or 'perl'), and the values are version specifications as described in VERSION SPECIFICATIONS. These dependencies are not required after the distribution is installed.
Example:
conflicts:
Data::Dumper: 0
File::Find: 1.03
(Spec 1.0) [optional] {map} A YAML mapping indicating any items that
cannot be installed while this distribution is installed. This is a
pretty uncommon situation. The keys for conflicts are the item
names (module names or 'perl'), and the values are version
specifications as described in VERSION SPECIFICATIONS.
Example:
dynamic_config: 0
(Spec 1.0) [optional] {boolean} A boolean flag indicating whether a Build.PL or Makefile.PL (or similar) must be executed when building this distribution, or whether it can be built, tested and installed solely from consulting its metadata file. The main reason to set this to a true value is that your module performs some dynamic configuration (asking questions, sensing the environment, etc.) as part of its build/install process.
Currently Module::Build doesn't actually do anything with this flag - it's probably going to be up to higher-level tools like CPAN to do something useful with it. It can potentially bring lots of security, packaging, and convenience improvements.
If this field is omitted, it defaults to 1 (true).
(Deprecated) (Spec 1.0) [optional] {map} This field has been renamed to no_index. See below.
Example:
provides:
Foo::Bar:
file: lib/Foo/Bar.pm
version: 0.27_02
Foo::Bar::Blah:
file: lib/Foo/Bar/Blah.pm
Foo::Bar::Baz:
file: lib/Foo/Bar/Baz.pm
version: 0.3
(Spec 1.1) [optional] {map} A YAML mapping that describes all packages provided by this distribution. This information can be (and, in some cases, is) used by distribution and automation mechanisms like PAUSE, CPAN, and search.cpan.org to build indexes saying in which distribution various packages can be found.
When using tools like the Module::Build manpage that can generate the
provides mapping for your distribution automatically, make sure you
examine what it generates to make sure it makes sense - indexers will
usually trust the provides field if it's present, rather than
scanning through the distribution files themselves to figure out
packages and versions. This is a good thing, because it means you can
use the provides field to tell the indexers precisely what you want
indexed about your distribution, rather than relying on them to
essentially guess what you want indexed.
Example:
no_index:
file:
- My/Module.pm
directory:
- My/Private
package:
- My::Module::Stuff
namespace:
- My::Module::Stuff
(Spec 1.1) [optional] {map} A YAML mapping that describes any files,
directories, packages, and namespaces that are private
(i.e. implementation artifacts) that are not of interest to searching
and indexing tools. This is useful when no provides field is
present.
For example, http://search.cpan.org/ excludes items listed in no_index
when searching for POD, meaning files in these directories will not
converted to HTML and made public - which is useful if you have
example or test PODs that you don't want the search engine to go
through.
(Spec 1.1) [optional] Exclude any listed file(s).
(Spec 1.1) [optional] Exclude anything below the listed directory(ies).
[Note: previous editions of the spec had dir instead of
directory, but I think MakeMaker and various users started using
directory, so in deference we switched to that.]
(Spec 1.1) [optional] Exclude the listed package(s).
(Spec 1.1) [optional] Excludes anything below the listed namespace(s),
but not the listed namespace(s) its self.
Example:
keywords:
- make
- build
- install
(Spec 1.1) [optional] {list} A sequence of keywords/phrases that describe this distribution.
Example:
resources:
license: http://dev.perl.org/licenses/
homepage: http://sourceforge.net/projects/module-build
bugtracker: http://rt.cpan.org/NoAuth/Bugs.html?Dist=Module-Build
repository: http://sourceforge.net/cvs/?group_id=45731
MailingList: http://lists.sourceforge.net/lists/listinfo/module-build-general
(Spec 1.1) [optional] {map} A mapping of any URL resources related to
this distribution. All-lower-case keys, such as homepage,
license, and bugtracker, are reserved by this specification, as
they have ``official'' meanings defined here in this specification. If
you'd like to add your own ``special'' entries (like the ``MailingList''
entry above), use at least one upper-case letter.
The current set of official keys is:
Example:
generated_by: Module::Build version 0.20
(Spec 1.0) [required] {string} Indicates the tool that was used to create this META.yml file. It's good form to include both the name of the tool and its version, but this field is essentially opaque, at least for the moment. If META.yml was generated by hand, it is suggested that the author be specified here.
[Note: My meta_stats.pl script which I use to gather statistics regarding META.yml usage prefers the form listed above, i.e. it splits on /\s+version\s+/ taking the first field as the name of the tool that generated the file and the second field as version of that tool. RWS]
Some fields require a version specification (ex. requires, recommends, build_requires, etc.) to indicate the particular version(s) of some other module that may be required as a prerequisite. This section details the version specification formats that are currently supported.
The simplest format for a version specification is just the version
number itself, e.g. 2.4. This means that at least version 2.4
must be present. To indicate that any version of a prerequisite is
okay, even if the prerequisite doesn't define a version at all, use
the version 0.
You may also use the operators < (less than), <= (less than or
equal), > (greater than), >= (greater than or equal), ==
(equal), and != (not equal). For example, the specification <
2.0 means that any version of the prerequisite less than 2.0 is
suitable.
For more complicated situations, version specifications may be AND-ed
together using commas. The specification >= 1.2, != 1.5, <
2.0 indicates a version that must be at least 1.2, less than
2.0, and not equal to 1.5.
CPAN
the ExtUtils::MakeMaker manpage
XML
YAML
configure, requires_packages,
requires_os, excludes_os, and no_index fields.
Bumped version.
generation, authored_by fields.
Add alternative proposal to the recommends field.
Add proposal for a requires_build_tools field.
auto_regenerate field.
index field as a compliment to no_index
Add keywords field as a means to aid searching distributions.
Add TERMINOLOGY section to explain certain terms that may be
ambiguous.
authored_by to author, since that's always been what
it's actually called in actual META.yml files.
Added the ``=='' operator to the list of supported version-checking
operators.
Noted that the distribution_type field is basically meaningless,
and shouldn't really be used.
Clarified dynamic_config a bit.
CPAN::META::Specification, since that implies a
module that doesn't actually exist.
| CPAN::Meta::History::Meta_1_4 - Version 1.4 metadata specification for META.yml |