WHAT?
Dist-Zilla-PluginBundle-Author-VDB (or just @Author::VDB) is a Dist-Zilla plugin
bundle used by VDB.
WHY?
I have published few distributions on CPAN. Every distribution have dist.ini
file. All the dist.ini files are very similar. Maintaining multiple very similar
dist.ini files is boring. Plugin bundle solves the problem.
NAMING
perl-Dist-Zilla-PluginBundle-Author-VDB is official software name.
However, in Perl world prefix "perl-" is redundant and not used. For example, on
meta::cpan this software is named as
Dist-Zilla-PluginBundle-Author-VDB. In the rest of the documentation shortened
name Dist-Zilla-PluginBundle-Author-VDB is used as synonym for full name
perl-Dist-Zilla-PluginBundle-Author-VDB. We are in the Perl world, aren't we?
You may notice that name may be spelled with dashes
(Dist-Zilla-PluginBundle-Author-VDB) or with double colons
(Dist::Zilla::PluginBundle::Author::VDB). Strictly speaking, there is
difference: the first one is software name, while the second is name of Perl
package, but often these names are interchangeable especially if software
consists of single package.
FORMS
You may face Dist-Zilla-PluginBundle-Author-VDB in *source* or *distribution*
forms.
If you are going to vDB's plugin bundle, you will likely be interested in
*using* Dist-Zilla-PluginBundle-Author-VDB *distribution*. If you are going to
*develop* (or *hack*) the Dist-Zilla-PluginBundle-Author-VDB itself, you will
likely need the *source*, not distribution.
Since Perl is an interpreting language, modules in the distribution *look* like
sources. Actually, they are Perl source files. But they are not *actual*
sources, because they are *built* (preprocessed or generated) by Dist-Zilla.
How to distinguish source and distribution:
* Source may contain Mercurial files and directories .hgignore, .hgtags, .hg/,
while distribution should not.
* Source should contain dist.ini file, while distribution may not.
* Source should *not* contain xt/ directory, while distribution should.
* Name of source directory does *not* include version (e. g.
Dist-Zilla-PluginBundle-Author-VDB), while name of distribution does (e. g.
Dist-Zilla-PluginBundle-Author-VDB-v0.7.1).
SOURCE
Dist-Zilla-PluginBundle-Author-VDB source is in Mercurial repository hosted on
fedorapeople.org. To clone the entire repository:
$ hg clone https://vandebugger.fedorapeople.org/hg/perl-Dist-Zilla-PluginBundle-Author-VDB
Source Files
Dist-Zilla-PluginBundle-Author-VDB source files usually include a comment near
the top of the file:
This file is part of perl-Dist-Zilla-PluginBundle-Author-VDB.
Not all source files are included into distribution. Some source files are used
at distribution build time only, and not required for installation.
DISTRIBUTION
Dist-Zilla-PluginBundle-Author-VDB distributions are published on CPAN
.
Generated Files
Distribution may contain files preprocessed or generated by Dist-Zilla and its
plugins. Some generated files are made from Dist-Zilla-PluginBundle-Author-VDB
source, but some are generated from third-party templates. Files generated from
third-party templates usually include a comment near the top of the file:
This file was generated with NAME
(where *NAME* is a name of the plugin generated the file). Such files are *not*
part of Dist-Zilla-PluginBundle-Author-VDB source, and
Dist-Zilla-PluginBundle-Author-VDB copyright and license are not applicable to
such files.
INSTALLING
With cpanm
cpanm tool is (probably) the easiest way to install distribution. It automates
downloading, building, testing, installing, and uninstalling.
To install the latest version from CPAN:
$ cpanm Dist::Zilla::PluginBundle::Author::VDB
To install a specific version (e. g. *v0.7.1*) from CPAN:
$ cpanm Dist::Zilla::PluginBundle::Author::VDB@v0.7.1
To install locally available distribution (e. g. previously downloaded from CPAN
or built from sources):
$ cpanm ./Dist-Zilla-PluginBundle-Author-VDB-v0.7.1.tar.gz
To uninstall the distribution:
$ cpanm -U Dist::Zilla::PluginBundle::Author::VDB
Manually
To install distribution tarball manually (let us assume you have version
*v0.7.1* of the distribution):
$ tar xaf Dist-Zilla-PluginBundle-Author-VDB-v0.7.1.tar.gz
$ cd Dist-Zilla-PluginBundle-Author-VDB-v0.7.1
$ perl Build.PL
$ ./Build build
$ ./Build test
$ ./Build install
See Also
How to install CPAN modules
HACKING
For hacking, you will need Mercurial, Perl interpreter and Dist-Zilla (with some
plugins), and likely cpanm to install missed parts.
Clone the repository first:
$ hg clone https://vandebugger.fedorapeople.org/hg/perl-Dist-Zilla-PluginBundle-Author-VDB
$ cd perl-Dist-Zilla-PluginBundle-Author-VDB
To build a distribution from the source, run:
$ dzil build
If required Dist-Zilla plugins are missed, dzil tool will warn you and show the
command to install all the required plugins, e. g.:
Required plugin Dist::Zilla::Plugin::Test::EOL isn't installed.
Run 'dzil authordeps' to see a list of all required plugins.
You can pipe the list to your CPAN client to install or update them:
dzil authordeps --missing | cpanm
To run the tests:
$ dzil test
To run all the tests, including release tests:
$ dzil test --release
To install the distribution:
$ dzil install
or
$ cpanm ./Dist-Zilla-PluginBundle-Author-VDB-VERSION.tar.gz
where *VERSION* is a version of built distribution.
To clean the directory:
$ dzil clean
DOCUMENTATION
Online
The easiest way is browsing the documentation online at meta::cpan
.
Locally Installed
If you have the distribution installed, use perldoc tool to browse locally
installed documentation:
$ perldoc Dist::Zilla::PluginBundle::Author::VDB::Manual
$ perldoc Dist::Zilla::PluginBundle::Author::VDB
Built from Source
Build Dist-Zilla-PluginBundle-Author-VDB first (see "HACKING"), then:
$ cd Dist-Zilla-PluginBundle-Author-VDB-VERSION
$ perldoc Dist::Zilla::PluginBundle::Author::VDB::Manual
$ perldoc Dist::Zilla::PluginBundle::Author::VDB
where *VERSION* is a version of built distribution.
FEEDBACK
CPAN Request Tracker
The quickest way to report a bug in Dist-Zilla-PluginBundle-Author-VDB is by
sending email to bug-Dist-Zilla-PluginBundle-Author-VDB [at] rt.cpan.org.
CPAN request tracker can be used via web interface also:
Browse bugs
Browsing bugs does not require authentication.
Report bugs
You need to be a CPAN author, have a BitCard
account, or OpenID in order to report bugs via the web interface.
(On 2015-04-27 I have logged in successfully with my LiveJournal OpenID, but
my Google OpenID did not work for CPAN. I did not check other OpenID
providers.)
Send Email to Author
As a last resort, send email to author: Van de Bugger .
Please start message subject with "perl-Dist-Zilla-PluginBundle-Author-VDB:".
GLOSSARY
CPAN
Comprehensive Perl Archive Network, a large collection of Perl software and
documentation. See cpan.org , What is CPAN?
.
Distribution
Tarball, containing Perl modules and accompanying files (documentation,
metainfo, tests). Usually distributions are uploaded to CPAN, and can be
installed with dedicated tools (cpan, cpanm, and others).
Module
Perl library file, usually with .pm suffix. Usually contains one package.
See perlmod .
Package
Perl language construct. See package
and perlmod
.