{perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS
since pkgsrc enforces the newest perl version anyway, so they
should always pick perl, but sometimes (pkg_add) don't due to the
design of the {,} syntax.
No effective change for the above reason.
Ok joerg
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.
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:
- Set PERL5_MODULE_TYPE to Module::Install
- Add dependency on time/p5-DateTime
Upstream changes:
0.12 Wed May 27 16:59:36 2009
Fix use of meta-attribute removed from triggers (Sartak)
ChangeLog:
0.11 Depend on Any::Moose instead of Moose
0.10
Releng fixes
Use a predicate for has_config_file
0.09
Hash::Merge and Path::Class are now depended-upon only if you want
cascading directory config
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=...").
from the DESCR:
Jifty is a full-stack web framework. It provides an optional REST
interface for applications. Using this module, you can interact with
that REST interface to write client-side utilities. You can use this
module directly, but you'll be better off subclassing it, such as what
we've done for Net::Hiveminder. This module also provides a number of
convenient methods for writing short scripts.
