- updated to 1.03

Features:
     - Added options 'ssl_ca_file and 'ssl_ca_path' options
       to Event::RPC::Client, which enable SSL peer verifcation
       on the client. Thanks for the report about a security
       warning of IO::Socket::SSL to Moritz Bunkus.
 
     Features:
     - Added AnyEvent mainloop implementation.

OBS-URL: https://build.opensuse.org/package/show/devel:languages:perl/perl-Event-RPC?expand=0&rev=5

perl-Event-RPC.spec

@@ -1,66 +1,96 @@
-# vim: set sw=4 ts=4 et nu:
-# norootforbuild
+#
+# spec file for package perl-Event-RPC
+#
+# Copyright (c) 2013 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
+# upon. The license for this file, and modifications and additions to the
+# file, is the same license as for the pristine package itself (unless the
+# license for the pristine package is not an Open Source License, in which
+# case the license is the MIT License). An "Open Source License" is a
+# license that conforms to the Open Source Definition (Version 1.9)
+# published by the Open Source Initiative.
+
+# Please submit bugfixes or comments via http://bugs.opensuse.org/
+#
+
 
 Name:           perl-Event-RPC
-Version:        1.01
+Version:        1.03
 Release:        0
+%define cpan_name Event-RPC
 Summary:        Event based transparent Client/Server RPC framework
-Source:         http://search.cpan.org/CPAN/authors/id/J/JR/JRED/Event-RPC-%{version}.tar.gz
-URL:            http://search.cpan.org/dist/Event-RPC/
+License:        GPL-1.0+ or Artistic-1.0
 Group:          Development/Libraries/Perl
-License:        Perl License
-BuildRoot:      %{_tmppath}/build-%{name}-%{version}
-%{perl_requires}
-BuildRequires:  make perl
+Url:            http://search.cpan.org/dist/Event-RPC/
+Source:         http://www.cpan.org/authors/id/J/JR/JRED/%{cpan_name}-%{version}.tar.gz
+BuildArch:      noarch
+BuildRoot:      %{_tmppath}/%{name}-%{version}-build
+BuildRequires:  perl
 BuildRequires:  perl-macros
 BuildRequires:  perl(Event)
 BuildRequires:  perl(Glib)
-BuildRequires:  perl(IO::Socket::INET)
 BuildRequires:  perl(IO::Socket::SSL)
 BuildRequires:  perl(Net::SSLeay)
-BuildRequires:  perl(Storable)
-BuildRequires:  perl(Test::More)
+#BuildRequires: perl(AnyEvent)
+#BuildRequires: perl(Event::RPC)
+#BuildRequires: perl(Event::RPC::AuthPasswdHash)
+#BuildRequires: perl(Event::RPC::Client)
+#BuildRequires: perl(Event::RPC::Connection)
+#BuildRequires: perl(Event::RPC::LogConnection)
+#BuildRequires: perl(Event::RPC::Logger)
+#BuildRequires: perl(Event::RPC::Loop)
+#BuildRequires: perl(Event::RPC::Message)
+#BuildRequires: perl(Event::RPC::Server)
+#BuildRequires: perl(Event_RPC_Test)
+#BuildRequires: perl(Event_RPC_Test2)
 Requires:       perl(Event)
-#Recommends:     perl(Glib)
-Requires:       perl(IO::Socket::INET)
+Requires:       perl(Glib)
 Requires:       perl(IO::Socket::SSL)
 Requires:       perl(Net::SSLeay)
-Requires:       perl(Storable)
-Requires:       perl(Test::More)
+%{perl_requires}
 
 %description
-Event::RPC supports you in developing Event based networking client/server
-applications with transparent object/method access from the client to the
-server. Network communication is optionally encrypted using IO::Socket::SSL.
-Several event loop managers are supported due to an extensible API. Currently
-Event and Glib are implemented.
+Event::RPC consists of a server and a client library. The server exports a
+list of classes and methods, which are allowed to be called over the
+network. More specific it acts as a proxy for objects created on the server
+side (on demand of the connected clients) which handles client side methods
+calls with transport of method arguments and return values.
+
+The object proxy handles refcounting and destruction of objects created by
+clients properly. Objects as method parameters and return values are
+handled as well (although with some limitations, see below).
+
+For the client the whole thing is totally transparent - once connected to
+the server it doesn't know whether it calls methods on local or remote
+objects.
+
+Also the methods on the server newer know whether they are called locally
+or from a connected client. Your application logic is not affected by
+Event::RPC at all, at least if it has a rudimentary clean OO design.
+
+For details on implementing servers and clients please refer to the man
+pages of Event::RPC::Server and Event::RPC::Client.
 
 %prep
-%setup -q -n "Event-RPC-%{version}"
-%__sed -i '/^auto_install/d' Makefile.PL
+%setup -q -n %{cpan_name}-%{version}
+find . -type f -print0 | xargs -0 chmod 644
 
 %build
-%__perl Makefile.PL PREFIX="%{_prefix}"
-%__make %{?jobs:-j%{jobs}}
+%{__perl} Makefile.PL INSTALLDIRS=vendor
+%{__make} %{?_smp_mflags}
+
+%check
+%{__make} test
 
 %install
 %perl_make_install
 %perl_process_packlist
+%perl_gen_filelist
 
-%check
-%__make test
-
-%clean
-%{?buildroot:%__rm -rf "%{buildroot}"}
-
-%files
-%defattr(-,root,root)
-%doc Changes README
-%dir %{perl_vendorlib}/Event
-%{perl_vendorlib}/Event/RPC.pm
-%{perl_vendorlib}/Event/RPC
-%dir %{perl_vendorarch}/auto/Event
-%{perl_vendorarch}/auto/Event/RPC
-%doc %{perl_man3dir}/Event::RPC.%{perl_man3ext}%{ext_man}
-%doc %{perl_man3dir}/Event::RPC::*.%{perl_man3ext}%{ext_man}
+%files -f %{name}.files
+%defattr(-,root,root,755)
+%doc Changes examples README
 
+%changelog