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!
of scheduled update for editors/p5-Padre-Plugin-Catalyst.
This module provides Access Control List style path protection, with
arbitrary rules for Catalyst applications. It operates only on the
Catalyst private namespace, at least at the moment.
The two hierarchies of actions and controllers in Catalyst are:
* Private Namespace
Every action has its own private path. This path reflects the Perl
namespaces the actions were born in, and the namespaces of their
controllers.
* External Namespace
Some actions are also directly accessible from the outside, via a URL.
The private and external paths will be the same, if you are using
Local actions. Alternatively Path, Regex, or Global can be used to
specify a different external path for an action.
The ACL module currently only knows to exploit the private namespace. In
the future extensions may be made to support external namespaces as well.
When a path is visited, rules are tested one after the other, with the most
exact rule fitting the path first, and continuing up the path. Testing
continues until a rule explcitly allows or denies access.
