Result:
found more than 1391 distributions - search limited to the first 2001 files matching your query
( run in 2.521 )
Apachish-Examples
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.
Apachish
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.
Apigee-Edge
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.
Apophis
view release on metacpan or search on metacpan
lib/Apophis.pm view on Meta::CPAN
Same content always produces the same UUID. Different namespaces produce
different UUIDs for the same content.
Stored objects are sharded across a 2-level hex directory tree (65,536
directories) for efficient filesystem access at scale. Writes are atomic
(temp + rename). CAS is naturally idempotent — no locking required.
All logic is implemented in C for maximum performance. The Perl layer
is just C<XSLoader> — every method is an XSUB.
=head1 METHODS
lib/Apophis.pm view on Meta::CPAN
my $id = $ca->store(\$content, store_dir => '/other');
my $id = $ca->store(\$content, meta => { mime_type => 'image/png' });
Identifies the content and writes it to the sharded store. Returns the
UUID. If the content already exists, returns immediately (CAS dedup).
Writes are atomic via temp file + rename.
=head2 fetch
my $data_ref = $ca->fetch($id);
App-256colors
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-AFNI-SiemensPhysio
view release on metacpan or search on metacpan
lib/App/AFNI/SiemensPhysio.pm view on Meta::CPAN
# with either command, the original output name will be "oba.slibase.1D"
# change that to our basename (assume resp and puls have same basename, use one from resp)
my $outputname = $self->{dat}->{resp};
$outputname =~ s/.resp.dat$/.slibase.1D/;
# or rename to specified input
#my $outputname=shift if $#_;
my $runcmd="";
if($runtype =~ /matlab/i){
lib/App/AFNI/SiemensPhysio.pm view on Meta::CPAN
if( $runcmd && ! -e "oba.slibase.1D" ){
croak "failed to run $runcmd";
} else {
# move file to output name if told to
rename "oba.slibase.1D", $outputname if $outputname;
}
}
App-ANSIColorUtils
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-APA
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-ASCIIUtils
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-AVR-Fuses
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-AYCABTU
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-AcmeCpanauthors
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-AcmeCpanlists
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-Acmeman
view release on metacpan or search on metacpan
1.05 2018-04-17
- null source
- dns checking (core.check-dns statement)
- core.restart renamed to core.postrenew
- per-domain postrenew script (domain.*.postrenew)
- Improve Makefile.PL (--no-autoinstall option).
1.04 2017-09-13
App-Addex-AddressBook-Abook
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-Addex-AddressBook-Apple
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-Addex-AddressBook-AppleScript
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-Addex-AddressBook-LDAP
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-Addex-Plugin-Hiveminder
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-Addex-Plugin-Nobody
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-Addex
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-AdditivesUtils
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-Adenosine
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-AlgorithmBackoffUtils
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-AlgorithmDiffUtils
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-Alice
view release on metacpan or search on metacpan
lib/App/Alice/IRC.pm view on Meta::CPAN
sub nick_change {
my ($self, $cl, $old_nick, $new_nick, $is_self) = @_;
utf8::decode($_) for ($old_nick, $new_nick);
$self->nick_cached($new_nick) if $is_self;
$self->rename_nick($old_nick, $new_nick);
$self->broadcast(
map {$_->format_event("nick", $old_nick, $new_nick)}
$self->nick_windows($new_nick)
);
}
lib/App/Alice/IRC.pm view on Meta::CPAN
if (my $window = $self->find_window($msg->{params}[1])) {
$self->broadcast($window->format_announcement("No such nick."));
}
}
sub rename_nick {
my ($self, $nick, $new_nick) = @_;
return unless $self->includes_nick($nick);
my $info = $self->get_nick_info($nick);
$info->{nick} = $new_nick;
$self->set_nick_info($new_nick, $info);
App-Aliyun
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-AllMyChangesUtils
view release on metacpan or search on metacpan
* Fixing dependencies
* Using lowercase namespace and name in `get_github_favorites`
1.0.4 2015-08-02
[Patch]
* Fixing get_pauseid_favorites (it was broken because ElasticSearch was renamed to Search::Elasticsearch)
* Fixing get_pauseid_distributions (it was broken because ElasticSearch was renamed to Search::Elasticsearch)
* Fixing get_github_favorites to return all starred repositories instead of first 30
* Using https instead of http link to allmychanges.com
1.0.5 2015-08-07
[Patch]
App-AltSQL
view release on metacpan or search on metacpan
lib/App/AltSQL/Term/Plugin/SyntaxHighlight.pm view on Meta::CPAN
low_priority
match max_rows middleint min_rows minute minute_second modify month myisam
natural no
on optimize option optionally order outer outfile
pack_keys partial password primary privileges procedure process processlist
read references reload rename replace restrict returns revoke right row rows
second select show shutdown soname sql_big_result sql_big_selects sql_big_tables sql_log_off
sql_log_update sql_low_priority_updates sql_select_limit sql_small_result sql_warnings starting
status straight_join string
table tables temporary terminated to trailing type
unique unlock unsigned update usage use using
App-Anchr
view release on metacpan or search on metacpan
lib/App/Anchr.pm view on Meta::CPAN
anchors: selete anchors from k-unitigs or superreads
break: break long reads by anthors
contained: discard contained super-reads, k-unitigs, or anchors
cover: trusted regions in the first file covered by the second
dazzname: rename FASTA reads for dazz_db
dep: check or install dependances
group: group anthors by long reads
kunitigs: create k-unitigs from corrected reads
layout: layout anthor group
merge: merge overlapped super-reads, k-unitigs, or anchors
( run in 2.521 seconds using v1.01-cache-2.11-cpan-39bf76dae61 )