Hello community,

here is the log from the commit of package perl-Event for openSUSE:Factory
checked in at Wed Jun 1 10:39:29 CEST 2011.



--------
--- perl-Event/perl-Event.changes       2010-12-01 14:44:23.000000000 +0100
+++ /mounts/work_src_done/STABLE/perl-Event/perl-Event.changes  2011-05-04 
09:58:49.000000000 +0200
@@ -1,0 +2,5 @@
+Wed May  4 07:36:15 UTC 2011 - [email protected]
+
+- updated to 1.15, no Changelog provided
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


Old:
----
  Event-1.13.tar.bz2

New:
----
  Event-1.15.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ perl-Event.spec ++++++
--- /var/tmp/diff_new_pack.0bVOEH/_old  2011-06-01 10:38:30.000000000 +0200
+++ /var/tmp/diff_new_pack.0bVOEH/_new  2011-06-01 10:38:30.000000000 +0200
@@ -1,7 +1,7 @@
 #
-# spec file for package perl-Event (Version 1.13)
+# spec file for package perl-Event
 #
-# 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,51 +15,81 @@
 # Please submit bugfixes or comments via http://bugs.opensuse.org/
 #
 
-# norootforbuild
 
 
 Name:           perl-Event
-Summary:        Event Loop Processing
-Version:        1.13
-Release:        4
-License:        Artistic
+Version:        1.15
+Release:        1
+License:        GPL+ or Artistic
+%define cpan_name Event
+Summary:        Event loop processing
+Url:            http://search.cpan.org/dist/Event/
 Group:          Development/Libraries/Perl
-Url:            http://search.cpan.org/dist/Event
-Source0:        http://www.cpan.org/authors/id/JPRIT/Event-%{version}.tar.bz2
-Source1:        %{name}-rpmlintrc
-Patch:          Event-1.0-warning.patch
+Source:         
http://www.cpan.org/authors/id/J/JP/JPRIT/%{cpan_name}-%{version}.tar.gz
+Patch0:         Event-1.0-warning.patch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
-%{perl_requires}
 BuildRequires:  perl
 BuildRequires:  perl-macros
+%{perl_requires}
 
 %description
-Event - A Generic Perl Event Loop
-
-This extension aims to provide an simple and optimized event loop for a
-broad class of applications.
-
-Available via http://www.perl.com/CPAN/authors/id/JPRIT/
+ALERT: Marc Lehmann may have taken over the future of event loops in Perl.
+Check out his libev library and EV Perl module. 25 Aug 2009
 
-
-
-Authors:
---------
-    Joshua Nathaniel Pritikin <[email protected]>
+The Event module provide a central facility to watch for various types of
+events and invoke a callback when these events occur. The idea is to delay
+the handling of events so that they may be dispatched in priority order
+when it is safe for callbacks to execute.
+
+Events (in the ordinary sense of the word) are detected by *watchers*,
+which reify them as *events* (in the special Event module sense). For
+clarity, the former type of events may be called "source events", and the
+latter "target events". Source events, such as signals arriving, happen
+whether or not they are being watched. If a source event occurs which a
+watcher is actively watching then the watcher generates a corresponding
+target event. Target events are only created by watchers. If several
+watchers are interested in the same source event then each will generate
+their own target event. Hence, any particular source event may result in
+zero, one, two, or any number of target events: the same as the number of
+watchers which were actively watching for it.
+
+Target events are queued to be processed in priority order (priority being
+determined by the creating watcher) and in FIFO order among events of the
+same priority. Queued ("pending") events can, in some cases, be cancelled
+before being processed. A queued event is processed by being passed to the
+callback function (or method on a particular object or class) which was
+specified to the watcher.
+
+A watcher, once created, operates autonomously without the Event user
+having to retain any reference to it. However, keeping a reference makes it
+possible to modify most of the watcher's characteristics. A watcher can be
+switched between active and inactive states. When inactive, it does not
+generate target events.
+
+Some types of source event are not reified as target events immediately.
+Signals received, for example, are counted initially. The counted signals
+are reified at certain execution points. Hence, signal events may be
+processed out of order, and if handled carelessly, on the wrong side of a
+state change in event handling. A useful way to view this is that
+occurrence of the source event is not actually the arrival of the signal
+but is triggered by the counting of the signal.
+
+Reification can be forced when necessary. The schedule on which some other
+events are created is non-obvious. This is especially the case with
+watchers that watch for a condition rather than an event. In some cases,
+target events are generated on a schedule that depends on the operation of
+the event loop.
 
 %prep
-%setup -n Event-%{version}
-%patch
+%setup -q -n %{cpan_name}-%{version}
+%patch0
 
 %build
-%{__perl} Makefile.PL OPTIMIZE="$RPM_OPT_FLAGS -Wall"
+%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE="%{optflags}"
 %{__make} %{?_smp_mflags}
 
-%ifnarch ppc64 s390x
-
 %check
 %{__make} test
-%endif
 
 %install
 %perl_make_install
@@ -67,10 +97,10 @@
 %perl_gen_filelist
 
 %clean
-%{__rm} -rf $RPM_BUILD_ROOT
+%{__rm} -rf %{buildroot}
 
 %files -f %{name}.files
-%defattr(-,root,root)
-%doc ANNOUNCE ChangeLog README* TODO Tutorial.pdf demo
+%defattr(-,root,root,755)
+%doc ANNOUNCE ChangeLog README README.EV TODO Tutorial.pdf 
Tutorial.pdf-errata.txt
 
 %changelog


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



Remember to have fun...

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to