rpms/perl-AnyEvent
5
0
Fork 0
Code Issues Pull Requests Releases Activity

Update to 7.07

Browse Source 
- New upstream release 7.07:
  - The documentation for custom tls verify schemes was wrong; make it agree
    with the code
  - Added cbor read and write types to AnyEvent::Handle (using CBOR::XS)
  - Work around an API change in openssl that could cause wrong tls connection
    aborts, likely on windows only
  - Calling AnyEvent->now_update with AnyEvent::Impl::Perl caused an endless
    loop
  - Add tlsv1_1 and tlsv1_2 protocols to AnyEvent::TLS
  - Document AnyEvent::Impl::IOAsync::set_loop and
    $AnyEvent::Impl::IOAsync::LOOP; though only documented now, this
    functionality has always been available
  - Force a toplevel domain name in t/81_hosts.t
  - Document that AnyEvent::Log uses AnyEvent::IO
  - Warn about AnyEvent::Filesys::Notify performance
  - Praise the joys of AnyEvent::Fork::*
  - Time for an =encoding directive
  - No longer use JSON to create a default json coder; use JSON::XS or JSON::PP
    directly
This commit is contained in:
Paul Howarth 2013-12-17 21:36:38 +00:00
parent c3b973425e
commit 3d95c063e6
2 changed files with 23 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
perl-AnyEvent.spec
View File

@ -4,7 +4,7 @@
%global debug_package %{nil}
Name: perl-AnyEvent
Version: 7.05
Version: 7.07
Release: 1%{?dist}
Summary: Framework for multiple event loops
Group: Development/Libraries
@ -146,6 +146,27 @@ make test
%changelog
* Tue Dec 17 2013 Paul Howarth <paul@city-fan.org> - 7.07-1
- Update to 7.07:
- The documentation for custom tls verify schemes was wrong; make it agree
with the code
- Added cbor read and write types to AnyEvent::Handle (using CBOR::XS)
- Work around an API change in openssl that could cause wrong tls connection
aborts, likely on windows only
- Calling AnyEvent->now_update with AnyEvent::Impl::Perl caused an endless
loop
- Add tlsv1_1 and tlsv1_2 protocols to AnyEvent::TLS
- Document AnyEvent::Impl::IOAsync::set_loop and
$AnyEvent::Impl::IOAsync::LOOP; though only documented now, this
functionality has always been available
- Force a toplevel domain name in t/81_hosts.t
- Document that AnyEvent::Log uses AnyEvent::IO
- Warn about AnyEvent::Filesys::Notify performance
- Praise the joys of AnyEvent::Fork::*
- Time for an =encoding directive
- No longer use JSON to create a default json coder; use JSON::XS or JSON::PP
directly
* Wed Aug 21 2013 Paul Howarth <paul@city-fan.org> - 7.05-1
- Update to 7.05:
- uts46data.pl couldn't be found due to wrong naming of the file

2
sources
View File

@ -1 +1 @@
e329cb8549d2eedcacee56a962a7e3fe AnyEvent-7.05.tar.gz
e5ef99081b2acc3df80851838f9acfc4 AnyEvent-7.07.tar.gz