{
    "mode": "perldoc",
    "parameter": "CPAN::Meta::History::Meta_1_0",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/perldoc/CPAN%3A%3AMeta%3A%3AHistory%3A%3AMeta_1_0/json",
    "generated": "2026-06-03T10:13:09Z",
    "sections": {
        "NAME": {
            "content": "CPAN::Meta::History::Meta10 - Version 1.0 metadata specification for META.yml\n",
            "subsections": []
        },
        "PREFACE": {
            "content": "This is a historical copy of the version 1.0 specification for META.yml files, copyright by Ken\nWilliams and licensed under the same terms as Perl itself.\n\nModifications from the original:\n\n*   Conversion from the original HTML to POD format\n\n*   Include list of valid licenses from Module::Build 0.17 rather than linking to the module,\nwith minor updates to text and links to reflect versions at the time of publication.\n\n*   Fixed some dead links to point to active resources.\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "This document describes version 1.0 of the META.yml specification.\n\nThe META.yml file describes important properties of contributed Perl distributions such as the\nones found on CPAN <http://www.cpan.org>. It is typically created by tools like Module::Build\nand ExtUtils::MakeMaker.\n\nThe fields in the META.yml file are meant to be helpful to people maintaining module collections\n(like CPAN), for people writing installation tools (like CPAN or CPANPLUS), or just people who\nwant to know some stuff about a distribution before downloading it and starting to install it.\n",
            "subsections": []
        },
        "Format": {
            "content": "META.yml files are written in the YAML <http://www.yaml.org/> format. The reasons we chose YAML\ninstead of, say, XML or Data::Dumper are discussed in this thread\n<http://www.nntp.perl.org/group/perl.makemaker/2002/04/msg406.html> on the MakeMaker mailing\nlist.\n\nThe first line of a META.yml file should be a valid YAML document header\n<http://yaml.org/spec/history/2002-10-31.html#syntax-document> like \"--- #YAML:1.0\"\n",
            "subsections": []
        },
        "Fields": {
            "content": "The rest of the META.yml file is one big YAML mapping\n<http://yaml.org/spec/history/2002-10-31.html#syntax-mapping>, whose keys are described here.\n\nname\nExample: \"Module-Build\"\n\nThe name of the distribution. Often created by taking the \"main module\" in the distribution\nand changing \"::\" to \"-\". Sometimes it's completely different, however, as in the case of\nthe libwww-perl <http://search.cpan.org/author/GAAS/libwww-perl/> distribution.\n\nversion\nExample: 0.16\n\nThe version of the distribution to which the META.yml file refers.\n\nlicense\nExample: \"perl\"\n\nThe license under which this distribution may be used and redistributed.\n\nMust be one of the following licenses:\n\nperl\nThe distribution may be copied and redistributed under the same terms as perl itself\n(this is by far the most common licensing option for modules on CPAN). This is a dual\nlicense, in which the user may choose between either the GPL version 1 or the Artistic\nversion 1 license.\n\ngpl The distribution is distributed under the terms of the GNU General Public License\nversion 2 (<http://opensource.org/licenses/GPL-2.0>).\n\nlgpl\nThe distribution is distributed under the terms of the GNU Lesser General Public License\nversion 2 (<http://opensource.org/licenses/LGPL-2.1>).\n\nartistic\nThe distribution is licensed under the Artistic License version 1, as specified by the\nArtistic file in the standard perl distribution\n(<http://opensource.org/licenses/Artistic-Perl-1.0>).\n\nbsd The distribution is licensed under the BSD 3-Clause License\n(<http://opensource.org/licenses/BSD-3-Clause>).\n\nopensource\nThe distribution is licensed under some other Open Source Initiative-approved license\nlisted at <http://www.opensource.org/licenses/>.\n\nunrestricted\nThe distribution is licensed under a license that is not approved by www.opensource.org\n<http://www.opensource.org/> but that allows distribution without restrictions.\n\nrestrictive\nThe distribution may not be redistributed without special permission from the author\nand/or copyright holder.\n\ndistributiontype\nExample: \"module\"\n\nWhat kind of stuff is contained in this distribution. Most things on CPAN are \"module\"s\n(which can also mean a collection of modules), but some things are \"script\"s.\n\nrequires\nExample:\n\nData::Dumper: 0\nFile::Find: 1.03\n\nA YAML mapping <http://yaml.org/spec/history/2002-10-31.html#syntax-mapping> indicating the\nPerl modules this distribution requires for proper operation. The keys are the module names,\nand the values are version specifications as described in the documentation for\nModule::Build's \"requires\" parameter.\n\n*Note: the exact nature of the fancy specifications like \">= 1.2, != 1.5, < 2.0\" is subject\nto change. Advance notice will be given here. The simple specifications like \"1.2\" will not\nchange in format.*\n\nrecommends\nExample:\n\nData::Dumper: 0\nFile::Find: 1.03\n\nA YAML mapping <http://yaml.org/spec/history/2002-10-31.html#syntax-mapping> indicating the\nPerl modules this distribution recommends for enhanced operation.\n\nbuildrequires\nExample:\n\nData::Dumper: 0\nFile::Find: 1.03\n\nA YAML mapping <http://yaml.org/spec/history/2002-10-31.html#syntax-mapping> indicating the\nPerl modules required for building and/or testing of this distribution. These dependencies\nare not required after the module is installed.\n\nconflicts\nExample:\n\nData::Dumper: 0\nFile::Find: 1.03\n\nA YAML mapping <http://yaml.org/spec/history/2002-10-31.html#syntax-mapping> indicating the\nPerl modules that cannot be installed while this distribution is installed. This is a pretty\nuncommon situation.\n\ndynamicconfig\nExample: 0\n\nA boolean flag indicating whether a Build.PL or Makefile.PL (or similar) must be executed,\nor whether this module can be built, tested and installed solely from consulting its\nmetadata file. The main reason to set this to a true value if that your module performs some\ndynamic configuration (asking questions, sensing the environment, etc.) as part of its\nbuild/install process.\n\nCurrently Module::Build doesn't actually do anything with this flag - it's probably going to\nbe up to higher-level tools like CPAN.pm to do something useful with it. It can potentially\nbring lots of security, packaging, and convenience improvements.\n\ngeneratedby\nExample: \"Module::Build version 0.16\"\n\nIndicates the tool that was used to create this META.yml file. It's good form to include\nboth the name of the tool and its version, but this field is essentially opaque, at least\nfor the moment.\n",
            "subsections": []
        },
        "Related Projects": {
            "content": "DOAP\nAn RDF vocabulary to describe software projects. <http://usefulinc.com/doap>.\n",
            "subsections": []
        },
        "History": {
            "content": "*   March 14, 2003 (Pi day) - created version 1.0 of this document.\n\n*   May 8, 2003 - added the \"dynamicconfig\" field, which was missing from the initial version.\n",
            "subsections": []
        }
    },
    "summary": "CPAN::Meta::History::Meta10 - Version 1.0 metadata specification for META.yml",
    "flags": [],
    "examples": [],
    "see_also": []
}