File perl-RMI.spec of Package perl-RMI

Overview Repositories Revisions Requests Users Attributes Meta

File perl-RMI.spec of Package perl-RMI (Revision 4d76184cec27137f4736d07b6c16114e)

Currently displaying revision 4d76184cec27137f4736d07b6c16114e , Show latest

#
# spec file for package perl-RMI
#
# Copyright (c) 2019 SUSE LINUX 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 https://bugs.opensuse.org/
#

Name:           perl-RMI
Version:        0.08
Release:        0
%define cpan_name RMI
Summary:        Remote Method Invocation with transparent proxies v0.07
License:        Artistic-1.0 OR GPL-1.0-or-later
Group:          Development/Libraries/Perl
Url:            https://metacpan.org/release/%{cpan_name}
Source0:        https://cpan.metacpan.org/authors/id/S/SA/SAKOHT/%{cpan_name}-v%{version}.tar.gz
BuildArch:      noarch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  perl
BuildRequires:  perl-macros
BuildRequires:  perl(App::Prove)
BuildRequires:  perl(Test::More) >= 0.86
BuildRequires:  perl(version)
Requires:       perl(version)
%{perl_requires}

%description
RMI stands for Remote Method Invocation. The RMI modules allow one process
to have virtual object "stubs" which are proxies for real objects in
another process. When methods are invoked on the proxy, the method actually
runs in the other process. When results are returned, those values may also
be proxies for the real items in the other process. Parameters from the
client are also automatically proxied on the server side during method
execution.

In addition to invoking methods on proxy objects trasparently, an
RMI::Client can invoke class methods, regular function calls, and other
Perl functionaity on the remote server. Calls like these are typically the
first step to obtain a remote object in the first place. This is different
than implementations in other languages, which typically require that a
server have limited and specific objects it returns, with all further
proxying happening through them.

The procedure typically goes as follows:

1. a server is started which has access to some objects or data which is of
value

2. a client connects to that server, and asks that it execute code on its
behalf

3. the results returned may contain objects or other references, which the
client recieves as proxies which "seem like" the real thing

4. further interaction with the returned proxy objects/refs automatically
make calls through the client to the server internally

%prep
%setup -q -n %{cpan_name}-v%{version}
find . -type f ! -name \*.pl -print0 | xargs -0 chmod 644

%build
perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}

%check
make test

%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist

%files -f %{name}.files
%defattr(-,root,root,755)
%doc Changes examples prove-all.sh README
%license LICENSE

%changelog

Places

File perl-RMI.spec of Package perl-RMI (Revision 4d76184cec27137f4736d07b6c16114e)

Places