Hello community,
here is the log from the commit of package perl-AnyEvent for openSUSE:Factory
checked in at Tue Jul 5 14:03:06 CEST 2011.
--------
--- perl-AnyEvent/perl-AnyEvent.changes 2010-12-01 14:37:33.000000000 +0100
+++ /mounts/work_src_done/STABLE/perl-AnyEvent/perl-AnyEvent.changes 2011-06-12 00:05:45.000000000 +0200
@@ -1,0 +2,74 @@
+Sat Jun 11 22:03:01 UTC 2011 - pascal.bleser@opensuse.org
+
+- switch to bm.pl, as cpanspec created an RPM that didn't provide
+ perl(AnyEvent)
+
+-------------------------------------------------------------------
+Sat Jun 11 01:27:13 UTC 2011 - pascal.bleser@opensuse.org
+
+- update to 5.34:
+ * AE::TLS didn't support both cert_file and key at the same time, due to some
+ copy&paste bug
+ * improve AE::Handle timeout documentation slightly
+
+- changes from 5.33:
+ * AnyEvent::Handle on_connect_error - do not try to destroy a handle object
+ when it's already gone
+ * update idna algorithm(s) to UTS#46 version 6.0.0
+ * preserve trailing dot in idn_to_ascii - testsuite says to preserve, uts46
+ says it's an error, and testsuite makes more sense
+ * remove leading dots in idn_to_ascii - testsuite says to remove, uts46 says
+ it's an error, and testsuite makes more sense
+ * fixed a bug in idn ignored character processing
+
+- changes from 5.31:
+ * work around a POE bug where POE would first poll for new events and invoke
+ handlers BEFORE handling the message queue
+ * fix parsing of "domain" statement in resolv.conf
+ * stop_read now does just that in TLS mode; see its documentation for caveats
+ * update to common::sense 3.4 warning set (some warnings in perl impose an
+ arbitrary 32kb limit on regex matches, which affects AnyEvent::Handle)
+ * AE::Handle had a broken rbuf_max method and missing wbuf_max method
+ * new experimental AE::Handle::resettls method
+
+- changes from 5.3:
+ * major IOAsync patch by Paul Evans - 0.33 is required, as the major issues
+ with IO::Async have been solved in that version, including the availabilty
+ of a default loop!
+ * implement new wbuf_max parameter for AnyEvent::Handle
+ * added Cocoa::EventLoop backend
+ * set CLOEXEC flag on parent-side fd's in AnyEvent::Util::run_cmd, to avoid
+ leaking them to any child processes
+ * try to force files into the arch-dependend lib directory, for the
+ half-"turly obsessive compulsive person"(s) that depend on it
+
+- changes from 5.29:
+ * convert EV backend to EV 4.00 API (so better upgrade EV too)
+ * AE::Handle: implement dynamic read_size adjustment, add max_read_size
+ parameter, reduce default read_size to 2048
+ * add some FAQ entries for servers and/or on_eof vs. on_error
+ * reduce memory usage slightly when connect was used in AE::Handle
+ * work around more segfaults in Tk
+ * document tls_ctx => undef as valid
+ * detect WNOHANG value at compiletime
+ * include some probably linux-only support for building AnyEvent as part of
+ the perl core
+ * make AnyEvent::Strict truly optional (in case somebody builds a minimal perl...)
+
+- changes from 5.28:
+ * due to a glitch, AnyEvent's internal getprotobyname wasn't actually used in
+ tcp_server
+ * implement AnyEvent::CondVar->new method, which was documented but missing
+ * support autoloading of read types in unshift_read
+ * AnyEvent::Strict: do the test for invalid fh arguments differently,
+ resulting in more informative error messages
+ * new AnyEvent::FAQ manpage
+ * clarify that you can actually call push_read etc. in on_read
+ * put keys and certs in /tmp, not into the current directory and document
+ this in the SECURITY CONSIDERATIONS sections of AnyEvent::TLS
+ * support ";" as resolv.conf comment character in AnyEvent::DNS
+ * AnyEvent::Handle now croaks when negative timeouts are passed
+ * add a shitload of TCP_xxx sockopt name constants to AnyEvent::Util,
+ undocumented, but who knows when they might come in handy
+
+-------------------------------------------------------------------
calling whatdependson for head-i586
Old:
----
AnyEvent-5.271.tar.bz2
New:
----
AnyEvent-5.34.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ perl-AnyEvent.spec ++++++
--- /var/tmp/diff_new_pack.TNkUuU/_old 2011-07-05 14:02:02.000000000 +0200
+++ /var/tmp/diff_new_pack.TNkUuU/_new 2011-07-05 14:02:02.000000000 +0200
@@ -1,7 +1,7 @@
#
-# spec file for package perl-AnyEvent (Version 5.271)
+# spec file for package perl-AnyEvent
#
-# Copyright (c) 2010 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2011 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@@ -15,24 +15,19 @@
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
-# norootforbuild
Name: perl-AnyEvent
-Summary: DBI of event loop programming
-Version: 5.271
-Release: 2
-License: Artistic License, GPL
+Version: 5.34
+Release: 1
+Summary: DBI of Event Loop Programming
+Source: http://search.cpan.org/CPAN/authors/id/M/ML/MLEHMANN/AnyEvent-%{version}.tar.gz
+Url: http://search.cpan.org/dist/AnyEvent
Group: Development/Libraries/Perl
-Url: http://search.cpan.org/dist/AnyEvent/
-#Source: http://www.cpan.org/modules/by-module/AnyEvent/AnyEvent-%{version}.tar.gz
-Source: AnyEvent-%{version}.tar.bz2
-BuildArch: noarch
+License: GNU General Public License version 2 or later or Artistic (GPLv2+ or Artistic)
BuildRoot: %{_tmppath}/%{name}-%{version}-build
%{perl_requires}
-BuildRequires: perl
BuildRequires: perl-macros
-#
Recommends: perl(Async::Interrupt) >= 1
Recommends: perl(EV) >= 3.05
Recommends: perl(Guard) >= 1.02
@@ -41,39 +36,61 @@
Recommends: perl(Net::SSLeay) >= 1.33
%description
-AnyEvent provides an identical interface to multiple event loops. This
-allows module authors to utilise an event loop without forcing module users
-to use the same event loop (as only a single event loop can coexist
-peacefully at any one time).
-
+AnyEvent provides a uniform interface to various event loops. This allows
+module authors to use event loop functionality without forcing module
+users to use a specific event loop implementation (since more than one
+event loop cannot coexist peacefully).
The interface itself is vaguely similar, but not identical to the Event
module.
- Author: Marc Lehmann