Commit graph

12 commits

Author SHA1 Message Date
jlam
9c8b5ede43 Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
2006-03-04 21:28:51 +00:00
jlam
7fbb8d9527 Bump the PKGREVISIONs of all (638) packages that hardcode the locations
of Perl files to deal with the perl-5.8.7 update that moved all
pkgsrc-installed Perl files into the "vendor" directories.
2005-08-06 06:19:03 +00:00
jlam
7a6521287b Turn PERL5_PACKLIST into a relative path instead of an absolute path.
These paths are now relative to PERL5_PACKLIST_DIR, which currently
defaults to ${PERL5_SITEARCH}.  There is no change to the binary
packages.
2005-07-13 18:01:18 +00:00
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
jlam
cc44d0be98 * Teach devel/p5-Module-Build to write .packlists just like MakeMaker.pm
does.  This allows us to use dynamic PLISTs for Perl modules that are
  built using Module::Build.  Bump the PKGREVISION of p5-Module-Build
  to 1.

* Drop the use of PERL5_USES_MODULE_BUILD and introduce a new variable
  PERL5_MODULE_TYPE that is either "MakeMaker" or "Module::Build" that
  names the framework used to build/install the module.

* Split out the variables set in perl5/buildlink3.mk that are also used
  by perl5/module.mk into a new file perl5/vars.mk.  Move some PERL5_*
  variable definitions from pkgsrc/mk/bsd.pkg.use.mk into perl5/vars.mk.
  This just centralizes the common PERL5_* definitions into a single
  file location.

* Convert the known packages that use Module::Build to set
  PERL5_MODULE_TYPE and PERL5_PACKLIST:

	devel/p5-Class-Container
	devel/p5-Exception-Class
	devel/p5-Log-Dispatch
	devel/p5-Array-Compare
	textproc/p5-Pod-Coverage
	www/p5-Apache-Session-Wrapper
	www/p5-MasonX-Request-WithApacheSession
2005-02-24 22:38:41 +00:00
wiz
34b098a495 Update to 0.12:
0.12  Sun Jan 23 21:02:35 CST 2005

 - Fixed a bug in the container() method, which was only returning
   valid results for delayed objects, not auto-created ones. [Spotted
   by Sebastian Willert]
2005-02-23 16:58:52 +00:00
wiz
9775195b8c Update to 0.12:
0.12  Sun Jan 23 21:02:35 CST 2005

 - Fixed a bug in the container() method, which was only returning
   valid results for delayed objects, not auto-created ones. [Spotted
   by Sebastian Willert]
2005-02-23 16:58:18 +00:00
grant
908e765695 since perl is now built with threads on most platforms, the perl archlib
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").

binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.

addresses PR pkg/28619 from H. Todd Fujinaka.
2004-12-20 11:30:55 +00:00
he
1090118ace Update p5-Class-Container from version 0.10 to 0.11.
Point HOMEPAGE to an author-independent CPAN link.

Change log:

0.11  Wed Mar  3 21:34:51 CST 2004

 - Fixed a bug in the code that detects whether Scalar::Util is
   loadable. [Spotted by Michael Alan Dorman]
2004-12-05 15:58:08 +00:00
minskim
6d214ee391 Bl3ify and enable pkgviews installation. 2004-04-25 04:15:06 +00:00
kim
264f7d1b3b Scalar::Util is recommended by Class::Container, and required by
HTML::Mason so require it here to avoid possible inconsistancies
in building Class::Container.
2003-10-11 04:26:10 +00:00
he
a17082fe1f Import p5-Class-Container version 0.10.
This class facilitates building frameworks of several classes that
inter-operate. It was first designed and built for "HTML::Mason", in which
the Compiler, Lexer, Interpreter, Resolver, Component, Buffer, and several
other objects must create each other transparently, passing the appropriate
parameters to the right class, possibly substituting other subclasses for
any of these objects.
2003-08-30 18:56:46 +00:00