Main   Changelog   Spec   Patches   Sources   Download   Gear   Bugs and FR  Repocop 

#
#   - Data-Buffer -
#   This spec file was automatically generated by cpan2rpm [ver: 2.027]
#   (ALT Linux revision)
#   The following arguments were used:
#       --spec-only Data::Buffer
#   For more information on cpan2rpm please visit: http://perl.arix.com/
#

%define module Data-Buffer
%define m_distro Data-Buffer
%define m_name Data-Buffer
%define m_author_id unknown
%define _enable_test 1

Name: perl-Data-Buffer
Version: 0.04
Release: alt2.1

Summary: Data-Buffer - Read/write buffer class

License: Artistic
Group: Development/Perl
Url: http://www.cpan.org

Packager: Vitaly Lipatov <lav at altlinux.ru>

BuildArch: noarch
Source: http://search.cpan.org//CPAN/authors/id/B/BT/BTROTT/%m_distro-%version.tar.gz

# Automatically added by buildreq on Sat Aug 27 2005
BuildRequires: perl-devel

%description
*Data::Buffer* implements a low-level binary buffer in which
you can get and put integers, strings, and other data.
Internally the implementation is based on "pack" and "unpack",
such that *Data::Buffer* is really a layer on top of those
built-in functions.

All of the *get_** and *put_** methods respect the
internal offset state in the buffer object. This means that
you should read data out of the buffer in the same order that
you put it in. For example:

   $buf->put_int16(24);
   $buf->put_int32(1233455);
   $buf->put_int16(99);

   $buf->get_int16;   # 24
   $buf->get_int32;   # 1233455
   $buf->get_int16;   # 99

Of course, this assumes that you *know* the order of the data
items in the buffer. If your setup is such that your sending
and receiving processes won't necessarily know what's inside
the buffers they receive, take a look at the *TEMPLATE USAGE*
section.

%prep
%setup -q -n %m_distro-%version
%build
%perl_vendor_build

%install
%perl_vendor_install

%files
%perl_vendor_privlib/Data/

%changelog
…
Full changelog you can see here