Initial import of gcc49-4.9.1 as lang/gcc49.

Changes, New Features, and Fixes in GCC 4.9 can be found here:

  https://gcc.gnu.org/gcc-4.9/changes.html

This is based heavily on lang/gcc47 but updated for GCC 4.9.1.  Tested on
SmartOS (32-bit and 64-bit) and NetBSD 6.1.4/amd64.
Added lang/gcc49 version 4.9.1
Add gcc49.
Initial import of gcc49-libs-4.9.1nb1 as lang/gcc49-libs.

This packages provides GCC support libraries from gcc49 in a specific
location and allows packages to depend on just the libraries rather than
having to pull in the full GCC package.  It is heavily based on
lang/gcc47-libs.
Added lang/gcc49-libs version 4.9.1nb1
Add gcc49-libs.
Add infrastructure support for lang/gcc49 and lang/gcc49-libs
Remove duplicate gcc-4.9.1 entry.
Import libestr-0.1.9 as devel/libestr.

libestr is a library for some string essentials.
Added devel/libestr version 0.1.9
Fix incorrect PKGPATH.
Import liblogging-1.0.4 as sysutils/liblogging.

Liblogging is an easy to use library for logging. It offers
an enhanced replacement for the syslog() call, but retains
its ease of use.
Added sysutils/liblogging version 1.0.4
Import liblognorm-1.0.1 as sysutils/liblognorm.

liblognorm shall help to make sense out of syslog data, or, actually,
any event data that is present in text form.

In short words, one will be able to throw arbitrary log message to
liblognorm, one at a time, and for each message it will output
well-defined name-value pairs and a set of tags describing the message.
Added sysutils/liblognorm version 1.0.1
Define location of local plugins directory.  Bump PKGREVISION.
Update to 0.28

0.28 2013-11-21
  - Removed silly micro-optimization that was responsible for generating a
    warning in Perl versions prior to 5.18.

0.27 2013-10-06
  - Merged pull request from David Steinbrunner: specifying meta-spec
    so metadata can be seen/used.
  - Fixed t/05-kwalitee.t to work with latest revisions on Test::Kwalitee.
p5-Bytes-Random-Secure update
Update to 2.14. From the changelog:

[FIXES]
The -s flag would fail to suppress certain warnings.  Thanks, Kassio
Borges. (GitHub ticket #439)

The -w flag would fail to work properly with regex features such as
alternation.  Thanks to Ed Avis for the report (GitHub ticket #443)

The -g flag should now work faster on larger codebases.  Thanks to
Manuel Meurer for the report (GitHub ticket #458)

More fixes for Windows tests.  Thanks to GitHub user @ispedals.

More whack-a-mole with Windows failures.  This time, it's POSIX::mkfifo
dying on Windows instead of returning undef like the docs implied,
or at least that I inferred.

Fixed incorrect deduping of config files under Windows.  Thanks,
Denis Howe.

More build fixes for Windows.  Windows config finder fixes from
James McCoy.

t/ack-named-pipes.t uses POSIX::mkfifo instead of the external
command, which should be more portable.  Thanks, Pete Krawczyk.

The building of ack-standalone relied on the output of `perldoc
-l`, which I apparently can't rely on having been installed.  I've
changed the way that the squash program finds File::Next.

Issue #313: ack would fail when trying to check files for readability
on some networked filesystems, or on Mac OS X with ACLs.  Now it
uses the filetest pragma.  Thanks, Jonathan Perret.

[ENHANCEMENTS]
ack now ignores JavaScript and CSS source maps.  Thanks, Chris
Rebert.

ack now ships with customized shell completion scripts for bash and zsh.

Add docs for available colors in ack.

--create-ackrc keeps the comments that describe each of the options,
and it shows the ack version number.

Now ignores Cabal (Haskell) sandboxes.  Thanks, Fraser Tweedale.

Added filetypes for Jade, Smarty and Stylus.  Thanks, RaÃºl GundÃ­n.

[INTERNALS]
ack's entire test suite now runs under Perl's -T taint flag.  We'll
build more security tests on top of this.

Added some checks to the squash program that I hope will turn up
errors in the Windows builds.
Import p5-WWW-CSRF 1.00

This module generates tokens to help protect against a website attack
known as Cross-Site Request Forgery (CSRF, also known as XSRF). CSRF
is an attack where an attacker fools a browser into make a request to
a web server for which that browser will automatically include some
form of credentials (cookies, cached HTTP Basic authentication, etc.),
thus abusing the web server's trust in the user for malicious use.

The most common CSRF mitigation is sending a special, hard-to-guess
token with every request, and then require that any request that is
not idempotent (i.e., has side effects) must be accompanied with such
a token. This mitigation depends critically on the fact that while an
attacker can easily make the victim's browser make a request, the
browser security model (same-origin policy, or SOP for short) prevents
third-party sites from reading the results of that request.