view release on metacpan or  search on metacpan

lib/Alien/Build.pm  view on Meta::CPAN

      {
        before => sub {
          $tmp = Alien::Build::TempDir->new($self, "download");
          $CWD = "$tmp";
        },
        verify => sub {
          my @list = grep { $_->basename !~ /^\./, } _path('.')->children;

          my $count = scalar @list;

          if($count == 0)

lib/Alien/Build.pm  view on Meta::CPAN

      # will be used for the build step, and technically
      # extract is a substage of build anyway.
      $tmp = Alien::Build::TempDir->new($self, $nick_name);
      $CWD = "$tmp";
    },
    verify => sub {

      my $path = '.';
      if($self->meta_prop->{out_of_source} && $self->install_prop->{extract})
      {
        $path = $self->install_prop->{extract};

lib/Alien/Build.pm  view on Meta::CPAN

    $args{before}->() if $args{before};
    if(ref($hook) eq 'CODE')
    {
      $value = eval {
        my $value = $wrapper->(sub { $hook->(@_) }, @args);
        $args{verify}->('code') if $args{verify};
        $value;
      };
    }
    else
    {
      $value = $wrapper->(sub {
        eval {
          $hook->execute(@_);
          $args{verify}->('command') if $args{verify};
        };
        defined $args{ok} ? $args{ok} : 1;
      }, @args);
    }
    $error = $@;

lib/Alien/Build.pm  view on Meta::CPAN

Same as C<destdir_filter> except applies to C<build_ffi> instead of C<build>.

=item digest

This properties contains the cryptographic digests (if any) that should
be used when verifying any fetched and downloaded files.  It is a hash
reference where the key is the filename and the value is an array
reference containing a pair of values, the first being the algorithm
('SHA256' is recommended) and the second is the actual digest.  The
special filename C<*> may be specified to indicate that any downloaded
file should match that digest.  If there are both real filenames and

 view release on metacpan or  search on metacpan

SIGNATURE  view on Meta::CPAN

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

 view release on metacpan or  search on metacpan

SIGNATURE  view on Meta::CPAN

This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.

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

 view release on metacpan or  search on metacpan

src/Source/FreeImage/PluginEXR.cpp  view on Meta::CPAN

	half *halfData = NULL;

	if(!dib || !handle) return FALSE;

	try {
		// check for EXR_LC compression and verify that the format is RGB
		if((flags & EXR_LC) == EXR_LC) {
			FREE_IMAGE_TYPE image_type = FreeImage_GetImageType(dib);
			if(((image_type != FIT_RGBF) && (image_type != FIT_RGBAF)) || ((flags & EXR_FLOAT) == EXR_FLOAT)) {
				THROW (Iex::IoExc, "EXR_LC compression is only available with RGB[A]F images");
			}

 view release on metacpan or  search on metacpan

lib/Alien/Gnuplot.pm  view on Meta::CPAN

=head1 NAME

Alien::Gnuplot - Find and verify functionality of the gnuplot executable.

=head1 SYNOPSIS

 package MyGnuplotter;

lib/Alien/Gnuplot.pm  view on Meta::CPAN

setting the environment variable GNUPLOT_BINARY to the path.  Otherwise
your path will be searched (using File::Spec) for the executable file.

If there is no executable application in your path or in the location
pointed to by GNUPLOT_BINARY, then the module throws an exception.
You can also verify that it has not completed successfully, by
examining $Alien::Gnuplot::version, which is undefined in case of
failure and contains the gnuplot version string on success.

If you think the global state of the gnuplot executable may have
changed, you can either reload the module or explicitly call

 view release on metacpan or  search on metacpan

doc/html/AutoCompleter.html  view on Meta::CPAN

  <div class="TN_node" id="onLegalValue">
    <h3 class="TN_label">onLegalValue</h3>
    <div class="TN_content">
      <p>This event is triggered when the autocompleter is in strict mode,
the input field has just been left (<code>onBlur</code> event), and the 
autocompleter was able to verify that the current input value
belongs to the list of available choices.</p>
<p>The event contains a <code>value</code> property (current value in the 
input element), and a <code>choice</code> property (member of the 
<code>choices</code> array that matches the current value).
The <code>controller</code> property is null because the event may

doc/html/AutoCompleter.html  view on Meta::CPAN

  <div class="TN_node" id="onIllegalValue">
    <h3 class="TN_label">onIllegalValue</h3>
    <div class="TN_content">
      <p>This event is triggered when the autocompleter is in strict mode,
the input field has just been left (<code>onBlur</code> event), and the 
autocompleter was not able to verify that the current input value
belongs to the list of available choices.</p>
<p>The event only contains a <code>value</code> property (current value in the 
input element). The <code>controller</code> property is null (same reasons
as <code>onLegalValue</code> above).</p>
<p>return <code>true</code> in onIllegalValue handler to override the illegal behavior; i.e. coloring the 

 view release on metacpan or  search on metacpan

src/judy-1.0.5/autom4te.cache/output.0  view on Meta::CPAN

	mmap private fixed at somewhere currently unmapped
	mmap private fixed at somewhere already mapped
	mmap shared not fixed
	mmap shared fixed at somewhere currently unmapped
	mmap shared fixed at somewhere already mapped
   For private mappings, we should verify that changes cannot be read()
   back from the file, nor mmap's back from the file at a different
   address.  (There have been systems where private was not correctly
   implemented like the infamous i386 svr4.0, and systems where the
   VM page cache was not coherent with the file system buffer cache
   like early versions of FreeBSD and possibly contemporary NetBSD.)
   For shared mappings, we should conversely verify that changes get
   propagated back to all the places they're supposed to be.

   Grep wants private fixed already mapped.
   The main things grep needs to know about mmap are:
   * does it exist and is it safe to write into the mmap'd area

 view release on metacpan or  search on metacpan

libjit/jit/jit-compile.c  view on Meta::CPAN

 * @code{JIT_RESULT_OUT_OF_MEMORY}, @code{JIT_RESULT_COMPILE_ERROR} or
 * possibly some other more specific @code{JIT_RESULT_} code.
 *
 * Normally this function should not be used because @code{jit_compile}
 * performs all the optimization anyway.  However it might be useful for
 * debugging to verify the effect of the @code{libjit} code optimization.
 * This might be done, for instance, by calling @code{jit_dump_function}
 * before and after @code{jit_optimize}.
 * @end deftypefun
@*/
int

 view release on metacpan or  search on metacpan

SIGNATURE  view on Meta::CPAN

This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.81.

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

 view release on metacpan or  search on metacpan

lib/Alien/Libarchive/Installer.pm  view on Meta::CPAN

=over 4

=item test

Specifies the test type that should be used to verify the integrity
of the system libarchive.  Generally this should be
set according to the needs of your module.  Should be one of:

=over 4

=item compile

use L<test_compile_run|Alien::Libarchive::Installer#test_compile_run> to verify.
This is the default.

=item ffi

use L<test_ffi|Alien::Libarchive::Installer#test_ffi> to verify

=item both

use both
L<test_compile_run|Alien::Libarchive::Installer#test_compile_run>
and
L<test_ffi|Alien::Libarchive::Installer#test_ffi>
to verify

=back

=item alien

lib/Alien/Libarchive/Installer.pm  view on Meta::CPAN

Empty directory to be used to extract the libarchive
source and to build from.

=item test

Specifies the test type that should be used to verify the integrity
of the build after it has been installed.  Generally this should be
set according to the needs of your module.  Should be one of:

=over 4

=item compile

use L<test_compile_run|Alien::Libarchive::Installer#test_compile_run> to verify.
This is the default.

=item ffi

use L<test_ffi|Alien::Libarchive::Installer#test_ffi> to verify

=item both

use both
L<test_compile_run|Alien::Libarchive::Installer#test_compile_run>
and
L<test_ffi|Alien::Libarchive::Installer#test_ffi>
to verify

=back

=back

 view release on metacpan or  search on metacpan

inc/Alien/LZO/Installer.pm  view on Meta::CPAN

=over 4

=item test

Specifies the test type that should be used to verify the integrity
of the system lzo.  Generally this should be
set according to the needs of your module.  Should be one of:

=over 4

=item compile

use L<test_compile_run|Alien::LZO::Installer#test_compile_run> to verify.
This is the default.

=item ffi

use L<test_ffi|Alien::LZO::Installer#test_ffi> to verify

=item both

use both
L<test_compile_run|Alien::LZO::Installer#test_compile_run>
and
L<test_ffi|Alien::LZO::Installer#test_ffi>
to verify

=back

=item alien

inc/Alien/LZO/Installer.pm  view on Meta::CPAN

Empty directory to be used to extract the lzo
source and to build from.

=item test

Specifies the test type that should be used to verify the integrity
of the build after it has been installed.  Generally this should be
set according to the needs of your module.  Should be one of:

=over 4

=item compile

use L<test_compile_run|Alien::LZO::Installer#test_compile_run> to verify.
This is the default.

=item ffi

use L<test_ffi|Alien::LZO::Installer#test_ffi> to verify

=item both

use both
L<test_compile_run|Alien::LZO::Installer#test_compile_run>
and
L<test_ffi|Alien::LZO::Installer#test_ffi>
to verify

=back

=back

 view release on metacpan or  search on metacpan

t/base.t  view on Meta::CPAN

use Test::Alien;
use Alien::Libdogecoin;

alien_ok 'Alien::Libdogecoin';
my @symbols = qw(
    dogecoin_ecc_start dogecoin_ecc_stop generatePrivPubKeypair verifyPrivPubKeypair verifyP2pkhAddress
);

ok scalar Alien::Libdogecoin->dynamic_libs, 'Dynamic libs returns true';

ffi_ok { symbols => \@symbols, api => 1 }, with_subtest {

t/base.t  view on Meta::CPAN

    for my $name (qw( dogecoin_ecc_start dogecoin_ecc_stop )) {
        my $func = $ffi->function( $name => [] => 'void' );
        is $func->call(), undef, "$name() returns nothing";
    }

    my $verify = $ffi->function( verifyP2pkhAddress => ['string', 'uchar'] => 'int' );
    is $verify->call( 'DFhv7MMnDBGeaNmKybvfwF3HaJxN3Dtg3y', 34 ), 1, '... and verifyP2pkhAddress should succeed';
    is $verify->call( 'DFhv7MMnDBGeaNmKybvfwF3HaJxN3D', 30 ), 0, '... or fail as appropriate';
};

done_testing;

 view release on metacpan or  search on metacpan

dist.ini  view on Meta::CPAN

[ShareDir]              ; include `share/' for File::ShareDir
[ModuleBuild::Custom]   ; create Build.PL from template
mb_version = 0.2808_01  ; version available in 5.10.0
[Manifest]              ; build MANIFEST file (do this last)

; verify and release the distribution
; XXX: disabled for now - testing would require installation
;[TestRelease]           ; run tests before releasing
[ConfirmRelease]        ; ask to confirm release/upload
[UploadToCPAN]          ; push it to CPAN
[Git::Push]             ; push everything to remote repository

 view release on metacpan or  search on metacpan

t/c/test.c  view on Meta::CPAN

#include <libxml/parser.h>
#include <libxml/tree.h>

/*
 * C version of the test can be used to see verify if alien is doing something wonky
 * compile and run with pkg-config:
 * cc `pkg-config --cflags libxml-2.0` t/c/test.c `pkg-config --libs libxml-2.0` && ./a.out
 * compile and run with xml2-config:
 * cc `xml2-config --cflags` t/c/test.c  `xml2-config --libs` && ./a.out
 */

 view release on metacpan or  search on metacpan

SIGNATURE  view on Meta::CPAN

This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.79.

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

 view release on metacpan or  search on metacpan

t/01-signature.t  view on Meta::CPAN

      "Set the environment variable TEST_SIGNATURE to enable this test.";
}
elsif (!eval { require Module::Signature; 1 }) {
    plan skip_all => 
      "Next time around, consider installing Module::Signature, ".
      "so you can verify the integrity of this distribution.";
}
elsif ( !-e 'SIGNATURE' ) {
    plan skip_all => "SIGNATURE not found";
}
elsif ( -s 'SIGNATURE' == 0 ) {

t/01-signature.t  view on Meta::CPAN

}
else {
    plan tests => 1;
}

my $ret = Module::Signature::verify();
SKIP: {
    skip "Module::Signature cannot verify", 1 
      if $ret eq Module::Signature::CANNOT_VERIFY();

    cmp_ok $ret, '==', Module::Signature::SIGNATURE_OK(), "Valid signature";
}

 view release on metacpan or  search on metacpan

inc/inc_Module-Build/Module/Build.pm  view on Meta::CPAN

[version 0.2806]

This is just like the C<test> action, but doesn't actually build the
distribution first, and doesn't add F<blib/> to the load path, and
therefore will test against a I<previously> installed version of the
distribution.  This can be used to verify that a certain installed
distribution still works, or to see whether newer versions of a
distribution still pass the old regression tests, and so on.

=item skipcheck

 view release on metacpan or  search on metacpan

corpus/autoheck-libpalindrome/ltmain.sh  view on Meta::CPAN

      rmfiles=$file

      case $name in
      *.la)
	# Possibly a libtool archive, so verify it.
	if func_lalib_p "$file"; then
	  func_source $dir/$name

	  # Delete the libtool libraries and symlinks.
	  for n in $library_names; do

corpus/autoheck-libpalindrome/ltmain.sh  view on Meta::CPAN

	  esac
	fi
	;;

      *.lo)
	# Possibly a libtool object, so verify it.
	if func_lalib_p "$file"; then

	  # Read the .lo file
	  func_source $dir/$name

 view release on metacpan or  search on metacpan

patches/SDL-1.2.14-ltmain_sh  view on Meta::CPAN

      rmfiles="$file"

      case $name in
      *.la)
	# Possibly a libtool archive, so verify it.
	if func_lalib_p "$file"; then
	  func_source $dir/$name

	  # Delete the libtool libraries and symlinks.
	  for n in $library_names; do

patches/SDL-1.2.14-ltmain_sh  view on Meta::CPAN

	  esac
	fi
	;;

      *.lo)
	# Possibly a libtool object, so verify it.
	if func_lalib_p "$file"; then

	  # Read the .lo file
	  func_source $dir/$name

 view release on metacpan or  search on metacpan

MANIFEST  view on Meta::CPAN

src/subversion/subversion/tests/cmdline/svntest/main.py
src/subversion/subversion/tests/cmdline/svntest/objects.py
src/subversion/subversion/tests/cmdline/svntest/sandbox.py
src/subversion/subversion/tests/cmdline/svntest/testcase.py
src/subversion/subversion/tests/cmdline/svntest/tree.py
src/subversion/subversion/tests/cmdline/svntest/verify.py
src/subversion/subversion/tests/cmdline/svntest/wc.py
src/subversion/subversion/tests/cmdline/svnversion_tests.py
src/subversion/subversion/tests/cmdline/switch_tests.py
src/subversion/subversion/tests/cmdline/theta.bin
src/subversion/subversion/tests/cmdline/trans_tests.py

MANIFEST  view on Meta::CPAN

src/subversion/tools/dev/svnqlite3-dump
src/subversion/tools/dev/svnraisetreeconflict/svnraisetreeconflict.c
src/subversion/tools/dev/trails.py
src/subversion/tools/dev/unix-build/Makefile.svn
src/subversion/tools/dev/unix-build/README
src/subversion/tools/dev/verify-history.py
src/subversion/tools/dev/warn-ignored-err.sh
src/subversion/tools/dev/wc-format.py
src/subversion/tools/dev/wc-ng/bump-to-19.py
src/subversion/tools/dev/wc-ng/count-progress.py
src/subversion/tools/dev/wc-ng/gather-data.sh

MANIFEST  view on Meta::CPAN

src/subversion/tools/hook-scripts/svnperms.conf.example
src/subversion/tools/hook-scripts/svnperms.py
src/subversion/tools/hook-scripts/validate-extensions.py
src/subversion/tools/hook-scripts/validate-files.conf.example
src/subversion/tools/hook-scripts/validate-files.py
src/subversion/tools/hook-scripts/verify-po.py
src/subversion/tools/po/l10n-report.py
src/subversion/tools/po/po-update.sh
src/subversion/tools/server-side/fsfs-reshard.py
src/subversion/tools/server-side/fsfs-stats.c
src/subversion/tools/server-side/mod_dontdothat/mod_dontdothat.c

 view release on metacpan or  search on metacpan

SIGNATURE  view on Meta::CPAN

This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.79.

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

 view release on metacpan or  search on metacpan

alienfile  view on Meta::CPAN

    test sub {
        my ($build) = @_;
        my $runTests_dir = path( $build->{install_prop}->{extract}, 'tests' );

        my @test_logs = map { path $runTests_dir, $_ }
          qw(test_basic.log test_isa.log test_verify.log);
        for (@test_logs) {
            open my $fh, '<', $_
              or croak("Can't open test log file $_\n");
            ## localize record separator to undef and then slurp all
            ## file contents

 view release on metacpan or  search on metacpan

share/swagger-ui-bundle.js.map  view on Meta::CPAN

{"version":3,"sources":["webpack://SwaggerUIBundle/webpack/universalModuleDefinition","webpack://SwaggerUIBundle/webpack/bootstrap","webpack://SwaggerUIBundle/./node_modules/react/react.js","webpack://SwaggerUIBundle/./node_modules/immutable/dist/imm...

 view release on metacpan or  search on metacpan

dist.ini  view on Meta::CPAN

;;[Test::Kwalitee]
;;skiptest = use_strict
[Test::ReportPrereqs]
:version = 0.022
version_extractor = Module::Metadata
verify_prereqs = 1

[@Git]
allow_dirty = dist.ini
push_to     = origin master:master
tag_format  = %v

 view release on metacpan or  search on metacpan

src/tccgen.c  view on Meta::CPAN

        pstrcat(buf, buf_size, varstr);
    }
 no_var: ;
}

/* verify type compatibility to store vtop in 'dt' type, and generate
   casts if needed. */
static void gen_assign_cast(CType *dt)
{
    CType *st, *type1, *type2, tmp_type1, tmp_type2;
    char buf1[256], buf2[256];

 view release on metacpan or  search on metacpan

src/tccgen.c  view on Meta::CPAN

        pstrcat(buf, buf_size, varstr);
    }
 no_var: ;
}

/* verify type compatibility to store vtop in 'dt' type, and generate
   casts if needed. */
static void gen_assign_cast(CType *dt)
{
    CType *st, *type1, *type2, tmp_type1, tmp_type2;
    char buf1[256], buf2[256];

 view release on metacpan or  search on metacpan

inc/inc_Module-Build/Module/Build.pm  view on Meta::CPAN

[version 0.2806]

This is just like the C<test> action, but doesn't actually build the
distribution first, and doesn't add F<blib/> to the load path, and
therefore will test against a I<previously> installed version of the
distribution.  This can be used to verify that a certain installed
distribution still works, or to see whether newer versions of a
distribution still pass the old regression tests, and so on.

=item skipcheck