Commit graph

7 commits

Author SHA1 Message Date
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
agc
4a3d2f7ce2 Add RMD160 digests. 2005-02-23 22:24:08 +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
wiz
6fefceb6cd Update to 1.03, provided by Hiramatsu Yoshifumi in PR 28463.
Changes since 1.00:
  - Added 'get_my_factory()' and 'get_my_factory_type()'
  - Ensure that new() returns undef if get_factory_class() doesn't
  work properly and factory_error() is overridden (and the
  overridden method doesn't die)
  - Added a few more tests to ensure factory_log() and
  factory_error() working properly
  - add_factory_type() checks %INC to see if a class is already
  loaded.
  - All log/error messages now have variables in apostrophes
  rather than brackes.
2004-11-29 20:52:39 +00:00
minskim
7fa0b2927c Import p5-Class-Factory from pkgsrc-wip. Packaged by Hiramatsu Yoshifumi.
This is a simple module that factory classes can use to generate new
types of objects on the fly, providing a consistent interface to common
groups of objects.

Factory classes are used when you have different implementations for the
same set of tasks but may not know in advance what implementations you
will be using.
2004-10-23 00:20:37 +00:00