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!
The (so called) "Security Images" are so popular. Most internet
software use these in their registration screens to block robot
programs (which may register tons of fake member accounts). Security
images are basicaly, graphical CAPTCHAs (Completely Automated Public
Turing Test to Tell Computers and Humans Apart). This module gives
you a basic interface to create such an image. The final output is
the actual graphic data, the mime type of the graphic and the
created random string. The module also has some "styles" that are
used to create the background (or foreground) of the image.
If you are an Authen::Captcha user, see GD::SecurityImage::AC for
migration from Authen::Captcha to GD::SecurityImage.
This module is just an image generator. Not a captcha handler. The
validation of the generated graphic is left to your programming
taste. But there are some captcha handlers for several Perl
FrameWorks. If you are an user of one of these frameworks, see
"GD::SecurityImage Implementations" in "SEE ALSO" section for
information.
