This module manages a set of Log::Dispatch::* output objects that can be
logged to via a unified interface.

The idea is that you create a Log::Dispatch object and then add various
logging objects to it (such as a file logger or screen logger). Then you
call the 'log' method of the dispatch object, which passes the message to
each of the objects, which in turn decide whether or not to accept the
message and what to do with it.

This makes it possible to call single method and send a message to a log
file, via email, to the screen, and anywhere else, all with very little
code needed on your part, once the dispatching object has been created.

Module::Info gives you information about Perl modules *without actually
loading the module*. It actually isn't specific to modules and should work
on any perl code.

This module makes the functionality of the perltidy utility available to
perl scripts. Any or all of the input parameters may be omitted, in which
case the @ARGV array will be used to provide input parameters as described
in the perltidy(1) man page.

PostScript::Simple allows you to have a simple method of writing
PostScript files from Perl. It has several graphics primitives that
allow lines, circles, polygons and boxes to be drawn. Text can be added
to the page using standard PostScript fonts.

By default, this module exports a single hash ('%RE') that stores or
generates commonly needed regular expressions (see the "List of available
patterns" manpage).

There is an alternative, subroutine-based syntax described in the
"Subroutine-based interface" manpage.

"Spiffy" is a framework and methodology for doing object oriented (OO)
programming in Perl. Spiffy combines the best parts of Exporter.pm,
base.pm, mixin.pm and SUPER.pm into one magic foundation class. It
attempts to fix all the nits and warts of traditional Perl OO, in a
clean, straightforward and (perhaps someday) standard way. Spiffy
borrows ideas from other OO languages like Python, Ruby, Java and Perl
6. It also adds a few tricks of its own.

Testing is usually the ugly part of Perl module authoring. Perl gives you a
standard way to run tests with Test::Harness, and basic testing primitives
with Test::More. After that you are pretty much on your own to develop a
testing framework and philosophy. Test::More encourages you to make your
own framework by subclassing Test::Builder, but that is not trivial.

Test::Base gives you a way to write your own test framework base class that
_is_ trivial. In fact it is as simple as two lines:

package MyTestFramework;
use Test::Base -Base;

A module called 'MyTestFramework.pm' containing those two lines, will give
all the power of Test::More and all the power of Test::Base to every test
file that uses it. As you build up the capabilities of 'MyTestFramework',
your tests will have all of that power as well.

'MyTestFramework' becomes a place for you to put all of your reusable
testing bits. As you write tests, you will see patterns and duplication,
and you can "upstream" them into 'MyTestFramework'. Of course, you don't
have to subclass Test::Base at all. You can use it directly in many
applications, including everywhere you would use Test::More.

Test::Base concentrates on offering reusable data driven patterns, so that
you can write tests with a minimum of code. At the heart of all testing you
have inputs, processes and expected outputs. Test::Base provides some clean
ways for you to express your input and expected output data, so you can
spend your time focusing on that rather than your code scaffolding.

The YAML.pm module implements a YAML Loader and Dumper based on the YAML
1.0 specification. the http://www.yaml.org/spec/ manpage

YAML is a generic data serialization language that is optimized for human
readability. It can be used to express the data structures of most modern
programming languages. (Including Perl!!!)

For information on the YAML syntax, please refer to the YAML specification.

Psi is the premiere Instant Messaging application designed for
GNU/Linux, Microsoft Windows, Apple Mac OS X. Built upon an open
protocol named Jabber, Psi is a fast and lightweight messaging client
that utilises the best in open source technologies. Psi contains all
the features necessary to chat, with no bloated extras that slow your
computer down.

This package contains a plugin for "off the record" encryption (OTR).

Another frontend for the smpppd. With this frontend you can start and
stop a dialup network connection via your web browser.

An http-server such as Apache is required. The usage of mod-perl is not
a must, but recommended, because the speed improvement is significant.

Udhcp is a small dhcp client / server mainly used to support Xen
para-virtualized PXE booting.

Yafc is an OpenSource console mode FTP client. It has support for
Kerberos 4/5 authentication and sftp (ssh2). Other features include tab
completion, directory cache, powerful aliases, recursive file commands
and bookmarks with autologin.

mytop is a console-based (non-GUI) tool for monitoring the threads and
overall performance of MySQL 3.22.x, 3.23.x, and 4.x servers.

- With Term::ANSIColor installed you even get color.

- If you install Time::HiRes, get good real-time queries/second stats.

This package provides the YaST2 configuration for Internet Storage
Naming Service (iSNS).

The iSNS provides registration functions that allow all entities in a
storage network to register and query the iSNS database. Both iSCSI
initiators and targets register with this service. Discovery Domains
are used in the iSNS service to place register nodes into manageable
groupings. This package provide the ability to administer these
Discovery Domains.

The packages are automatically synchronized from https://build.suse.de/project/monitor/Devel:YaST:SLE-12-SP2 by https://ci.suse.de/view/YaST/job/yast-obs-sync-sle12-sp2/ Jenkins job.

** That means the packages are automatically overwritten!! **

The packages are automatically synchronized from https://build.suse.de/project/monitor/Devel:YaST:SLE-12-SP3 by https://ci.suse.de/view/YaST/job/yast-obs-sync-sle12-sp3/ Jenkins job.

** That means the packages are automatically overwritten!! **

The packages are automatically synchronized from https://build.suse.de/project/monitor/Devel:YaST:SLE-12-SP4 by https://ci.suse.de/view/YaST/job/yast-obs-sync-sle12-sp4/ Jenkins job.

** That means the packages are automatically overwritten!! **

The packages are automatically synchronized from https://build.suse.de/project/monitor/Devel:YaST:SLE-12-SP5 by https://ci.suse.de/view/YaST/job/yast-obs-sync-sle12-sp5/ Jenkins job.

** That means the packages are automatically overwritten!! **