Free exports software for linux

BBDB::Export is a Perl module to export data from The Insidious Big Brother Database.

SYNOPSIS

use BBDB::Export;

# export to LDIF
my $exporter = BBDB::Export::LDIF->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => "export.ldif",
dc => "dc=geekfarm, dc=org",
}
);
$exporter->export();

# sync with ldap via ldapadd and ldapdelete
my $exporter = BBDB::Export::LDAP->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => "/tmp/tempfile",
dc => "dc=geekfarm, dc=org",
ldappass => "supersecret",
}
);

$exporter->export();

# export to vcards
my $exporter = BBDB::Export::vCard->new(
{
bbdb_file => "/path/to/.bbdb",
output_dir => "/some/path/",
}
);

$exporter->export();

# create .mail_aliases
my $exporter = BBDB::Export::MailAliases->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => ".mail_aliases",
}
);

$exporter->export();

This module was designed to export to your bbdb data to a wide array of formats, and also to make it easy to write new modules to export to new formats. Current export options include building an LDIF, vCard, or .mail_aliases, and automatically updating an ldap server.
For a fully functional command line converter, see the bbdb-export script that comes with this module.

BBDB::Export should not be used directly. Use any of the available subclasses using the examples above. For more examples of using BBDB::Export, see the test cases.

Perl6::Export::Attrs - the Perl 6 is export(...) trait as a Perl 5 attribute.
SYNOPSIS
package Some::Module;
use Perl6::Export::Attrs;
# Export &foo by default, when explicitly requested,
# or when the :ALL export set is requested...
sub foo :Export(:DEFAULT) {
print "phooo!";
}
# Export &var by default, when explicitly requested,
# or when the :bees, :pubs, or :ALL export set is requested...
# the parens after is export are like the parens of a qw(...)
sub bar :Export(:DEFAULT :bees :pubs) {
print "baaa!";
}
# Export &baz when explicitly requested
# or when the :bees or :ALL export set is requested...
sub baz :Export(:bees) {
print "baassss!";
}
# Always export &qux
# (no matter what else is explicitly or implicitly requested)
sub qux :Export(:MANDATORY) {
print "quuuuuuuuux!";
}
IMPORT {
# This block is called when the module is used (as usual),
# but it is called after any export requests have been handled.
# Those requests will have been stripped from its @_ argument list
}
Implements a Perl 5 native version of what the Perl 6 symbol export mechanism will look like.
Its very straightforward:
- If you want a subroutine to be capable of being exported (when explicitly requested in the use arguments), you mark it with the :Export attribute.
- If you want a subroutine to be automatically exported when the module is used (without specific overriding arguments), you mark it with the :Export(:DEFAULT) attribute.
- If you want a subroutine to be automatically exported when the module is used (even if the user specifies overriding arguments), you mark it with the :Export(:MANDATORY) attribute.
- If the subroutine should also be exported when particular export groups are requested, you add the names of those export groups to the attributes argument list.

iTunes Export provides useful features that are not included in the iTunes application. iTunes Export project is open source and freely available for use.

iTunes Export currently provides the ability to export iTunes Playlists to the standard .m3u file format. Unfortunately, this feature is not included in the iTunes application and is extremely useful for users who wish to use iTunes with other applications or devices.

iTunes Export provides a simple command line application that can be used to generate playlists, a Graphical UI that provides a wizard interface to exporting playlists, or a DLL that can be used by other developers to add the ability to read iTunes Music Library XML files to other applications.

iTunes Export is written using C# on the .NET runtime. It should work on all versions of Windows that support .NET. The iTunesExport command line application also works on Linux using Mono 0.29 or later.

Sub::Exporter::Tutorial is a friendly guide to exporting with Sub::Exporter.

Whats an Exporter?

When you use a module, first it is required, then its import method is called. The Perl documentation tells us that the following two lines are equivalent:

use Module LIST;

BEGIN { require Module; Module->import(LIST); }

The import method is the modules exporter.

The Basics of Sub::Exporter

Sub::Exporter builds a custom exporter which can then be installed into your module. It builds this method based on configuration passed to its setup_exporter method.

A very basic use case might look like this:

package Addition;
use Sub::Exporter;
Sub::Exporter::setup_exporter({ exports => [ qw(plus) ]});

sub plus { my ($x, $y) = @_; return $x + $y; }

This would mean that when someone used your Addition module, they could have its plus routine imported into their package:

use Addition qw(plus);

my $z = plus(2, 2); # this works, because now plus is in the main package

That syntax to set up the exporter, above, is a little verbose, so for the simple case of just naming some exports, you can write this:

use Sub::Exporter -setup => { exports => [ qw(plus) ] };
...which is the same as the original example -- except that now the exporter is built and installed at compile time. Well, that and you typed less.

Using Export Groups

You can specify whole groups of things that should be exportable together. These are called groups. Exporter calls these tags. To specify groups, you just pass a groups key in your exporter configuration:

package Food;
use Sub::Exporter -setup => {
exports => [ qw(apple banana beef fluff lox rabbit) ],
groups => {
fauna => [ qw(beef lox rabbit) ],
flora => [ qw(apple banana) ],
}
};

Now, to import all that delicious foreign meat, your consumer needs only to write:

use Food qw(:fauna);
use Food qw(-fauna);

Either one of the above is acceptable. A colon is more traditional, but barewords with a leading colon cant be enquoted by a fat arrow. Well see why that matters later on.

Groups can contain other groups. If you include a group name (with the leading dash or colon) in a group definition, it will be expanded recursively when the exporter is called. The exporter will not recurse into the same group twice while expanding groups.

There are two special groups: all and default. The all group is defined by default, and contains all exportable subs. You can redefine it, if you want to export only a subset when all exports are requested. The default group is the set of routines to export when nothing specific is requested. By default, there is no default group.

flow-tools is a set of programs for processing and managing NetFlow exports from Cisco and Juniper routers. The tools included are: flow-capture, flow-cat, flow-dscan, flow-expire, flow-export, flow-fanout, flow-filter, flow-gen, flow-header, flow-import, flow-mask, flow-merge, flow-nfilter, flow-print, flow-receive, flow-report, flow-send, flow-split, flow-stat, flow-tag, and flow-xlate.

Flow data is collected and stored by default in host byte ordera nd the files are portable across every endian architectures.

Commands that utilize the network use a localip/remoteip/port designation for communication. "localip" is the IP address the host will use as a source for sending or bind to when receiving NetFlow PDUs (ie the destination address of the exporter. Configuring the "localip" to 0 will force the kernel to decide what IP address to use for sending and listen on all IP addresses for receiving. "remoteip" is the destination IP address used for sending or the expected address of the source when receiving. If the "remoteip" is 0 then the application will accept flows from any source address. The "port" is the UDP port number used for sending or receiving. When using multicast addresses the localip/remoteip/port is used to represent the source, group, and port respectively.

Flows are exported from a router in a number of different configurable versions. A flow is a collection of key fields and additional data. The flow key is {srcaddr, dstaddr, input, output, srcport, dstport, prot, ToS}. Flow-tools supports one export version per file.

Export versions 1, 5, 6, and 7 all maintain {nexthop, dPkts, dOctets, First, Last, flags}, ie the next-hop IP address, number of packets, number of octets (bytes), start time, end time, and flags such as the TCP header bits. Version 5 adds the additional fields {src_as, dst_as, src_mask, dst_mask}, ie source AS, destination AS, source network mask, and destination network mask. Version 7 which is specific to the Catalyst switches adds in addition to the version 5 fields {router_sc}, which is the Router IP address which populates the flow cache shortcut in the Supervisor. Version 6 which is not officially supported by Cisco adds in addition to the version 5 fields {in_encaps, out_encaps, peer_nexthop}, ie the input and output interface encapsulation size, and the IP address of the next hop within the peer. Version 1 exports do not contain a sequence number and therefore should be avoided, although it is safe to store the data as version 1 if the additional fields are not used.

Version 8 IOS NetFlow is a second level flow cache that reduces the data exported from the router. There are currently 11 formats, all of which provide {dFlows, dOctets, dPkts, First, Last} for the key fields.

8.1 - Source and Destination AS, Input and Output interface
8.2 - Protocol and Port
8.3 - Source Prefix and Input interface
8.4 - Destination Prefix and Output interface
8.5 - Source/Destination Prefix and Input/Output interface
8.9 - 8.1 + ToS
8.10 - 8.2 + ToS
8.11 - 8.3 + ToS
8.12 - 8.5 + ToS
8.13 - 8.2 + ToS
8.14 - 8.3 + ports + ToS

Version 8 CatIOS NetFlow appears to be a less fine grained first level flow cache.

8.6 - Destination IP, ToS, Marked ToS,
8.7 - Source/Destination IP, Input/Output interface, ToS, Marked ToS,
8.8 - Source/Destination IP, Source/Destination Port,
Input/Output interface, ToS, Marked ToS,

The following programs are included in the flow-tools distribution.

flow-capture - Collect, compress, store, and manage disk space for exported flows from a router.
flow-cat - Concatenate flow files. Typically flow files will contain a small window of 5 or 15 minutes of exports. Flow-cat can be used to append files for generating reports that span longer time periods.
flow-fanout - Replicate NetFlow datagrams to unicast or multicast destinations. Flow-fanout is used to facilitate multiple collectors attached to a single router.
flow-report - Generate reports for NetFlow data sets. Reports include source/destination IP pairs, source/destination AS, and top talkers. Over 50 reports are currently supported.
flow-tag - Tag flows based on IP address or AS #. Flow-tag is used to group flows by customer network. The tags can later be used with flow-fanout or flow-report to generate customer based traffic reports.
flow-filter - Filter flows based on any of the export fields. Flow-filter is used in-line with other programs to generate reports based on flows matching filter expressions.
flow-import - Import data from ASCII or cflowd format.
flow-export - Export data to ASCII or cflowd format.
flow-send - Send data over the network using the NetFlow protocol.
flow-receive - Receive exports using the NetFlow protocol without storing to disk like flow-capture.
flow-gen - Generate test data.
flow-dscan - Simple tool for detecting some types of network scanning and Denial of Service attacks.
flow-merge - Merge flow files in chronoligical order.
flow-xlate - Perform translations on some flow fields.
flow-expire - Expire flows using the same policy of flow-capture.
flow-header - Display meta information in flow file.
flow-split - Split flow files into smaller files based on size, time, or tags.

TextCite is a program for organizing and commenting textual citations from texts (books, articles, or other published works) for use in producing scientific or academic publications. You can organize by publication, author, category, or outline.

It works with bibliographic management programs like Citation, EndNote, RefWorks, and BibTeX, providing important text/citation management capabilities that these programs lack, while still allowing for rapid footnote and bibliography generation by means of your favorite bibliography manager. The project also exports to PDF and Word (RTF).

Bundle::Perl6 is a Perl bundle to install Perl6-related modules.

SYNOPSIS

perl -MCPAN -e install Bundle::Perl6

CONTENTS

Attribute::Handlers - Simpler definition of attribute handlers
Attribute::Types - Attributes that confer type on variables
Attribute::Overload - Attribute that makes overloading easier
Attribute::TieClasses - Attribute wrappers for CPAN Tie classes
Attribute::Util - A selection of general-utility attributes
Attribute::Deprecated - Mark deprecated methods
CLASS - Alias for __PACKAGE__
Class::Object - Each object is its own class
Coro - create and manage coroutines
Exporter::Simple - Easier set-up of module exports with attributes
NEXT - Provide a pseudo-class NEXT for method redispatch
Scalar::Properties - Run-time properties on scalar variables
Switch - A switch statement for Perl
Perl6::Binding - implement Perl6 aliasing features
Perl6::Classes - First class classes in Perl 5
Perl6::Currying - Perl 6 subroutine currying for Perl 5
Perl6::Export - Implements the Perl 6 is export(...) trait
Perl6::Form - Implements the Perl 6 form built-in
Perl6::Gather - Implements the Perl 6 gather/take control structure in Perl 5
Perl6::Interpolators - Use Perl 6 function-interpolation syntax
Perl6::Parameters - Perl 6-style prototypes with named parameters
Perl6::Placeholders - Perl 6 implicitly declared parameters for Perl 5
Perl6::Say - Implements the Perl 6 say (print-with-newline) function
Perl6::Tokener - Its a Perl 6 tokener. It tokenises Perl 6.
Perl6::Variables - Perl 6 variable syntax for Perl 5
UNIVERSAL::exports - Lightweight, universal exporting of variables
Want - Implement the want() command

Errno package contains system errno constants.

SYNOPSIS

use Errno qw(EINTR EIO :POSIX);

Errno defines and conditionally exports all the error constants defined in your system errno.h include file. It has a single export tag, :POSIX, which will export all POSIX defined error numbers.

Errno also makes %! magic such that each element of %! has a non-zero value only if $! is set to that value. For example:

use Errno;

unless (open(FH, "/fangorn/spouse")) {
if ($!{ENOENT}) {
warn "Get a wife!n";
} else {
warn "This path is barred: $!";
}
}

If a specified constant EFOO does not exist on the system, $!{EFOO} returns "". You may use exists $!{EFOO} to check whether the constant is available on the system.

CAVEATS

Importing a particular constant may not be very portable, because the import will fail on platforms that do not have that constant. A more portable way to set $! to a valid value is to use:

if (exists &Errno::EFOO) {
$! = &Errno::EFOO;
}