Gentoo Packages

Search

Install

Install this package:

emerge -a dev-perl/Module-Build-Pluggable

If the package is masked, you can unmask it using the autounmask tool or standard emerge options:

autounmask dev-perl/Module-Build-Pluggable

Or alternatively:

emerge --autounmask-write -a dev-perl/Module-Build-Pluggable

Package Information

Description:

Module::Build::Pluggable adds pluggability for Module::Build. HOW CAN I WRITE MY OWN PLUGIN? Module::Build::Pluggable call HOOK_prepare on preparing arguments for Module::Build->new, HOOK_configure on configuration step, and HOOK_build on build step. That's all. And if you want a help, you can use Module::Build::Pluggable::Base as base class.

Versions

Metadata

Description

• Module::Build::Pluggable adds pluggability for Module::Build. HOW CAN I WRITE MY OWN PLUGIN? Module::Build::Pluggable call HOOK_prepare on preparing arguments for Module::Build->new, HOOK_configure on configuration step, and HOOK_build on build step. That's all. And if you want a help, you can use Module::Build::Pluggable::Base as base class.

Maintainers

• Chris Travers (chris.travers@gmail.com) - Type: person
• Proxy Maintainers (proxy-maint@gentoo.org) - Type: project
• Unknown (perl@gentoo.org) - Type: project

Upstream

• Remote IDs:
  • cpan: Module::Build::Pluggable
  • cpan-module: Module::Build::Pluggable
  • cpan-module: Module::Build::Pluggable::Base
  • cpan-module: Module::Build::Pluggable::GithubMeta
  • cpan-module: Module::Build::Pluggable::Repository
  • cpan-module: Module::Build::Pluggable::Util

<pkgmetadata>
	<maintainer type="person" proxied="yes">
		<email>chris.travers@gmail.com</email>
		<name>Chris Travers</name>
	</maintainer>
	<maintainer type="project" proxied="proxy">
		<email>proxy-maint@gentoo.org</email>
		<name>Proxy Maintainers</name>
	</maintainer>
	<maintainer type="project">
		<email>perl@gentoo.org</email>
	</maintainer>
	<longdescription lang="en">
Module::Build::Pluggable adds pluggability for Module::Build.

HOW CAN I WRITE MY OWN PLUGIN?
Module::Build::Pluggable call HOOK_prepare on preparing arguments for Module::Build->new, HOOK_configure on configuration step, and HOOK_build on build step.

That's all.

And if you want a help, you can use Module::Build::Pluggable::Base as base class.</longdescription>
	<upstream>
		<remote-id type="cpan">Module::Build::Pluggable</remote-id>
		<remote-id type="cpan-module">Module::Build::Pluggable</remote-id>
		<remote-id type="cpan-module">Module::Build::Pluggable::Base</remote-id>
		<remote-id type="cpan-module">Module::Build::Pluggable::GithubMeta</remote-id>
		<remote-id type="cpan-module">Module::Build::Pluggable::Repository</remote-id>
		<remote-id type="cpan-module">Module::Build::Pluggable::Util</remote-id>
	</upstream>
</pkgmetadata>

Lint Warnings

• [Warning] Ebuild 0.100.0 is missing HOMEPAGE
• [Error] Missing md5-cache for ebuild Module-Build-Pluggable-0.100.0

Manifest