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.
* Various patches by Chorny at cpan dot org and fREW frioux at gmail dot com:
* Windows NTFS compatibility fixes.
* Allow PID to be negative.
* Lexically scope temp file handles to reduce changes of memory leak and
avoid unintentional glob clobberation.
* Security fix: 3 arg open().
* Repair test suites logics.
* Fixed infinite freezing on Strawberry Perl v5.10.0.
* Fixed infinite freezing on ActiveState Perl v5.12.1.
* Sorry for the past 8 years of suffering.
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=...").
File::NFSLock - perl module to do NFS (or not) locking
Program based of concept of hard linking of files being atomic
across NFS. This concept was mentioned in Mail::Box::Locker (which
was originally presented in Mail::Folder::Maildir). Some routine
flow is taken from there -- particularly the idea of creating a
random local file, hard linking a common file to the local file,
and then checking the nlink status. Some ideologies were not complete
(uncache mechanism, shared locking) and some coding was even
incorrect (wrong stat index). File::NFSLock was written to be light,
generic, and fast.
