Result:
found more than 673 distributions - search limited to the first 2001 files matching your query
( run in 0.937 )
Archive-Extract-Libarchive
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.68.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
Archive-Har
view release on metacpan or search on metacpan
],
"cookies": [],
"content": {
"size": 136732,
"mimeType": "text/javascript",
"text": "/* _GlobalPrefix_ */\nthis.gbar_=this.gbar_||{};(function(_){var window=this;\n/* _Module_:syp */\ntry{\nvar On=function(){};_.y(On,Error);_.Pn=function(){this.b=\"pending\";this.B=[];this.w=this.C=void 0};_.ae(_.Pn);var Qn=funct...
},
"redirectURL": "",
"headersSize": -1,
"bodySize": 0,
"_transferSize": 0
Archive-Ipkg
view release on metacpan or search on metacpan
return $self->{version};
}
# verification
sub verify {
my $self = shift;
my $verify = undef;
# required: package, version, architecture, maintainer, section, description
$verify .= "No package name\n" unless (defined $self->{name});
# version should be at least empty
$verify .= "No version\n" unless (defined $self->{architecture});
$verify .= "No architecture\n" unless (defined $self->{architecture});
$verify .= "No maintainer\n" unless (defined $self->{maintainer});
$verify .= "No section\n" unless (defined $self->{section});
$verify .= "No description\n" unless (defined $self->{description});
return $verify;
}
# file handling
sub add_files {
}
sub data {
my $self = shift;
return undef if $self->verify;
# make control package
$self->{TAR_CONTROL} = Archive::Tar->new();
$self->{TAR_CONTROL}->add_data("./control", $self->control, { mode => 0100644 });
foreach (qw(preinst postinst prerm postrm)) {
=item C<$ctl = $ipkg-E<gt>control()>
Returns the text of the control file that will be written. You just need this
if you want to check the file.
=item C<$errmsg = $ipkg-E<gt>verify()>
Verifies whether the archive can be written by checking whether at least the
required properties are set (see below).
Returns an error message if unsuccessful, else undef (!).
=over 4
=item C<$ipkg-E<gt>sloppy_checks>
Will switch of all syntax checks in accessor functions. C<verify> will still
check whether all required properties are set.
=item C<$ipkg-E<gt>strict_checks>
Re-enables syntax checks in accessor functions (this is the default).
Archive-Libarchive-XS
view release on metacpan or search on metacpan
xs/ppport.h view on Meta::CPAN
F<xs/ppport.h> on your source code. See the next section for
details.
=head1 EXAMPLES
To verify whether F<xs/ppport.h> is needed for your module, whether you
should make any changes to your code, and whether any special defines
should be used, F<xs/ppport.h> can be run as a Perl script to check your
source code. Simply say:
perl xs/ppport.h
xs/ppport.h view on Meta::CPAN
vTHX|5.006000||Viu
VT_NATIVE|5.021004||Viu
vtohl|5.003007||Viu
vtohs|5.003007||Viu
VUTIL_REPLACE_CORE|5.019008||Viu
vverify|5.009003|5.009003|
VVERIFY|5.019008||Viu
vwarn|5.006000|5.006000|
vwarner|5.006000|5.006000|p
wait4pid|5.003007||Viu
wait|5.005000||Viu
Archive-Peek-External
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.68.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
Archive-Peek-Libarchive
view release on metacpan or search on metacpan
F<ppport.h> on your source code. See the next section for
details.
=head1 EXAMPLES
To verify whether F<ppport.h> is needed for your module, whether you
should make any changes to your code, and whether any special defines
should be used, F<ppport.h> can be run as a Perl script to check your
source code. Simply say:
perl ppport.h
vmess|5.006000||p
vnewSVpvf|5.006000|5.004000|p
vnormal||5.009002|
vnumify||5.009000|
vstringify||5.009000|
vverify||5.009003|
vwarner||5.006000|
vwarn||5.006000|
wait4pid|||
warn_nocontext|||pvn
warn_sv|5.013001||p
Archive-Probe
view release on metacpan or search on metacpan
t/deep_nest_all_test.t view on Meta::CPAN
});
my $base = catdir($test_data_dir, $test_data_no);
$probe->reset_matches();
$probe->search($base, 1);
# verify that the .abc file is found
my $exp = catdir(
'a.rar__',
'b.tgz__',
'c.bz2__',
'd.zip__',
t/deep_nest_all_test.t view on Meta::CPAN
$probe->working_dir($tmpdir);
$base = catdir($test_data_dir, $test_data_no, "a.rar");
$probe->reset_matches();
$probe->search($base, 1);
# verify that the .abc file is found
is(
$map->{abc},
$exp,
'file search in deep nested archive(start w/ file)'
);
Archive-Raw
view release on metacpan or search on metacpan
F<ppport.h> on your source code. See the next section for
details.
=head1 EXAMPLES
To verify whether F<ppport.h> is needed for your module, whether you
should make any changes to your code, and whether any special defines
should be used, F<ppport.h> can be run as a Perl script to check your
source code. Simply say:
perl ppport.h
vmess|5.006000|5.006000|p
vnewSVpvf|5.006000|5.004000|p
vnormal||5.009002|
vnumify||5.009000|
vstringify||5.009000|
vverify||5.009003|
vwarner||5.006000|
vwarn||5.006000|
wait4pid|||
warn_nocontext|||pvn
warn_sv|5.013001||p
Archive-SCS
view release on metacpan or search on metacpan
lib/Archive/SCS/HashFS.pm view on Meta::CPAN
}
$crc == $entry->{crc}
or warnings::warnif io =>
sprintf "%s: Found CRC32 %08X, expected %08X",
$path->basename, $crc, $entry->{crc};
# The official SCS extractor doesn't seem to verify the CRC
# Parse directory listing
$entry->{is_dir} or return $data;
my %dir_index;
Archive-Tar-Builder
view release on metacpan or search on metacpan
src/ppport.h view on Meta::CPAN
F<ppport.h> on your source code. See the next section for
details.
=head1 EXAMPLES
To verify whether F<ppport.h> is needed for your module, whether you
should make any changes to your code, and whether any special defines
should be used, F<ppport.h> can be run as a Perl script to check your
source code. Simply say:
perl ppport.h
src/ppport.h view on Meta::CPAN
vmess||5.006000|
vnewSVpvf|5.006000|5.004000|p
vnormal||5.009002|
vnumify||5.009000|
vstringify||5.009000|
vverify||5.009003|
vwarner||5.006000|
vwarn||5.006000|
wait4pid|||
warn_nocontext|||vn
warner_nocontext|||vn
Archive-Tar
view release on metacpan or search on metacpan
t/02_methods.t view on Meta::CPAN
### write tar tests
{ my $out = $OUT_TAR_FILE;
### bug #41798: 'Nonempty $\ when writing a TAR file produces a
### corrupt TAR file' shows that setting $\ breaks writing tar files
### set it here purposely so we can verify NOTHING breaks
local $\ = 'FOOBAR';
{ ### write()
ok( $obj->write($out),
" Wrote tarfile using 'write'" );
Archive-TarGzip
view release on metacpan or search on metacpan
t/Archive/Data/Secs2.pm view on Meta::CPAN
# 'ascii'
# ]
#
##################
# verify write configuration
#
[config('type')]
# [
Archive-Unzip-Burst
view release on metacpan or search on metacpan
F<ppport.h> on your source code. See the next section for
details.
=head1 EXAMPLES
To verify whether F<ppport.h> is needed for your module, whether you
should make any changes to your code, and whether any special defines
should be used, F<ppport.h> can be run as a Perl script to check your
source code. Simply say:
perl ppport.h
( run in 0.937 second using v1.01-cache-2.11-cpan-39bf76dae61 )