Lector de Feeds

In Mageia/cauldron/i586: systemd is a system and session manager for Linux, compatible with SysV and LSB init scripts. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux cgroups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit.

In Mageia/cauldron/x86_64: This module provides a simple syntax for creating object classes, which uses private variables that look like lexicals as object member fields. While most of this module has evolved into a stable state in practice, parts remain *experimental* because the design is still evolving, and many features and ideas have yet to implemented. I don't yet guarantee I won't have to change existing details in order to continue its development. Feel free to try it out in experimental or newly-developed code, but don't complain if a later version is incompatible with your current code and you'll have to change it. That all said, please do get in contact if you find the module overall useful. The more feedback you provide in terms of what features you are using, what you find works, and what doesn't, will help the ongoing development and hopefully eventual stability of the design. See the the /FEEDBACK manpage section.

In Mageia/cauldron/i586: This module provides a simple syntax for creating object classes, which uses private variables that look like lexicals as object member fields. While most of this module has evolved into a stable state in practice, parts remain *experimental* because the design is still evolving, and many features and ideas have yet to implemented. I don't yet guarantee I won't have to change existing details in order to continue its development. Feel free to try it out in experimental or newly-developed code, but don't complain if a later version is incompatible with your current code and you'll have to change it. That all said, please do get in contact if you find the module overall useful. The more feedback you provide in terms of what features you are using, what you find works, and what doesn't, will help the ongoing development and hopefully eventual stability of the design. See the the /FEEDBACK manpage section.

In Mageia/cauldron/i586: You don't need to load this module yourself in most cases. Business::ISBN will load it when it loads. These data are generated from the RangeMessage.xml file provided by the ISBN Agency. You can retrieve this yourself at https://www.isbn-international.org/range_file_generation. This file is included as part of the distribution and should be installed at ~lib/Business/ISBN/Data/RangeMessage.xml.

In Mageia/cauldron/x86_64: You don't need to load this module yourself in most cases. Business::ISBN will load it when it loads. These data are generated from the RangeMessage.xml file provided by the ISBN Agency. You can retrieve this yourself at https://www.isbn-international.org/range_file_generation. This file is included as part of the distribution and should be installed at ~lib/Business/ISBN/Data/RangeMessage.xml.

In Mageia/cauldron/x86_64: Pod::Man is a module to convert documentation in the POD format (the preferred language for documenting Perl) into *roff input using the man macro set. The resulting *roff code is suitable for display on a terminal using the nroff(1) manpage, normally via the man(1) manpage, or printing using the troff(1) manpage. It is conventionally invoked using the driver script *pod2man*, but it can also be used directly. As a derived class from Pod::Simple, Pod::Man supports the same methods and interfaces. See the Pod::Simple manpage for all the details. new() can take options, in the form of key/value pairs that control the behavior of the parser. See below for details.

In Mageia/cauldron/i586: Pod::Man is a module to convert documentation in the POD format (the preferred language for documenting Perl) into *roff input using the man macro set. The resulting *roff code is suitable for display on a terminal using the nroff(1) manpage, normally via the man(1) manpage, or printing using the troff(1) manpage. It is conventionally invoked using the driver script *pod2man*, but it can also be used directly. As a derived class from Pod::Simple, Pod::Man supports the same methods and interfaces. See the Pod::Simple manpage for all the details. new() can take options, in the form of key/value pairs that control the behavior of the parser. See below for details.

In Mageia/cauldron/x86_64: This module allows you to deliberately hide modules from a program even though they are installed. This is mostly useful for testing modules that have a fallback when a certain dependency module is not installed.

In Mageia/cauldron/i586: This module allows you to deliberately hide modules from a program even though they are installed. This is mostly useful for testing modules that have a fallback when a certain dependency module is not installed.

In Mageia/cauldron/x86_64: The most basic test one can write is "does it compile ?". This module tests if the code compiles and play nice with Test::Simple modules. Another good practice this module can test is to "use strict;" in all perl files. By setting a minimum test coverage through all_cover_ok(), a code author can ensure his code is tested above a preset level of kwality throughout the development cycle. Along with Test::Pod, this module can provide the first tests to setup for a module author.

In Mageia/cauldron/i586: The most basic test one can write is "does it compile ?". This module tests if the code compiles and play nice with Test::Simple modules. Another good practice this module can test is to "use strict;" in all perl files. By setting a minimum test coverage through all_cover_ok(), a code author can ensure his code is tested above a preset level of kwality throughout the development cycle. Along with Test::Pod, this module can provide the first tests to setup for a module author.

In Mageia/cauldron/x86_64: This module implements an object class, instances of which store a (mutable) string buffer that supports tags. A tag is a name/value pair that applies to some non-empty extent of the underlying string. The types of tag names ought to be strings, or at least values that are well-behaved as strings, as the names will often be used as the keys in hashes or applied to the 'eq' operator. The types of tag values are not restricted - any scalar will do. This could be a simple integer or string, ARRAY or HASH reference, or even a CODE reference containing an event handler of some kind.

In Mageia/cauldron/i586: This module implements an object class, instances of which store a (mutable) string buffer that supports tags. A tag is a name/value pair that applies to some non-empty extent of the underlying string. The types of tag names ought to be strings, or at least values that are well-behaved as strings, as the names will often be used as the keys in hashes or applied to the 'eq' operator. The types of tag values are not restricted - any scalar will do. This could be a simple integer or string, ARRAY or HASH reference, or even a CODE reference containing an event handler of some kind.

In Mageia/cauldron/i586: Module::CoreList contains data about what perl modules are shipped with given versions of perl (and their versions). It comes also with a command-line utility, corelist, to retrieve this information easily.

In Mageia/cauldron/x86_64: Module::CoreList contains data about what perl modules are shipped with given versions of perl (and their versions). It comes also with a command-line utility, corelist, to retrieve this information easily.

In Mageia/cauldron/i586: Neovim is a project that seeks to aggressively refactor Vim in order to: - Simplify maintenance and encourage contributions - Split the work between multiple developers - Enable advanced UIs without modifications to the core - Maximize extensibility

In Mageia/cauldron/x86_64: Neovim is a project that seeks to aggressively refactor Vim in order to: - Simplify maintenance and encourage contributions - Split the work between multiple developers - Enable advanced UIs without modifications to the core - Maximize extensibility

In Mageia/cauldron/i586: Eureka is a cross-platform map editor for the classic DOOM games. It started when the ported the Yadex editor to a proper GUI toolkit, namely FLTK, and implemented a system for multi-level Undo / Redo. These and other features have required rewriting large potions of the existing code, and adding lots of new code too. Eureka is now an independent program with its own work-flow and its own quirks.

In Mageia/cauldron/x86_64: Eureka is a cross-platform map editor for the classic DOOM games. It started when the ported the Yadex editor to a proper GUI toolkit, namely FLTK, and implemented a system for multi-level Undo / Redo. These and other features have required rewriting large potions of the existing code, and adding lots of new code too. Eureka is now an independent program with its own work-flow and its own quirks.

In Mageia/cauldron/i586: Widgets and other objects used for indicators.