to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
Changes from 1.04:
1.06 Tue Nov 6 21:16:07 CET 2007
- Added remove_factory_type(), unregister_factory_type() and
get_factory_type_for(). Marcel Gruenauer <marcel@cpan.org>
1.05 Thu Feb 1 22:57:21 PST 2007
- Added method get_registered_class(), suggested by
Sebastian Knapp <giftnuss@netscape.net>
Patch provided by Martin Wilke via PR 34329.
Changes:
1.04 Mon Aug 20 22:26:15 PST 2006
- New maintainer, Fred Moyer <fred@redhotpenguin.com>
- Add Devel::Cover support, current coverage is 71%
- Moved check for Test::More to MY::test
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.
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.
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.
