Codex

CPAN::Meta::History::Meta_1_0

Section: User Contributed Perl Documentation (3pm)

Updated: 2014-09-26

Index?action=index Return to Main Contents


NAME

CPAN::Meta::History::Meta_1_0 - Version 1.0 metadata specification for META.yml

PREFACE

This is a historical copy of the version 1.0 specification for META.yml files, copyright by Ken Williams.

Modifications from the original:

Conversion from the original HTML to POD format:

DESCRIPTION

This document describes version 1.0 of the META.yml specification.

The META.yml file describes important properties of contributed Perl distributions such as the ones found on CPAN <http://www.cpan.org>. It is typically created by tools like Module::Build and ExtUtils::MakeMaker.

The fields in the META.yml file are meant to be helpful to people maintaining module collections (like CPAN), for people writing installation tools (like CPAN or CPANPLUS), or just people who want to know some stuff about a distribution before downloading it and starting to install it.

Format

META.yml files are written in the YAML <http://www.yaml.org/> format. The reasons we chose YAML instead of, say, XML or Data::Dumper are discussed in this thread <http:[email protected]/msg00405.html> on the MakeMaker mailing list.

The first line of a META.yml file should be a valid YAML document header <http://www.yaml.org/spec/#.Document> like

Fields

The rest of the META.yml file is one big YAML mapping <http://www.yaml.org/spec/#.-syntax-mapping-Mapping->, whose keys are described here.

name
Example:

The name of the distribution. 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 <http://search.cpan.org/author/GAAS/libwww-perl/> distribution.

:

version
Example:

The version of the distribution to which the META.yml file refers.

:

license
Example:

The license under which this distribution may be used and redistributed. See Module::Build for the list of valid options.

:

distribution_type
Example:
What kind of stuff is contained in this distribution. Most things on CPAN are s (which can also mean a collection of modules), but some things are s.

:

requires
Example:

A YAML mapping <http://www.yaml.org/spec/#.-syntax-mapping-Mapping-> indicating the Perl modules this distribution requires for proper operation. The keys are the module names, and the values are version specifications as described in the Module::Build.

Note: the exact nature of the fancy specifications like ">= 1.2, != 1.5, < 2.0" is subject to change. Advance notice will be given here. The simple specifications like "1.2" will not change in format.

:

recommends
Example:

A YAML mapping <http://www.yaml.org/spec/#.-syntax-mapping-Mapping-> indicating the Perl modules this distribution recommends for enhanced operation.

:

build_requires
Example:

A YAML mapping <http://www.yaml.org/spec/#.-syntax-mapping-Mapping-> indicating the Perl modules required for building and/or testing of this distribution. These dependencies are not required after the module is installed.

:

conflicts
Example:

A YAML mapping <http://www.yaml.org/spec/#.-syntax-mapping-Mapping-> indicating the Perl modules that cannot be installed while this distribution is installed. This is a pretty uncommon situation.

:

dynamic_config
Example:

A boolean flag indicating whether a Build.PL or Makefile.PL (or similar) must be executed, or whether this module can be built, tested and installed solely from consulting its metadata file. The main reason to set this to a true value if 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.

:

generated_by
Example:

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.

:

Related Projects

DOAP
An RDF vocabulary to describe software projects. <http://usefulinc.com/doap>.:

History

March 14, 2003 (Pi day) - created version 1.0 of this document.:
May 8, 2003 - added the ``dynamic_config'' field, which was missing from the initial version.:

Index

NAME

PREFACE

DESCRIPTION

Format

Fields

Related Projects

History