Result:
found more than 1391 distributions - search limited to the first 2001 files matching your query
( run in 2.826 )
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.
App-CPANIDX-HTTP-Server
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-CPANIDX
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-CPANMetaUtils
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-CPANModulesUtils
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-CPANRepo
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-CPANStreaks
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-CPANTS-Lint
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-CPANURLUtils
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-CPANfile2OPML
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-CPANtoRPM
view release on metacpan or search on metacpan
lib/App/CPANtoRPM.pm view on Meta::CPAN
return @opts;
}
###############################################################################
# This either renames or copies a file.
#
sub _backup_file {
my($self,$file1,$file2,$copy) = @_;
if ($copy) {
lib/App/CPANtoRPM.pm view on Meta::CPAN
if (! $succ) {
$self->_log_message('ERR',"Unable to copy file: $file1 -> $file2");
}
} else {
if (! rename $file1,$file2) {
$self->_log_message('ERR',"Unable to back up file: $file1");
}
}
}
lib/App/CPANtoRPM.pm view on Meta::CPAN
END:
{
my $macros = "$ENV{HOME}/.rpmmacros";
my $self = $package{'self'};
if ($package{'restore'}) {
rename "$macros.cpantorpm",$macros ||
$self->_log_message('WARN',"Unable to restore .rpmmacros file: $!");
} elsif ($package{'remove'}) {
unlink $macros ||
$self->_log_message('WARN',
"Unable to remove temporary .rpmmacros file: $!");
lib/App/CPANtoRPM.pm view on Meta::CPAN
if (! $succ) {
$self->_log_message('ERR',"Unable to extract archive: $package{archive}");
}
if ($$self{'extracted'}) {
if (! rename("$TMPDIR/$dir","$TMPDIR/$package{dir}")) {
$self->_log_message
('ERR',
"Unable to rename extracted directory: $package{archive}");
}
}
}
############################################################################
App-CPRReporter
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-CSE
view release on metacpan or search on metacpan
lib/App/CSE/Command/Index.pm view on Meta::CPAN
$indexer->commit();
$PROGRESS_BAR->update($ESTIMATED_SIZE);
rmtree $cse->index_dir()->stringify();
rename $index_dir , $self->cse->index_dir()->stringify();
$self->cse->index_meta->{index_time} = DateTime->now()->iso8601();
# Also inject the right version
$self->cse->index_meta->{version} = $self->cse->version();;
App-CSV2Chart
view release on metacpan or search on metacpan
lib/App/CSV2Chart/Command/svg.pm view on Meta::CPAN
)
{
die "ssconvert failed";
}
# Use ->copy instead of ->move because rename does
# not handle cross-partition moves.
$svg_fn->copy($output_fn);
if (@$exe)
{
App-CSVUtils-csv_mix_formulas
view release on metacpan or search on metacpan
lib/App/CSVUtils/csv_mix_formulas.pm view on Meta::CPAN
Normally, you output to a different file than input. If you try to output to the
same file (C<-o INPUT.csv -O>) you will clobber the input file; thus the utility
prevents you from doing it. However, with this C<--inplace> option, you can
output to the same file. Like perl's C<-i> option, this will first output to a
temporary file in the same directory as the input file then rename to the final
file at the end. You cannot specify output file (C<-o>) when using this option,
but you can specify backup extension with C<-b> option.
Some caveats:
=over
=item * if input file is a symbolic link, it will be replaced with a regular file;
=item * renaming (implemented using C<rename()>) can fail if input filename is too long;
=item * value specified in C<-b> is currently not checked for acceptable characters;
=item * things can also fail if permissions are restrictive;
lib/App/CSVUtils/csv_mix_formulas.pm view on Meta::CPAN
=item * B<inplace_backup_ext> => I<str> (default: "")
Extension to add for backup of input file.
In inplace mode (C<--inplace>), if this option is set to a non-empty string, will
rename the input file using this extension as a backup. The old existing backup
will be overwritten, if any.
=item * B<input_escape_char> => I<str>
Specify character to escape value in field in input CSV, will be passed to Text::CSV_XS.
App-CSVUtils
view release on metacpan or search on metacpan
lib/App/CSVUtils.pm view on Meta::CPAN
Normally, you output to a different file than input. If you try to output to the
same file (`-o INPUT.csv -O`) you will clobber the input file; thus the utility
prevents you from doing it. However, with this `--inplace` option, you can
output to the same file. Like perl's `-i` option, this will first output to a
temporary file in the same directory as the input file then rename to the final
file at the end. You cannot specify output file (`-o`) when using this option,
but you can specify backup extension with `-b` option.
Some caveats:
- if input file is a symbolic link, it will be replaced with a regular file;
- renaming (implemented using `rename()`) can fail if input filename is too long;
- value specified in `-b` is currently not checked for acceptable characters;
- things can also fail if permissions are restrictive;
_
tags => ['category:output'],
lib/App/CSVUtils.pm view on Meta::CPAN
schema => 'str*',
default => '',
description => <<'_',
In inplace mode (`--inplace`), if this option is set to a non-empty string, will
rename the input file using this extension as a backup. The old existing backup
will be overwritten, if any.
_
cmdline_aliases => {b=>{}},
tags => ['category:output'],
lib/App/CSVUtils.pm view on Meta::CPAN
(my $input_filename = $output_filename) =~ s/\.\w{5}\z//
or die [500, "BUG: Can't get original input file '$output_filename'"];
if (length(my $ext = $r->{util_args}{inplace_backup_ext})) {
my $backup_filename = $input_filename . $ext;
log_info "[csvutil] Backing up input file '$output_filename' -> '$backup_filename' ...";
rename $input_filename, $backup_filename or die [500, "Can't rename '$input_filename' -> '$backup_filename': $!"];
}
log_info "[csvutil] Renaming from temporary output file '$output_filename' -> '$input_filename' ...";
rename $output_filename, $input_filename or die [500, "Can't rename back '$output_filename' -> '$input_filename': $!"];
}
}
delete $r->{output_filenames};
delete $r->{output_filename};
delete $r->{output_rownum};
App-CSelUtils
view release on metacpan or search on metacpan
- [ux] Add -e as alias for --eval (--action eval:E).
0.088 2021-06-27 Released-By: PERLANCAR; Urgency: medium
- Update prereq (renamed module Tree::{To,To::}TextLines).
0.087 2021-02-19 Released-By: PERLANCAR; Urgency: low
- No functional changes.
- [dist] Edit Changes: rename Backward-Compatible property in
Release Note to Backward-Incompatible.
0.086 2020-04-29 Released-By: PERLANCAR; Urgency: low
0.082 2019-07-29 Released-By: PERLANCAR; Urgency: medium; Backward-Incompatible: yes
- [refactor][imcompatible change] Extract common subroutine: foosel(),
add --select-action, rename --actions to --node-actions, tweak dump
output. Rename package varibles.
0.081 2019-07-27 Released-By: PERLANCAR; Urgency: medium
App-CalId
view release on metacpan or search on metacpan
0.08 2014-09-06 Released-By: PERLANCAR
- Adjust to Perinci::Sub::Wrapper 0.62
(_perinci.sub.wrapper.validate_args is now renamed).
0.07 2014-06-19 Released-By: SHARYANTO
- No functional changes.
App-CalcAccumulatedDiscounts
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-CalcAccumulatedInflation
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-CalendarDatesUtils
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-CaseUtils
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.
( run in 2.826 seconds using v1.01-cache-2.11-cpan-39bf76dae61 )