ASPEER-MakeMaker

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

The module is designed to be loaded from a Makefile.PL. On import it can
wrap selected ExtUtils::MakeMaker sections, add project-specific
Makefile macros, and append a reusable postamble containing common make
targets.

GitHub Attestations

The release workflow generates GitHub artifact attestations for
distribution archives. Install the GitHub CLI with gh attestation
support and authenticate with gh auth login.

Download ASPEER-MakeMaker-VERSION.tar.gz from a GitHub release,
MetaCPAN, or a CPAN mirror, replace VERSION, and verify it with:

    gh attestation verify ASPEER-MakeMaker-VERSION.tar.gz --repo aspeer/pm-ASPEER-MakeMaker

A successful verification confirms that the archive checksum matches an
attestation from this repository. The workflow publishes the same
archive to GitHub Releases and CPAN. Older releases and GitHub's
automatically generated source-code archives are not covered.

README  view on Meta::CPAN

- MakeMaker import hooks for selected Makefile generation sections.
- A const_config extension that publishes shared constants as Makefile
  macros.
- A postamble extension that appends common make targets from a
  template.
- A post_initialize extension that controls the install map and records
  the Git revision beside VERSION_FROM.
- A retained util_sync target and method for copying the shared utility
  files into an older or standalone distribution when required.
- Shared logging, file, argument-parsing, and Perl runtime construction
  helpers.

Basic Usage

In a consuming Makefile.PL, load the module before calling
WriteMakefile:

    use ASPEER::MakeMaker;
    use ExtUtils::MakeMaker;

README.md  view on Meta::CPAN

`ExtUtils::MakeMaker` customizations across ASPEER MakeMaker plugins.

The module is designed to be loaded from a `Makefile.PL`. On import it can
wrap selected `ExtUtils::MakeMaker` sections, add project-specific Makefile
macros, and append a reusable postamble containing common make targets.

## GitHub Attestations

The release workflow generates [GitHub artifact attestations](https://docs.github.com/en/actions/concepts/security/artifact-attestations)
for distribution archives. Install the [GitHub CLI](https://cli.github.com/)
with `gh attestation` support and authenticate with `gh auth login`.

Download `ASPEER-MakeMaker-VERSION.tar.gz` from a GitHub release, MetaCPAN,
or a CPAN mirror, replace `VERSION`, and verify it with:

```sh
gh attestation verify ASPEER-MakeMaker-VERSION.tar.gz --repo aspeer/pm-ASPEER-MakeMaker
```

A successful verification confirms that the archive checksum matches an
attestation from this repository. The workflow publishes the same archive to

README.md  view on Meta::CPAN

copied between plugin distributions. In particular it provides:

- MakeMaker import hooks for selected Makefile generation sections.
- A `const_config` extension that publishes shared constants as Makefile
  macros.
- A `postamble` extension that appends common make targets from a template.
- A `post_initialize` extension that controls the install map and records the
  Git revision beside `VERSION_FROM`.
- A retained `util_sync` target and method for copying the shared utility files
  into an older or standalone distribution when required.
- Shared logging, file, argument-parsing, and Perl runtime construction helpers.

## Basic Usage

In a consuming `Makefile.PL`, load the module before calling `WriteMakefile`:

```perl
use ASPEER::MakeMaker;
use ExtUtils::MakeMaker;

WriteMakefile(

SECURITY.md  view on Meta::CPAN

Please do not report security vulnerabilities through public GitHub issues,
public pull requests, RT, mailing lists, social media, chat channels, or other
public forums.

Please include enough detail to reproduce and assess the issue, including:

- the affected ASPEER::MakeMaker version
- the affected Perl version and operating system, if relevant
- a proof of concept, test case, or reproduction steps
- relevant logs, code snippets, configuration, or request/response examples
- whether the issue is known to be actively exploited
- whether you want public credit when the issue is disclosed

Do not include passwords, tokens, private keys, personal data, or other
sensitive information in the report unless it is strictly necessary and safe
to share with the maintainers.

If you would like help triaging the issue, need CVE coordination, cannot reach
the maintainer, or believe the issue is being actively exploited, you may also
copy the CPAN Security Group (CPANSec):