| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: perl-File-FcntlLock | Distribution: openSUSE Tumbleweed |
| Version: 0.22 | Vendor: openSUSE |
| Release: 1.13 | Build date: Tue Apr 14 20:13:28 2015 |
| Group: Development/Libraries/Perl | Build host: reproducible |
| Size: 101061 | Source RPM: perl-File-FcntlLock-0.22-1.13.src.rpm |
| Packager: https://bugs.opensuse.org | |
| Url: http://search.cpan.org/dist/File-FcntlLock/ | |
| Summary: File locking with L<fcntl(2)> | |
File locking in Perl is usually done using the 'flock' function. Unfortunately, this only allows locks on whole files and is often implemented in terms of the the flock(2) manpage system function which has some shortcomings (especially concerning locks on remotely mounted file systems) and slightly different behaviour than the fcntl(2) manpage. Using this module file locking via the fcntl(2) manpage can be done (obviously, this restricts the use of the module to systems that have a the fcntl(2) manpage system call). Before a file (or parts of a file) can be locked, an object simulating a flock structure, containing information in a binary format to be passed to the fcntl(2) manpage for locking requests, must be created and its properties set. Afterwards, by calling the the lock() manpage method a lock can be set and removed or it can be determined if and which process currently holds the lock. File::FcntlLock (or its alias File::FcntlLock::XS) uses a shared library, build during installation, to call the the fcntl(2) manpage system function directly. If this is unsuitable there are two alternatives, File::FcntlLock::Pure and File::FcntlLock::Inline. Both call the Perl 'fcntl' function instead and use Perl code to assemble and disassemble the structure. For this at some time the (system-dependent) binary layout of the flock structure must have been determined via a program written in C. The difference between File::FcntlLock::Pure and File::FcntlLock::Inline is that for the former this happened when the package is installed while for the latter it is done each time the package is loaded (e.g., with 'use'). Thus, for File::FcntlLock::Inline to work a C compiler must be available. There are some minor differences in the functionality and the behaviour on passing the method for locking invalid arguments to be described below.
Artistic-1.0 or GPL-1.0+
* Tue Apr 14 2015 coolo@suse.com
- updated to 0.22
see /usr/share/doc/packages/perl-File-FcntlLock/Changes
0.22 Thu July 31 2014
- Exports still didn't work from the XS, Pure and Inline modules,
hopefully fixed.
0.21 Thu July 31 2014
- Missing @EXPORT of constants fixed with patch supplied by
Raphaël Hertzog <hertzog@debian.org> (thank you;-)
* Fri Jul 25 2014 coolo@suse.com
- updated to 0.20
- Problem on GNU Hurd hopefully fixed and some cosmetic changes.
0.19 Tue May 27 2014
- Builds failed on 32-bit systems due to missing CFLAGS derived
from the Perl installation.
0.18 Mon May 26 2014
- CPAN didn't find the version number in FcntlLock.pm which
was derived from that of Core.pm:-(
0.17 Mon May 26 2014
- CPAN testing showed that there are 32-bit systems where the
off_t member of the flock struct is a 64-bit integer but Perl
doesn't support the 'q' format for pack() and unpack(). On these
systems there seem to be no good way of assembling a flock
structure useing "pure Perl" and thus the File::FcntlLock::Pure
and File::FcntlLock::Inline modules won't get installed.
0.16 Sun May 25 2014
- Missing file in 0.15, Pure.pm, in MANIFEST added.
0.15 Thu May 20 2014
- Module rewritten as three modules, one working
exactly as before, and two new ones that instead of
being XS-based use Perl code. For the first one the
Perl code for packing/unpacking the C flock struct is
generated when 'perl Makefile.PL' is run. For the other
a C program is created, compiled and run each time the
module gets loaded. This is in response to some concerns
the Debian dpkg package managers (who use the module) had
for certain circumstances when new Perl versions need to
be installed (as far as I understand;-)
* Tue Sep 25 2012 frank.lichtenheld@sophos.com
- initial packaging based on cpanspec
* made backwards compatible to SLE 11 SP2
/usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock.pm /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock.pod /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock/Core.pm /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock/Errors.pm /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock/Inline.pm /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock/Inline.pod /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock/Pure.pm /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock/Pure.pod /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock/XS.pm /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/File/FcntlLock/XS.pod /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/auto/File /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/auto/File/FcntlLock /usr/lib/perl5/vendor_perl/5.40.0/riscv64-linux-thread-multi/auto/File/FcntlLock/FcntlLock.so /usr/share/doc/packages/perl-File-FcntlLock /usr/share/doc/packages/perl-File-FcntlLock/Changes /usr/share/doc/packages/perl-File-FcntlLock/README /usr/share/man/man3/File::FcntlLock.3pm.gz /usr/share/man/man3/File::FcntlLock::Inline.3pm.gz /usr/share/man/man3/File::FcntlLock::Pure.3pm.gz /usr/share/man/man3/File::FcntlLock::XS.3pm.gz
Generated by rpm2html 1.8.1
Fabrice Bellet, Wed Nov 13 00:41:02 2024