Bug 55115 - update devel/p5-Module-Build
Summary: update devel/p5-Module-Build
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Dmitry Sivachenko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-31 14:50 UTC by Mathieu Arnold
Modified: 2003-08-21 14:10 UTC (History)
1 user (show)

See Also:


Attachments
p5-Module-Build-0.19_1.diff (5.52 KB, patch)
2003-07-31 14:50 UTC, Mathieu Arnold
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Arnold 2003-07-31 14:50:11 UTC
Update devel/p5-Module-Build to 0.19_03

Man page generation works with all 3 perls.
PREFIX is respected provided you use ${PORTSDIR}/devel/p5-Module-Build/inc.build.mk
in Makefile.

* Fixed a problem with the 'install_path' parameter given to 'Build.PL' being
  lost in subsequent actions.
* The installation process will now create man(1) and man(3) pages from POD in
  modules & scripts, and install them.
* version_from_file() now ignores $VERSION variables that are defined
  in POD or comments.  It can still be tricked by $VERSIONs in string literals,
  though.
* The code to find packages in module files now uses Steve's scanning
  method (above) to skip package-declaration-lookalikes in POD or comments.
* The 'disttest' action will now propagate its @INC settings to its
  subprocesses.
* Added a notes() feature, which helps share data transparently between the
  Build.PL and t/*.t scripts.  (XXX needs documentation)

Fix: The use of inc.build.mk is the best I could think of.

Tell me what you believe the best could be.

All ports depending on Module::Build to build would have to be updated so that
they include their newly born man pages. It should not be a problem as I seem
to be the only one with perl ports depending on it.

btw, portlint was a bit picky with the patch, saying that the $File may be
interpreted as a CVS token. I don't think it would as there is not $ after it,
but maybe -ko would not harm.
Comment 1 Kirill Ponomarev freebsd_committer freebsd_triage 2003-07-31 20:54:49 UTC
Responsible Changed
From-To: freebsd-ports-bugs->demon

Over to maintainer.
Comment 2 Mathieu Arnold freebsd_committer freebsd_triage 2003-08-21 14:10:06 UTC
State Changed
From-To: open->closed

committed