Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Upstream changes:
0.09 4 August 2010
- Use Catalyst::Utils::ensure_class_loaded on the adapted class,
instead of eval/require, so that inner classes in already-loaded
packages will work.
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!
pkgsrc changes:
- Adjust module type
Upstream changes:
0.08 9 Febuary 2010
- Correctly built distribution. MANIFEST.SKIP fixed to avoid the issue
in future.
0.07 9 Febuary 2010
- Catalyst::Runtime is a runtime dependency. RT#48842
pkgsrc changes:
- Updating MASTER_SITES
- Adding license (perl license)
- Adjusting dependencies
Upstream changes:
0.05 7 August 2009
- Fix a minor documentation problem. Reported by Eric Prestemon.
(Closes RT#48487)
- Switch from Class::C3 to MRO::Compat.
0.04 16 July 2009
- If no arguments are supplied, then construct new objects with {}
by default, rather than undef, as Moose classes fail if given undef.
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=...").
Catalyst is an elegant web application framework, extremely flexible yet
extremely simple. It's similar to Ruby on Rails, Spring (Java) and
Maypole, upon which it was originally based.
Catalyst follows the Model-View-Controller (MVC) design pattern, allowing
you to easily separate concerns, like content, presentation and flow control,
into separate modules. This separation allows you to modify code that handles
one concern without affecting code that handles the others. Catalyst promotes
re-use of existing Perl modules that already handle common web application
concerns well.
