Result:
found more than 1401 distributions - search limited to the first 2001 files matching your query
( run in 1.470 )
App-Benchmark-Accessors
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-Bernard
view release on metacpan or search on metacpan
lib/App/Bernard/Magic/Single.pm view on Meta::CPAN
sub replace_inplace {
my ($settings) = @_;
if ($settings->{'inplace'}) {
rename $settings->{'output'}, $settings->{'input'};
}
}
sub handle {
App-BigQuery-Importer-MySQL
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-Bin4TSV
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-BinPackUtils
view release on metacpan or search on metacpan
lib/App/BinPackUtils.pm view on Meta::CPAN
mkdir $bin_name or return [500, "Can't create directory $bin_name: $!"];
}
# move files to bins
for my $row (@rows) {
log_info "Moving '$row->{file}' to $row->{bin} ...";
rename($row->{file}, "$row->{bin}/$row->{file}") or do {
log_warn "Can't move '$row->{file}' to $row->{bin}/: $!, skipped";
};
}
}
App-BitBucketCli
view release on metacpan or search on metacpan
Fixing required params (Ivan Wills)
Setting up getting default host/user/pass (Ivan Wills)
Fixed last missing headings (Ivan Wills)
Jenkins API words (Ivan Wills)
Adding missing method headings (Ivan Wills)
Fixed renamed file (Ivan Wills)
Added words to skip (Ivan Wills)
Updated date (Ivan Wills)
Added new files to manifest (Ivan Wills)
Removed unused dist dir (Ivan Wills)
Fixed typo (Ivan Wills)
App-Bitcoin-PaperWallet
view release on metacpan or search on metacpan
site such as uunet.uu.net, or by allowing the Copyright Holder to include
your modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict
with standard executables, which must also be provided, and provide
a separate manual page for each non-standard executable that clearly
documents how it differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-BlockWebFlooders
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-BloomUtils
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-BluetoothUtils
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-Bondage
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-BoolFindGrep
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-Bootstrap-Perl
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-Bootstrap
view release on metacpan or search on metacpan
lib/App/Bootstrap.pm view on Meta::CPAN
Version 0.02
=head1 DESCRIPTION
This module has been renamed App::Install. Go use that instead. I'll
be deleting this stub at the end of July 2007.
=cut
our $VERSION = '0.02';
App-BorderStyleUtils
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-BorgRestore
view release on metacpan or search on metacpan
lib/App/BorgRestore/DB.pm view on Meta::CPAN
1 => sub {
$self->{dbh}->do('create table if not exists `files` (`path` text, primary key (`path`)) without rowid;');
$self->{dbh}->do('create table if not exists `archives` (`archive_name` text unique);');
},
2 => sub {
$self->{dbh}->do('alter table `archives` rename to `archives_old`');
$self->{dbh}->do('create table `archives` (`id` integer primary key autoincrement, `archive_name` text unique);');
$self->{dbh}->do('insert into `archives` select null, * from `archives_old`');
$self->{dbh}->do('drop table `archives_old`');
my $st = $self->{dbh}->prepare("select `archive_name` from `archives`;");
lib/App/BorgRestore/DB.pm view on Meta::CPAN
# We trust all values here since they have already been
# sucessfully put into the DB previously. Thus they must be
# safe to deal with.
$archive = untaint($archive, qr(.*));
my $archive_id = $self->get_archive_id($archive);
$self->{dbh}->do("alter table `files` rename column `timestamp-$archive` to `$archive_id`");
}
},
3 => sub {
# Drop all cached files due to a bug in
# lib/App/BorgRestore/PathTimeTable/DB.pm that caused certain files
lib/App/BorgRestore/DB.pm view on Meta::CPAN
@columns_to_copy = ('`path`', @columns_to_copy);
$self->{dbh}->do('insert into `files_new` select '.join(',', @columns_to_copy).' from files');
}
$self->{dbh}->do('drop table `files`');
$self->{dbh}->do('alter table `files_new` rename to `files`');
},
};
my $ran_migrations = 0;
for my $target_version (sort { $a <=> $b } keys %$schema) {
lib/App/BorgRestore/DB.pm view on Meta::CPAN
$self->{dbh}->do('insert into `files_new` select '.join(',', @columns_to_copy).' from files');
}
$self->{dbh}->do('drop table `files`');
$self->{dbh}->do('alter table `files_new` rename to `files`');
if (@timestamp_columns_to_copy > 0) {
my $sql = 'delete from `files` where ';
$sql .= join(' is null and ', @timestamp_columns_to_copy);
$sql .= " is null";
App-BraveUtils
view release on metacpan or search on metacpan
site such as uunet.uu.net, or by allowing the Copyright Holder to include
your modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict
with standard executables, which must also be provided, and provide
a separate manual page for each non-standard executable that clearly
documents how it differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-BrowserOpenUtils
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-BrowserUtils
view release on metacpan or search on metacpan
- [build] Rebuild with newer Perinci::CmdLine::POD to render a more
complete usage line of Perinci::CmdLine scripts in POD (now all
options are listed, not just '[options]').
- UPDATE 2020-05-02: rename version to 0.005.1.
0.005 2020-04-19 Released-By: PERLANCAR; Urgency: medium
- Support action 'is_running'.
App-Build
view release on metacpan or search on metacpan
lib/App/Build.pm view on Meta::CPAN
$self->log_info("Mirroring $url to $file\n");
require File::Fetch;
my $ff = File::Fetch->new(uri => $url);
my $where = $ff->fetch(to => File::Basename::dirname($file));
if($where) {
rename($where, $file);
}
}
else {
$self->log_info("Mirrored file $file up to date\n");
}
App-Buuilt-CLI
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-CELL
view release on metacpan or search on metacpan
- work on ticket #38
- move former api/bin/ to api-dev/ to keep api/ free of distractions
- another tweak on api-dev/release.sh
- make API pass manifest.t
- add unit test for CELL::Util and fix bug in that module
- rename CELL::Error to CELL::Status
- stop using tags after they possibly cause origin to get into detached
HEAD state
0.032-0.036 2014-01-14
- revamp Status.pm to enable "OK" status level
- Config.pm: fix regex, don't use meta param for re-entrantness
- Message.pm: make init be re-entrant and report errors
- put unit test of CELL::Message::init in the right file
0.065 2014-01-30 15:26
- rename to App::CELL (from just plain CELL)
0.066 2014-01-31 16:54
- refactor Localization Guide
- draft Apologia (attempt to justify App::CELL's existence to CPAN gurus)
- implement major design change: migrate to Log::Any (ticket #27)
- t/001-log.t: rewrite to use Log::Any::Test
- remove dependency on Log::Fast
0.090 2014-05-11 21:23
- Log.pm: rename 'configure' subroutine to 'init', tweak POD,
expand permitted levels (ticket #28)
- audit all calls to App::CELL::Status->new (ticket #5)
0.091 2014-05-11 22:29
- CELL_Config.pm, Message.pm: add CELL_SUPPORTED_LANGUAGES and
'sitedir' parameter specifying a full path, or an 'enviro' parameter
specifying name of environment variable containing a full path. The only
alternative considered is the CELL_SITEDIR environment variable. This
makes more sense than what we were attempting before, and streamlines the
code.
- t/050-find-and-parse.t renamed -> t/050-load.t
- t/070-config.h: rewriting (ticket #33) - WIP
- add LICENSE and WISHLIST files to dist/ directory
0.099-0.0100 2014-05-16
- Load.pm: tweaked log messages, fixed bug in _report_load_status: "success
0.196 2014-08-12 15:34 CEST
- Load.pm: when complaining about duplicate message/parameter definitions,
include both offending and original file in error message
0.197 2014-10-15 10:25 CEST
- Config.pm: add 'get_param' routine; rename 'get_all' routine to more
descriptive 'get_param_metadata'
- t/006-config.t: add test case for 'get_param'
0.198 2014-10-16 23:08 CEST
- t/070-config.t: add test case for Bug #51
App-CGIThis
view release on metacpan or search on metacpan
site such as uunet.uu.net, or by allowing the Copyright Holder to include
your modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict
with standard executables, which must also be provided, and provide
a separate manual page for each non-standard executable that clearly
documents how it differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-CLITestUtils
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-CPAN-Changes
view release on metacpan or search on metacpan
lib/App/CPAN/Changes.pm view on Meta::CPAN
my $tempfile = sprintf("%s.%05d.tmp", $file, rand()*65536);
sysopen my($fh), $tempfile, O_WRONLY|O_CREAT|O_EXCL
or die "Can't open temp file '$tempfile': $!";
print $fh _serialize($ch, $reverse);
rename $file, "$file.bak"
or die "Can't move '$file' to '$file.bak': $!";
rename $tempfile, $file
or die "Can't move '$tempfile' to '$file': $!";
}
$SPEC{preamble} = {
v => 1.1,
App-CPAN-Fresh
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-CPAN2Pkg
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-CPANChangesCwaliteeUtils
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-CPANChangesUtils
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
App-CPANGhq
view release on metacpan or search on metacpan
such as ftp.uu.net, or by allowing the Copyright Holder to include your
modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
( run in 1.470 second using v1.01-cache-2.11-cpan-131fc08a04b )