./lang/perl5, Practical Extraction and Report Language

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 5.18.2nb1, Package name: perl-5.18.2nb1, Maintainer: pkgsrc-users

Perl is a general-purpose programming language originally developed
for text manipulation and now used for a wide range of tasks including
system administration, web development, network programming, GUI
development, and more. The language is intended to be practical (easy
to use, efficient, complete) rather than beautiful (tiny, elegant,
minimal). Its major features are that it's easy to use, supports both
procedural and object-oriented (OO) programming, has powerful built-in
support for text processing, and has one of the world's most impressive
collections of third-party modules.



Package options: 64bitauto, threads

Master sites: (Expand)

SHA1: b8b87ef46630b5a2287b86b6e0c69088da36adfd
RMD160: 1b656ae4f53845aac11e62b71c2d84c156ebfbd0
Filesize: 13729.017 KB

Version history: (Expand)


CVS history: (Expand)


   2014-04-09 23:05:58 by Matthias Scheler | Files touched by this commit (1)
Log message:
Don't enable "dtrace" support by default under Solaris 10. It doesn't
build for me on an UltraSPARC system.
   2014-03-14 23:41:10 by Ryo ONODERA | Files touched by this commit (6)
Log message:
Fix build under SCO OpenServer 5.0.7/3.2
and add workaround for empty result of nl_langinfo(CODESET).
This workaround is needed for devel/gtexinfo.
   2014-03-13 12:08:54 by Jonathan Perkin | Files touched by this commit (67)
Log message:
Set USE_GCC_RUNTIME=yes for packages which build shared libraries but do
not use libtool to do so.  This is required to correctly depend upon a
gcc runtime package (e.g. gcc47-libs) when using USE_PKGSRC_GCC_RUNTIME.
   2014-02-17 05:28:45 by OBATA Akio | Files touched by this commit (1)
Log message:
put a apace before "||" operator.
   2014-02-16 23:40:57 by Jens Rehsack | Files touched by this commit (1)
Log message:
Minor cleanup op PERL5_MODULE_TYPE & Bundle support for M::B
   2014-01-31 18:38:48 by Eric Schnoebelen | Files touched by this commit (2) | Package updated
Log message:
pkg/48500:  add a hack on NetBSD/alpha to add the gcc compiler flag
	    -fno-tree-ter, removing the alignment warnings printed by the
	    NetBSD/alpha kernel when perl was executed.

	    bump PKGREVISION
   2014-01-24 17:37:19 by Ryo ONODERA | Files touched by this commit (2)
Log message:
Fix OpenBSD 5.3 build and supress warning under OpenBSD 5.4

* OpenBSD has no libdb like NetBSD
   2014-01-13 10:59:16 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
Changes 5.18.2:
* B has been upgraded from version 1.42_01 to 1.42_02.
* B::Concise has been upgraded from version 0.95 to 0.95_01.
* English has been upgraded from version 1.06 to 1.06_01. This fixes an error \ 
about the performance of $`, $&, and c<$'>.
* File::Glob has been upgraded from version 1.20 to 1.20_01.
Bugs fixed:
* Perl 5.18.1 introduced a regression along with a bugfix for lexical subs. Some \ 
B::SPECIAL results from B::CV::GV became undefs instead. This broke Devel::Cover \ 
among other libraries.
* Perl 5.18.0 introduced a regression whereby [:^ascii:], if used in the same \ 
character class as other qualifiers, would fail to match characters in the \ 
Latin-1 block.
* Perl 5.18.0 introduced a regression when using ->SUPER::method with \ 
AUTOLOAD by looking up AUTOLOAD from the current package, rather than the \ 
current package’s superclass.
* Perl 5.18.0 introduced a regression whereby -bareword was no longer permitted \ 
under the strict and integer pragmata when used together.
* Previously PerlIOBase_dup didn't check if pushing the new layer succeeded \ 
before (optionally) setting the utf8 flag. This could cause \ 
segfaults-by-nullpointer.
* A buffer overflow with very long identifiers has been fixed.
* A regression from 5.16 in the handling of padranges led to assertion failures \ 
if a keyword plugin declined to handle the second ‘my’, but only after \ 
creating a padop.
* The construct $r=qr/.../; /$r/p is now handled properly, an issue which had \ 
been worsened by changes 5.18.0.