Result:
found more than 1264 distributions - search limited to the first 2001 files matching your query
( run in 4.160 )
Amon2-Web-Dispatcher-RouterSimple-Extended
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
Amp-Client
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
Analizo
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
Ananke-SqlLink
view release on metacpan or search on metacpan
Makefile.old view on Meta::CPAN
POSTOP = @$(NOOP)
ZIP = zip
DIST_DEFAULT = tardist
CI = ci -u
SHAR = shar
COMPRESS = gzip --best
DIST_CP = best
PREOP = @$(NOOP)
TARFLAGS = cvf
DISTVNAME = $(DISTNAME)-$(VERSION)
SUFFIX = .gz
RCS_LABEL = rcs -Nv$(VERSION_SYM): -q
Ananke-Template
view release on metacpan or search on metacpan
Makefile.old view on Meta::CPAN
POSTOP = @$(NOOP)
ZIP = zip
DIST_DEFAULT = tardist
CI = ci -u
SHAR = shar
COMPRESS = gzip --best
DIST_CP = best
PREOP = @$(NOOP)
TARFLAGS = cvf
DISTVNAME = $(DISTNAME)-$(VERSION)
SUFFIX = .gz
RCS_LABEL = rcs -Nv$(VERSION_SYM): -q
Ananke-Utils
view release on metacpan or search on metacpan
Makefile.old view on Meta::CPAN
POSTOP = @$(NOOP)
ZIP = zip
DIST_DEFAULT = tardist
CI = ci -u
SHAR = shar
COMPRESS = gzip --best
DIST_CP = best
PREOP = @$(NOOP)
TARFLAGS = cvf
DISTVNAME = $(DISTNAME)-$(VERSION)
SUFFIX = .gz
RCS_LABEL = rcs -Nv$(VERSION_SYM): -q
Anarres-Mud-Driver
view release on metacpan or search on metacpan
Efun/Core/Core.xs view on Meta::CPAN
int
invoke(arg)
SV * arg
CODE:
RETVAL = SvIOKp(arg); /* Not necessarily the best way? */
OUTPUT:
RETVAL
MODULE = Anarres::Mud::Driver::Efun::Core PACKAGE = Anarres::Mud::Driver::Efun::Core::floatp
Ancient
view release on metacpan or search on metacpan
xs/const/ppport.h view on Meta::CPAN
#ifndef IVSIZE
# ifdef LONGSIZE
# define IVSIZE LONGSIZE
# else
# define IVSIZE 4 /* A bold guess, but the best we can make. */
# endif
#endif
#ifndef UVTYPE
# define UVTYPE unsigned IVTYPE
#endif
xs/const/ppport.h view on Meta::CPAN
#undef SvGETMAGIC
#ifndef SvGETMAGIC
# define SvGETMAGIC(x) ((void)(UNLIKELY(SvGMAGICAL(x)) && mg_get(x)))
#endif
/* That's the best we can do... */
#ifndef sv_catpvn_nomg
# define sv_catpvn_nomg sv_catpvn
#endif
#ifndef sv_catsv_nomg
Android-ElectricSheep-Automator
view release on metacpan or search on metacpan
Added 'adb-path-to-executable' parameter to the constructor of Automator.
0.04 2025/04/29
dump_current_screen_ui() sometimes could not find the dump to a device file, so checking if the file is there and repeating and sleeping for some iterations. Hopefully this fixes this issue.
Pod changes.
0.05 2025/07/28
Important change: this module now requires Data::Roundtrip to be at least v0.30. You will need to upgrade Data::Roundtrip if you have an older version before installing this module. If you can't then just change the dependency on Makefile.PL ...
Important change: Android::ElectricSheep::Automator::Plugins has migrated to Android::ElectricSheep::Automator::Plugins::Apps
Added two new methods pgrep() and pidof() to search the process table of the device.
Added one new method Android::ElectricSheep::Automator::is_app_running() which checks if the specified app is running on the device.
Added one new method Android::ElectricSheep::Automator::Plugins::Apps::Base::is_app_running() which checks if the Viber app is running on the device.
Moved functionality for opening and closing an app into the Android::ElectricSheep::Automator::Plugins::Apps::Base (before they were in the Android::ElectricSheep::Automator::Plugins::Apps::Viber). Also moved appname() into the Base as well.
Android-Releases
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
Anego
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
Aniki
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
Anki-Import
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
Annelidous-snapshot
view release on metacpan or search on metacpan
Annelidous/Connector/EC2.pm view on Meta::CPAN
sub shutdown {
my $self=shift;
return $self->transport->terminate_instances(InstanceId => $self->instance->{id});
}
# Not likely to work quite yet, but our EC2 module has the best
# attempt at an implementation for this yet.
sub console {
my $self=shift;
my $tty=$self->get_console_output(InstanceId => $self->instance->{id});
my $cap=new Annelidous::Capabilities;
AnnoCPAN-Perldoc-SyncDB
view release on metacpan or search on metacpan
lib/AnnoCPAN/Perldoc/SyncDB.pm view on Meta::CPAN
the Artisic license or the GPL does not meet the needs of your
project, please contact us at info@clotho.com or visit the above URL.
We release open source software to help the world. We hope that you
will enjoy this software, and we also hope and that you will hire us.
As authors of this software, we are best able to help you integrate it
into your project and to assist you with any problems.
=head1 SYNOPSIS
use AnnoCPAN::Perldoc::SyncDB;
lib/AnnoCPAN/Perldoc/SyncDB.pm view on Meta::CPAN
=item compress => flag
Specifies which version of the database to download. The options are
C<bz2>, C<gz>, the empty string (i.e. no compression) or C<undef>,
which means autodetection. The autodetect mode checks if you have
Compress::Bzip2 or Compress::Zlib installed before picking the best of
the other flag values.
Defaults to C<undef> (that is, autodetect mode).
=item verbose => boolean
AnnoCPAN
view release on metacpan or search on metacpan
lib/AnnoCPAN/DBI.pm view on Meta::CPAN
sub before_delete {
my ($self) = @_;
# make sure no notes use us as their reference section...
for my $note ($self->original_notes) {
my $max_sim = 0;
my $best_sect;
for my $notepos ($note->notepos) {
if ($notepos->section->id != $self->id
and $notepos->score > $max_sim)
{
$max_sim = $notepos->score;
$best_sect = $notepos->section;
}
}
$note->section($best_sect);
$note->update;
}
}
=head2 AnnoCPAN::DBI::User
lib/AnnoCPAN/DBI.pm view on Meta::CPAN
# XXX version check might go here
my $ref_section = $self->section or return;
my $orig_cont = $ref_section->content;
my $max_sim = AnnoCPAN::Config->option('min_similarity') || 0;
my $best_sect;
for my $sect ($podver->raw_sections) {
next if $sect->{type} & COMMAND; # can't attach notes to commands
my $sim = similarity($orig_cont, $sect->{content}, $max_sim);
if ($sim > $max_sim) {
$max_sim = $sim;
$best_sect = $sect;
}
}
if ($best_sect) {
AnnoCPAN::DBI::NotePos->create({ note => $self,
section => $best_sect->{id}, score => int($max_sim * SCALE),
status => CALCULATED });
return 1;
}
return;
}
Ansible-Util
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
AntTweakBar
view release on metacpan or search on metacpan
src/ppport.h view on Meta::CPAN
#ifndef IVSIZE
# ifdef LONGSIZE
# define IVSIZE LONGSIZE
# else
# define IVSIZE 4 /* A bold guess, but the best we can make. */
# endif
#endif
#ifndef UVTYPE
# define UVTYPE unsigned IVTYPE
#endif
src/ppport.h view on Meta::CPAN
#ifndef PERL_MAGIC_ext
# define PERL_MAGIC_ext '~'
#endif
/* That's the best we can do... */
#ifndef sv_catpvn_nomg
# define sv_catpvn_nomg sv_catpvn
#endif
#ifndef sv_catsv_nomg
Antispam-Toolkit
view release on metacpan or search on metacpan
lib/Antispam/Toolkit.pm view on Meta::CPAN
to continue working on this particular software. I will continue to do so,
inasmuch as I have in the past, for as long as it interests me.
Similarly, a donation made in this way will probably not make me work on this
software much more, unless I get so many donations that I can consider working
on free software full time, which seems unlikely at best.
To donate, log into PayPal and send money to autarch@urth.org or use the
button on this page: L<http://www.urth.org/~autarch/fs-donation.html>
=head1 AUTHOR
Antispam-httpBL
view release on metacpan or search on metacpan
lib/Antispam/httpBL.pm view on Meta::CPAN
to continue working on this particular software. I will continue to do so,
inasmuch as I have in the past, for as long as it interests me.
Similarly, a donation made in this way will probably not make me work on this
software much more, unless I get so many donations that I can consider working
on free software full time, which seems unlikely at best.
To donate, log into PayPal and send money to autarch@urth.org or use the
button on this page: L<http://www.urth.org/~autarch/fs-donation.html>
=head1 AUTHOR
Antsy
view release on metacpan or search on metacpan
lib/Antsy.pm view on Meta::CPAN
OSC 1337 ; PopKeyLabels ST
You can optionally label the entry in the stack when you push so that pop will pop multiple sets of key labels if needed. This is useful if a program crashes or an ssh session exits unexpectedly. The corresponding codes with labels are:
OSC 1337 ; PushKeyLabels=[label] ST
OSC 1337 ; PopKeyLabels=[label] ST
Where [label] is an ASCII string that works best if it is unique in the stack.
=item * unicode_version
iTerm2 by default uses Unicode 9's width tables. The user can opt to use Unicode 8's tables with a preference (for backward compatibility with older locale databases). Since not all apps will be updated at the same time, you can tell iTerm2 to use a ...
Any-Daemon-HTTP
view release on metacpan or search on metacpan
lib/Any/Daemon/HTTP/VirtualHost.pod view on Meta::CPAN
Alias for L<addHandler()|Any::Daemon::HTTP::VirtualHost/"Handler">.
=item $obj-E<gt>B<findHandler>($uri|$path|@segments)
Find the handler which matches the given $uri best. The $uri is the
rewritten URI of the request, an URI object. It's $path is sufficient,
may also be broken into path @segments already.
=item $obj-E<gt>B<handleRequest>( $server, $session, $request, [$uri] )
lib/Any/Daemon/HTTP/VirtualHost.pod view on Meta::CPAN
Translate the $uri into a filename, without checking for existence. Returns
C<undef> is not possible.
=item $obj-E<gt>B<sourceFor>($path|$path_segments)
Find the best matching L<Any::Daemon::HTTP::Source|Any::Daemon::HTTP::Source> object, which
might be a C<::UserDirs>, a C<::Directory>, or a C<::Proxy>.
=back
=head2 Proxies
Any-Moose
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
Any-Renderer
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
Any-Template-ProcessDir
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
Any-Template
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
AnyData
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
AnyData2
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
AnyEvent-Beanstalk
view release on metacpan or search on metacpan
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
AnyEvent
view release on metacpan or search on metacpan
lib/AnyEvent.pm view on Meta::CPAN
=head3 Signal Races, Delays and Workarounds
Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support
attaching callbacks to signals in a generic way, which is a pity,
as you cannot do race-free signal handling in perl, requiring
C libraries for this. AnyEvent will try to do its best, which
means in some cases, signals will be delayed. The maximum time
a signal might be delayed is 10 seconds by default, but can
be overriden via C<$ENV{PERL_ANYEVENT_MAX_SIGNAL_LATENCY}> or
C<$AnyEvent::MAX_SIGNAL_LATENCY> - see the L<ENVIRONMENT VARIABLES>
section for details.
lib/AnyEvent.pm view on Meta::CPAN
EV is the preferred backend when no other event loop seems to be in
use. If EV is not installed, then AnyEvent will fall back to its own
pure-perl implementation, which is available everywhere as it comes with
AnyEvent itself.
AnyEvent::Impl::EV based on EV (interface to libev, best choice).
AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
=item Backends that are transparently being picked up when they are used.
These will be used if they are already loaded when the first watcher
lib/AnyEvent.pm view on Meta::CPAN
dictate which event model to use.
If the program is not event-based, it need not do anything special, even
when it depends on a module that uses an AnyEvent. If the program itself
uses AnyEvent, but does not care which event loop is used, all it needs
to do is C<use AnyEvent>. In either case, AnyEvent will choose the best
available loop implementation.
If the main program relies on a specific event model - for example, in
Gtk2 programs you have to rely on the Glib module - you should load the
event module before loading AnyEvent or any module that uses it: generally
lib/AnyEvent.pm view on Meta::CPAN
does nothing for those backends.
=item L<EV>
This module isn't really "optional", as it is simply one of the backend
event loops that AnyEvent can use. However, it is simply the best event
loop available in terms of features, speed and stability: It supports
the AnyEvent API optimally, implements all the watcher types in XS, does
automatic timer adjustments even when no monotonic clock is available,
can take avdantage of advanced kernel interfaces such as C<epoll> and
C<kqueue>, and is the fastest backend I<by far>. You can even embed
( run in 4.160 seconds using v1.01-cache-2.11-cpan-39bf76dae61 )