Factorize xrdcp config files into a transitional library so that they could be used by the new client
Add libXrdAppUtils to the libs package
Disable sendfile on Mac - it gets detected and compiled correctly but doesn't work
Undo the side-effect of commit ff8bdbd6 that prevented the frm from sending stage notifications to xrootd; causing opens and xrdstagetool to hang with dynamic staging enabled.
Update pre-release notes for frm issue.
Create a general place for platform dependent utility methods.
Update prerelease notes for XrdSysUtils class.
Correct log processing for sites that use the root directory as the stomping
ground for newly created files.
Update pre-release notes for cns_ssi update fix.
Prevent double-free abort when more than 16 files have been opened by a client
and the client terminates the session without closing the 17th one.
Update pre-release notes for double-free abort.
Additional fixes for exterme copy to prevent hangs in server/server copies.
Update pre-release notes for xrdcp/xrdcpy fixes.
   - In case of 'limited proxy' look for VOMS attributes also in the parent proxy
     as the extension is not ported to the limite proxy certificate.
     The first argument of the internal auxilliary function ExtractVOMS has been
     changed to XrdCryptoX509Chain so that the lookup can be done if required.
   - Adapt XrdSecgsiProxy (xrdgsiproxy) to such a case.
   - Improve debug statements in XrdCryptosslX509ParseFile .
Fix build on Solaris
   Add possibility to load a function for VOMS extraction via plug-in.
   The plug-in must contain two functions, to be all declared as 'extern C':

     1. The main function:

               int XrdSecgsiVOMSFun(XrdSecEntity &entity)

        here entity is the XrdSecEntity object associated with the handshake on the
        server side. On input entity contains:
          - in 'name' the username, DN, DN hash according to the GMAP option
          - in 'host' the client hostname
          - in 'creds'the proxy chain
        The proxy chain can be either in 'raw' or 'PEM base64' format (see below).
        This function returns
                              0      on success
                             <0      on error (implies authentication failure if VOMS
                                               attributes are required)

     2. The initialization function:

               int XrdSecgsiVOMSInit(const char *)

        here 'parameters' is the string of parameters, separated by ' '.
        This function return <0 in case of failure or the format type of the proxy chain
        expected by the main function:
                              0       raw, to be used with XrdCrypto tools
                              1       PEM (base64 standard string)

    An example of plug-in doing exactly what is now done by XrdSecProtocolgsi::ExtractVOMS
    can be found in XrdSecgsiVOMSFunLite.cc under src/XrdSecgsi.

    Load of this plugin is controlled by two new switches for the GSI plugin:

           -vomsfun           defining the location of the library
           -vomsfunparms      defining the parameters parsed by XrdSecgsiVOMSInit

    The existing switch 'vomsat' has been augmented of one case to include the case when
    VOMS attributes are required:

           -vomsat            0   do not look for VOMS
                              1   extract if available
                              2   fail if not available
* Implement comprehensive version checking for dynamic as well as built-in
   plug-ins.
* Make version checking mandatory for all authentication plug-ins. This
   means that un-versioned authentication plug-ins cannot  be loaded.
   However, authentication plug-ins will load un-versioned extensions (e.g.
   gsi authz extensions) with a server-side warning.
* Display a warning when loading an un-versioned plug-in. To avoid the
   warning, plug-in writers must supply version information as described in
   the plug-in header file (i.e. an include of XrdVersion.hh and a
   corresponding macro instantiation).
* Display version information when loading unreleased plug-ins or using
   unreleased loaders.
* Display an error message when encountering an incompatible plug-in along
   with the minimum or maximum version required for the plug-in to be
   compatible.
* Be aware that version checking will, in many cases, prohibit mixing
   released shared library versions.
Part of version checking. Define version checking rules and standardize on the way the
name2name library is handled.
Correct test whether or not to initialize redirect monitoring.
Update pre-release notes for redirect monitoring fix.