Result:
found more than 1401 distributions - search limited to the first 2001 files matching your query
( run in 1.332 )
AnyEvent-Net-MPD
view release on metacpan or search on metacpan
lib/AnyEvent/Net/MPD.pm view on Meta::CPAN
A database update has started or finished. If the database was modified during
the update, the B<database> event is also emitted.
=item B<stored_playlist>
A stored playlist has been modified, renamed, created or deleted.
=item B<playlist>
The current playlist has been modified.
lib/AnyEvent/Net/MPD.pm view on Meta::CPAN
The volume has been changed.
=item B<output>
An audio output has been added, removed or modified (e.g. renamed, enabled or
disabled)
=item B<options>
Options like repeat, random, crossfade, replay gain.
AnyEvent-OWNet
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.
AnyEvent-Onkyo
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.
AnyEvent-Open3-Simple
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.
AnyEvent-Pg
view release on metacpan or search on metacpan
0.02 Jul 18, 2011
- push_query was not triggering database dialog
- add debugging support
- add cancel_query method
- add queue_size method
- rename fail method to abort_all
0.01 Wed Jun 1 13:02:52 2011
- original version; created by h2xs 1.23 with options
-AXn AnyEvent::Pg
AnyEvent-PgRecvlogical
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.
AnyEvent-Plackup
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.
AnyEvent-ProcessPool
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.
AnyEvent-Promises
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.
AnyEvent-RFXCOM
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.
AnyEvent-RabbitMQ-Fork
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.
AnyEvent-RabbitMQ-PubSub
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.
AnyEvent-RabbitMQ-Simple
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.
AnyEvent-RabbitMQ
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.
AnyEvent-Redis-RipeRedis
view release on metacpan or search on metacpan
- Improved other tests.
- POD has been complemented.
1.244 Sat Apr 13 00:41:25 MSK 2013
- Added CONFIGURE_REQUIRES section in Makefile.PL.
- TEST_REQUIRES section renamed back to BUILD_REQUIRES.
1.243 Sat Apr 13 00:41:25 MSK 2013
- Minor fixes in POD.
1.242 Fri Apr 12 16:54:10 MSK 2013
- Minor fixes in POD.
1.114 Wed Oct 31 14:37:55 MSK 2012
- Added protection from deep recursion in case of some errors.
- Renamed constants (hope no one used them yet):
- E_AUTH_REQUIRED renamed to E_OPRN_NOT_PERMITTED.
- E_COMMAND_EXEC renamed to E_OPRN_ERROR.
- E_CLIENT renamed to E_UNEXPECTED_DATA,
- Changes in POD.
1.112 Fri Oct 27 15:30:25 MSK 2012
- POD edited.
- Slight optimization.
- Added section 'resources' in Makefile.PL for META.yml.
- Some changes in POD.
1.104 Sat Sep 1 03:14:45 MSK 2012
- E_IO_OPERATION renamed to E_IO.
- E_CONN_CLOSED_ON_DEMAND renamed to E_CONN_CLOSED_BY_CLIENT.
- E_UNEXPECTED renamed to E_CLIENT.
1.103 Fri Aug 31 14:24:45 MSK 2012
- POD has been complemented.
- Cosmetic changes.
AnyEvent-Retry
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.
AnyEvent-Riak
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.
AnyEvent-RipeRedis-Cluster
view release on metacpan or search on metacpan
- Fixes in tests.
- Fixes in example script.
- Cosmetic changes in code.
0.08 Fri Sep 2 18:17:52 MSK 2016
- "min_reconnect_interval" renamed to "reconnect_interval"
0.06 Fri Sep 2 08:20:10 MSK 2016
- Improved command routing and transaction handling.
- Added public function "hash_slot()".
- Service functions now can be imported.
AnyEvent-RipeRedis
view release on metacpan or search on metacpan
0.28 Fri Sep 23 12:10:33 MSK 2016
- Bugfix. If the client object was destroyed prematurely, in some cases
"_process_reply" method have been called on undefined value.
0.26 Fri Sep 2 18:17:17 MSK 2016
- "min_reconnect_interval" renamed to "reconnect_interval"
0.24 Fri Sep 2 08:20:05 MSK 2016
- Error "not allowed after "multi"" now raise exception.
- Unit tests improved.
- POD Improved.
- Unit tests improved.
0.08 Wed Aug 25 11:18:30 MSK 2016
- Added method "execute()".
- Getter "selected_database()" renamed to "database()".
- Bugfix. "DISCARD" command do not turned off transaction mode.
- Refactoring.
- POD Improved.
0.06 Fri Jul 29 10:51:10 MSK 2016
AnyEvent-SIP
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.
AnyEvent-SKKServ
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.
AnyEvent-SNMP-TrapReceiver
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.
AnyEvent-Sereal
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.
AnyEvent-SerialPort
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.
AnyEvent-SlackRTM
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.
AnyEvent-Sub-Retry
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.
AnyEvent-Subprocess
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.
AnyEvent-TLS-SNI
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.
AnyEvent-TermKey
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.
AnyEvent-Tickit
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.332 second using v1.01-cache-2.11-cpan-e9daa2b36ef )