From e58c691d06024a8dbc59d536e9b48fcd9973f77f Mon Sep 17 00:00:00 2001
From: Jenkins for Enea Linux Test Framework
Date: Mon, 22 Feb 2021 19:25:12 +0100
Subject: Updated licenses.xml
---
.../doc/licenses.xml | 9190 --------------------
1 file changed, 9190 deletions(-)
(limited to 'doc/book-enea-nfv-access-platform-open-source')
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
index 15af6e2..e69de29 100644
--- a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
@@ -1,9190 +0,0 @@
-
-
-
- Packages and Licenses
-
-
- Packages
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Package Name
- Version
- Description
- License
-
-
-
-
-
-
- 4g-sierra
- 1.0
- Scripts to setup 4G modems from Sierra
- Enea
-
-
- acl
- 2.2.52
- Utilities for managing POSIX Access Control Lists.
- LGPL-2.1, GPL-2.0
-
-
- alsa-lib
- 1.1.4.1
- ALSA sound library.
- LGPL-2.1, GPL-2.0
-
-
- ant
- 1.8.1
- Another Neat Tool - build system for Java
- Apache-2.0
-
-
- antlr
- 2.7.7
- Framework for constructing recognizers interpreters compilers and translators
- PD
-
-
- apache2
- 2.4.27
- The Apache HTTP Server is a powerful efficient and extensible web server.
- Apache-2.0
-
-
- apr-util
- 1.6.0
- Apache Portable Runtime (APR) companion library.
- Apache-2.0
-
-
- apr
- 1.6.2
- Apache Portable Runtime (APR) library.
- Apache-2.0
-
-
- apt
- 1.2.24
- Advanced front-end for dpkg.
- GPL-2.0
-
-
- attr
- 2.4.47
- Utilities for manipulating filesystem extended attributes.
- LGPL-2.1, GPL-2.0
-
-
- aufs-util
- 4.4
- Tools for managing AUFS mounts.
- GPL-2.0
-
-
- augeas
- 1.5.0
- Augeas configuration API.
- LGPL-2.1
-
-
- autoconf-archive
- 2016.09.16
- a collection of freely re-usable Autoconf macros.
- GPL-3.0-with-autoconf-exception
-
-
- autoconf
- 2.69
- Autoconf is an extensible package of M4 macros that produce shell scripts to automatically configure software source code packages. Autoconf creates a configuration script for a package from a template file that lists the operating system features that the package can use in the form of M4 macro calls.
- GPL-2.0, GPL-3.0
-
-
- automake
- 1.15.1
- Automake is a tool for automatically generating `Makefile.in' files compliant with the GNU Coding Standards. Automake requires the use of Autoconf.
- GPL-2.0
-
-
- avahi
- 0.6.32
- "Avahi is a fully LGPL framework for Multicast DNS Service Discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. This tool implements IPv4LL ""Dynamic Configuration of IPv4 Link-Local Addresses"" (IETF RFC3927) a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server."
- GPL-2.0, LGPL-2.1
-
-
- avalon-framework-api
- 4.3
- Common way for components to be created initialized configured started. (API-only)
- Apache-2.0
-
-
- base-files
- 3.0.14
- The base-files package creates the basic system directory structure and provides a small set of key configuration files for the system.
- GPL-2.0
-
-
- base-passwd
- 3.5.29
- The master copies of the user database files (/etc/passwd and /etc/group). The update-passwd tool is also provided to keep the system databases synchronized with these master files.
- GPL-2.0
-
-
- bash-completion
- 2.7
- Programmable Completion for Bash 4.
- GPL-2.0
-
-
- bash
- 4.4
- An sh-compatible command language interpreter.
- GPL-3.0
-
-
- bc
- 1.06
- Arbitrary precision calculator language.
- GPL-2.0, LGPL-2.1
-
-
- bcel
- 5.2
- Java Bytecode manipulation library
- Apache-2.0
-
-
- bind
- 9.10.5-P3
- ISC Internet Domain Name Server.
- ISC, BSD
-
-
- binutils-cross-x86_64
- 2.29.1
- The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
- GPL-3.0
-
-
- binutils
- 2.29.1
- The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
- GPL-3.0
-
-
- bison
- 3.0.4
- Bison is a general-purpose parser generator that converts an annotated context-free grammar into an LALR(1) or GLR parser for that grammar. Bison is upward compatible with Yacc: all properly-written Yacc grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with little trouble.
- GPL-3.0
-
-
- bjam
- 1.64.0
- Portable Boost.Jam build tool for boost.
- BSL-1.0, MIT, Python-2.0
-
-
- bmap-tools
- 3.4
- "Bmap-tools - tools to generate block map (AKA bmap) and flash images using bmap. Bmaptool is a generic tool for creating the block map (bmap) for a file and copying files using the block map. The idea is that large file containing unused blocks like raw system image files can be copied or flashed a lot faster with bmaptool than with traditional tools like ""dd"" or ""cp""."
- GPL-2.0
-
-
- boost
- 1.64.0
- Free peer-reviewed portable C++ source libraries.
- BSL-1.0, MIT, Python-2.0
-
-
- bridge-utils
- 1.5
- Tools for ethernet bridging.
- GPL-2.0
-
-
- bsf
- 2.4.0
- Bean Scripting Framework package
- Apache-2.0
-
-
- btrfs-tools
- 4.12
- Btrfs is a new copy on write filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance repair and easy administration. This package contains utilities (mkfs fsck btrfsctl) used to work with btrfs and an utility (btrfs-convert) to make a btrfs filesystem from an ext3.
- GPL-2.0
-
-
- busybox
- 1.24.1
- BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for most of the utilities you usually find in GNU fileutils shellutils etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete POSIX environment for any small or embedded system.
- GPL-2.0, BSD-4-Clause
-
-
- bzip2
- 1.0.6
- bzip2 compresses files using the Burrows-Wheeler block-sorting text compression algorithm and Huffman coding. Compression is generally considerably better than that achieved by more conventional LZ77/LZ78-based compressors and approaches the performance of the PPM family of statistical compressors.
- BSD-4-Clause
-
-
- ca-certificates
- 20170717
- This package includes PEM files of CA certificates to allow SSL-based applications to check for the authenticity of SSL connections. This derived from Debian's CA Certificates.
- GPL-2.0, MPL-2.0
-
-
- cacao-initial
- 0.98
- CacaoVM for use as OpenEmbedded's Java VM
- GPL-2.0
-
-
- cdrkit
- 1.1.11
- CD/DVD command line tools.
- GPL-2.0
-
-
- cdrtools
- 3.01a31
- A set of tools for CD recording including cdrecord.
- GPL-2.0, CDDL-1.0, LGPL-2.1
-
-
- classpath-initial
- 0.93
- Java1.4-compatible GNU Classpath variant that is used as bootclasspath for jikes-native.
- GPL-2.0, SAX-PD
-
-
- classpath
- 0.99
- GNU Classpath standard Java libraries - For native Java-dependent programs
- GPL-2.0, SAX-PD
-
-
- cloud-init
- 0.7.6
- Init scripts for use on cloud images
- GPL-3.0
-
-
- cmake
- 3.8.2
- Cross-platform open-source make system.
- BSD
-
-
- commons-logging
- 1.1.1
- Java Internet protocol suite library
- Apache-2.0
-
-
- commons-net
- 1.4.1
- Java Internet protocol suite library
- Apache-2.0
-
-
- compose-file
- 3.0
- Parser for the Compose file format (version 3)
- Apache-2.0
-
-
- containerd-docker
- v0.2.x
- containerd is a daemon to control runC built for performance and density. containerd leverages runC's advanced features such as seccomp and user namespace support as well as checkpoint and restore for cloning and live migration of containers.
- Apache-2.0
-
-
- core-image-minimal-initramfs
- 1.0
- Small image capable of booting a device. The kernel includes the Minimal RAM-based Initial Root Filesystem (initramfs) which finds the first 'init' program more efficiently.
- MIT
-
-
- coreutils
- 8.27
- The GNU Core Utilities provide the basic file shell and text manipulation utilities. These are the core utilities which are expected to exist on every system.
- GPL-3.0
-
-
- cross-localedef
- 2.26
- Cross locale generation tool for glibc.
- LGPL-2.1
-
-
- cryptodev-linux
- 1.9
- A /dev/crypto device driver header file.
- GPL-2.0
-
-
- cup
- 0.10k
- Lexical analyzer generator for Java
- CUP
-
-
- curl
- 7.58.0
- Command line tool and library for client-side URL transfers.
- MIT
-
-
- cwautomacros
- 20110201
- Collection of autoconf m4 macros.
- GPL-2.0
-
-
- db
- 5.3.28
- Berkeley Database v5.
- Sleepycat
-
-
- dbus-glib
- 0.108
- GLib bindings for the D-Bus message bus that integrate the D-Bus library with the GLib thread abstraction and main loop.
- AFL-2.0, GPL-2.0
-
-
- dbus-test
- 1.10.20
- D-Bus test package (for D-bus functionality testing only).
- AFL-2.0, GPL-2.0
-
-
- dbus
- 1.10.20
- "D-Bus is a message bus system a simple way for applications to talk to one another. In addition to interprocess communication D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a \""single instance\"" application or daemon and to launch applications and daemons on demand when their services are needed."
- AFL-2.0, GPL-2.0
-
-
- debianutils
- 4.8.1.1
- Miscellaneous utilities specific to Debian.
- GPL-2.0, SMAIL_GPL
-
-
- depmodwrapper
- 1.0
- Wrapper script for the Linux kernel module dependency indexer.
- MIT
-
-
- dhcp
- 4.3.6
- DHCP (Dynamic Host Configuration Protocol) is a protocol which allows individual devices on an IP network to get their own network configuration information from a server. DHCP helps make it easier to administer devices.
- ISC
-
-
- diffutils
- 3.6
- Diffutils contains the GNU diff diff3 sdiff and cmp utilities. These programs are usually used for creating patch files.
- GPL-3.0
-
-
- dmidecode
- 3.1
- DMI (Desktop Management Interface) table related utilities.
- GPL-2.0
-
-
- dnsmasq
- 2.78
- Lightweight easy to configure DNS forwarder and DHCP server.
- GPL-2.0, GPL-3.0
-
-
- docker
- 17.06.0
- Linux container runtime Docker complements kernel namespacing with a high-level API which operates at the process level. It runs unix processes with strong guarantees of isolation and repeatability across servers. . Docker is a great building block for automating distributed systems: large-scale web deployments database clusters continuous deployment systems private PaaS service-oriented architectures etc. . This package contains the daemon and client. Using docker.io is officially supported on x86_64 and arm (32-bit) hosts. Other architectures are considered experimental. . Also note that kernel version 3.10 or above is required for proper operation of the daemon process and that any lower versions may have subtle and/or glaring issues.
- Apache-2.0
-
-
- dosfstools
- 4.1
- DOS FAT Filesystem Utilities.
- GPL-3.0
-
-
- dpdk-dev-libibverbs
- 1.2.1-3.4-2.0.0.0
- libibverbs library to support Mellanox config
- GPL-2.0
-
-
- dpdk
- 18.02
- Intel(r) Data Plane Development Kit
- BSD, LGPL-2.0, GPL-2.0
-
-
- dpkg
- 1.18.24
- Package maintenance system from Debian.
- GPL-2.0
-
-
- dtc
- 1.4.4
- The Device Tree Compiler is a tool used to manipulate the Open-Firmware-like device tree used by PowerPC kernels.
- GPL-2.0, BSD
-
-
- e2fsprogs
- 1.43.5
- The Ext2 Filesystem Utilities (e2fsprogs) contain all of the standard utilities for creating fixing configuring and debugging ext2 filesystems.
- GPL-2.0, LGPL-2.0, BSD, MIT
-
-
- ebtables
- 2.0.10-4
- Utility for basic Ethernet frame filtering on a Linux bridge advanced logging MAC DNAT/SNAT and brouting.
- GPL-2.0
-
-
- ecj-bootstrap
- 1.0
- JDT Core Batch Compiler - Bootstrap variant
- MIT
-
-
- ecj-initial
- 1.0
- JDT Core Batch Compiler - Bootstrap variant
- MIT
-
-
- efibootmgr
- 0.15
- Linux user-space application to modify the EFI Boot Manager.
- GPL-2.0
-
-
- efitools
- 1.7.0
- From the EFI Tools package in the Linux user-space it's now possible to read and manipulate the UEFI signatures database via the new efi-readvar and efi-updatevar commands. Aside from needing efitools 1.4 the EFIVARFS file-system is also needed which was only introduced in the Linux 3.8 kernel.
- GPL-2.0
-
-
- efivar
- 0.31
- efivar provides a simple command line interface to the UEFI variable facility
- LGPL-2.1
-
-
- element-vcpe
- 4.1.3
- vCPE(based on Element-ODM)
- Enea, BSD, BSD-2-Clause, GPL-3.0, ISC, LGPL-2.1
-
-
- elfutils
- 0.170
- Utilities and libraries for handling compiled object files.
- GPL-3.0, Elfutils-Exception
-
-
- enea-nfv-access-vnf
- 1.0
- VNF image of the Enea NFV Access Platform includes kernel rootfs and boot parameters
- MIT
-
-
- enea-nfv-access
- 1.0
- Image for the host side of the Enea NFV Access Platform with ODM and NETCONF Edgelink customizations
- MIT
-
-
- ethtool
- 4.11
- A small utility for examining and tuning the settings of your ethernet-based network interfaces.
- GPL-2.0
-
-
- expat
- 2.2.3
- Expat is an XML parser library written in C. It is a stream-oriented parser in which an application registers handlers for things the parser might find in the XML document (like start tags)
- MIT
-
-
- fastjar
- 0.98
- jar replacement written in C.
- GPL-2.0
-
-
- file
- 5.31
- File attempts to classify files depending on their contents and prints a description if a match is found.
- BSD
-
-
- findutils
- 4.6.0
- The GNU Find Utilities are the basic directory searching utilities of the GNU operating system. These programs are typically used in conjunction with other programs to provide modular and powerful directory search and file locating capabilities to other commands.
- GPL-3.0
-
-
- flex
- 2.6.0
- Flex is a fast lexical analyser generator. Flex is a tool for generating programs that recognize lexical patterns in text.
- BSD
-
-
- fontconfig
- 2.12.4
- Fontconfig is a font configuration and customization library which does not depend on the X Window System. It is designed to locate fonts within the system and select them according to requirements specified by applications. Fontconfig is not a rasterization library nor does it impose a particular rasterization library on the application. The X-specific library 'Xft' uses fontconfig along with freetype to specify and rasterize fonts.
- MIT, PD
-
-
- freetype
- 2.8
- FreeType is a software font engine that is designed to be small efficient highly customizable and portable while capable of producing high-quality output (glyph images). It can be used in graphics libraries display servers font conversion tools text image generation tools and many other products as well.
- FreeType, GPL-2.0
-
-
- fuse
- 2.9.7
- FUSE (Filesystem in Userspace) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. FUSE also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations.
- GPL-2.0, LGPL-2.0
-
-
- gawk
- 4.1.4
- The GNU version of awk a text processing utility. Awk interprets a special-purpose programming language to do quick and easy text pattern matching and reformatting jobs.
- GPL-3.0
-
-
- gcc-cross-initial-x86_64
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc-cross-x86_64
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc-runtime
- 7.3.0
- Runtime libraries from GCC.
- GPL-3.0-with-GCC-exception
-
-
- gcc-source-7.3.0
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gdbm
- 1.13
- Key/value database library with extensible hashing.
- GPL-3.0
-
-
- gettext-minimal
- 0.19.8.1
- Contains the m4 macros sufficient to support building autoconf/automake. This provides a significant build time speedup by the removal of gettext-native from most dependency chains (now only needed for gettext for the target).
- FSF-Unlimited
-
-
- gettext
- 0.19.8.1
- GNU gettext is a set of tools that provides a framework to help other programs produce multi-lingual messages. These tools include a set of conventions about how programs should be written to support message catalogs a directory and file naming organization for the message catalogs themselves a runtime library supporting the retrieval of translated messages and a few stand-alone programs to massage in various ways the sets of translatable and already translated strings.
- GPL-3.0, LGPL-2.1
-
-
- giflib
- 5.1.4
- shared library for GIF images.
- MIT
-
-
- git
- 2.13.3
- Distributed version control system.
- GPL-2.0
-
-
- glib-2.0
- 2.52.3
- GLib is a general-purpose utility library which provides many useful data types macros type conversions string utilities file utilities a main loop abstraction and so on.
- LGPL-2.0, BSD, PD
-
-
- glibc-locale
- 2.26
- Locale data from glibc.
- GPL-2.0, LGPL-2.1
-
-
- glibc
- 2.26
- The GNU C Library is used as the system C library in most systems with the Linux kernel.
- GPL-2.0, LGPL-2.1
-
-
- gmp
- 6.1.2
- GMP is a free library for arbitrary precision arithmetic operating on signed integers rational numbers and floating point numbers
- GPL-2.0, LGPL-3.0
-
-
- gnome-desktop-testing
- 2014.1
- Test runner for GNOME-style installed tests.
- LGPL-2.0
-
-
- gnu-config
- 20150728
- Tool that installs the GNU config.guess / config.sub into a directory tree
- GPL-3.0-with-autoconf-exception
-
-
- gnu-efi
- 3.0.6
- Libraries for producing EFI binaries.
- GPL-2.0, BSD-2-Clause
-
-
- gnujaf
- 1.1.1
- Provides a mean to type data and locate components suitable for performing various kinds of action on it.
- GPL-2.0-with-GCC-exception
-
-
- gnulib
- 2017-08-20.18
- A collection of software subroutines which are designed to be usable on many operating systems. The goal of the project is to make it easy for free software authors to make their software run on many operating systems. Since source is designed to be copied from gnulib it is not a library per-se as much as a collection of portable idioms to be used in other projects.
- LGPL-2.0
-
-
- gnumail
- 1.1.2
- GNU's free implementation of the JavaMail API specification
- GPL-2.0-with-GCC-exception
-
-
- gnutls
- 3.5.13
- GNU Transport Layer Security Library.
- GPL-3.0, LGPL-2.1
-
-
- go-capability
- 0.0
- Utilities for manipulating POSIX capabilities in Go.
- BSD-2-Clause
-
-
- go-cli
- 1.1.0
- A small package for building command line apps in Go
- MIT
-
-
- go-connections
- 0.2.1
- Utility package to work with network connections
- Apache-2.0
-
-
- go-context
- git
- A golang registry for global request variables.
- BSD-3-Clause
-
-
- go-cross-x86_64
- 1.9.4
- The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
- BSD-3-Clause
-
-
- go-dbus
- 4.0.0
- Native Go bindings for D-Bus
- BSD-2-Clause
-
-
- go-distribution
- 2.6.0
- The Docker toolset to pack ship store and deliver content
- Apache-2.0
-
-
- go-fsnotify
- 1.2.11
- A golang registry for global request variables.
- BSD-3-Clause
-
-
- go-libtrust
- 0.0
- Primitives for identity and authorization
- Apache-2.0
-
-
- go-logrus
- 0.11.0
- A golang registry for global request variables.
- MIT
-
-
- go-mux
- git
- A powerful URL router and dispatcher for golang.
- BSD-3-Clause
-
-
- go-patricia
- 2.2.6
- A generic patricia trie (also called radix tree) implemented in Go (Golang)
- MIT
-
-
- go-pty
- git
- PTY interface for Go
- MIT
-
-
- go-systemd
- 4
- Go bindings to systemd socket activation journal D-Bus and unit files
- Apache-2.0
-
-
- go
- 1.9.4
- The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
- BSD-3-Clause
-
-
- gobject-introspection
- 1.52.1
- Middleware layer between GObject-using C libraries and language bindings.
- LGPL-2.0, GPL-2.0
-
-
- gotty
- 1.0
- Run a terminal application as a web service
- MIT
-
-
- gperf
- 3.1
- GNU gperf is a perfect hash function generator
- GPL-3.0
-
-
- gpgme
- 1.9.0
- GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a High-Level Crypto API for encryption decryption signing signature verification and key management
- GPL-2.0, LGPL-2.1
-
-
- gptfdisk
- 1.0.3
- GPT fdisk is a disk partitioning tool loosely modeled on Linux fdisk but used for modifying GUID Partition Table (GPT) disks. The related FixParts utility fixes some common problems on Master Boot Record (MBR) disks.
- GPL-2.0
-
-
- grep
- 3.1
- GNU grep utility.
- GPL-3.0
-
-
- groff
- 1.22.3
- The groff (GNU troff) software is a typesetting package which reads plain text mixed with formatting commands and produces formatted output.
- GPL-3.0
-
-
- grpc-go
- 1.4.0
- The Go language implementation of gRPC. HTTP/2 based RPC
- BSD
-
-
- grub-disable-fallback
- 1.0
- Enea service to disable grub fallback when boot is successful
- Enea
-
-
- grub-efi
- 2.02
- GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
- GPL-3.0
-
-
- grub
- 2.02
- GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
- GPL-3.0
-
-
- gtk-doc
- 1.25
- Gtk-doc is a set of scripts that extract specially formatted comments from glib-based software and produce a set of html documentation files from them
- GPL-2.0
-
-
- gzip
- 1.8
- GNU Gzip is a popular data compression program originally written by Jean-loup Gailly for the GNU project. Mark Adler wrote the decompression part
- GPL-3.0
-
-
- help2man
- 1.47.4
- Program for creating simple man pages.
- GPL-3.0
-
-
- htop
- 1.0.3
- htop process monitor.
- GPL-2.0
-
-
- hugepage-reservation
- 1.0
- Reserve hugepages on system startup.
- Enea
-
-
- icedtea7
- 2.1.3
- Harness to build the source code from OpenJDK using Free Software build tools
- GPL-2.0-with-classpath-exception
-
-
- icu
- 59.1
- The International Component for Unicode (ICU) is a mature portable set of C/C++ and Java libraries for Unicode support software internationalization (I18N) and globalization (G11N) giving applications the same results on all platforms.
- ICU
-
-
- inetlib
- 1.1.1
- GNU Classpath inetlib is an extension library to provide extra network protocol support for GNU Classpath and ClasspathX project but it can also used standalone to add http imap pop3 and smtp client support applications.
- GPL-2.0-with-GCC-exception
-
-
- initramfs-framework
- 1.0
- Modular initramfs system.
- MIT
-
-
- initramfs-module-install-efi
- 1.0
- initramfs-framework module for EFI installation option.
- MIT
-
-
- initramfs-module-install
- 1.0
- initramfs-framework module for installation option.
- MIT
-
-
- initramfs-module-setup-live
- 1.0
- initramfs-framework module for live booting.
- MIT
-
-
- initramfs-ostree-image
- 1.0
- OSTree initramfs image
- MIT
-
-
- inputproto
- 2.3.2
- This package provides the wire protocol for the X Input extension. The extension supports input devices other then the core X keyboard and pointer.
- MIT
-
-
- intltool
- 0.51.0
- Utility scripts for internationalizing XML.
- GPL-2.0
-
-
- iperf3
- 3.2
- iperf is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing protocols and buffers. For each test it reports the bandwidth loss and other parameters.
- BSD
-
-
- iproute2
- 4.11.0
- Iproute2 is a collection of utilities for controlling TCP / IP networking and traffic control in Linux. Of the utilities ip and tc are the most important. ip controls IPv4 and IPv6 configuration and tc stands for traffic control.
- GPL-2.0
-
-
- iptables
- 1.6.1
- iptables is the userspace command line program used to configure and control network packet filtering code in Linux.
- GPL-2.0
-
-
- iw
- 4.9
- iw is a new nl80211 based CLI configuration utility for wireless devices. It supports almost all new drivers that have been added to the kernel recently.
- BSD
-
-
- jacl
- 1.4.1
- Tcl interpreter for Java
- UCB, SUN, AMD, CDS
-
-
- jamvm
- 2.0.0-devel
- A compact Java Virtual Machine which conforms to the JVM specification version 2.
- GPL-2.0
-
-
- jansson
- 2.9
- Jansson is a C library for encoding decoding and manipulating JSON data.
- MIT
-
-
- jaxp1.3
- 1.4.01
- Java XML parser and transformer APIs (DOM SAX JAXP TrAX)
- Apache-2.0, W3C, PD
-
-
- jdepend
- 2.9.1
- Design quality metrics generator for each Java
- BSD
-
-
- jikes-initial
- 1.0
- Initial Java 1.4-compatible (and not higher) compiler.
- MIT
-
-
- jikes
- 1.22
- Java compiler adhering to language and VM specifications
- IPL-1.0
-
-
- jlex
- 1.2.6
- Lexical analyzer generator for Java
- JLEX
-
-
- jq
- 1.5
- jq is like sed for JSON data you can use it to slice and filter and map and transform structured data with the same ease that sed awk grep and friends let you play with text.
- MIT
-
-
- jsch
- 0.1.40
- SSH implementation in Java
- BSD
-
-
- junit
- 3.8.2
- JUnit is a testing framework for Java
- CPL-1.0
-
-
- jzlib
- 1.0.7
- zlib implementation in Java
- BSD
-
-
- kbd
- 2.0.4
- Keytable files and keyboard utilities.
- GPL-2.0
-
-
- kbproto
- 1.0.7
- This package provides the wire protocol for the X Keyboard extension. This extension is used to control options related to keyboard handling and layout.
- MIT
-
-
- kern-tools
- 0.2
- Tools for managing Yocto Project style branched kernels.
- GPL-2.0
-
-
- keymaps
- 1.0
- Keymaps and initscript to set the keymap on bootup.
- GPL-2.0
-
-
- keyutils
- 1.5.10
- Utilities to control the kernel key management facility and to provide a mechanism by which the kernel call back to userspace to get a key instantiated.
- LGPL-2.1, GPL-2.0
-
-
- kmod
- 24
- kmod is a set of tools to handle common tasks with Linux kernel modules like insert remove list check properties resolve dependencies and aliases.
- GPL-2.0, LGPL-2.1
-
-
- krb5
- 1.15.1
- "Kerberos is a system for authenticating users and services on a network. Kerberos is a trusted third-party service. That means that there is a third party (the Kerberos server) that is trusted by all the entities on the network (users and services usually called ""principals""). . This is the MIT reference implementation of Kerberos V5. . This package contains the Kerberos key server (KDC). The KDC manages all authentication credentials for a Kerberos realm holds the master keys for the realm and responds to authentication requests. This package should be installed on both master and slave KDCs."
- MIT
-
-
- ldconfig
- 2.12.1
- A standalone native ldconfig build.
- GPL-2.0
-
-
- less
- 487
- Less is a program similar to more i.e. a terminal based program for viewing text files and the output from other programs. Less offers many features beyond those that more does.
- GPL-3.0, BSD-2-Clause
-
-
- libaio
- 0.3.110
- Asynchronous input/output library that uses the kernels native interface
- LGPL-2.1
-
-
- libarchive
- 3.3.2
- C library and command-line tools for reading and writing tar cpio zip ISO and other archive formats
- BSD
-
-
- libassuan
- 2.4.3
- IPC library used by GnuPG and GPGME.
- GPL-3.0, LGPL-2.1
-
-
- libbsd
- 0.8.6
- This library provides useful functions commonly found on BSD systems and lacking on others like GNU systems thus making it easier to port projects with strong BSD origins without needing to embed the same code over and over again on each project.
- BSD-4-Clause, ISC, PD
-
-
- libcap
- 2.25
- Library for getting/setting POSIX.1e capabilities.
- BSD, GPL-2.0
-
-
- libcgroup
- 0.41
- libcgroup is a library that abstracts the control group file system in Linux. Control groups allow you to limit account and isolate resource usage (CPU memory disk I/O etc.) of groups of processes.
- LGPL-2.1
-
-
- libcheck
- 0.10.0
- Check - unit testing framework for C code.
- LGPL-2.1
-
-
- libdaemon
- 0.14
- Lightweight C library which eases the writing of UNIX daemons.
- LGPL-2.1
-
-
- libdevmapper
- 2.02.171
- LVM2 is a set of utilities to manage logical volumes in Linux.
- GPL-2.0, LGPL-2.0
-
-
- libecj-bootstrap
- 3.6.2
- JDT Core Batch Compiler - Jar only
- EPL-1.0
-
-
- libffi
- 3.2.1
- The `libffi' library provides a portable high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. FFI stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The `libffi' library really only provides the lowest machine dependent layer of a fully featured foreign function interface. A layer must exist above `libffi' that handles type conversions for values passed between the two languages.
- MIT
-
-
- libfile-slurp-perl
- 9999.19
- This module provides subroutines to read or write entire files with a simple call. It also has a subroutine for reading the list of filenames in a directory.
- Artistic-1.0, GPL-1.0
-
-
- libgcc-initial
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception
-
-
- libgcc
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- libgcrypt
- 1.8.0
- General purpose cryptographic library based on the code from GnuPG.
- GPL-2.0, LGPL-2.1, GPL-3.0
-
-
- libgpg-error
- 1.27
- Small library that defines common error values for all GnuPG components.
- GPL-2.0, LGPL-2.1
-
-
- libgudev
- 231
- GObject wrapper for libudev.
- LGPL-2.1
-
-
- libice
- 1.0.9
- The Inter-Client Exchange (ICE) protocol provides a generic framework for building protocols on top of reliable byte-stream transport connections. It provides basic mechanisms for setting up and shutting down connections for performing authentication for negotiating versions and for reporting errors.
- MIT
-
-
- libidn
- 1.33
- Implementation of the Stringprep Punycode and IDNA specifications defined by the IETF Internationalized Domain Names (IDN) working group.
- LGPL-2.1, LGPL-3.0, GPL-3.0
-
-
- libjpeg-turbo
- 1.5.2
- libjpeg-turbo is a derivative of libjpeg that uses SIMD instructions (MMX SSE2 NEON) to accelerate baseline JPEG compression and decompression
- BSD-3-Clause
-
-
- libmbim
- 1.16.0
- libmbim is a glib-based library for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol
- GPL-2.0, LGPL-2.1
-
-
- libmnl
- 1.0.4
- Minimalistic user-space library oriented to Netlink developers providing functions for common tasks in parsing validating and constructing both the Netlink header and TLVs.
- LGPL-2.1
-
-
- libmpc
- 1.0.3
- Mpc is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result. It is built upon and follows the same principles as Mpfr
- LGPL-3.0
-
-
- libndp
- 1.6
- Library for IPv6 Neighbor Discovery Protocol.
- LGPL-2.1
-
-
- libnewt
- 0.52.20
- Newt is a programming library for color text mode widget based user interfaces. Newt can be used to add stacked windows entry widgets checkboxes radio buttons labels plain text fields scrollbars etc. to text mode user interfaces. This package also contains the shared library needed by programs built with newt as well as a /usr/bin/dialog replacement called whiptail. Newt is based on the slang library.
- LGPL-2.0
-
-
- libnl
- 3.4.0
- A library for applications dealing with netlink sockets.
- LGPL-2.1
-
-
- libnss-mdns
- 0.10
- Name Service Switch module for Multicast DNS (zeroconf) name resolution.
- LGPL-2.1
-
-
- libpcap
- 1.8.1
- Libpcap provides a portable framework for low-level network monitoring. Libpcap can provide network statistics collection security monitoring and network debugging.
- BSD
-
-
- libpciaccess
- 0.13.5
- libpciaccess provides functionality for X to access the PCI bus and devices in a platform-independent way.
- MIT
-
-
- libpcre
- 8.41
- The PCRE library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. PCRE has its own native API as well as a set of wrapper functions that correspond to the POSIX regular expression API.
- BSD
-
-
- libpng
- 1.6.31
- PNG image format decoding library.
- Libpng
-
-
- libpthread-stubs
- 0.4
- This library provides weak aliases for pthread functions not provided in libc or otherwise available by default.
- MIT
-
-
- libqmi
- 1.20.2
- libqmi is a glib-based library for talking to WWAN modems and devices which speak the Qualcomm MSM Interface (QMI) protocol
- GPL-2.0, LGPL-2.1
-
-
- libsdl
- 1.2.15
- Simple DirectMedia Layer is a cross-platform multimedia library designed to provide low level access to audio keyboard mouse joystick 3D hardware via OpenGL and 2D video framebuffer.
- LGPL-2.1
-
-
- libsign
- 0.3.2
- This project targets to provide a generic signing framework. This framework separates the signing request and signing process and correspondingly forms the so-called signlet and signaturelet. Each signaturelet only concerns about the details about how to construct the layout of a signature format and signlet only cares how to construct the signing request.
- BSD-3-Clause
-
-
- libsm
- 1.2.2
- "The Session Management Library (SMlib) is a low-level \""C\"" language interface to XSMP. The purpose of the X Session Management Protocol (XSMP) is to provide a uniform mechanism for users to save and restore their sessions. A session is a group of clients each of which has a particular state."
- MIT
-
-
- libtasn1
- 4.12
- Library for ASN.1 and DER manipulation.
- GPL-3.0, LGPL-2.1
-
-
- libtool
- 2.4.6
- This is GNU libtool a generic library support script. Libtool hides the complexity of generating special library types (such as shared libraries) behind a consistent interface.
- GPL-2.0, LGPL-2.1
-
-
- libunistring
- 0.9.7
- Text files are nowadays usually encoded in Unicode and may consist of very different scripts from Latin letters to Chinese Hanzi with many kinds of special characters accents right-to-left writing marks hyphens Roman numbers and much more. But the POSIX platform APIs for text do not contain adequate functions for dealing with particular properties of many Unicode characters. In fact the POSIX APIs for text have several assumptions at their base which don't hold for Unicode text. This library provides functions for manipulating Unicode strings and for manipulating C strings according to the Unicode standard. This package contains documentation.
- LGPL-3.0, GPL-2.0
-
-
- libusb1
- 1.0.21
- Userspace library to access USB (version 1.0).
- LGPL-2.1
-
-
- libvirt
- 4.2.0
- A toolkit to interact with the virtualization capabilities of recent versions of Linux.
- LGPL-2.1, GPL-2.0
-
-
- libx11
- 1.6.5
- This package provides a client interface to the X Window System otherwise known as 'Xlib'. It provides a complete API for the basic functions of the window system.
- MIT, BSD
-
-
- libxau
- 1.0.8
- libxau provides the main interfaces to the X11 authorisation handling which controls authorisation for X connections both client-side and server-side.
- MIT
-
-
- libxcb
- 1.12
- The X protocol C-language Binding (XCB) is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
- MIT
-
-
- libxdmcp
- 1.1.2
- The purpose of the X Display Manager Control Protocol (XDMCP) is to provide a uniform mechanism for an autonomous display to request login service from a remote host. An X terminal (screen keyboard mouse processor network interface) is a prime example of an autonomous display.
- MIT
-
-
- libxext
- 1.3.3
- libXext provides an X Window System client interface to several extensions to the X protocol. The supported protocol extensions are DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. libXext also provides a small set of utility functions to aid authors of client APIs for X protocol extensions.
- MIT
-
-
- libxkbcommon
- 0.7.1
- libxkbcommon is a keymap compiler and support library which processes a reduced subset of keymaps as defined by the XKB specification.
- MIT
-
-
- libxml-parser-perl
- 2.44
- XML::Parser - A perl module for parsing XML documents.
- Artistic-1.0, GPL-1.0
-
-
- libxml2
- 2.9.5
- The XML Parser Library allows for manipulation of XML files. Libxml2 exports Push and Pull type parser interfaces for both XML and HTML. It can do DTD validation at parse time on a parsed document instance or with an arbitrary DTD. Libxml2 includes complete XPath XPointer and Xinclude implementations. It also has a SAX like interface which is designed to be compatible with Expat.
- MIT
-
-
- libxrandr
- 1.5.1
- The X Resize Rotate and Reflect Extension called RandR for short brings the ability to resize rotate and reflect the root window of a screen. It is based on the X Resize and Rotate Extension as specified in the Proceedings of the 2001 Usenix Technical Conference [RANDR].
- MIT
-
-
- libxrender
- 0.9.10
- The X Rendering Extension (Render) introduces digital image composition as the foundation of a new rendering model within the X Window System. Rendering geometric figures is accomplished by client-side tessellation into either triangles or trapezoids. Text is drawn by loading glyphs into the server and rendering sets of them.
- MIT
-
-
- libxslt
- 1.1.29
- GNOME XSLT library.
- MIT
-
-
- libyaml
- 0.1.7
- LibYAML is a C library for parsing and emitting data in YAML 1.1 a human-readable data serialization format.
- MIT
-
-
- linux-firmware
- 0.0
- Firmware files for use with Linux kernel.
- Redistributable binaries
-
-
- linux-intel-guest
- 4.14.123
- Linux kernel.
- GPL-2.0
-
-
- linux-intel-host
- 4.14.123
- Linux kernel.
- GPL-2.0
-
-
- linux-libc-headers
- 4.12
- Sanitized set of kernel headers for the C library's use.
- GPL-2.0
-
-
- log-collector
- 1.0
- Service that collects platform logs
- Enea
-
-
- log4j1.2
- 1.2.17
- Java library to help the programmer output log statements to a variety of output targets
- Apache-2.0
-
-
- logkit
- 1.2.2
- Logging toolkit designed for secure performance orientated logging in Java applications
- Apache-2.0
-
-
- logrotate
- 3.12.3
- Rotates compresses removes and mails system log files.
- GPL-2.0
-
-
- lsb
- 4.1
- LSB support for OpenEmbedded.
- GPL-2.0
-
-
- lsbinitscripts
- 9.72
- SysV init scripts which are only used in an LSB image.
- GPL-2.0
-
-
- lshw
- 02.17
- A small tool to provide detailed information on the hardware configuration of the machine. It can report exact memory configuration firmware version mainboard configuration CPU version and speed cache configuration bus speed etc. on DMI-capable or EFI systems.
- GPL-2.0
-
-
- lsof
- 4.89
- Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open Files and it does just that.
- BSD
-
-
- lvm2
- 2.02.171
- LVM2 is a set of utilities to manage logical volumes in Linux.
- GPL-2.0, LGPL-2.0
-
-
- lxc
- 2.0.8
- lxc aims to use these new functionnalities to provide an userspace container object
- GPL-2.0
-
-
- lxd
- git
- "LXD is a container ""hypervisor"" and a new user experience for LXC Specifically it's made of three components: - A system-wide daemon (lxd) - A command line client (lxc) - An OpenStack Nova plugin (nova-compute-lxd)"
- Apache-2.0
-
-
- lz4
- 1.7.4
- LZ4 is a very fast lossless compression algorithm providing compression speed at 400 MB/s per core scalable with multi-cores CPU. It also features an extremely fast decoder with speed in multiple GB/s per core typically reaching RAM speed limits on multi-core systems.
- BSD, BSD-2-Clause, GPL-2.0
-
-
- lzo
- 2.10
- Lossless data compression library.
- GPL-2.0
-
-
- lzop
- 1.03
- lzop is a compression utility which is designed to be a companion to gzip. \nIt is based on the LZO data compression library and its main advantages over \ngzip are much higher compression and decompression speed at the cost of some \ncompression ratio. The lzop compression utility was designed with the goals \nof reliability speed portability and with reasonable drop-in compatibility \nto gzip.
- GPL-2.0
-
-
- m4
- 1.4.18
- GNU m4 is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible although it has some extensions (for example handling more than 9 positional parameters to macros). GNU M4 also has built-in functions for including files running shell commands doing arithmetic etc.
- GPL-3.0
-
-
- make
- 4.2.1
- Make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. Make gets its knowledge of how to build your program from a file called the makefile which lists each of the non-source files and how to compute it from other files.
- GPL-3.0, LGPL-2.0
-
-
- makedepend
- 1.0.5
- The makedepend program reads each sourcefile in sequence and parses it like a C-preprocessor processing all #include #define #undef #ifdef #ifndef #endif #if #elif and #else directives so that it can correctly tell which #include directives would be used in a compilation. Any #include directives can reference files having other #include directives and parsing will occur in these files as well.
- MIT
-
-
- makedevs
- 1.0.1
- Tool for creating device nodes.
- GPL-2.0
-
-
- mklibs
- 0.1.43
- mklibs produces cut-down shared libraries that contain only the routines required by a particular set of executables.
- GPL-2.0
-
-
- modemmanager
- 1.7.991
- ModemManager is a DBus-activated daemon which controls mobile broadband (2G/3G/4G) devices and connections
- GPL-2.0, LGPL-2.1
-
-
- mokutil
- 0.3.0
- The utility to manipulate machines owner keys which managed in shim.
- GPL-3.0
-
-
- mozjs
- 17.0.0
- SpiderMonkey is Mozilla's JavaScript engine written in C/C++.
- MPL-2.0
-
-
- mpfr
- 3.1.5
- C library for multiple-precision floating-point computations with exact rounding.
- GPL-3.0, LGPL-3.0
-
-
- mtools
- 4.0.18
- Mtools is a collection of utilities to access MS-DOS disks from GNU and Unix without mounting them.
- GPL-3.0
-
-
- nasm
- 2.13.01
- General-purpose x86 assembler.
- BSD-2-Clause
-
-
- ncurses
- 6.0
- SVr4 and XSI-Curses compatible curses library and terminfo tools including tic infocmp captoinfo. Supports color multiple highlights forms-drawing characters and automatic recognition of keypad and function-key sequences. Extensions include resizable windows and mouse support on both xterm and Linux console using the gpm library.
- MIT
-
-
- net-snmp
- 5.7.3
- Various tools relating to the Simple Network Management Protocol.
- BSD
-
-
- net-tools
- 1.60-26
- A collection of programs that form the base set of the NET-3 networking distribution for the Linux operating system
- GPL-2.0
-
-
- netbase
- 5.4
- This package provides the necessary infrastructure for basic TCP/IP based networking
- GPL-2.0
-
-
- netcat-openbsd
- 1.105
- A simple Unix utility which reads and writes data across network connections using TCP or UDP protocol. It is designed to be a reliable 'back-end' tool that can be used directly or easily driven by other programs and scripts. At the same time it is a feature-rich network debugging and exploration tool since it can create almost any kind of connection you would need and has several interesting built-in capabilities.
- BSD-3-Clause
-
-
- netcf
- 0.2.8
- netcf is a cross-platform network configuration library.
- LGPL-2.1
-
-
- nettle
- 3.3
- A low level cryptographic library.
- LGPL-3.0, GPL-2.0
-
-
- networkmanager
- 1.10.10
- NetworkManager.
- GPL-2.0
-
-
- nfv-init
- 1.0
- Enea service expected to be run after cloud-init
- Enea
-
-
- nfv-installer
- 1.0
- Enea NFV Access installer
- Enea
-
-
- nfva-cfgtool
- 1.0
- Command line tool to for accessing the Enea NFV Access install configuration json file
- Enea
-
-
- nfva-hotfixes
- 1.0
- Different hotfixes
- Enea
-
-
- nfva-startup
- 1.0
- Service that configures the network according to installer settings
- Enea
-
-
- nodejs
- 8.4.0
- nodeJS Evented I/O for V8 JavaScript
- MIT, BSD, Artistic-2.0
-
-
- notary
- 0.4.2
- Notary is a Docker project that allows anyone to have trust over arbitrary collections of data
- Apache-2.0
-
-
- nspr
- 4.16
- Netscape Portable Runtime Library.
- GPL-2.0, MPL-2.0, LGPL-2.1
-
-
- nss
- 3.31.1
- Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3 TLS PKCS 5 PKCS 7 PKCS 11 PKCS 12 S/MIME X.509 v3 certificates and other security standards.
- MPL-2.0, GPL-2.0, MPL-2.0, LGPL-2.1
-
-
- ntp-user-stub
- 1.0
- The NTP user/group were added in previous NFVA releases and are needed for OSTree upgrades to ensure backwards compatibility.
- Enea
-
-
- numactl
- 2.0.11
- Simple NUMA policy support. It consists of a numactl program to run other programs with a specific NUMA policy and a libnuma to do allocations with NUMA policy in applications.
- GPL-2.0, LGPL-2.1
-
-
- onig
- 5.9.6
- Regular expressions library. The characteristics of this library is that different character encoding for every regular expression object can be specified.
- BSD
-
-
- openjdk-8
- 102b14
- Java runtime based upon the OpenJDK Project
- GPL-2.0-with-classpath-exception
-
-
- openssh
- 7.5p1
- Secure rlogin/rsh/rcp/telnet replacement (OpenSSH) Ssh (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine.
- BSD
-
-
- openssl
- 1.0.2o
- Secure Socket Layer (SSL) binary and related cryptographic tools.
- OpenSSL
-
-
- openvswitch
- 2.9
- Open vSwitch is a production quality multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension while still supporting standard management interfaces and protocols (e.g. NetFlow sFlow SPAN RSPAN CLI LACP 802.1ag)
- Apache-2.0
-
-
- opkg-utils
- 0.3.5
- Additional utilities for the opkg package manager.
- GPL-2.0
-
-
- oro
- 2.0.8
- Perl5-compatible regular expressions library for Java
- Apache-2.0
-
-
- os-release
- 1.0
- The /etc/os-release file contains operating system identification data.
- MIT
-
-
- ostree-initrd
- 3
- Extremely basic live image init script.
- MIT
-
-
- ostree-rw
- 1.0
- Enea bash script to make current ostree hash writable
- Enea
-
-
- ostree
- v2018.7
- Tool for managing bootable immutable versioned filesystem trees.
- LGPL-2.0
-
-
- packagegroup-core-boot
- 1.0
- The minimal set of packages required to boot the system
- MIT
-
-
- packagegroup-core-ssh-openssh
- 1.0
- OpenSSH SSH client/server.
- MIT
-
-
- packagegroup-efi-secure-boot
- 1.0
- EFI Secure Boot packages for secure-environment.
- MIT
-
-
- packagegroup-enea-virtualization-4gusb-modems
- 1.0
- Packagegroup for 4G usb modems.
- MIT
-
-
- packagegroup-enea-virtualization-docker
- 1.0
- Packagegroup for Docker.
- MIT
-
-
- packagegroup-enea-virtualization-dpdk
- 1.0
- Packagegroup for DPDK.
- MIT
-
-
- packagegroup-enea-virtualization-guest
- 1.0
- This package group includes packages and packagegroups specific to the guest side of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-virtualization-host
- 1.0
- This package group includes packages and packagegroups specific to the host side of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-virtualization-libvirt
- 1.0
- Package group for libvirt.
- MIT
-
-
- packagegroup-enea-virtualization-lxc
- 1.0
- Packagegroup for LXC.
- MIT
-
-
- packagegroup-enea-virtualization-lxd
- 1.0
- Packagegroup for LXD.
- MIT
-
-
- packagegroup-enea-virtualization-ovs
- 1.0
- Packagegroup for Open vSwitch.
- MIT
-
-
- packagegroup-enea-virtualization-qemu
- 1.0
- Packagegroup for QEMU.
- MIT
-
-
- packagegroup-enea-virtualization
- 1.0
- This packagegroup includes packages and packagegroups required for both host and guest images of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-wifi
- 1.0
- This package group includes packages and packagegroups that enable WiFi connectivity in the Enea NFV Access platform
- MIT
-
-
- parted
- 3.2
- Disk partition editing/resizing utility.
- GPL-3.0
-
-
- partrt
- 1.1
- partrt is a tool for dividing a SMP Linux system into a real time domain and a non-real time domain.
- BSD
-
-
- pciutils
- 3.5.5
- The PCI Utilities package contains a library for portable access to PCI bus configuration space and several utilities based on this library.
- GPL-2.0
-
-
- perl
- 5.24.1
- Perl scripting language.
- Artistic-1.0, GPL-1.0
-
-
- pigz
- 2.3.4
- pigz which stands for parallel implementation of gzip is a fully functional replacement for gzip that exploits multiple processors and multiple cores to the hilt when compressing data. pigz was written by Mark Adler and uses the zlib and pthread libraries.
- Zlib, Apache-2.0
-
-
- pixman
- 0.34.0
- Pixman provides a library for manipulating pixel regions -- a set of Y-X banded rectangles image compositing using the Porter/Duff model and implicit mask generation for geometric primitives including trapezoids triangles and rectangles.
- MIT, PD
-
-
- pkgconfig
- 0.29.2
- pkg-config is a helper tool used when compiling applications and libraries. It helps determined the correct compiler/link options. It is also language-agnostic.
- GPL-2.0
-
-
- pm-utils
- 1.4.1
- Simple shell command line tools to suspend and hibernate.
- GPL-2.0
-
-
- polkit
- 0.113
- The polkit package is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes.
- LGPL-2.0
-
-
- popt
- 1.16
- Library for parsing command line options.
- MIT
-
-
- prelink
- 1.0
- The prelink package contains a utility which modifies ELF shared libraries and executables so that far fewer relocations need to be resolved at runtime and thus programs come up faster.
- GPL-2.0
-
-
- procps
- 3.3.12
- Procps contains a set of system utilities that provide system information about processes using the /proc filesystem. The package includes the programs ps top vmstat w kill and skill.
- GPL-2.0, LGPL-2.0
-
-
- pseudo
- 1.8.2
- Pseudo gives fake root capabilities to a normal user.
- LGPL-2.1
-
-
- ptest-runner
- 2.1
- The ptest-runner2 package installs a ptest-runner program which loops through all installed ptest test suites and runs them in sequence.
- GPL-2.0
-
-
- python-asn1crypto
- 0.23.0
- Python binding to the Networking and Cryptography (NaCl) library
- Apache-2.0
-
-
- python-certifi
- 2017.7.27.1
- This installable Python package contains a CA Bundle that you can reference in your Python code. This is useful for verifying HTTP requests for example. This is the same CA Bundle which ships with the Requests codebase and is derived from Mozilla Firefox's canonical set.
- ISC
-
-
- python-cffi
- 1.11.2
- Foreign Function Interface for Python calling C code.
- MIT
-
-
- python-chardet
- 3.0.4
- Universal encoding detector for Python 2 and 3.
- LGPL-2.1
-
-
- python-cryptography-vectors
- 2.0.3
- Test vectors for the cryptography package..
- Apache-2.0, BSD
-
-
- python-cryptography
- 2.0.3
- Provides cryptographic recipes and primitives to python developers.
- Apache-2.0, BSD
-
-
- python-cython
- 0.27.1
- Cython is a language specially designed for writing Python extension modules. It's designed to bridge the gap between the nice high-level easy-to-use world of Python and the messy low-level world of C.
- Apache-2.0
-
-
- python-enum34
- 1.1.6
- backport of Python 3.4's enum package.
- BSD-3-Clause
-
-
- python-functools32
- 3.2.3-2
- Backport of the functools module from Python 3.2.3 for use on 2.7 and PyPy..
- Python-2.0
-
-
- python-futures
- 3.0.5
- The concurrent.futures module provides a high-level interface for asynchronously executing callables.
- BSD
-
-
- python-idna
- 2.6
- Internationalised Domain Names in Applications.
- BSD-3-Clause, Python-2.0, Unicode
-
-
- python-ipaddress
- 1.0.18
- Python 3.3+'s ipaddress for Python 2.6 2.7 3.2..
- Python-2.0
-
-
- python-iso8601
- 0.1.12
- Simple module to parse ISO 8601 dates.
- MIT
-
-
- python-jsonpatch
- 1.16
- Appling JSON patches in Python 2.6+ and 3.x.
- BSD
-
-
- python-jsonpointer
- 1.12
- Resolve JSON Pointers in Python.
- BSD
-
-
- python-jsonschema
- 2.6.0
- An implementation of JSON Schema validation for Python.
- MIT
-
-
- python-ndg-httpsclient
- 0.4.3
- Provides enhanced HTTPS support for httplib and urllib2 using PyOpenSSL
- BSD
-
-
- python-netaddr
- 0.7.19
- A network address manipulation library for Python..
- BSD
-
-
- python-netifaces
- 0.10.6
- Portable network interface information.
- MIT
-
-
- python-pip
- 9.0.1
- PIP is a tool for installing and managing Python packages.
- MIT, LGPL-2.1
-
-
- python-pretend
- 1.0.8
- A library for stubbing in Python.
- BSD
-
-
- python-prettytable
- 0.7.2
- Python library for displaying tabular data in a ASCII table format.
- BSD
-
-
- python-psutil
- 5.3.1
- A cross-platform process and system utilities module for Python.
- BSD
-
-
- python-py
- 1.4.34
- Library with cross-python path ini-parsing io code log facilities.
- MIT
-
-
- python-pyasn1
- 0.3.6
- Python library implementing ASN.1 types..
- BSD-2-Clause
-
-
- python-pycparser
- 2.18
- Parser of the C language written in pure Python.
- BSD-3-Clause
-
-
- python-pyopenssl
- 17.3.0
- Simple Python wrapper around the OpenSSL library.
- Apache-2.0
-
-
- python-pysocks
- 1.6.7
- A Python SOCKS client module
- BSD
-
-
- python-pytest-runner
- 2.12.1
- Invoke py.test as distutils command with dependency resolution.
- MIT
-
-
- python-pytest
- 3.2.2
- Simple powerful teting with python.
- MIT
-
-
- python-pyyaml
- 3.11
- YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. . PyYAML features a complete YAML 1.1 parser Unicode support pickle support capable extension API and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. . PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistance.
- MIT
-
-
- python-requests
- 2.18.4
- Python HTTP for Humans.
- Apache-2.0
-
-
- python-rfc3987
- 1.3.7
- Parsing and validation of URIs (RFC 3986) and IRIs (RFC 3987).
- GPL-3.0
-
-
- python-setuptools-scm
- 1.15.6
- the blessed package to manage your versions by scm tags.
- MIT
-
-
- python-setuptools
- 36.2.7
- Download build install upgrade and uninstall Python packages.
- MIT
-
-
- python-six
- 1.11.0
- Python 2 and 3 compatibility library.
- MIT
-
-
- python-strict-rfc3339
- 0.7
- Strict simple lightweight RFC3339 function.s.
- GPL-3.0
-
-
- python-urllib3
- 1.22
- Python HTTP library with thread-safe connection pooling file post support sanity friendly and more.
- MIT
-
-
- python-vcversioner
- 2.16.0.0
- Python vcversioner automagically update the project's version.
- ISC
-
-
- python
- 2.7.13
- The Python Programming Language.
- Python-2.0
-
-
- python3-netifaces
- 0.10.6
- Portable network interface information.
- MIT
-
-
- python3-pip
- 9.0.1
- The PyPA recommended tool for installing Python packages.
- MIT
-
-
- python3-setuptools
- 36.2.7
- Download build install upgrade and uninstall Python packages.
- MIT
-
-
- python3-six
- 1.10.0
- Python 2 and 3 compatibility library.
- MIT
-
-
- python3-twisted
- 13.2.0
- Twisted is an event-driven networking framework written in Python and licensed under the LGPL. Twisted supports TCP UDP SSL/TLS multicast Unix sockets a large number of protocols (including HTTP NNTP IMAP SSH IRC FTP and others) and much more.
- MIT
-
-
- python3-zopeinterface
- 4.4.3
- Interface definitions for Zope products.
- ZPL-2.1
-
-
- python3
- 3.5.3
- The Python Programming Language.
- Python-2.0
-
-
- qemu-helper
- 1.0
- Helper utilities needed by the runqemu script.
- GPL-2.0
-
-
- qemu
- 2.11.1
- Fast open source processor emulator.
- GPL-2.0, LGPL-2.1
-
-
- qemuwrapper
- 1.0
- QEMU wrapper script.
- MIT
-
-
- quilt
- 0.65
- Tool for working with series of patches.
- GPL-2.0
-
-
- randrproto
- 1.5.0
- This package provides the wire protocol for the X Resize Rotate and Reflect extension. This extension provides the ability to resize rotate and reflect the root window of a screen.
- MIT
-
-
- readline
- 7.0
- The GNU Readline library provides a set of functions for use by applications that allow users to edit command lines as they are typed in. Both Emacs and vi editing modes are available. The Readline library includes additional functions to maintain a list of previously-entered command lines to recall and perhaps reedit those lines and perform csh-like history expansion on previous commands.
- GPL-3.0
-
-
- regexp
- 1.5
- Java Regular Expression package
- Apache-2.0
-
-
- renderproto
- 0.11.1
- This package provides the wire protocol for the X Rendering extension. This is the basis the image composition within the X window system.
- MIT
-
-
- rhino
- 1.7r4
- Lexical analyzer generator for Java
- MPL-2.0
-
-
- rpm
- 4.13.90
- The RPM Package Manager (RPM) is a powerful command line driven package management system capable of installing uninstalling verifying querying and updating software packages. Each software package consists of an archive of files along with information about the package like its version a description etc.
- GPL-2.0
-
-
- rsync
- 3.1.3
- File synchronization tool.
- GPL-3.0
-
-
- run-postinsts
- 1.0
- Runs postinstall scripts on first boot of the target device.
- MIT
-
-
- runc-docker
- 1.0.0-rc3
- runc is a CLI tool for spawning and running containers according to the OCI specification.
- Apache-2.0
-
-
- sbsigntool
- 0.6
- Utilities for signing UEFI binaries for use with secure boot.
- GPL-3.0
-
-
- sed
- 4.2.2
- Stream EDitor (text filtering utility).
- GPL-3.0
-
-
- seloader
- 0.4.6
- The SELoader is designed to authenticate the non-PE files such as grub configuration initrd grub modules which cannot be verified by the MOK Verify Protocol registered by shim loader. In order to conveniently authenticate the PE file with gBS->LoadImage() and gBS->StartImage() the SELoader hooks EFI Security2 Architectural Protocol and employs MOK Verify Protocol to verify the PE file. If only UEFI Secure Boot is enabled the SELoader just simplily calls gBS->LoadImage() and gBS->StartImage() to allow BIOS to verify PE file. The SELoader publishes MOK2 Verify Protocol which provides a flexible interface to allow the bootloader to verify the file file buffer or memory buffer without knowing the file format.
- BSD-3-Clause
-
-
- servlet2.3
- 4.1.37
- Servlet API 2.3 (from Tomcat 4.1)
- Apache-2.0
-
-
- shadow-securetty
- 4.2.1
- Provider of the machine specific securetty file.
- MIT
-
-
- shadow-sysroot
- 4.2.1
- Shadow utils requirements for useradd.bbclass.
- BSD, Artistic-1.0
-
-
- shadow
- 4.2.1
- Tools to change and administer password and group data.
- BSD, Artistic-1.0
-
-
- shared-mime-info
- 1.8
- Shared MIME type database and specification.
- LGPL-2.0
-
-
- shim
- 12
- shim is a trivial EFI application that when run attempts to open and execute another application. It will initially attempt to do this via the standard EFI LoadImage() and StartImage() calls. If these fail (because secure boot is enabled and the binary is not signed with an appropriate key for instance) it will then validate the binary against a built-in certificate. If this succeeds and if the binary or signing key are not blacklisted then shim will relocate and execute the binary.
- BSD-2-Clause
-
-
- simpleproxy
- 1.0
- Simpleproxy.
- GPL-2.0
-
-
- slang
- 2.3.1a
- S-Lang is an interpreted language and a programming library. The S-Lang language was designed so that it can be easily embedded into a program to provide the program with a powerful extension language. The S-Lang library provided in this package provides the S-Lang extension language. S-Lang's syntax resembles C which makes it easy to recode S-Lang procedures in C if you need to.
- GPL-2.0
-
-
- sqlite3
- 3.20.0
- Embeddable SQL database engine.
- PD
-
-
- squashfs-tools
- 4.3
- Tools for manipulating SquashFS filesystems.
- GPL-2.0, PD
-
-
- sshpass
- 1.06
- Tool for non-interactivly performing ssh password authentication
- GPL-2.0
-
-
- swig
- 3.0.12
- SWIG - Simplified Wrapper and Interface Generator.
- BSD, GPL-3.0
-
-
- sysfsutils
- 2.1.0
- Tools for working with the sysfs virtual filesystem. The tool 'systool' can query devices by bus class and topology.
- GPL-2.0, LGPL-2.1
-
-
- sysklogd
- 1.5.1
- The sysklogd package implements two system log daemons: syslogd klogd
- GPL-2.0, BSD
-
-
- syslinux
- 6.03
- Multi-purpose linux bootloader.
- GPL-2.0
-
-
- systemd-boot
- 234
- systemd is a system and service 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.
- GPL-2.0, LGPL-2.1
-
-
- systemd-compat-units
- 1.0
- Enhances systemd compatilibity with existing SysVinit scripts.
- MIT
-
-
- systemd-serialgetty
- 1.0
- Serial terminal support for systemd.
- GPL-2.0
-
-
- systemd-systemctl
- 1.0
- Wrapper for enabling systemd services.
- MIT
-
-
- systemd
- 234
- systemd is a system and service 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.
- GPL-2.0, LGPL-2.1
-
-
- tar
- 1.29
- GNU tar saves many files together into a single tape or disk archive and can restore individual files from the archive.
- GPL-3.0
-
-
- tcl
- 8.6.7
- Tool Command Language.
- tcl, BSD-3-Clause
-
-
- tcpdump
- 4.9.2
- A sophisticated network protocol analyzer.
- BSD
-
-
- texinfo-dummy
- 1.0
- Fake version of the texinfo utility suite.
- MIT
-
-
- thin-provisioning-tools
- 0.6.3
- A suite of tools for manipulating the metadata of the dm-thin device-mapper target.
- GPL-3.0
-
-
- tunctl
- 1.5
- Tool for controlling the Linux TUN/TAP driver.
- GPL-2.0
-
-
- tzcode
- 2018c
- tzcode timezone zoneinfo utils -- zic zdump tzselect.
- PD, BSD, BSD-3-Clause
-
-
- tzdata
- 2018c
- Timezone data.
- PD, BSD, BSD-3-Clause
-
-
- udev-extraconf
- 1.1
- Extra machine specific configuration files for udev specifically blacklist information.
- MIT
-
-
- unifdef
- 2.11
- Selectively remove #ifdef statements from sources.
- BSD-2-Clause
-
-
- unzip
- 6.0
- Utilities for extracting and viewing files in .zip archives.
- BSD-3-Clause
-
-
- update-rc.d
- 0.7
- update-rc.d is a utility that allows the management of symlinks to the initscripts in the /etc/rcN.d directory structure.
- GPL-2.0
-
-
- usb-modeswitch-data
- 20170205
- Data files for usbmodeswitch.
- GPL-2.0
-
-
- usb-modeswitch
- 2.5.0
- A mode switching tool for controlling 'flip flop' (multiple device) USB gear.
- GPL-2.0
-
-
- usbutils
- 013
- Contains the lsusb utility for inspecting the devices connected to the USB bus.
- GPL-2.0, GPL-3.0
-
-
- util-linux
- 2.30
- Util-linux includes a suite of basic system administration utilities commonly found on most Linux systems. Some of the more important utilities include disk partitioning kernel message management filesystem creation and system login.
- GPL-2.0, LGPL-2.1, BSD
-
-
- util-macros
- 1.19.1
- M4 autotools macros used by various X.org programs.
- MIT
-
-
- v86d
- 0.1.10
- User support binary for the uvesafb kernel module.
- GPL-2.0
-
-
- vala
- 0.36.4
- Vala is a C#-like language dedicated to ease GObject programming. Vala compiles to plain C and has no runtime environment nor penalities whatsoever.
- LGPL-2.1
-
-
- volatile-binds
- 1.0
- Volatile bind mount setup and configuration for read-only-rootfs
- MIT
-
-
- web-installer-backend
- 0.1
- Web installer go server
- Enea, BSD-3-Clause
-
-
- web-installer-frontend
- 0.1
- Web installer post-install application
- Enea, Apache-2.0, BSD, BSD-2-Clause, BSD-3-Clause, CC-BY-4.0, ISC, MIT, Zlib
-
-
- which
- 2.21
- Which is a utility that prints out the full path of the executables that bash(1) would execute when the passed program names would have been entered on the shell prompt. It does this by using the exact same algorithm as bash.
- GPL-3.0
-
-
- wpa-supplicant
- 2.6
- Client for Wi-Fi Protected Access (WPA).
- BSD
-
-
- xalan-j
- 2.7.1
- Java XSLT processor
- Apache-2.0
-
-
- xcb-proto
- 1.12
- Function prototypes for the X protocol C-language Binding (XCB). XCB is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
- MIT
-
-
- xerces-j
- 2.11.0
- Reference implementation of XNI the Xerces Native Interface and also a fully conforming XML Schema processor.
- Apache-2.0
-
-
- xextproto
- 7.3.0
- This package provides the wire protocol for several X extensions. These protocol extensions include DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. In addition a small set of utility functions are also available.
- MIT
-
-
- xkeyboard-config
- 2.21
- The non-arch keyboard configuration database for X Window. The goal is to provide the consistent well-structured frequently released open source of X keyboard configuration data for X Window System implementations. The project is targeted to XKB-based systems.
- MIT
-
-
- xml-commons-resolver1.1
- 1.2
- Library to resolve various public or system identifiers into accessible URLs (Java)
- Apache-2.0
-
-
- xproto
- 7.0.31
- This package provides the basic headers for the X Window System.
- MIT
-
-
- xtrans
- 1.3.5
- The X Transport Interface is intended to combine all system and transport specific code into a single place. This API should be used by all libraries clients and servers of the X Window System. Use of this API should allow the addition of new types of transports and support for new platforms without making any changes to the source except in the X Transport Interface code.
- MIT
-
-
- xz
- 5.2.3
- Utilities for managing LZMA compressed files.
- GPL-2.0, GPL-3.0-with-autoconf-exception, LGPL-2.1, PD
-
-
- yajl
- 2.1.0
- YAJL is a small event-driven (SAX-style) JSON parser written in ANSI C and a small validating JSON generator.
- ISC
-
-
- zip
- 3.0
- Compressor/archiver for creating and modifying .zip files.
- BSD-3-Clause
-
-
- zisofs-tools
- 1.0.8
- Utilities for creating compressed CD-ROM filesystems.
- GPL-2.0
-
-
- zlib
- 1.2.11
- Zlib is a general-purpose patent-free lossless data compression library which is used by many different programs.
- Zlib
-
-
-
-
-
-
- Open Source Licenses
-
-AFL-2.0
-
-
-The Academic Free License
- v. 2.0
-
-This Academic Free License (the "License") applies to any original work of authorship
-(the "Original Work") whose owner (the "Licensor") has placed the following notice
-immediately following the copyright notice for the Original Work:
-Licensed under the Academic Free License version 2.0
-
-1) Grant of Copyright License. Licensor hereby grants You a world-wide, royalty-free,
-non-exclusive, perpetual, sublicenseable license to do the following:
-a) to reproduce the Original Work in copies;
-
-b) to prepare derivative works ("Derivative Works") based upon the Original Work;
-
-c) to distribute copies of the Original Work and Derivative Works to the public;
-
-d) to perform the Original Work publicly; and
-
-e) to display the Original Work publicly.
-
-2) Grant of Patent License. Licensor hereby grants You a world-wide, royalty-free,
-non-exclusive, perpetual, sublicenseable license, under patent claims owned or
-controlled by the Licensor that are embodied in the Original Work as furnished by the
-Licensor, to make, use, sell and offer for sale the Original Work and Derivative
-Works.
-
-3) Grant of Source Code License. The term "Source Code" means the preferred form of
-the Original Work for making modifications to it and all available documentation
-describing how to modify the Original Work. Licensor hereby agrees to provide a
-machine-readable copy of the Source Code of the Original Work along with each copy of
-the Original Work that Licensor distributes. Licensor reserves the right to satisfy
-this obligation by placing a machine-readable copy of the Source Code in an
-information repository reasonably calculated to permit inexpensive and convenient
-access by You for as long as Licensor continues to distribute the Original Work, and
-by publishing the address of that information repository in a notice immediately
-following the copyright notice that applies to the Original Work.
-
-4) Exclusions From License Grant. Neither the names of Licensor, nor the names of any
-contributors to the Original Work, nor any of their trademarks or service marks, may
-be used to endorse or promote products derived from this Original Work without express
-prior written permission of the Licensor. Nothing in this License shall be deemed to
-grant any rights to trademarks, copyrights, patents, trade secrets or any other
-intellectual property of Licensor except as expressly stated herein. No patent
-license is granted to make, use, sell or offer to sell embodiments of any patent
-claims other than the licensed claims defined in Section 2. No right is granted to
-the trademarks of Licensor even if such marks are included in the Original Work.
-Nothing in this License shall be interpreted to prohibit Licensor from licensing under
-different terms from this License any Original Work that Licensor otherwise would have
-a right to license.
-
-5) This section intentionally omitted.
-
-6) Attribution Rights. You must retain, in the Source Code of any Derivative Works
-that You create, all copyright, patent or trademark notices from the Source Code of
-the Original Work, as well as any notices of licensing and any descriptive text
-identified therein as an "Attribution Notice." You must cause the Source Code for any
-Derivative Works that You create to carry a prominent Attribution Notice reasonably
-calculated to inform recipients that You have modified the Original Work.
-
-7) Warranty of Provenance and Disclaimer of Warranty. Licensor warrants that the
-copyright in and to the Original Work and the patent rights granted herein by Licensor
-are owned by the Licensor or are sublicensed to You under the terms of this License
-with the permission of the contributor(s) of those copyrights and patent rights.
-Except as expressly stated in the immediately proceeding sentence, the Original Work
-is provided under this License on an "AS IS" BASIS and WITHOUT WARRANTY, either
-express or implied, including, without limitation, the warranties of NON-INFRINGEMENT,
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
-QUALITY OF THE ORIGINAL WORK IS WITH YOU. This DISCLAIMER OF WARRANTY constitutes an
-essential part of this License. No license to Original Work is granted hereunder
-except under this disclaimer.
-
-8) Limitation of Liability. Under no circumstances and under no legal theory, whether
-in tort (including negligence), contract, or otherwise, shall the Licensor be liable
-to any person for any direct, indirect, special, incidental, or consequential damages
-of any character arising as a result of this License or the use of the Original Work
-including, without limitation, damages for loss of goodwill, work stoppage, computer
-failure or malfunction, or any and all other commercial damages or losses. This
-limitation of liability shall not apply to liability for death or personal injury
-resulting from Licensor`s negligence to the extent applicable law prohibits such
-limitation. Some jurisdictions do not allow the exclusion or limitation of incidental
-or consequential damages, so this exclusion and limitation may not apply to You.
-
-9) Acceptance and Termination. If You distribute copies of the Original Work or a
-Derivative Work, You must make a reasonable effort under the circumstances to obtain
-the express assent of recipients to the terms of this License. Nothing else but this
-License (or another written agreement between Licensor and You) grants You permission
-to create Derivative Works based upon the Original Work or to exercise any of the
-rights granted in Section 1 herein, and any attempt to do so except under the terms of
-this License (or another written agreement between Licensor and You) is expressly
-prohibited by U.S. copyright law, the equivalent laws of other countries, and by
-international treaty. Therefore, by exercising any of the rights granted to You in
-Section 1 herein, You indicate Your acceptance of this License and all of its terms
-and conditions.
-
-10) Termination for Patent Action. This License shall terminate automatically and You
-may no longer exercise any of the rights granted to You by this License as of the date
-You commence an action, including a cross-claim or counterclaim, for patent
-infringement (i) against Licensor with respect to a patent applicable to software or
-(ii) against any entity with respect to a patent applicable to the Original Work (but
-excluding combinations of the Original Work with other software or hardware).
-
-11) Jurisdiction, Venue and Governing Law. Any action or suit relating to this License
-may be brought only in the courts of a jurisdiction wherein the Licensor resides or in
-which Licensor conducts its primary business, and under the laws of that jurisdiction
-excluding its conflict-of-law provisions. The application of the United Nations
-Convention on Contracts for the International Sale of Goods is expressly excluded.
-Any use of the Original Work outside the scope of this License or after its
-termination shall be subject to the requirements and penalties of the U.S. Copyright
-Act, 17 U.S.C. ¤ 101 et seq., the equivalent laws of other countries, and
-international treaty. This section shall survive the termination of this License.
-
-12) Attorneys Fees. In any action to enforce the terms of this License or seeking
-damages relating thereto, the prevailing party shall be entitled to recover its costs
-and expenses, including, without limitation, reasonable attorneys` fees and costs
-incurred in connection with such action, including any appeal of such action. This
-section shall survive the termination of this License.
-
-13) Miscellaneous. This License represents the complete agreement concerning the
-subject matter hereof. If any provision of this License is held to be unenforceable,
-such provision shall be reformed only to the extent necessary to make it enforceable.
-
-14) Definition of "You" in This License. "You" throughout this License, whether in
-upper or lower case, means an individual or a legal entity exercising rights under,
-and complying with all of the terms of, this License. For legal entities, "You"
-includes any entity that controls, is controlled by, or is under common control with
-you. For purposes of this definition, "control" means (i) the power, direct or
-indirect, to cause the direction or management of such entity, whether by contract or
-otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares,
-or (iii) beneficial ownership of such entity.
-
-15) Right to Use. You may use the Original Work in all ways not otherwise restricted
-or conditioned by this License or by law, and Licensor promises not to interfere with
-or be responsible for such uses by You.
-
-This license is Copyright (C) 2003 Lawrence E. Rosen. All rights reserved.
-Permission is hereby granted to copy and distribute this license without modification.
-This license may not be modified without the express written permission of its
-copyright owner.
-
-
-
-
-AMD
-
-� 2005 Advanced Micro Devices, Inc. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that existing copyright notices
-are retained in all copies, this notice is included verbatim in any
-distributions, and the terms and conditions hererin are met.
-
-Use of the this software manifests acceptance of the terms of this
-license by performance.
-
-The name of Advanced Micro Devices, Inc. may not be used to endorse or
-promote products derived from this software without specific prior
-written permission.
-
-THIS SOFTWARE IS PROVIDED BY ADVANCED MICRO DEVICES, INC. "AS IS" AND ANY
-EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
-PURPOSE AND NON-INFRINGEMENT, OR THOSE ARISING FROM CUSTOM OF TRADE OR
-COURSE OF USAGE ARE DISCLAIMED.
-
-IN NO EVENT SHALL ADVANCED MICRO DEVICES, INC. BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED, AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE ITS DOCUMENTATION OR ANY DERIVATIVES
-THEREOF, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BY USING THIS
-SOFTWARE WITHOUT CHARGE, YOU ACCEPT THIS ALLOCATION OF RISK. THIS
-DISCLAIMER OF LIABILITY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE.
-ADVANCED MICRO DEVICES, INC. HAS NO OBLIGATION TO PROVIDE MAINTENANCE,
-SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS OF THIS SOFTWARE.
-
-In the redistribution and use of this software, each party shall at all
-times comply with all applicable governmental laws, statutes, ordinances,
-rules, regulations, orders, and other requirements, including without
-limitation such governmental requirements applicable to environmental
-protection, health, safety, wages, hours, equal employment opportunity,
-nondiscrimination, working conditions, import or export control, and
-transportation. Without limiting the foregoing, each party shall adhere
-to the U.S. Export Administration Regulations (EAR), currently found at
-15 C.F.R. Sections 730 through 744, and, unless properly authorized by
-the U.S. Government, shall not (1) export, re-export or release restricted
-technology, software, or source code to a national of a country in Country
-Groups D:1 or E:1, or (2) export to Country Groups D:1 or E:1 the direct
-product of such technology or software, if such foreign produced direct
-product is subject to national security controls as identified on the
-Commerce Control List (currently found in Supplement 1 to Section 774 of EAR).
-These export requirements shall survive any expiration or termination
-of this agreement.
-
-
-
-Apache-2.0
-
-
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don`t include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
-
-Artistic-1.0
-
-
-The Artistic License
-Preamble
-
-The intent of this document is to state the conditions under which a Package may be
-copied, such that the Copyright Holder maintains some semblance of artistic control
-over the development of the package, while giving the users of the package the right
-to use and distribute the Package in a more-or-less customary fashion, plus the right
-to make reasonable modifications.
-
-Definitions:
-
-"Package" refers to the collection of files distributed by the Copyright Holder, and
-derivatives of that collection of files created through textual modification.
-"Standard Version" refers to such a Package if it has not been modified, or has been
-modified in accordance with the wishes of the Copyright Holder.
-"Copyright Holder" is whoever is named in the copyright or copyrights for the package.
-"You" is you, if you`re thinking about copying or distributing this Package.
-"Reasonable copying fee" is whatever you can justify on the basis of media cost,
-duplication charges, time of people involved, and so on. (You will not be required to
-justify it to the Copyright Holder, but only to the computing community at large as a
-market that must bear the fee.)
-"Freely Available" means that no fee is charged for the item itself, though there may
-be fees involved in handling the item. It also means that recipients of the item may
-redistribute it under the same conditions they received it.
-1. You may make and give away verbatim copies of the source form of the Standard
-Version of this Package without restriction, provided that you duplicate all of the
-original copyright notices and associated disclaimers.
-
-2. You may apply bug fixes, portability fixes and other modifications derived from the
-Public Domain or from the Copyright Holder. A Package modified in such a way shall
-still be considered the Standard Version.
-
-3. You may otherwise modify your copy of this Package in any way, provided that you
-insert a prominent notice in each changed file stating how and when you changed that
-file, and provided that you do at least ONE of the following:
-
-a) place your modifications in the Public Domain or otherwise make them Freely
-Available, such as by posting said modifications to Usenet or an equivalent medium, or
-placing the modifications on a major archive site 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.
-
-4. You may distribute the programs of this Package in object code or executable form,
-provided that you do at least ONE of the following:
-
-a) distribute a Standard Version of the executables and library files, together with
-instructions (in the manual page or equivalent) on where to get the Standard Version.
-
-b) accompany the distribution with the machine-readable source of the Package with
-your modifications.
-
-c) accompany any non-standard executables with their corresponding Standard Version
-executables, giving the non-standard executables non-standard names, and clearly
-documenting the differences in manual pages (or equivalent), together with
-instructions on where to get the Standard Version.
-
-d) make other distribution arrangements with the Copyright Holder.
-
-5. You may charge a reasonable copying fee for any distribution of this Package. You
-may charge any fee you choose for support of this Package. You may not charge a fee
-for this Package itself. However, you may distribute this Package in aggregate with
-other (possibly commercial) programs as part of a larger (possibly commercial)
-software distribution provided that you do not advertise this Package as a product of
-your own.
-
-6. The scripts and library files supplied as input to or produced as output from the
-programs of this Package do not automatically fall under the copyright of this
-Package, but belong to whomever generated them, and may be sold commercially, and may
-be aggregated with this Package.
-
-7. C or perl subroutines supplied by you and linked into this Package shall not be
-considered part of this Package.
-
-8. The name of the Copyright Holder may not be used to endorse or promote products
-derived from this software without specific prior written permission.
-
-9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
-INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS
-FOR A PARTICULAR PURPOSE.
-
-The End
-
-
-
-
-Artistic-2.0
-
-
- The Artistic License 2.0
-
- Copyright (c) 2000-2006, The Perl Foundation.
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-Preamble
-
-This license establishes the terms under which a given free software
-Package may be copied, modified, distributed, and/or redistributed.
-The intent is that the Copyright Holder maintains some artistic
-control over the development of that Package while still keeping the
-Package available as open source and free software.
-
-You are always permitted to make arrangements wholly outside of this
-license directly with the Copyright Holder of a given Package. If the
-terms of this license do not permit the full use that you propose to
-make of the Package, you should contact the Copyright Holder and seek
-a different licensing arrangement.
-
-Definitions
-
- "Copyright Holder" means the individual(s) or organization(s)
- named in the copyright notice for the entire Package.
-
- "Contributor" means any party that has contributed code or other
- material to the Package, in accordance with the Copyright Holder`s
- procedures.
-
- "You" and "your" means any person who would like to copy,
- distribute, or modify the Package.
-
- "Package" means the collection of files distributed by the
- Copyright Holder, and derivatives of that collection and/or of
- those files. A given Package may consist of either the Standard
- Version, or a Modified Version.
-
- "Distribute" means providing a copy of the Package or making it
- accessible to anyone else, or in the case of a company or
- organization, to others outside of your company or organization.
-
- "Distributor Fee" means any fee that you charge for Distributing
- this Package or providing support for this Package to another
- party. It does not mean licensing fees.
-
- "Standard Version" refers to the Package if it has not been
- modified, or has been modified only in ways explicitly requested
- by the Copyright Holder.
-
- "Modified Version" means the Package, if it has been changed, and
- such changes were not explicitly requested by the Copyright
- Holder.
-
- "Original License" means this Artistic License as Distributed with
- the Standard Version of the Package, in its current version or as
- it may be modified by The Perl Foundation in the future.
-
- "Source" form means the source code, documentation source, and
- configuration files for the Package.
-
- "Compiled" form means the compiled bytecode, object code, binary,
- or any other form resulting from mechanical transformation or
- translation of the Source form.
-
-
-Permission for Use and Modification Without Distribution
-
-(1) You are permitted to use the Standard Version and create and use
-Modified Versions for any purpose without restriction, provided that
-you do not Distribute the Modified Version.
-
-
-Permissions for Redistribution of the Standard Version
-
-(2) You may Distribute verbatim copies of the Source form of the
-Standard Version of this Package in any medium without restriction,
-either gratis or for a Distributor Fee, provided that you duplicate
-all of the original copyright notices and associated disclaimers. At
-your discretion, such verbatim copies may or may not include a
-Compiled form of the Package.
-
-(3) You may apply any bug fixes, portability changes, and other
-modifications made available from the Copyright Holder. The resulting
-Package will still be considered the Standard Version, and as such
-will be subject to the Original License.
-
-
-Distribution of Modified Versions of the Package as Source
-
-(4) You may Distribute your Modified Version as Source (either gratis
-or for a Distributor Fee, and with or without a Compiled form of the
-Modified Version) provided that you clearly document how it differs
-from the Standard Version, including, but not limited to, documenting
-any non-standard features, executables, or modules, and provided that
-you do at least ONE of the following:
-
- (a) make the Modified Version available to the Copyright Holder
- of the Standard Version, under the Original License, so that the
- Copyright Holder may include your modifications in the Standard
- Version.
-
- (b) ensure that installation of your Modified Version does not
- prevent the user installing or running the Standard Version. In
- addition, the Modified Version must bear a name that is different
- from the name of the Standard Version.
-
- (c) allow anyone who receives a copy of the Modified Version to
- make the Source form of the Modified Version available to others
- under
-
- (i) the Original License or
-
- (ii) a license that permits the licensee to freely copy,
- modify and redistribute the Modified Version using the same
- licensing terms that apply to the copy that the licensee
- received, and requires that the Source form of the Modified
- Version, and of any works derived from it, be made freely
- available in that license fees are prohibited but Distributor
- Fees are allowed.
-
-
-Distribution of Compiled Forms of the Standard Version
-or Modified Versions without the Source
-
-(5) You may Distribute Compiled forms of the Standard Version without
-the Source, provided that you include complete instructions on how to
-get the Source of the Standard Version. Such instructions must be
-valid at the time of your distribution. If these instructions, at any
-time while you are carrying out such distribution, become invalid, you
-must provide new instructions on demand or cease further distribution.
-If you provide valid instructions or cease distribution within thirty
-days after you become aware that the instructions are invalid, then
-you do not forfeit any of your rights under this license.
-
-(6) You may Distribute a Modified Version in Compiled form without
-the Source, provided that you comply with Section 4 with respect to
-the Source of the Modified Version.
-
-
-Aggregating or Linking the Package
-
-(7) You may aggregate the Package (either the Standard Version or
-Modified Version) with other packages and Distribute the resulting
-aggregation provided that you do not charge a licensing fee for the
-Package. Distributor Fees are permitted, and licensing fees for other
-components in the aggregation are permitted. The terms of this license
-apply to the use and Distribution of the Standard or Modified Versions
-as included in the aggregation.
-
-(8) You are permitted to link Modified and Standard Versions with
-other works, to embed the Package in a larger work of your own, or to
-build stand-alone binary or bytecode versions of applications that
-include the Package, and Distribute the result without restriction,
-provided the result does not expose a direct interface to the Package.
-
-
-Items That are Not Considered Part of a Modified Version
-
-(9) Works (including, but not limited to, modules and scripts) that
-merely extend or make use of the Package, do not, by themselves, cause
-the Package to be a Modified Version. In addition, such works are not
-considered parts of the Package itself, and are not subject to the
-terms of this license.
-
-
-General Provisions
-
-(10) Any use, modification, and distribution of the Standard or
-Modified Versions is governed by this Artistic License. By using,
-modifying or distributing the Package, you accept this license. Do not
-use, modify, or distribute the Package, if you do not accept this
-license.
-
-(11) If your Modified Version has been derived from a Modified
-Version made by someone other than you, you are nevertheless required
-to ensure that your Modified Version complies with the requirements of
-this license.
-
-(12) This license does not grant you the right to use any trademark,
-service mark, tradename, or logo of the Copyright Holder.
-
-(13) This license includes the non-exclusive, worldwide,
-free-of-charge patent license to make, have made, use, offer to sell,
-sell, import and otherwise transfer the Package with respect to any
-patent claims licensable by the Copyright Holder that are necessarily
-infringed by the Package. If you institute patent litigation
-(including a cross-claim or counterclaim) against any party alleging
-that the Package constitutes direct or contributory patent
-infringement, then this Artistic License to you shall terminate on the
-date that such litigation is filed.
-
-(14) Disclaimer of Warranty:
-THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS
-IS` AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
-NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL
-LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL
-BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
-DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-BSD
-
-Copyright (c) The Regents of the University of California.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. Neither the name of the University nor the names of its contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-
-
-BSD-2-Clause
-
-
-The FreeBSD Copyright
-
-Copyright 1992-2010 The FreeBSD Project. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions of source code must retain the above copyright notice, this list of
-conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright notice, this list of
-conditions and the following disclaimer in the documentation and/or other materials
-provided with the distribution.
-THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS`` AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD
-PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-The views and conclusions contained in the software and documentation are those of the
-authors and should not be interpreted as representing official policies, either
-expressed or implied, of the FreeBSD Project.
-
-
-
-
-BSD-3-Clause
-
-
-Copyright (c) <YEAR>, <OWNER>
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions of source code must retain the above copyright notice, this list of
-conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright notice, this list of
-conditions and the following disclaimer in the documentation and/or other materials
-provided with the distribution.
-Neither the name of the <ORGANIZATION> nor the names of its contributors may be
-used to endorse or promote products derived from this software without specific prior
-written permission.
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
-EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
-SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
-TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
-WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGE.
-
-
-
-
-BSD-4-Clause
-
-
-Copyright (c) <year>, <copyright holder>
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. All advertising materials mentioning features or use of this software
- must display the following acknowledgement:
- This product includes software developed by the <organization>.
-4. Neither the name of the <organization> nor the
- names of its contributors may be used to endorse or promote products
- derived from this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY <COPYRIGHT HOLDER> ``AS IS`` AND ANY
-EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
-DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
-ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-BSL-1.0
-
-
-Boost Software License - Version 1.0 - August 17th, 2003
-
-Permission is hereby granted, free of charge, to any person or organization
-obtaining a copy of the software and accompanying documentation covered by
-this license (the "Software") to use, reproduce, display, distribute,
-execute, and transmit the Software, and to prepare derivative works of the
-Software, and to permit third-parties to whom the Software is furnished to
-do so, all subject to the following:
-
-The copyright notices in the Software and this entire statement, including
-the above license grant, this restriction and the following disclaimer,
-must be included in all copies of the Software, in whole or in part, and
-all derivative works of the Software, unless such copies or derivative
-works are solely in the form of machine-executable object code generated by
-a source language processor.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
-SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
-FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
-ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
-DEALINGS IN THE SOFTWARE.
-
-
-
-
-CC-BY-4.0
-
-Attribution 4.0 International
-
-=======================================================================
-
-Creative Commons Corporation ("Creative Commons") is not a law firm and
-does not provide legal services or legal advice. Distribution of
-Creative Commons public licenses does not create a lawyer-client or
-other relationship. Creative Commons makes its licenses and related
-information available on an "as-is" basis. Creative Commons gives no
-warranties regarding its licenses, any material licensed under their
-terms and conditions, or any related information. Creative Commons
-disclaims all liability for damages resulting from their use to the
-fullest extent possible.
-
-Using Creative Commons Public Licenses
-
-Creative Commons public licenses provide a standard set of terms and
-conditions that creators and other rights holders may use to share
-original works of authorship and other material subject to copyright
-and certain other rights specified in the public license below. The
-following considerations are for informational purposes only, are not
-exhaustive, and do not form part of our licenses.
-
- Considerations for licensors: Our public licenses are
- intended for use by those authorized to give the public
- permission to use material in ways otherwise restricted by
- copyright and certain other rights. Our licenses are
- irrevocable. Licensors should read and understand the terms
- and conditions of the license they choose before applying it.
- Licensors should also secure all rights necessary before
- applying our licenses so that the public can reuse the
- material as expected. Licensors should clearly mark any
- material not subject to the license. This includes other CC-
- licensed material, or material used under an exception or
- limitation to copyright. More considerations for licensors:
- wiki.creativecommons.org/Considerations_for_licensors
-
- Considerations for the public: By using one of our public
- licenses, a licensor grants the public permission to use the
- licensed material under specified terms and conditions. If
- the licensor's permission is not necessary for any reason--for
- example, because of any applicable exception or limitation to
- copyright--then that use is not regulated by the license. Our
- licenses grant only permissions under copyright and certain
- other rights that a licensor has authority to grant. Use of
- the licensed material may still be restricted for other
- reasons, including because others have copyright or other
- rights in the material. A licensor may make special requests,
- such as asking that all changes be marked or described.
- Although not required by our licenses, you are encouraged to
- respect those requests where reasonable. More_considerations
- for the public:
- wiki.creativecommons.org/Considerations_for_licensees
-
-=======================================================================
-
-Creative Commons Attribution 4.0 International Public License
-
-By exercising the Licensed Rights (defined below), You accept and agree
-to be bound by the terms and conditions of this Creative Commons
-Attribution 4.0 International Public License ("Public License"). To the
-extent this Public License may be interpreted as a contract, You are
-granted the Licensed Rights in consideration of Your acceptance of
-these terms and conditions, and the Licensor grants You such rights in
-consideration of benefits the Licensor receives from making the
-Licensed Material available under these terms and conditions.
-
-
-Section 1 -- Definitions.
-
- a. Adapted Material means material subject to Copyright and Similar
- Rights that is derived from or based upon the Licensed Material
- and in which the Licensed Material is translated, altered,
- arranged, transformed, or otherwise modified in a manner requiring
- permission under the Copyright and Similar Rights held by the
- Licensor. For purposes of this Public License, where the Licensed
- Material is a musical work, performance, or sound recording,
- Adapted Material is always produced where the Licensed Material is
- synched in timed relation with a moving image.
-
- b. Adapter's License means the license You apply to Your Copyright
- and Similar Rights in Your contributions to Adapted Material in
- accordance with the terms and conditions of this Public License.
-
- c. Copyright and Similar Rights means copyright and/or similar rights
- closely related to copyright including, without limitation,
- performance, broadcast, sound recording, and Sui Generis Database
- Rights, without regard to how the rights are labeled or
- categorized. For purposes of this Public License, the rights
- specified in Section 2(b)(1)-(2) are not Copyright and Similar
- Rights.
-
- d. Effective Technological Measures means those measures that, in the
- absence of proper authority, may not be circumvented under laws
- fulfilling obligations under Article 11 of the WIPO Copyright
- Treaty adopted on December 20, 1996, and/or similar international
- agreements.
-
- e. Exceptions and Limitations means fair use, fair dealing, and/or
- any other exception or limitation to Copyright and Similar Rights
- that applies to Your use of the Licensed Material.
-
- f. Licensed Material means the artistic or literary work, database,
- or other material to which the Licensor applied this Public
- License.
-
- g. Licensed Rights means the rights granted to You subject to the
- terms and conditions of this Public License, which are limited to
- all Copyright and Similar Rights that apply to Your use of the
- Licensed Material and that the Licensor has authority to license.
-
- h. Licensor means the individual(s) or entity(ies) granting rights
- under this Public License.
-
- i. Share means to provide material to the public by any means or
- process that requires permission under the Licensed Rights, such
- as reproduction, public display, public performance, distribution,
- dissemination, communication, or importation, and to make material
- available to the public including in ways that members of the
- public may access the material from a place and at a time
- individually chosen by them.
-
- j. Sui Generis Database Rights means rights other than copyright
- resulting from Directive 96/9/EC of the European Parliament and of
- the Council of 11 March 1996 on the legal protection of databases,
- as amended and/or succeeded, as well as other essentially
- equivalent rights anywhere in the world.
-
- k. You means the individual or entity exercising the Licensed Rights
- under this Public License. Your has a corresponding meaning.
-
-
-Section 2 -- Scope.
-
- a. License grant.
-
- 1. Subject to the terms and conditions of this Public License,
- the Licensor hereby grants You a worldwide, royalty-free,
- non-sublicensable, non-exclusive, irrevocable license to
- exercise the Licensed Rights in the Licensed Material to:
-
- a. reproduce and Share the Licensed Material, in whole or
- in part; and
-
- b. produce, reproduce, and Share Adapted Material.
-
- 2. Exceptions and Limitations. For the avoidance of doubt, where
- Exceptions and Limitations apply to Your use, this Public
- License does not apply, and You do not need to comply with
- its terms and conditions.
-
- 3. Term. The term of this Public License is specified in Section
- 6(a).
-
- 4. Media and formats; technical modifications allowed. The
- Licensor authorizes You to exercise the Licensed Rights in
- all media and formats whether now known or hereafter created,
- and to make technical modifications necessary to do so. The
- Licensor waives and/or agrees not to assert any right or
- authority to forbid You from making technical modifications
- necessary to exercise the Licensed Rights, including
- technical modifications necessary to circumvent Effective
- Technological Measures. For purposes of this Public License,
- simply making modifications authorized by this Section 2(a)
- (4) never produces Adapted Material.
-
- 5. Downstream recipients.
-
- a. Offer from the Licensor -- Licensed Material. Every
- recipient of the Licensed Material automatically
- receives an offer from the Licensor to exercise the
- Licensed Rights under the terms and conditions of this
- Public License.
-
- b. No downstream restrictions. You may not offer or impose
- any additional or different terms or conditions on, or
- apply any Effective Technological Measures to, the
- Licensed Material if doing so restricts exercise of the
- Licensed Rights by any recipient of the Licensed
- Material.
-
- 6. No endorsement. Nothing in this Public License constitutes or
- may be construed as permission to assert or imply that You
- are, or that Your use of the Licensed Material is, connected
- with, or sponsored, endorsed, or granted official status by,
- the Licensor or others designated to receive attribution as
- provided in Section 3(a)(1)(A)(i).
-
- b. Other rights.
-
- 1. Moral rights, such as the right of integrity, are not
- licensed under this Public License, nor are publicity,
- privacy, and/or other similar personality rights; however, to
- the extent possible, the Licensor waives and/or agrees not to
- assert any such rights held by the Licensor to the limited
- extent necessary to allow You to exercise the Licensed
- Rights, but not otherwise.
-
- 2. Patent and trademark rights are not licensed under this
- Public License.
-
- 3. To the extent possible, the Licensor waives any right to
- collect royalties from You for the exercise of the Licensed
- Rights, whether directly or through a collecting society
- under any voluntary or waivable statutory or compulsory
- licensing scheme. In all other cases the Licensor expressly
- reserves any right to collect such royalties.
-
-
-Section 3 -- License Conditions.
-
-Your exercise of the Licensed Rights is expressly made subject to the
-following conditions.
-
- a. Attribution.
-
- 1. If You Share the Licensed Material (including in modified
- form), You must:
-
- a. retain the following if it is supplied by the Licensor
- with the Licensed Material:
-
- i. identification of the creator(s) of the Licensed
- Material and any others designated to receive
- attribution, in any reasonable manner requested by
- the Licensor (including by pseudonym if
- designated);
-
- ii. a copyright notice;
-
- iii. a notice that refers to this Public License;
-
- iv. a notice that refers to the disclaimer of
- warranties;
-
- v. a URI or hyperlink to the Licensed Material to the
- extent reasonably practicable;
-
- b. indicate if You modified the Licensed Material and
- retain an indication of any previous modifications; and
-
- c. indicate the Licensed Material is licensed under this
- Public License, and include the text of, or the URI or
- hyperlink to, this Public License.
-
- 2. You may satisfy the conditions in Section 3(a)(1) in any
- reasonable manner based on the medium, means, and context in
- which You Share the Licensed Material. For example, it may be
- reasonable to satisfy the conditions by providing a URI or
- hyperlink to a resource that includes the required
- information.
-
- 3. If requested by the Licensor, You must remove any of the
- information required by Section 3(a)(1)(A) to the extent
- reasonably practicable.
-
- 4. If You Share Adapted Material You produce, the Adapter's
- License You apply must not prevent recipients of the Adapted
- Material from complying with this Public License.
-
-
-Section 4 -- Sui Generis Database Rights.
-
-Where the Licensed Rights include Sui Generis Database Rights that
-apply to Your use of the Licensed Material:
-
- a. for the avoidance of doubt, Section 2(a)(1) grants You the right
- to extract, reuse, reproduce, and Share all or a substantial
- portion of the contents of the database;
-
- b. if You include all or a substantial portion of the database
- contents in a database in which You have Sui Generis Database
- Rights, then the database in which You have Sui Generis Database
- Rights (but not its individual contents) is Adapted Material; and
-
- c. You must comply with the conditions in Section 3(a) if You Share
- all or a substantial portion of the contents of the database.
-
-For the avoidance of doubt, this Section 4 supplements and does not
-replace Your obligations under this Public License where the Licensed
-Rights include other Copyright and Similar Rights.
-
-
-Section 5 -- Disclaimer of Warranties and Limitation of Liability.
-
- a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
- EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
- AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
- ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
- IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
- WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
- PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
- ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
- KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
- ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
-
- b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
- TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
- NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
- INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
- COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
- USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
- ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
- DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
- IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
-
- c. The disclaimer of warranties and limitation of liability provided
- above shall be interpreted in a manner that, to the extent
- possible, most closely approximates an absolute disclaimer and
- waiver of all liability.
-
-
-Section 6 -- Term and Termination.
-
- a. This Public License applies for the term of the Copyright and
- Similar Rights licensed here. However, if You fail to comply with
- this Public License, then Your rights under this Public License
- terminate automatically.
-
- b. Where Your right to use the Licensed Material has terminated under
- Section 6(a), it reinstates:
-
- 1. automatically as of the date the violation is cured, provided
- it is cured within 30 days of Your discovery of the
- violation; or
-
- 2. upon express reinstatement by the Licensor.
-
- For the avoidance of doubt, this Section 6(b) does not affect any
- right the Licensor may have to seek remedies for Your violations
- of this Public License.
-
- c. For the avoidance of doubt, the Licensor may also offer the
- Licensed Material under separate terms or conditions or stop
- distributing the Licensed Material at any time; however, doing so
- will not terminate this Public License.
-
- d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
- License.
-
-
-Section 7 -- Other Terms and Conditions.
-
- a. The Licensor shall not be bound by any additional or different
- terms or conditions communicated by You unless expressly agreed.
-
- b. Any arrangements, understandings, or agreements regarding the
- Licensed Material not stated herein are separate from and
- independent of the terms and conditions of this Public License.
-
-
-Section 8 -- Interpretation.
-
- a. For the avoidance of doubt, this Public License does not, and
- shall not be interpreted to, reduce, limit, restrict, or impose
- conditions on any use of the Licensed Material that could lawfully
- be made without permission under this Public License.
-
- b. To the extent possible, if any provision of this Public License is
- deemed unenforceable, it shall be automatically reformed to the
- minimum extent necessary to make it enforceable. If the provision
- cannot be reformed, it shall be severed from this Public License
- without affecting the enforceability of the remaining terms and
- conditions.
-
- c. No term or condition of this Public License will be waived and no
- failure to comply consented to unless expressly agreed to by the
- Licensor.
-
- d. Nothing in this Public License constitutes or may be interpreted
- as a limitation upon, or waiver of, any privileges and immunities
- that apply to the Licensor or You, including from the legal
- processes of any jurisdiction or authority.
-
-
-=======================================================================
-
-Creative Commons is not a party to its public
-licenses. Notwithstanding, Creative Commons may elect to apply one of
-its public licenses to material it publishes and in those instances
-will be considered the ”Licensor.” The text of the Creative Commons
-public licenses is dedicated to the public domain under the CC0 Public
-Domain Dedication. Except for the limited purpose of indicating that
-material is shared under a Creative Commons public license or as
-otherwise permitted by the Creative Commons policies published at
-creativecommons.org/policies, Creative Commons does not authorize the
-use of the trademark "Creative Commons" or any other trademark or logo
-of Creative Commons without its prior written consent including,
-without limitation, in connection with any unauthorized modifications
-to any of its public licenses or any other arrangements,
-understandings, or agreements concerning use of licensed material. For
-the avoidance of doubt, this paragraph does not form part of the
-public licenses.
-
-Creative Commons may be contacted at creativecommons.org.
-
-
-
-CDDL-1.0
-
-
-COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
-Version 1.0
-1. Definitions.
-
-1.1. “Contributor” means each individual or entity that creates or
-contributes to the creation of Modifications.
-
-1.2. “Contributor Version” means the combination of the Original
-Software, prior Modifications used by a Contributor (if any), and the Modifications
-made by that particular Contributor.
-
-1.3. “Covered Software” means (a) the Original Software, or (b)
-Modifications, or (c) the combination of files containing Original Software with files
-containing Modifications, in each case including portions thereof.
-
-1.4. “Executable” means the Covered Software in any form other
-than Source Code.
-
-1.5. “Initial Developer” means the individual or entity that first
-makes Original Software available under this License.
-
-1.6. “Larger Work” means a work which combines Covered Software or
-portions thereof with code not governed by the terms of this License.
-
-1.7. “License” means this document.
-
-1.8. “Licensable” means having the right to grant, to the maximum
-extent possible, whether at the time of the initial grant or subsequently acquired,
-any and all of the rights conveyed herein.
-
-1.9. “Modifications” means the Source Code and Executable form of
-any of the following:
-
-A. Any file that results from an addition to, deletion from or modification of the
-contents of a file containing Original Software or previous Modifications;
-
-B. Any new file that contains any part of the Original Software or previous
-Modification; or
-
-C. Any new file that is contributed or otherwise made available under the terms of
-this License.
-
-1.10. “Original Software” means the Source Code and Executable
-form of computer software code that is originally released under this License.
-
-1.11. “Patent Claims” means any patent claim(s), now owned or
-hereafter acquired, including without limitation, method, process, and apparatus
-claims, in any patent Licensable by grantor.
-
-1.12. “Source Code” means (a) the common form of computer software
-code in which modifications are made and (b) associated documentation included in or
-with such code.
-
-1.13. “You” (or “Your”) means an individual or
-a legal entity exercising rights under, and complying with all of the terms of, this
-License. For legal entities, “You” includes any entity which
-controls, is controlled by, or is under common control with You. For purposes of this
-definition, “control” means (a) the power, direct or indirect, to
-cause the direction or management of such entity, whether by contract or otherwise, or
-(b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial
-ownership of such entity.
-
-2. License Grants.
-
-2.1. The Initial Developer Grant.
-
-Conditioned upon Your compliance with Section 3.1 below and subject to third party
-intellectual property claims, the Initial Developer hereby grants You a world-wide,
-royalty-free, non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark) Licensable by
-Initial Developer, to use, reproduce, modify, display, perform, sublicense and
-distribute the Original Software (or portions thereof), with or without Modifications,
-and/or as part of a Larger Work; and
-
-(b) under Patent Claims infringed by the making, using or selling of Original
-Software, to make, have made, use, practice, sell, and offer for sale, and/or
-otherwise dispose of the Original Software (or portions thereof).
-
-(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial
-Developer first distributes or otherwise makes the Original Software available to a
-third party under the terms of this License.
-
-(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code
-that You delete from the Original Software, or (2) for infringements caused by: (i)
-the modification of the Original Software, or (ii) the combination of the Original
-Software with other software or devices.
-
-2.2. Contributor Grant.
-
-Conditioned upon Your compliance with Section 3.1 below and subject to third party
-intellectual property claims, each Contributor hereby grants You a world-wide,
-royalty-free, non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark) Licensable by
-Contributor to use, reproduce, modify, display, perform, sublicense and distribute the
-Modifications created by such Contributor (or portions thereof), either on an
-unmodified basis, with other Modifications, as Covered Software and/or as part of a
-Larger Work; and
-
-(b) under Patent Claims infringed by the making, using, or selling of Modifications
-made by that Contributor either alone and/or in combination with its Contributor
-Version (or portions of such combination), to make, use, sell, offer for sale, have
-made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or
-portions thereof); and (2) the combination of Modifications made by that Contributor
-with its Contributor Version (or portions of such combination).
-
-(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
-Contributor first distributes or otherwise makes the Modifications available to a
-third party.
-
-(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any
-code that Contributor has deleted from the Contributor Version; (2) for infringements
-caused by: (i) third party modifications of Contributor Version, or (ii) the
-combination of Modifications made by that Contributor with other software (except as
-part of the Contributor Version) or other devices; or (3) under Patent Claims
-infringed by Covered Software in the absence of Modifications made by that
-Contributor.
-
-3. Distribution Obligations.
-
-3.1. Availability of Source Code.
-
-Any Covered Software that You distribute or otherwise make available in Executable
-form must also be made available in Source Code form and that Source Code form must be
-distributed only under the terms of this License. You must include a copy of this
-License with every copy of the Source Code form of the Covered Software You distribute
-or otherwise make available. You must inform recipients of any such Covered Software
-in Executable form as to how they can obtain such Covered Software in Source Code form
-in a reasonable manner on or through a medium customarily used for software exchange.
-
-3.2. Modifications.
-
-The Modifications that You create or to which You contribute are governed by the terms
-of this License. You represent that You believe Your Modifications are Your original
-creation(s) and/or You have sufficient rights to grant the rights conveyed by this
-License.
-
-3.3. Required Notices.
-
-You must include a notice in each of Your Modifications that identifies You as the
-Contributor of the Modification. You may not remove or alter any copyright, patent or
-trademark notices contained within the Covered Software, or any notices of licensing
-or any descriptive text giving attribution to any Contributor or the Initial
-Developer.
-
-3.4. Application of Additional Terms.
-
-You may not offer or impose any terms on any Covered Software in Source Code form that
-alters or restricts the applicable version of this License or the
-recipients’ rights hereunder. You may choose to offer, and to charge a fee
-for, warranty, support, indemnity or liability obligations to one or more recipients
-of Covered Software. However, you may do so only on Your own behalf, and not on behalf
-of the Initial Developer or any Contributor. You must make it absolutely clear that
-any such warranty, support, indemnity or liability obligation is offered by You alone,
-and You hereby agree to indemnify the Initial Developer and every Contributor for any
-liability incurred by the Initial Developer or such Contributor as a result of
-warranty, support, indemnity or liability terms You offer.
-
-3.5. Distribution of Executable Versions.
-
-You may distribute the Executable form of the Covered Software under the terms of this
-License or under the terms of a license of Your choice, which may contain terms
-different from this License, provided that You are in compliance with the terms of
-this License and that the license for the Executable form does not attempt to limit or
-alter the recipient’s rights in the Source Code form from the rights set
-forth in this License. If You distribute the Covered Software in Executable form under
-a different license, You must make it absolutely clear that any terms which differ
-from this License are offered by You alone, not by the Initial Developer or
-Contributor. You hereby agree to indemnify the Initial Developer and every Contributor
-for any liability incurred by the Initial Developer or such Contributor as a result of
-any such terms You offer.
-
-3.6. Larger Works.
-
-You may create a Larger Work by combining Covered Software with other code not
-governed by the terms of this License and distribute the Larger Work as a single
-product. In such a case, You must make sure the requirements of this License are
-fulfilled for the Covered Software.
-
-4. Versions of the License.
-
-4.1. New Versions.
-
-Sun Microsystems, Inc. is the initial license steward and may publish revised and/or
-new versions of this License from time to time. Each version will be given a
-distinguishing version number. Except as provided in Section 4.3, no one other than
-the license steward has the right to modify this License.
-
-4.2. Effect of New Versions.
-
-You may always continue to use, distribute or otherwise make the Covered Software
-available under the terms of the version of the License under which You originally
-received the Covered Software. If the Initial Developer includes a notice in the
-Original Software prohibiting it from being distributed or otherwise made available
-under any subsequent version of the License, You must distribute and make the Covered
-Software available under the terms of the version of the License under which You
-originally received the Covered Software. Otherwise, You may also choose to use,
-distribute or otherwise make the Covered Software available under the terms of any
-subsequent version of the License published by the license steward.
-
-4.3. Modified Versions.
-
-When You are an Initial Developer and You want to create a new license for Your
-Original Software, You may create and use a modified version of this License if You:
-(a) rename the license and remove any references to the name of the license steward
-(except to note that the license differs from this License); and (b) otherwise make it
-clear that the license contains terms which differ from this License.
-
-5. DISCLAIMER OF WARRANTY.
-
-COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS”
-BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
-LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT
-FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
-PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
-DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR)
-ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
-WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE
-IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
-
-6. TERMINATION.
-
-6.1. This License and the rights granted hereunder will terminate automatically if You
-fail to comply with terms herein and fail to cure such breach within 30 days of
-becoming aware of the breach. Provisions which, by their nature, must remain in effect
-beyond the termination of this License shall survive.
-
-6.2. If You assert a patent infringement claim (excluding declaratory judgment
-actions) against Initial Developer or a Contributor (the Initial Developer or
-Contributor against whom You assert such claim is referred to as
-“Participant”) alleging that the Participant Software (meaning the
-Contributor Version where the Participant is a Contributor or the Original Software
-where the Participant is the Initial Developer) directly or indirectly infringes any
-patent, then any and all rights granted directly or indirectly to You by such
-Participant, the Initial Developer (if the Initial Developer is not the Participant)
-and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days
-notice from Participant terminate prospectively and automatically at the expiration of
-such 60 day notice period, unless if within such 60 day period You withdraw Your claim
-with respect to the Participant Software against such Participant either unilaterally
-or pursuant to a written agreement with Participant.
-
-6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user
-licenses that have been validly granted by You or any distributor hereunder prior to
-termination (excluding licenses granted to You by any distributor) shall survive
-termination.
-
-7. LIMITATION OF LIABILITY.
-
-UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
-CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR
-ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE
-TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
-CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,
-WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL
-DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF
-SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
-PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT
-APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
-EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
-LIMITATION MAY NOT APPLY TO YOU.
-
-8. U.S. GOVERNMENT END USERS.
-
-The Covered Software is a “commercial item,” as that term is
-defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of “commercial computer
-software” (as that term is defined at 48 C.F.R. §
-252.227-7014(a)(1)) and “commercial computer software
-documentation” as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
-Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
-1995), all U.S. Government End Users acquire Covered Software with only those rights
-set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes,
-any other FAR, DFAR, or other clause or provision that addresses Government rights in
-computer software under this License.
-
-9. MISCELLANEOUS.
-
-This License represents the complete agreement concerning subject matter hereof. If
-any provision of this License is held to be unenforceable, such provision shall be
-reformed only to the extent necessary to make it enforceable. This License shall be
-governed by the law of the jurisdiction specified in a notice contained within the
-Original Software (except to the extent applicable law, if any, provides otherwise),
-excluding such jurisdiction’s conflict-of-law provisions. Any litigation
-relating to this License shall be subject to the jurisdiction of the courts located in
-the jurisdiction and venue specified in a notice contained within the Original
-Software, with the losing party responsible for costs, including, without limitation,
-court costs and reasonable attorneys’ fees and expenses. The application of
-the United Nations Convention on Contracts for the International Sale of Goods is
-expressly excluded. Any law or regulation which provides that the language of a
-contract shall be construed against the drafter shall not apply to this License. You
-agree that You alone are responsible for compliance with the United States export
-administration regulations (and the export control laws and regulation of any other
-countries) when You use, distribute or otherwise make available any Covered Software.
-
-10. RESPONSIBILITY FOR CLAIMS.
-
-As between Initial Developer and the Contributors, each party is responsible for
-claims and damages arising, directly or indirectly, out of its utilization of rights
-under this License and You agree to work with Initial Developer and Contributors to
-distribute such responsibility on an equitable basis. Nothing herein is intended or
-shall be deemed to constitute any admission of liability.
-
-
-
-
-CDS
-
-This software is copyrighted by Cadence Design Systems, Inc., and other
-parties. The following terms apply to all files associated with the
-software unless explicitly disclaimed in individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
------------------------------------------------------------------------
- Following is the original agreement for the Tcl/Tk software from
- Sun Microsystems.
------------------------------------------------------------------------
-
-This software is copyrighted by the Regents of the University of
-California, Sun Microsystems, Inc., and other parties. The following
-terms apply to all files associated with the software unless explicitly
-disclaimed in individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
-
-
-CPL-1.0
-
-
-Common Public License Version 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
-LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
-CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-
-"Contribution" means:
-
-a) in the case of the initial Contributor, the initial code and
-documentation distributed under this Agreement, and
-
-b) in the case of each subsequent Contributor:
-
-i) changes to the Program, and
-
-ii) additions to the Program;
-
-where such changes and/or additions to the Program originate from and are
-distributed by that particular Contributor. A Contribution `originates` from a
-Contributor if it was added to the Program by such Contributor itself or anyone
-acting on such Contributor`s behalf. Contributions do not include additions to
-the Program which: (i) are separate modules of software distributed in
-conjunction with the Program under their own license agreement, and (ii) are not
-derivative works of the Program.
-
-"Contributor" means any person or entity that distributes the Program.
-
-"Licensed Patents " mean patent claims licensable by a Contributor which are
-necessarily infringed by the use or sale of its Contribution alone or when
-combined with the Program.
-
-"Program" means the Contributions distributed in accordance with this Agreement.
-
-"Recipient" means anyone who receives the Program under this Agreement,
-including all Contributors.
-
-2. GRANT OF RIGHTS
-
-a) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free copyright license to
-reproduce, prepare derivative works of, publicly display, publicly perform,
-distribute and sublicense the Contribution of such Contributor, if any, and such
-derivative works, in source code and object code form.
-
-b) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
-Patents to make, use, sell, offer to sell, import and otherwise transfer the
-Contribution of such Contributor, if any, in source code and object code form.
-This patent license shall apply to the combination of the Contribution and the
-Program if, at the time the Contribution is added by the Contributor, such
-addition of the Contribution causes such combination to be covered by the
-Licensed Patents. The patent license shall not apply to any other combinations
-which include the Contribution. No hardware per se is licensed hereunder.
-
-c) Recipient understands that although each Contributor grants the licenses
-to its Contributions set forth herein, no assurances are provided by any
-Contributor that the Program does not infringe the patent or other intellectual
-property rights of any other entity. Each Contributor disclaims any liability to
-Recipient for claims brought by any other entity based on infringement of
-intellectual property rights or otherwise. As a condition to exercising the
-rights and licenses granted hereunder, each Recipient hereby assumes sole
-responsibility to secure any other intellectual property rights needed, if any.
-For example, if a third party patent license is required to allow Recipient to
-distribute the Program, it is Recipient`s responsibility to acquire that license
-before distributing the Program.
-
-d) Each Contributor represents that to its knowledge it has sufficient
-copyright rights in its Contribution, if any, to grant the copyright license set
-forth in this Agreement.
-
-3. REQUIREMENTS
-
-A Contributor may choose to distribute the Program in object code form under its
-own license agreement, provided that:
-
-a) it complies with the terms and conditions of this Agreement; and
-
-b) its license agreement:
-
-i) effectively disclaims on behalf of all Contributors all warranties and
-conditions, express and implied, including warranties or conditions of title and
-non-infringement, and implied warranties or conditions of merchantability and
-fitness for a particular purpose;
-
-ii) effectively excludes on behalf of all Contributors all liability for
-damages, including direct, indirect, special, incidental and consequential
-damages, such as lost profits;
-
-iii) states that any provisions which differ from this Agreement are offered
-by that Contributor alone and not by any other party; and
-
-iv) states that source code for the Program is available from such
-Contributor, and informs licensees how to obtain it in a reasonable manner on or
-through a medium customarily used for software exchange.
-
-When the Program is made available in source code form:
-
-a) it must be made available under this Agreement; and
-
-b) a copy of this Agreement must be included with each copy of the Program.
-
-Contributors may not remove or alter any copyright notices contained within the
-Program.
-
-Each Contributor must identify itself as the originator of its Contribution, if
-any, in a manner that reasonably allows subsequent Recipients to identify the
-originator of the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-
-Commercial distributors of software may accept certain responsibilities with
-respect to end users, business partners and the like. While this license is
-intended to facilitate the commercial use of the Program, the Contributor who
-includes the Program in a commercial product offering should do so in a manner
-which does not create potential liability for other Contributors. Therefore, if
-a Contributor includes the Program in a commercial product offering, such
-Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
-every other Contributor ("Indemnified Contributor") against any losses, damages
-and costs (collectively "Losses") arising from claims, lawsuits and other legal
-actions brought by a third party against the Indemnified Contributor to the
-extent caused by the acts or omissions of such Commercial Contributor in
-connection with its distribution of the Program in a commercial product
-offering. The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement. In order
-to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
-Contributor in writing of such claim, and b) allow the Commercial Contributor to
-control, and cooperate with the Commercial Contributor in, the defense and any
-related settlement negotiations. The Indemnified Contributor may participate in
-any such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial product
-offering, Product X. That Contributor is then a Commercial Contributor. If that
-Commercial Contributor then makes performance claims, or offers warranties
-related to Product X, those performance claims and warranties are such
-Commercial Contributor`s responsibility alone. Under this section, the
-Commercial Contributor would have to defend claims against the other
-Contributors related to those performance claims and warranties, and if a court
-requires any other Contributor to pay any damages as a result, the Commercial
-Contributor must pay those damages.
-
-5. NO WARRANTY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
-IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
-NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
-Recipient is solely responsible for determining the appropriateness of using and
-distributing the Program and assumes all risks associated with its exercise of
-rights under this Agreement, including but not limited to the risks and costs of
-program errors, compliance with applicable laws, damage to or loss of data,
-programs or equipment, and unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
-CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
-PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
-STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
-GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-
-If any provision of this Agreement is invalid or unenforceable under applicable
-law, it shall not affect the validity or enforceability of the remainder of the
-terms of this Agreement, and without further action by the parties hereto, such
-provision shall be reformed to the minimum extent necessary to make such
-provision valid and enforceable.
-
-If Recipient institutes patent litigation against a Contributor with respect to
-a patent applicable to software (including a cross-claim or counterclaim in a
-lawsuit), then any patent licenses granted by that Contributor to such Recipient
-under this Agreement shall terminate as of the date such litigation is filed. In
-addition, if Recipient institutes patent litigation against any entity
-(including a cross-claim or counterclaim in a lawsuit) alleging that the Program
-itself (excluding combinations of the Program with other software or hardware)
-infringes such Recipient`s patent(s), then such Recipient`s rights granted under
-Section 2(b) shall terminate as of the date such litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it fails to
-comply with any of the material terms or conditions of this Agreement and does
-not cure such failure in a reasonable period of time after becoming aware of
-such noncompliance. If all Recipient`s rights under this Agreement terminate,
-Recipient agrees to cease use and distribution of the Program as soon as
-reasonably practicable. However, Recipient`s obligations under this Agreement
-and any licenses granted by Recipient relating to the Program shall continue and
-survive.
-
-Everyone is permitted to copy and distribute copies of this Agreement, but in
-order to avoid inconsistency the Agreement is copyrighted and may only be
-modified in the following manner. The Agreement Steward reserves the right to
-publish new versions (including revisions) of this Agreement from time to time.
-No one other than the Agreement Steward has the right to modify this Agreement.
-IBM is the initial Agreement Steward. IBM may assign the responsibility to serve
-as the Agreement Steward to a suitable separate entity. Each new version of the
-Agreement will be given a distinguishing version number. The Program (including
-Contributions) may always be distributed subject to the version of the Agreement
-under which it was received. In addition, after a new version of the Agreement
-is published, Contributor may elect to distribute the Program (including its
-Contributions) under the new version. Except as expressly stated in Sections
-2(a) and 2(b) above, Recipient receives no rights or licenses to the
-intellectual property of any Contributor under this Agreement, whether
-expressly, by implication, estoppel or otherwise. All rights in the Program not
-expressly granted under this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and the
-intellectual property laws of the United States of America. No party to this
-Agreement will bring a legal action under this Agreement more than one year
-after the cause of action arose. Each party waives its rights to a jury trial in
-any resulting litigation.
-
-
-
-
-CUP
-
-CUP PARSER GENERATOR COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
-
-Copyright 1996 by Scott Hudson, Frank Flannery, C. Scott Ananian
-
-Permission to use, copy, modify, and distribute this software and its
-documentation for any purpose and without fee is hereby granted,
-provided that the above copyright notice appear in all copies and that
-both the copyright notice and this permission notice and warranty
-disclaimer appear in supporting documentation, and that the names of
-the authors or their employers not be used in advertising or publicity
-pertaining to distribution of the software without specific, written
-prior permission.
-
-The authors and their employers disclaim all warranties with regard to
-this software, including all implied warranties of merchantability and
-fitness. In no event shall the authors or their employers be liable
-for any special, indirect or consequential damages or any damages
-whatsoever resulting from loss of use, data or profits, whether in an
-action of contract, negligence or other tortious action, arising out of
-or in connection with the use or performance of this software.
-
-
-
-EPL-1.0
-
-
-Eclipse Public License - v 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE
-("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES
-RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-
-"Contribution" means:
-
-a) in the case of the initial Contributor, the initial code and documentation
-distributed under this Agreement, and
-b) in the case of each subsequent Contributor:
-i) changes to the Program, and
-ii) additions to the Program;
-where such changes and/or additions to the Program originate from and are distributed
-by that particular Contributor. A Contribution `originates` from a Contributor if it
-was added to the Program by such Contributor itself or anyone acting on such
-Contributor`s behalf. Contributions do not include additions to the Program which: (i)
-are separate modules of software distributed in conjunction with the Program under
-their own license agreement, and (ii) are not derivative works of the Program.
-"Contributor" means any person or entity that distributes the Program.
-
-"Licensed Patents" mean patent claims licensable by a Contributor which are
-necessarily infringed by the use or sale of its Contribution alone or when combined
-with the Program.
-
-"Program" means the Contributions distributed in accordance with this Agreement.
-
-"Recipient" means anyone who receives the Program under this Agreement, including all
-Contributors.
-
-2. GRANT OF RIGHTS
-
-a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
-non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare
-derivative works of, publicly display, publicly perform, distribute and sublicense the
-Contribution of such Contributor, if any, and such derivative works, in source code
-and object code form.
-b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
-non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make,
-use, sell, offer to sell, import and otherwise transfer the Contribution of such
-Contributor, if any, in source code and object code form. This patent license shall
-apply to the combination of the Contribution and the Program if, at the time the
-Contribution is added by the Contributor, such addition of the Contribution causes
-such combination to be covered by the Licensed Patents. The patent license shall not
-apply to any other combinations which include the Contribution. No hardware per se is
-licensed hereunder.
-c) Recipient understands that although each Contributor grants the licenses to its
-Contributions set forth herein, no assurances are provided by any Contributor that the
-Program does not infringe the patent or other intellectual property rights of any
-other entity. Each Contributor disclaims any liability to Recipient for claims brought
-by any other entity based on infringement of intellectual property rights or
-otherwise. As a condition to exercising the rights and licenses granted hereunder,
-each Recipient hereby assumes sole responsibility to secure any other intellectual
-property rights needed, if any. For example, if a third party patent license is
-required to allow Recipient to distribute the Program, it is Recipient`s
-responsibility to acquire that license before distributing the Program.
-d) Each Contributor represents that to its knowledge it has sufficient copyright
-rights in its Contribution, if any, to grant the copyright license set forth in this
-Agreement.
-3. REQUIREMENTS
-
-A Contributor may choose to distribute the Program in object code form under its own
-license agreement, provided that:
-
-a) it complies with the terms and conditions of this Agreement; and
-b) its license agreement:
-i) effectively disclaims on behalf of all Contributors all warranties and conditions,
-express and implied, including warranties or conditions of title and non-infringement,
-and implied warranties or conditions of merchantability and fitness for a particular
-purpose;
-ii) effectively excludes on behalf of all Contributors all liability for damages,
-including direct, indirect, special, incidental and consequential damages, such as
-lost profits;
-iii) states that any provisions which differ from this Agreement are offered by that
-Contributor alone and not by any other party; and
-iv) states that source code for the Program is available from such Contributor, and
-informs licensees how to obtain it in a reasonable manner on or through a medium
-customarily used for software exchange.
-When the Program is made available in source code form:
-
-a) it must be made available under this Agreement; and
-b) a copy of this Agreement must be included with each copy of the Program.
-Contributors may not remove or alter any copyright notices contained within the
-Program.
-
-Each Contributor must identify itself as the originator of its Contribution, if any,
-in a manner that reasonably allows subsequent Recipients to identify the originator of
-the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-
-Commercial distributors of software may accept certain responsibilities with respect
-to end users, business partners and the like. While this license is intended to
-facilitate the commercial use of the Program, the Contributor who includes the Program
-in a commercial product offering should do so in a manner which does not create
-potential liability for other Contributors. Therefore, if a Contributor includes the
-Program in a commercial product offering, such Contributor ("Commercial Contributor")
-hereby agrees to defend and indemnify every other Contributor ("Indemnified
-Contributor") against any losses, damages and costs (collectively "Losses") arising
-from claims, lawsuits and other legal actions brought by a third party against the
-Indemnified Contributor to the extent caused by the acts or omissions of such
-Commercial Contributor in connection with its distribution of the Program in a
-commercial product offering. The obligations in this section do not apply to any
-claims or Losses relating to any actual or alleged intellectual property infringement.
-In order to qualify, an Indemnified Contributor must: a) promptly notify the
-Commercial Contributor in writing of such claim, and b) allow the Commercial
-Contributor to control, and cooperate with the Commercial Contributor in, the defense
-and any related settlement negotiations. The Indemnified Contributor may participate
-in any such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial product offering,
-Product X. That Contributor is then a Commercial Contributor. If that Commercial
-Contributor then makes performance claims, or offers warranties related to Product X,
-those performance claims and warranties are such Commercial Contributor`s
-responsibility alone. Under this section, the Commercial Contributor would have to
-defend claims against the other Contributors related to those performance claims and
-warranties, and if a court requires any other Contributor to pay any damages as a
-result, the Commercial Contributor must pay those damages.
-
-5. NO WARRANTY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS"
-BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED
-INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
-NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient
-is solely responsible for determining the appropriateness of using and distributing
-the Program and assumes all risks associated with its exercise of rights under this
-Agreement , including but not limited to the risks and costs of program errors,
-compliance with applicable laws, damage to or loss of data, programs or equipment, and
-unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
-CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS),
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR
-DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-
-If any provision of this Agreement is invalid or unenforceable under applicable law,
-it shall not affect the validity or enforceability of the remainder of the terms of
-this Agreement, and without further action by the parties hereto, such provision shall
-be reformed to the minimum extent necessary to make such provision valid and
-enforceable.
-
-If Recipient institutes patent litigation against any entity (including a cross-claim
-or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations
-of the Program with other software or hardware) infringes such Recipient`s patent(s),
-then such Recipient`s rights granted under Section 2(b) shall terminate as of the date
-such litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it fails to comply with
-any of the material terms or conditions of this Agreement and does not cure such
-failure in a reasonable period of time after becoming aware of such noncompliance. If
-all Recipient`s rights under this Agreement terminate, Recipient agrees to cease use
-and distribution of the Program as soon as reasonably practicable. However,
-Recipient`s obligations under this Agreement and any licenses granted by Recipient
-relating to the Program shall continue and survive.
-
-Everyone is permitted to copy and distribute copies of this Agreement, but in order to
-avoid inconsistency the Agreement is copyrighted and may only be modified in the
-following manner. The Agreement Steward reserves the right to publish new versions
-(including revisions) of this Agreement from time to time. No one other than the
-Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is
-the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to
-serve as the Agreement Steward to a suitable separate entity. Each new version of the
-Agreement will be given a distinguishing version number. The Program (including
-Contributions) may always be distributed subject to the version of the Agreement under
-which it was received. In addition, after a new version of the Agreement is published,
-Contributor may elect to distribute the Program (including its Contributions) under
-the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
-receives no rights or licenses to the intellectual property of any Contributor under
-this Agreement, whether expressly, by implication, estoppel or otherwise. All rights
-in the Program not expressly granted under this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and the intellectual
-property laws of the United States of America. No party to this Agreement will bring a
-legal action under this Agreement more than one year after the cause of action arose.
-Each party waives its rights to a jury trial in any resulting litigation.
-
-
-
-
-Elfutils-Exception
-
- This file describes the limits of the Exception under which you are allowed
- to distribute Non-GPL Code in linked combination with Red Hat elfutils.
- For the full text of the license, please see one of the header files
- included with the source distribution or the file COPYING found in the
- top level directory of the source.
-
- The Approved Interfaces are the functions declared in the files:
-
- libelf.h
- libdw.h
- libdwfl.h
-
-
-
-
-FSF-Unlimited
-
-Copyright (C) 1997-2010 Free Software Foundation, Inc.
-This file is free software; the Free Software Foundation
-gives unlimited permission to copy and/or distribute it,
-with or without modifications, as long as this notice is preserved.
-
-
-
-FreeType
-
- The FreeType Project LICENSE
- ----------------------------
-
- 2006-Jan-27
-
- Copyright 1996-2002, 2006 by
- David Turner, Robert Wilhelm, and Werner Lemberg
-
-
-
-Introduction
-============
-
- The FreeType Project is distributed in several archive packages;
- some of them may contain, in addition to the FreeType font engine,
- various tools and contributions which rely on, or relate to, the
- FreeType Project.
-
- This license applies to all files found in such packages, and
- which do not fall under their own explicit license. The license
- affects thus the FreeType font engine, the test programs,
- documentation and makefiles, at the very least.
-
- This license was inspired by the BSD, Artistic, and IJG
- (Independent JPEG Group) licenses, which all encourage inclusion
- and use of free software in commercial and freeware products
- alike. As a consequence, its main points are that:
-
- o We don't promise that this software works. However, we will be
- interested in any kind of bug reports. (`as is' distribution)
-
- o You can use this software for whatever you want, in parts or
- full form, without having to pay us. (`royalty-free' usage)
-
- o You may not pretend that you wrote this software. If you use
- it, or only parts of it, in a program, you must acknowledge
- somewhere in your documentation that you have used the
- FreeType code. (`credits')
-
- We specifically permit and encourage the inclusion of this
- software, with or without modifications, in commercial products.
- We disclaim all warranties covering The FreeType Project and
- assume no liability related to The FreeType Project.
-
-
- Finally, many people asked us for a preferred form for a
- credit/disclaimer to use in compliance with this license. We thus
- encourage you to use the following text:
-
- """
- Portions of this software are copyright � <year> The FreeType
- Project (www.freetype.org). All rights reserved.
- """
-
- Please replace <year> with the value from the FreeType version you
- actually use.
-
-
-Legal Terms
-===========
-
-0. Definitions
---------------
-
- Throughout this license, the terms `package', `FreeType Project',
- and `FreeType archive' refer to the set of files originally
- distributed by the authors (David Turner, Robert Wilhelm, and
- Werner Lemberg) as the `FreeType Project', be they named as alpha,
- beta or final release.
-
- `You' refers to the licensee, or person using the project, where
- `using' is a generic term including compiling the project's source
- code as well as linking it to form a `program' or `executable'.
- This program is referred to as `a program using the FreeType
- engine'.
-
- This license applies to all files distributed in the original
- FreeType Project, including all source code, binaries and
- documentation, unless otherwise stated in the file in its
- original, unmodified form as distributed in the original archive.
- If you are unsure whether or not a particular file is covered by
- this license, you must contact us to verify this.
-
- The FreeType Project is copyright (C) 1996-2000 by David Turner,
- Robert Wilhelm, and Werner Lemberg. All rights reserved except as
- specified below.
-
-1. No Warranty
---------------
-
- THE FREETYPE PROJECT IS PROVIDED `AS IS' WITHOUT WARRANTY OF ANY
- KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
- WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
- PURPOSE. IN NO EVENT WILL ANY OF THE AUTHORS OR COPYRIGHT HOLDERS
- BE LIABLE FOR ANY DAMAGES CAUSED BY THE USE OR THE INABILITY TO
- USE, OF THE FREETYPE PROJECT.
-
-2. Redistribution
------------------
-
- This license grants a worldwide, royalty-free, perpetual and
- irrevocable right and license to use, execute, perform, compile,
- display, copy, create derivative works of, distribute and
- sublicense the FreeType Project (in both source and object code
- forms) and derivative works thereof for any purpose; and to
- authorize others to exercise some or all of the rights granted
- herein, subject to the following conditions:
-
- o Redistribution of source code must retain this license file
- (`FTL.TXT') unaltered; any additions, deletions or changes to
- the original files must be clearly indicated in accompanying
- documentation. The copyright notices of the unaltered,
- original files must be preserved in all copies of source
- files.
-
- o Redistribution in binary form must provide a disclaimer that
- states that the software is based in part of the work of the
- FreeType Team, in the distribution documentation. We also
- encourage you to put an URL to the FreeType web page in your
- documentation, though this isn't mandatory.
-
- These conditions apply to any software derived from or based on
- the FreeType Project, not just the unmodified files. If you use
- our work, you must acknowledge us. However, no fee need be paid
- to us.
-
-3. Advertising
---------------
-
- Neither the FreeType authors and contributors nor you shall use
- the name of the other for commercial, advertising, or promotional
- purposes without specific prior written permission.
-
- We suggest, but do not require, that you use one or more of the
- following phrases to refer to this software in your documentation
- or advertising materials: `FreeType Project', `FreeType Engine',
- `FreeType library', or `FreeType Distribution'.
-
- As you have not signed this license, you are not required to
- accept it. However, as the FreeType Project is copyrighted
- material, only this license, or another one contracted with the
- authors, grants you the right to use, distribute, and modify it.
- Therefore, by using, distributing, or modifying the FreeType
- Project, you indicate that you understand and accept all the terms
- of this license.
-
-4. Contacts
------------
-
- There are two mailing lists related to FreeType:
-
- o freetype@nongnu.org
-
- Discusses general use and applications of FreeType, as well as
- future and wanted additions to the library and distribution.
- If you are looking for support, start in this list if you
- haven't found anything to help you in the documentation.
-
- o freetype-devel@nongnu.org
-
- Discusses bugs, as well as engine internals, design issues,
- specific licenses, porting, etc.
-
- Our home page can be found at
-
- http://www.freetype.org
-
-
---- end of FTL.TXT ---
-
-
-
-
-GPL-1.0
-
-
-GNU General Public License, version 1
-
- GNU GENERAL PUBLIC LICENSE
- Version 1, February 1989
-
- Copyright (C) 1989 Free Software Foundation, Inc.
- 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The license agreements of most software companies try to keep users
-at the mercy of those companies. By contrast, our General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. The
-General Public License applies to the Free Software Foundation`s
-software and to any other program whose authors commit to using it.
-You can use it for your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Specifically, the General Public License is designed to make
-sure that you have the freedom to give away or sell copies of free
-software, that you receive source code or can get it if you want it,
-that you can change the software or use pieces of it in new free
-programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of a such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must tell them their rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author`s protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors` reputations.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License Agreement applies to any program or other work which
-contains a notice placed by the copyright holder saying it may be
-distributed under the terms of this General Public License. The
-"Program", below, refers to any such program or work, and a "work based
-on the Program" means either the Program or any work containing the
-Program or a portion of it, either verbatim or with modifications. Each
-licensee is addressed as "you".
-
- 1. You may copy and distribute verbatim copies of the Program`s source
-code as you receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice and
-disclaimer of warranty; keep intact all the notices that refer to this
-General Public License and to the absence of any warranty; and give any
-other recipients of the Program a copy of this General Public License
-along with the Program. You may charge a fee for the physical act of
-transferring a copy.
-
- 2. You may modify your copy or copies of the Program or any portion of
-it, and copy and distribute such modifications under the terms of Paragraph
-1 above, provided that you also do the following:
-
- a) cause the modified files to carry prominent notices stating that
- you changed the files and the date of any change; and
-
- b) cause the whole of any work that you distribute or publish, that
- in whole or in part contains the Program or any part thereof, either
- with or without modifications, to be licensed at no charge to all
- third parties under the terms of this General Public License (except
- that you may choose to grant warranty protection to some or all
- third parties, at your option).
-
- c) If the modified program normally reads commands interactively when
- run, you must cause it, when started running for such interactive use
- in the simplest and most usual way, to print or display an
- announcement including an appropriate copyright notice and a notice
- that there is no warranty (or else, saying that you provide a
- warranty) and that users may redistribute the program under these
- conditions, and telling the user how to view a copy of this General
- Public License.
-
- d) You may charge a fee for the physical act of transferring a
- copy, and you may at your option offer warranty protection in
- exchange for a fee.
-
-Mere aggregation of another independent work with the Program (or its
-derivative) on a volume of a storage or distribution medium does not bring
-the other work under the scope of these terms.
-
- 3. You may copy and distribute the Program (or a portion or derivative of
-it, under Paragraph 2) in object code or executable form under the terms of
-Paragraphs 1 and 2 above provided that you also do one of the following:
-
- a) accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- b) accompany it with a written offer, valid for at least three
- years, to give any third party free (except for a nominal charge
- for the cost of distribution) a complete machine-readable copy of the
- corresponding source code, to be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- c) accompany it with the information you received as to where the
- corresponding source code may be obtained. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form alone.)
-
-Source code for a work means the preferred form of the work for making
-modifications to it. For an executable file, complete source code means
-all the source code for all modules it contains; but, as a special
-exception, it need not include source code for modules which are standard
-libraries that accompany the operating system on which the executable
-file runs, or for standard header files or definitions files that
-accompany that operating system.
-
- 4. You may not copy, modify, sublicense, distribute or transfer the
-Program except as expressly provided under this General Public License.
-Any attempt otherwise to copy, modify, sublicense, distribute or transfer
-the Program is void, and will automatically terminate your rights to use
-the Program under this License. However, parties who have received
-copies, or rights to use copies, from you under this General Public
-License will not have their licenses terminated so long as such parties
-remain in full compliance.
-
- 5. By copying, distributing or modifying the Program (or any work based
-on the Program) you indicate your acceptance of this license to do so,
-and all its terms and conditions.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the original
-licensor to copy, distribute or modify the Program subject to these
-terms and conditions. You may not impose any further restrictions on the
-recipients` exercise of the rights granted herein.
-
- 7. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of the license which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-the license, you may choose any version ever published by the Free Software
-Foundation.
-
- 8. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- 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
-the exclusion of warranty; and each file should have at least the
-"copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program`s name and a brief idea of what it does.>
- Copyright (C) 19yy <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 1, or (at your option)
- any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) 19xx name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w`.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c` for details.
-
-The hypothetical commands `show w` and `show c` should show the
-appropriate parts of the General Public License. Of course, the
-commands you use may be called something other than `show w` and `show
-c`; they could even be mouse-clicks or menu items--whatever suits your
-program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the
- program `Gnomovision` (a program to direct compilers to make passes
- at assemblers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-That`s all there is to it!
-
-
-
-
-GPL-2.0
-
-
-GNU GENERAL PUBLIC LICENSE
-
-Version 2, June 1991
-
-Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-Preamble
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public License is intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users. This General Public License applies to most of the Free Software
-Foundation`s software and to any other program whose authors commit to using it. (Some
-other Free Software Foundation software is covered by the GNU Lesser General Public
-License instead.) You can apply it to your programs, too.
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for this service if you wish), that you receive
-source code or can get it if you want it, that you can change the software or use
-pieces of it in new free programs; and that you know you can do these things.
-
-To protect your rights, we need to make restrictions that forbid anyone to deny you
-these rights or to ask you to surrender the rights. These restrictions translate to
-certain responsibilities for you if you distribute copies of the software, or if you
-modify it.
-
-For example, if you distribute copies of such a program, whether gratis or for a fee,
-you must give the recipients all the rights that you have. You must make sure that
-they, too, receive or can get the source code. And you must show them these terms so
-they know their rights.
-
-We protect your rights with two steps: (1) copyright the software, and (2) offer you
-this license which gives you legal permission to copy, distribute and/or modify the
-software.
-
-Also, for each author`s protection and ours, we want to make certain that everyone
-understands that there is no warranty for this free software. If the software is
-modified by someone else and passed on, we want its recipients to know that what they
-have is not the original, so that any problems introduced by others will not reflect
-on the original authors` reputations.
-
-Finally, any free program is threatened constantly by software patents. We wish to
-avoid the danger that redistributors of a free program will individually obtain patent
-licenses, in effect making the program proprietary. To prevent this, we have made it
-clear that any patent must be licensed for everyone`s free use or not licensed at all.
-
-The precise terms and conditions for copying, distribution and modification follow.
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-0. This License applies to any program or other work which contains a notice placed by
-the copyright holder saying it may be distributed under the terms of this General
-Public License. The "Program", below, refers to any such program or work, and a "work
-based on the Program" means either the Program or any derivative work under copyright
-law: that is to say, a work containing the Program or a portion of it, either verbatim
-or with modifications and/or translated into another language. (Hereinafter,
-translation is included without limitation in the term "modification".) Each licensee
-is addressed as "you".
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running the Program is not restricted,
-and the output from the Program is covered only if its contents constitute a work
-based on the Program (independent of having been made by running the Program). Whether
-that is true depends on what the Program does.
-
-1. You may copy and distribute verbatim copies of the Program`s source code as you
-receive it, in any medium, provided that you conspicuously and appropriately publish
-on each copy an appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any warranty; and
-give any other recipients of the Program a copy of this License along with the
-Program.
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-2. You may modify your copy or copies of the Program or any portion of it, thus
-forming a work based on the Program, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-a) You must cause the modified files to carry prominent notices stating that you
-changed the files and the date of any change.
-b) You must cause any work that you distribute or publish, that in whole or in part
-contains or is derived from the Program or any part thereof, to be licensed as a whole
-at no charge to all third parties under the terms of this License.
-c) If the modified program normally reads commands interactively when run, you must
-cause it, when started running for such interactive use in the most ordinary way, to
-print or display an announcement including an appropriate copyright notice and a
-notice that there is no warranty (or else, saying that you provide a warranty) and
-that users may redistribute the program under these conditions, and telling the user
-how to view a copy of this License. (Exception: if the Program itself is interactive
-but does not normally print such an announcement, your work based on the Program is
-not required to print an announcement.)
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Program, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Program,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program with the
-Program (or with a work based on the Program) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-3. You may copy and distribute the Program (or a work based on it, under Section 2) in
-object code or executable form under the terms of Sections 1 and 2 above provided that
-you also do one of the following:
-
-a) Accompany it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a medium customarily
-used for software interchange; or,
-b) Accompany it with a written offer, valid for at least three years, to give any
-third party, for a charge no more than your cost of physically performing source
-distribution, a complete machine-readable copy of the corresponding source code, to be
-distributed under the terms of Sections 1 and 2 above on a medium customarily used for
-software interchange; or,
-c) Accompany it with the information you received as to the offer to distribute
-corresponding source code. (This alternative is allowed only for noncommercial
-distribution and only if you received the program in object code or executable form
-with such an offer, in accord with Subsection b above.)
-The source code for a work means the preferred form of the work for making
-modifications to it. For an executable work, complete source code means all the source
-code for all modules it contains, plus any associated interface definition files, plus
-the scripts used to control compilation and installation of the executable. However,
-as a special exception, the source code distributed need not include anything that is
-normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-If distribution of executable or object code is made by offering access to copy from a
-designated place, then offering equivalent access to copy the source code from the
-same place counts as distribution of the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-4. You may not copy, modify, sublicense, or distribute the Program except as expressly
-provided under this License. Any attempt otherwise to copy, modify, sublicense or
-distribute the Program is void, and will automatically terminate your rights under
-this License. However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such parties remain in
-full compliance.
-
-5. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Program or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Program or works based on it.
-
-6. Each time you redistribute the Program (or any work based on the Program), the
-recipient automatically receives a license from the original licensor to copy,
-distribute or modify the Program subject to these terms and conditions. You may not
-impose any further restrictions on the recipients` exercise of the rights granted
-herein. You are not responsible for enforcing compliance by third parties to this
-License.
-
-7. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Program at all. For example, if a patent license would not permit royalty-free
-redistribution of the Program by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply and the section as a
-whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system,
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-8. If the distribution and/or use of the Program is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Program under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-9. The Free Software Foundation may publish revised and/or new versions of the General
-Public License from time to time. Such new versions will be similar in spirit to the
-present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Program does not
-specify a version number of this License, you may choose any version ever published by
-the Free Software Foundation.
-
-10. If you wish to incorporate parts of the Program into other free programs whose
-distribution conditions are different, write to the author to ask for permission. For
-software which is copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this. Our decision will be
-guided by the two goals of preserving the free status of all derivatives of our free
-software and of promoting the sharing and reuse of software generally.
-
-NO WARRANTY
-
-11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
-WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-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 the "copyright" line and a pointer to where the
-full notice is found.
-
-one line to give the program`s name and an idea of what it does.
-Copyright (C) yyyy name of author
-
-This program is free software; you can redistribute it and/or
-modify it under the terms of the GNU General Public License
-as published by the Free Software Foundation; either version 2
-of the License, or (at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this when it starts
-in an interactive mode:
-
-Gnomovision version 69, Copyright (C) year name of author
-Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
-type `show w`. This is free software, and you are welcome
-to redistribute it under certain conditions; type `show c`
-for details.
-The hypothetical commands `show w` and `show c` should show the appropriate parts of
-the General Public License. Of course, the commands you use may be called something
-other than `show w` and `show c`; they could even be mouse-clicks or menu
-items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample;
-alter the names:
-
-Yoyodyne, Inc., hereby disclaims all copyright
-interest in the program `Gnomovision`
-(which makes passes at compilers) written
-by James Hacker.
-
-signature of Ty Coon, 1 April 1989
-Ty Coon, President of Vice
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may consider it
-more useful to permit linking proprietary applications with the library. If this is
-what you want to do, use the GNU Lesser General Public License instead of this
-License.
-
-
-
-
-GPL-2.0-with-GCC-exception
-
-
-insert GPL v2 text here
-
-GCC Linking Exception
-In addition to the permissions in the GNU General Public License, the Free
-Software Foundation gives you unlimited permission to link the compiled version
-of this file into combinations with other programs, and to distribute those
-combinations without any restriction coming from the use of this file. (The
-General Public License restrictions do apply in other respects; for example,
-they cover modification of the file, and distribution when not linked into a
-combine executable.)
-
-
-
-
-
-
-
-
-
-GPL-2.0-with-classpath-exception
-
-
-insert GPL v2 license text here
-
-Linking this library statically or dynamically with other modules is making a combined
-work based on this library. Thus, the terms and conditions of the GNU General Public
-License cover the whole combination.
-
-As a special exception, the copyright holders of this library give you permission to
-link this library with independent modules to produce an executable, regardless of the
-license terms of these independent modules, and to copy and distribute the resulting
-executable under terms of your choice, provided that you also meet, for each linked
-independent module, the terms and conditions of the license of that module. An
-independent module is a module which is not derived from or based on this library. If
-you modify this library, you may extend this exception to your version of the library,
-but you are not obligated to do so. If you do not wish to do so, delete this exception
-statement from your version.
-
-
-
-
-GPL-3.0
-
-GNU GENERAL PUBLIC LICENSE
-
-Version 3, 29 June 2007
-
-Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-Preamble
-
-The GNU General Public License is a free, copyleft license for software and other
-kinds of works.
-
-The licenses for most software and other practical works are designed to take away
-your freedom to share and change the works. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change all versions of a
-program--to make sure it remains free software for all its users. We, the Free
-Software Foundation, use the GNU General Public License for most of our software; it
-applies also to any other work released this way by its authors. You can apply it to
-your programs, too.
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for them if you wish), that you receive source
-code or can get it if you want it, that you can change the software or use pieces of
-it in new free programs, and that you know you can do these things.
-
-To protect your rights, we need to prevent others from denying you these rights or
-asking you to surrender the rights. Therefore, you have certain responsibilities if
-you distribute copies of the software, or if you modify it: responsibilities to
-respect the freedom of others.
-
-For example, if you distribute copies of such a program, whether gratis or for a fee,
-you must pass on to the recipients the same freedoms that you received. You must make
-sure that they, too, receive or can get the source code. And you must show them these
-terms so they know their rights.
-
-Developers that use the GNU GPL protect your rights with two steps: (1) assert
-copyright on the software, and (2) offer you this License giving you legal permission
-to copy, distribute and/or modify it.
-
-For the developers' and authors' protection, the GPL clearly explains that there is no
-warranty for this free software. For both users' and authors' sake, the GPL requires
-that modified versions be marked as changed, so that their problems will not be
-attributed erroneously to authors of previous versions.
-
-Some devices are designed to deny users access to install or run modified versions of
-the software inside them, although the manufacturer can do so. This is fundamentally
-incompatible with the aim of protecting users' freedom to change the software. The
-systematic pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable. Therefore, we have designed
-this version of the GPL to prohibit the practice for those products. If such problems
-arise substantially in other domains, we stand ready to extend this provision to those
-domains in future versions of the GPL, as needed to protect the freedom of users.
-
-Finally, every program is threatened constantly by software patents. States should not
-allow patents to restrict development and use of software on general-purpose
-computers, but in those that do, we wish to avoid the special danger that patents
-applied to a free program could make it effectively proprietary. To prevent this, the
-GPL assures that patents cannot be used to render the program non-free.
-
-The precise terms and conditions for copying, distribution and modification follow.
-TERMS AND CONDITIONS
-0. Definitions.
-
-”This License” refers to version 3 of the GNU General Public License.
-
-”Copyright” also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-”The Program” refers to any copyrightable work licensed under this
-License. Each licensee is addressed as ”you”. ”Licensees”
-and ”recipients” may be individuals or organizations.
-
-To ”modify” a work means to copy from or adapt all or part of the work in
-a fashion requiring copyright permission, other than the making of an exact copy. The
-resulting work is called a ”modified version” of the earlier work or a
-work ”based on” the earlier work.
-
-A ”covered work” means either the unmodified Program or a work based on
-the Program.
-
-To ”propagate” a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for infringement under
-applicable copyright law, except executing it on a computer or modifying a private
-copy. Propagation includes copying, distribution (with or without modification),
-making available to the public, and in some countries other activities as well.
-
-To ”convey” a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user through a computer
-network, with no transfer of a copy, is not conveying.
-
-An interactive user interface displays ”Appropriate Legal Notices” to the
-extent that it includes a convenient and prominently visible feature that (1) displays
-an appropriate copyright notice, and (2) tells the user that there is no warranty for
-the work (except to the extent that warranties are provided), that licensees may
-convey the work under this License, and how to view a copy of this License. If the
-interface presents a list of user commands or options, such as a menu, a prominent
-item in the list meets this criterion.
-1. Source Code.
-
-The ”source code” for a work means the preferred form of the work for
-making modifications to it. ”Object code” means any non-source form of a
-work.
-
-A ”Standard Interface” means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of interfaces
-specified for a particular programming language, one that is widely used among
-developers working in that language.
-
-The ”System Libraries” of an executable work include anything, other than
-the work as a whole, that (a) is included in the normal form of packaging a Major
-Component, but which is not part of that Major Component, and (b) serves only to
-enable use of the work with that Major Component, or to implement a Standard Interface
-for which an implementation is available to the public in source code form. A
-”Major Component”, in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system (if any) on which
-the executable work runs, or a compiler used to produce the work, or an object code
-interpreter used to run it.
-
-The ”Corresponding Source” for a work in object code form means all the
-source code needed to generate, install, and (for an executable work) run the object
-code and to modify the work, including scripts to control those activities. However,
-it does not include the work's System Libraries, or general-purpose tools or generally
-available free programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source includes interface
-definition files associated with source files for the work, and the source code for
-shared libraries and dynamically linked subprograms that the work is specifically
-designed to require, such as by intimate data communication or control flow between
-those subprograms and other parts of the work.
-
-The Corresponding Source need not include anything that users can regenerate
-automatically from other parts of the Corresponding Source.
-
-The Corresponding Source for a work in source code form is that same work.
-2. Basic Permissions.
-
-All rights granted under this License are granted for the term of copyright on the
-Program, and are irrevocable provided the stated conditions are met. This License
-explicitly affirms your unlimited permission to run the unmodified Program. The output
-from running a covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your rights of fair use
-or other equivalent, as provided by copyright law.
-
-You may make, run and propagate covered works that you do not convey, without
-conditions so long as your license otherwise remains in force. You may convey covered
-works to others for the sole purpose of having them make modifications exclusively for
-you, or provide you with facilities for running those works, provided that you comply
-with the terms of this License in conveying all material for which you do not control
-copyright. Those thus making or running the covered works for you must do so
-exclusively on your behalf, under your direction and control, on terms that prohibit
-them from making any copies of your copyrighted material outside their relationship
-with you.
-
-Conveying under any other circumstances is permitted solely under the conditions
-stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
-3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-No covered work shall be deemed part of an effective technological measure under any
-applicable law fulfilling obligations under article 11 of the WIPO copyright treaty
-adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention
-of such measures.
-
-When you convey a covered work, you waive any legal power to forbid circumvention of
-technological measures to the extent such circumvention is effected by exercising
-rights under this License with respect to the covered work, and you disclaim any
-intention to limit operation or modification of the work as a means of enforcing,
-against the work's users, your or third parties' legal rights to forbid circumvention
-of technological measures.
-4. Conveying Verbatim Copies.
-
-You may convey verbatim copies of the Program's source code as you receive it, in any
-medium, provided that you conspicuously and appropriately publish on each copy an
-appropriate copyright notice; keep intact all notices stating that this License and
-any non-permissive terms added in accord with section 7 apply to the code; keep intact
-all notices of the absence of any warranty; and give all recipients a copy of this
-License along with the Program.
-
-You may charge any price or no price for each copy that you convey, and you may offer
-support or warranty protection for a fee.
-5. Conveying Modified Source Versions.
-
-You may convey a work based on the Program, or the modifications to produce it from
-the Program, in the form of source code under the terms of section 4, provided that
-you also meet all of these conditions:
-
- * a) The work must carry prominent notices stating that you modified it, and
-giving a relevant date.
- * b) The work must carry prominent notices stating that it is released under this
-License and any conditions added under section 7. This requirement modifies the
-requirement in section 4 to ”keep intact all notices”.
- * c) You must license the entire work, as a whole, under this License to anyone
-who comes into possession of a copy. This License will therefore apply, along with any
-applicable section 7 additional terms, to the whole of the work, and all its parts,
-regardless of how they are packaged. This License gives no permission to license the
-work in any other way, but it does not invalidate such permission if you have
-separately received it.
- * d) If the work has interactive user interfaces, each must display Appropriate
-Legal Notices; however, if the Program has interactive interfaces that do not display
-Appropriate Legal Notices, your work need not make them do so.
-
-A compilation of a covered work with other separate and independent works, which are
-not by their nature extensions of the covered work, and which are not combined with it
-such as to form a larger program, in or on a volume of a storage or distribution
-medium, is called an ”aggregate” if the compilation and its resulting
-copyright are not used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work in an aggregate
-does not cause this License to apply to the other parts of the aggregate.
-6. Conveying Non-Source Forms.
-
-You may convey a covered work in object code form under the terms of sections 4 and 5,
-provided that you also convey the machine-readable Corresponding Source under the
-terms of this License, in one of these ways:
-
- * a) Convey the object code in, or embodied in, a physical product (including a
-physical distribution medium), accompanied by the Corresponding Source fixed on a
-durable physical medium customarily used for software interchange.
- * b) Convey the object code in, or embodied in, a physical product (including a
-physical distribution medium), accompanied by a written offer, valid for at least
-three years and valid for as long as you offer spare parts or customer support for
-that product model, to give anyone who possesses the object code either (1) a copy of
-the Corresponding Source for all the software in the product that is covered by this
-License, on a durable physical medium customarily used for software interchange, for a
-price no more than your reasonable cost of physically performing this conveying of
-source, or (2) access to copy the Corresponding Source from a network server at no
-charge.
- * c) Convey individual copies of the object code with a copy of the written offer
-to provide the Corresponding Source. This alternative is allowed only occasionally and
-noncommercially, and only if you received the object code with such an offer, in
-accord with subsection 6b.
- * d) Convey the object code by offering access from a designated place (gratis or
-for a charge), and offer equivalent access to the Corresponding Source in the same way
-through the same place at no further charge. You need not require recipients to copy
-the Corresponding Source along with the object code. If the place to copy the object
-code is a network server, the Corresponding Source may be on a different server
-(operated by you or a third party) that supports equivalent copying facilities,
-provided you maintain clear directions next to the object code saying where to find
-the Corresponding Source. Regardless of what server hosts the Corresponding Source,
-you remain obligated to ensure that it is available for as long as needed to satisfy
-these requirements.
- * e) Convey the object code using peer-to-peer transmission, provided you inform
-other peers where the object code and Corresponding Source of the work are being
-offered to the general public at no charge under subsection 6d.
-
-A separable portion of the object code, whose source code is excluded from the
-Corresponding Source as a System Library, need not be included in conveying the object
-code work.
-
-A ”User Product” is either (1) a ”consumer product”, which
-means any tangible personal property which is normally used for personal, family, or
-household purposes, or (2) anything designed or sold for incorporation into a
-dwelling. In determining whether a product is a consumer product, doubtful cases shall
-be resolved in favor of coverage. For a particular product received by a particular
-user, ”normally used” refers to a typical or common use of that class of
-product, regardless of the status of the particular user or of the way in which the
-particular user actually uses, or expects or is expected to use, the product. A
-product is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent the only
-significant mode of use of the product.
-
-”Installation Information” for a User Product means any methods,
-procedures, authorization keys, or other information required to install and execute
-modified versions of a covered work in that User Product from a modified version of
-its Corresponding Source. The information must suffice to ensure that the continued
-functioning of the modified object code is in no case prevented or interfered with
-solely because modification has been made.
-
-If you convey an object code work under this section in, or with, or specifically for
-use in, a User Product, and the conveying occurs as part of a transaction in which the
-right of possession and use of the User Product is transferred to the recipient in
-perpetuity or for a fixed term (regardless of how the transaction is characterized),
-the Corresponding Source conveyed under this section must be accompanied by the
-Installation Information. But this requirement does not apply if neither you nor any
-third party retains the ability to install modified object code on the User Product
-(for example, the work has been installed in ROM).
-
-The requirement to provide Installation Information does not include a requirement to
-continue to provide support service, warranty, or updates for a work that has been
-modified or installed by the recipient, or for the User Product in which it has been
-modified or installed. Access to a network may be denied when the modification itself
-materially and adversely affects the operation of the network or violates the rules
-and protocols for communication across the network.
-
-Corresponding Source conveyed, and Installation Information provided, in accord with
-this section must be in a format that is publicly documented (and with an
-implementation available to the public in source code form), and must require no
-special password or key for unpacking, reading or copying.
-7. Additional Terms.
-
-”Additional permissions” are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions. Additional
-permissions that are applicable to the entire Program shall be treated as though they
-were included in this License, to the extent that they are valid under applicable law.
-If additional permissions apply only to part of the Program, that part may be used
-separately under those permissions, but the entire Program remains governed by this
-License without regard to the additional permissions.
-
-When you convey a copy of a covered work, you may at your option remove any additional
-permissions from that copy, or from any part of it. (Additional permissions may be
-written to require their own removal in certain cases when you modify the work.) You
-may place additional permissions on material, added by you to a covered work, for
-which you have or can give appropriate copyright permission.
-
-Notwithstanding any other provision of this License, for material you add to a covered
-work, you may (if authorized by the copyright holders of that material) supplement the
-terms of this License with terms:
-
- * a) Disclaiming warranty or limiting liability differently from the terms of
-sections 15 and 16 of this License; or
- * b) Requiring preservation of specified reasonable legal notices or author
-attributions in that material or in the Appropriate Legal Notices displayed by works
-containing it; or
- * c) Prohibiting misrepresentation of the origin of that material, or requiring
-that modified versions of such material be marked in reasonable ways as different from
-the original version; or
- * d) Limiting the use for publicity purposes of names of licensors or authors of
-the material; or
- * e) Declining to grant rights under trademark law for use of some trade names,
-trademarks, or service marks; or
- * f) Requiring indemnification of licensors and authors of that material by anyone
-who conveys the material (or modified versions of it) with contractual assumptions of
-liability to the recipient, for any liability that these contractual assumptions
-directly impose on those licensors and authors.
-
-All other non-permissive additional terms are considered ”further
-restrictions” within the meaning of section 10. If the Program as you received
-it, or any part of it, contains a notice stating that it is governed by this License
-along with a term that is a further restriction, you may remove that term. If a
-license document contains a further restriction but permits relicensing or conveying
-under this License, you may add to a covered work material governed by the terms of
-that license document, provided that the further restriction does not survive such
-relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you must place, in the
-relevant source files, a statement of the additional terms that apply to those files,
-or a notice indicating where to find the applicable terms.
-
-Additional terms, permissive or non-permissive, may be stated in the form of a
-separately written license, or stated as exceptions; the above requirements apply
-either way.
-8. Termination.
-
-You may not propagate or modify a covered work except as expressly provided under this
-License. Any attempt otherwise to propagate or modify it is void, and will
-automatically terminate your rights under this License (including any patent licenses
-granted under the third paragraph of section 11).
-
-However, if you cease all violation of this License, then your license from a
-particular copyright holder is reinstated (a) provisionally, unless and until the
-copyright holder explicitly and finally terminates your license, and (b) permanently,
-if the copyright holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is reinstated permanently if
-the copyright holder notifies you of the violation by some reasonable means, this is
-the first time you have received notice of violation of this License (for any work)
-from that copyright holder, and you cure the violation prior to 30 days after your
-receipt of the notice.
-
-Termination of your rights under this section does not terminate the licenses of
-parties who have received copies or rights from you under this License. If your rights
-have been terminated and not permanently reinstated, you do not qualify to receive new
-licenses for the same material under section 10.
-9. Acceptance Not Required for Having Copies.
-
-You are not required to accept this License in order to receive or run a copy of the
-Program. Ancillary propagation of a covered work occurring solely as a consequence of
-using peer-to-peer transmission to receive a copy likewise does not require
-acceptance. However, nothing other than this License grants you permission to
-propagate or modify any covered work. These actions infringe copyright if you do not
-accept this License. Therefore, by modifying or propagating a covered work, you
-indicate your acceptance of this License to do so.
-10. Automatic Licensing of Downstream Recipients.
-
-Each time you convey a covered work, the recipient automatically receives a license
-from the original licensors, to run, modify and propagate that work, subject to this
-License. You are not responsible for enforcing compliance by third parties with this
-License.
-
-An ”entity transaction” is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an organization, or
-merging organizations. If propagation of a covered work results from an entity
-transaction, each party to that transaction who receives a copy of the work also
-receives whatever licenses to the work the party's predecessor in interest had or
-could give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if the predecessor
-has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the rights granted or
-affirmed under this License. For example, you may not impose a license fee, royalty,
-or other charge for exercise of rights granted under this License, and you may not
-initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging
-that any patent claim is infringed by making, using, selling, offering for sale, or
-importing the Program or any portion of it.
-11. Patents.
-
-A ”contributor” is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The work thus licensed
-is called the contributor's ”contributor version”.
-
-A contributor's ”essential patent claims” are all patent claims owned or
-controlled by the contributor, whether already acquired or hereafter acquired, that
-would be infringed by some manner, permitted by this License, of making, using, or
-selling its contributor version, but do not include claims that would be infringed
-only as a consequence of further modification of the contributor version. For purposes
-of this definition, ”control” includes the right to grant patent
-sublicenses in a manner consistent with the requirements of this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free patent license
-under the contributor's essential patent claims, to make, use, sell, offer for sale,
-import and otherwise run, modify and propagate the contents of its contributor
-version.
-
-In the following three paragraphs, a ”patent license” is any express
-agreement or commitment, however denominated, not to enforce a patent (such as an
-express permission to practice a patent or covenant not to sue for patent
-infringement). To ”grant” such a patent license to a party means to make
-such an agreement or commitment not to enforce a patent against the party.
-
-If you convey a covered work, knowingly relying on a patent license, and the
-Corresponding Source of the work is not available for anyone to copy, free of charge
-and under the terms of this License, through a publicly available network server or
-other readily accessible means, then you must either (1) cause the Corresponding
-Source to be so available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner consistent with
-the requirements of this License, to extend the patent license to downstream
-recipients. ”Knowingly relying” means you have actual knowledge that, but
-for the patent license, your conveying the covered work in a country, or your
-recipient's use of the covered work in a country, would infringe one or more
-identifiable patents in that country that you have reason to believe are valid.
-
-If, pursuant to or in connection with a single transaction or arrangement, you convey,
-or propagate by procuring conveyance of, a covered work, and grant a patent license to
-some of the parties receiving the covered work authorizing them to use, propagate,
-modify or convey a specific copy of the covered work, then the patent license you
-grant is automatically extended to all recipients of the covered work and works based
-on it.
-
-A patent license is ”discriminatory” if it does not include within the
-scope of its coverage, prohibits the exercise of, or is conditioned on the
-non-exercise of one or more of the rights that are specifically granted under this
-License. You may not convey a covered work if you are a party to an arrangement with a
-third party that is in the business of distributing software, under which you make
-payment to the third party based on the extent of your activity of conveying the work,
-and under which the third party grants, to any of the parties who would receive the
-covered work from you, a discriminatory patent license (a) in connection with copies
-of the covered work conveyed by you (or copies made from those copies), or (b)
-primarily for and in connection with specific products or compilations that contain
-the covered work, unless you entered into that arrangement, or that patent license was
-granted, prior to 28 March 2007.
-
-Nothing in this License shall be construed as excluding or limiting any implied
-license or other defenses to infringement that may otherwise be available to you under
-applicable patent law.
-12. No Surrender of Others' Freedom.
-
-If conditions are imposed on you (whether by court order, agreement or otherwise) that
-contradict the conditions of this License, they do not excuse you from the conditions
-of this License. If you cannot convey a covered work so as to satisfy simultaneously
-your obligations under this License and any other pertinent obligations, then as a
-consequence you may not convey it at all. For example, if you agree to terms that
-obligate you to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this License would be
-to refrain entirely from conveying the Program.
-13. Use with the GNU Affero General Public License.
-
-Notwithstanding any other provision of this License, you have permission to link or
-combine any covered work with a work licensed under version 3 of the GNU Affero
-General Public License into a single combined work, and to convey the resulting work.
-The terms of this License will continue to apply to the part which is the covered
-work, but the special requirements of the GNU Affero General Public License, section
-13, concerning interaction through a network will apply to the combination as such.
-14. Revised Versions of this License.
-
-The Free Software Foundation may publish revised and/or new versions of the GNU
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program specifies that a
-certain numbered version of the GNU General Public License ”or any later
-version” applies to it, you have the option of following the terms and
-conditions either of that numbered version or of any later version published by the
-Free Software Foundation. If the Program does not specify a version number of the GNU
-General Public License, you may choose any version ever published by the Free Software
-Foundation.
-
-If the Program specifies that a proxy can decide which future versions of the GNU
-General Public License can be used, that proxy's public statement of acceptance of a
-version permanently authorizes you to choose that version for the Program.
-
-Later license versions may give you additional or different permissions. However, no
-additional obligations are imposed on any author or copyright holder as a result of
-your choosing to follow a later version.
-15. Disclaimer of Warranty.
-
-THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM ”AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
-EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
-QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
-DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-16. Limitation of Liability.
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
-WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-17. Interpretation of Sections 15 and 16.
-
-If the disclaimer of warranty and limitation of liability provided above cannot be
-given local legal effect according to their terms, reviewing courts shall apply local
-law that most closely approximates an absolute waiver of all civil liability in
-connection with the Program, unless a warranty or assumption of liability accompanies
-a copy of the Program in return for a fee.
-
-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 the ”copyright” line and a pointer to
-where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program does terminal interaction, make it output a short notice like this when
-it starts in an interactive mode:
-
- <program> Copyright (C) <year> <name of author>
- This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate parts of
-the General Public License. Of course, your program's commands might be different; for
-a GUI interface, you would use an ”about box”.
-
-You should also get your employer (if you work as a programmer) or school, if any, to
-sign a ”copyright disclaimer” for the program, if necessary. For more
-information on this, and how to apply and follow the GNU GPL, see
-<http://www.gnu.org/licenses/>.
-
-The GNU General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may consider it
-more useful to permit linking proprietary applications with the library. If this is
-what you want to do, use the GNU Lesser General Public License instead of this
-License. But first, please read
-<http://www.gnu.org/philosophy/why-not-lgpl.html>.
-
-
-
-GPL-3.0-with-GCC-exception
-
-
-insert GPL v3 text here
-
-GCC RUNTIME LIBRARY EXCEPTION
-Version 3.1, 31 March 2009
-
-General information:
-http://www.gnu.org/licenses/gcc-exception.html
-Copyright (C) 2009 Free Software Foundation, Inc. <http://fsf.org/>
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-This GCC Runtime Library Exception ("Exception") is an additional permission under
-section 7 of the GNU General Public License, version 3 ("GPLv3"). It applies to a
-given file (the "Runtime Library") that bears a notice placed by the copyright holder
-of the file stating that the file is governed by GPLv3 along with this Exception.
-When you use GCC to compile a program, GCC may combine portions of certain GCC header
-files and runtime libraries with the compiled program. The purpose of this Exception
-is to allow compilation of non-GPL (including proprietary) programs to use, in this
-way, the header files and runtime libraries covered by this Exception.
-
-0. Definitions.
-A file is an "Independent Module" if it either requires the Runtime Library for
-execution after a Compilation Process, or makes use of an interface provided by the
-Runtime Library, but is not otherwise based on the Runtime Library.
-"GCC" means a version of the GNU Compiler Collection, with or without modifications,
-governed by version 3 (or a specified later version) of the GNU General Public License
-(GPL) with the option of using any subsequent versions published by the FSF.
-"GPL-compatible Software" is software whose conditions of propagation, modification
-and use would permit combination with GCC in accord with the license of GCC.
-"Target Code" refers to output from any compiler for a real or virtual target
-processor architecture, in executable form or suitable for input to an assembler,
-loader, linker and/or execution phase. Notwithstanding that, Target Code does not
-include data in any format that is used as a compiler intermediate representation, or
-used for producing a compiler intermediate representation.
-The "Compilation Process" transforms code entirely represented in non-intermediate
-languages designed for human-written code, and/or in Java Virtual Machine byte code,
-into Target Code. Thus, for example, use of source code generators and preprocessors
-need not be considered part of the Compilation Process, since the Compilation Process
-can be understood as starting with the output of the generators or preprocessors.
-A Compilation Process is "Eligible" if it is done using GCC, alone or with other
-GPL-compatible software, or if it is done without using any work based on GCC. For
-example, using non-GPL-compatible Software to optimize any GCC intermediate
-representations would not qualify as an Eligible Compilation Process.
-
-1. Grant of Additional Permission.
-You have permission to propagate a work of Target Code formed by combining the Runtime
-Library with Independent Modules, even if such propagation would otherwise violate the
-terms of GPLv3, provided that all Target Code was generated by Eligible Compilation
-Processes. You may then convey such a combination under terms of your choice,
-consistent with the licensing of the Independent Modules.
-
-2. No Weakening of GCC Copyleft.
-The availability of this Exception does not imply any general presumption that
-third-party software is unaffected by the copyleft requirements of the license of GCC.
-
-
-
-
-GPL-3.0-with-autoconf-exception
-
-
-insert GPL v3 text here
-
-AUTOCONF CONFIGURE SCRIPT EXCEPTION
-
-Version 3.0, 18 August 2009
-
-Copyright © 2009 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-
-This Exception is an additional permission under section 7 of the GNU General Public
-License, version 3 ("GPLv3"). It applies to a given file that bears a notice placed by
-the copyright holder of the file stating that the file is governed by GPLv3 along with
-this Exception.
-
-The purpose of this Exception is to allow distribution of Autoconf`s typical output
-under terms of the recipient`s choice (including proprietary).
-
-0. Definitions.
-"Covered Code" is the source or object code of a version of Autoconf that is a covered
-work under this License.
-
-"Normally Copied Code" for a version of Autoconf means all parts of its Covered Code
-which that version can copy from its code (i.e., not from its input file) into its
-minimally verbose, non-debugging and non-tracing output.
-
-"Ineligible Code" is Covered Code that is not Normally Copied Code.
-
-1. Grant of Additional Permission.
-You have permission to propagate output of Autoconf, even if such propagation would
-otherwise violate the terms of GPLv3. However, if by modifying Autoconf you cause any
-Ineligible Code of the version you received to become Normally Copied Code of your
-modified version, then you void this Exception for the resulting covered work. If you
-convey that resulting covered work, you must remove this Exception in accordance with
-the second paragraph of Section 7 of GPLv3.
-
-2. No Weakening of Autoconf Copyleft.
-The availability of this Exception does not imply any general presumption that
-third-party software is unaffected by the copyleft requirements of the license of
-Autoconf.
-
-
-
-
-ICU
-
-COPYRIGHT AND PERMISSION NOTICE
-
-Copyright (c) 1995-2012 International Business Machines Corporation and others
-
-All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this
-software and associated documentation files (the "Software"), to deal in the Software
-without restriction, including without limitation the rights to use, copy, modify,
-merge, publish, distribute, and/or sell copies of the Software, and to permit persons
-to whom the Software is furnished to do so, provided that the above copyright
-notice(s) and this permission notice appear in all copies of the Software and that
-both the above copyright notice(s) and this permission notice appear in supporting
-documentation.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
-INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
-PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
-COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
-SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
-LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
-TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
-SOFTWARE.
-
-Except as contained in this notice, the name of a copyright holder shall not be used
-in advertising or otherwise to promote the sale, use or other dealings in this
-Software without prior written authorization of the copyright holder.
-
-All trademarks and registered trademarks mentioned herein are the property of their
-respective owners.
-
-
-
-IPL-1.0
-
-
-IBM Public License Version 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM
-PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
-OF THE PROGRAM CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-"Contribution" means:
-
-in the case of International Business Machines Corporation ("IBM"), the Original
-Program, and
-in the case of each Contributor,
-changes to the Program, and
-additions to the Program;
-where such changes and/or additions to the Program originate from and
-are distributed by that particular Contributor. A Contribution
-`originates` from a Contributor if it was added to the Program by
-such Contributor itself or anyone acting on such Contributor`s
-behalf. Contributions do not include additions to the Program which:
-(i) are separate modules of software distributed in conjunction with
-the Program under their own license agreement, and (ii) are not
-derivative works of the Program.
-
-"Contributor" means IBM and any other entity that distributes the Program.
-
-"Licensed Patents " mean patent claims licensable by a
-Contributor which are necessarily infringed by the use or sale of its
-Contribution alone or when combined with the Program.
-
-"Original Program" means the original version of the software
-accompanying this Agreement as released by IBM, including source
-code, object code and documentation, if any.
-
-"Program" means the Original Program and Contributions.
-
-"Recipient" means anyone who receives the Program under this
-Agreement, including all Contributors.
-
-2. GRANT OF RIGHTS
-Subject to the terms of this Agreement, each Contributor hereby
-grants Recipient a non-exclusive, worldwide, royalty-free copyright
-license to reproduce, prepare derivative works of, publicly display,
-publicly perform, distribute and sublicense the Contribution of such
-Contributor, if any, and such derivative works, in source code and
-object code form.
-Subject to the terms of this Agreement, each Contributor hereby
-grants Recipient a non-exclusive, worldwide, royalty-free patent
-license under Licensed Patents to make, use, sell, offer to sell,
-import and otherwise transfer the Contribution of such Contributor,
-if any, in source code and object code form. This patent license
-shall apply to the combination of the Contribution and the Program
-if, at the time the Contribution is added by the Contributor, such
-addition of the Contribution causes such combination to be covered by
-the Licensed Patents. The patent license shall not apply to any
-other combinations which include the Contribution. No hardware per
-se is licensed hereunder.
-
-Recipient understands that although each Contributor grants the
-licenses to its Contributions set forth herein, no assurances are
-provided by any Contributor that the Program does not infringe the
-patent or other intellectual property rights of any other entity.
-Each Contributor disclaims any liability to Recipient for claims
-brought by any other entity based on infringement of intellectual
-property rights or otherwise. As a condition to exercising the
-rights and licenses granted hereunder, each Recipient hereby assumes
-sole responsibility to secure any other intellectual property rights
-needed, if any. For example, if a third party patent license is
-required to allow Recipient to distribute the Program, it is
-Recipient`s responsibility to acquire that license before
-distributing the Program.
-Each Contributor represents that to its knowledge it has
-sufficient copyright rights in its Contribution, if any, to grant the
-copyright license set forth in this Agreement.
-3. REQUIREMENTS
-A Contributor may choose to distribute
-the Program in object code form under its own license agreement,
-provided that:
-
-it complies with the terms and conditions of this Agreement; and
-its license agreement:
-effectively disclaims on behalf of all Contributors all warranties
-and conditions, express and implied, including warranties or
-conditions of title and non-infringement, and implied warranties or
-conditions of merchantability and fitness for a particular purpose;
-effectively excludes on behalf of all Contributors all liability
-for damages, including direct, indirect, special, incidental and
-consequential damages, such as lost profits;
-states that any provisions which differ from this Agreement are
-offered by that Contributor alone and not by any other party; and
-
-states that source code for the Program is available from such
-Contributor, and informs licensees how to obtain it in a reasonable
-manner on or through a medium customarily used for software exchange.
-When the Program is made available in source code form:
-
-it must be made available under this Agreement; and
-a copy of this Agreement must be included with each copy of the
-Program.
-Each Contributor must include the following in a conspicuous location in the Program:
-
-Copyright (C) 1996, 1999 International Business Machines Corporation and others. All
-Rights Reserved.
-
-In addition, each Contributor must identify itself as the originator
-of its Contribution, if any, in a manner that reasonably allows
-subsequent Recipients to identify the originator of the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-Commercial distributors of software may accept certain
-responsibilities with respect to end users, business partners and the
-like. While this license is intended to facilitate the commercial
-use of the Program, the Contributor who includes the Program in a
-commercial product offering should do so in a manner which does not
-create potential liability for other Contributors. Therefore, if a
-Contributor includes the Program in a commercial product offering,
-such Contributor ("Commercial Contributor") hereby agrees to defend
-and indemnify every other Contributor ("Indemnified Contributor")
-against any losses, damages and costs (collectively "Losses") arising
-from claims, lawsuits and other legal actions brought by a third
-party against the Indemnified Contributor to the extent caused by the
-acts or omissions of such Commercial Contributor in connection with
-its distribution of the Program in a commercial product offering.
-The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement.
-In order to qualify, an Indemnified Contributor must: a) promptly
-notify the Commercial Contributor in writing of such claim, and b)
-allow the Commercial Contributor to control, and cooperate with the
-Commercial Contributor in, the defense and any related settlement
-negotiations. The Indemnified Contributor may participate in any
-such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial
-product offering, Product X. That Contributor is then a Commercial
-Contributor. If that Commercial Contributor then makes performance
-claims, or offers warranties related to Product X, those performance
-claims and warranties are such Commercial Contributor`s
-responsibility alone. Under this section, the Commercial Contributor
-would have to defend claims against the other Contributors related to
-those performance claims and warranties, and if a court requires any
-other Contributor to pay any damages as a result, the Commercial
-Contributor must pay those damages.
-
-5. NO WARRANTY
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS
-PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
-WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY
-OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
-responsible for determining the appropriateness of using and
-distributing the Program and assumes all risks associated with its
-exercise of rights under this Agreement, including but not limited to
-the risks and costs of program errors, compliance with applicable
-laws, damage to or loss of data, programs or equipment, and
-unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT
-NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
-TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
-THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
-GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-If any provision of this Agreement is invalid or unenforceable under
-applicable law, it shall not affect the validity or enforceability of
-the remainder of the terms of this Agreement, and without further
-action by the parties hereto, such provision shall be reformed to the
-minimum extent necessary to make such provision valid and enforceable.
-
-If Recipient institutes patent litigation against a Contributor with
-respect to a patent applicable to software (including a cross-claim
-or counterclaim in a lawsuit), then any patent licenses granted by
-that Contributor to such Recipient under this Agreement shall
-terminate as of the date such litigation is filed. In addition, if
-Recipient institutes patent litigation against any entity (including
-a cross-claim or counterclaim in a lawsuit) alleging that the Program
-itself (excluding combinations of the Program with other software or
-hardware) infringes such Recipient`s patent(s), then such Recipient`s
-rights granted under Section 2(b) shall terminate as of the date such
-litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it
-fails to comply with any of the material terms or conditions of this
-Agreement and does not cure such failure in a reasonable period of
-time after becoming aware of such noncompliance. If all Recipient`s
-rights under this Agreement terminate, Recipient agrees to cease use
-and distribution of the Program as soon as reasonably practicable.
-However, Recipient`s obligations under this Agreement and any
-licenses granted by Recipient relating to the Program shall continue
-and survive.
-
-IBM may publish new versions (including revisions) of this Agreement
-from time to time. Each new version of the Agreement will be given a
-distinguishing version number. The Program (including Contributions)
-may always be distributed subject to the version of the Agreement
-under which it was received. In addition, after a new version of the
-Agreement is published, Contributor may elect to distribute the
-Program (including its Contributions) under the new version. No one
-other than IBM has the right to modify this Agreement. Except as
-expressly stated in Sections 2(a) and 2(b) above, Recipient receives
-no rights or licenses to the intellectual property of any Contributor
-under this Agreement, whether expressly, by implication, estoppel or
-otherwise. All rights in the Program not expressly granted under
-this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and
-the intellectual property laws of the United States of America. No
-party to this Agreement will bring a legal action under this
-Agreement more than one year after the cause of action arose. Each
-party waives its rights to a jury trial in any resulting litigation.
-
-
-
-
-ISC
-
-
-ISC License:
-
-Copyright © 2004-2010 by Internet Systems Consortium, Inc. ("ISC")
-Copyright © 1995-2003 by Internet Software Consortium
-
-Permission to use, copy, modify, and/or distribute this software for any purpose with
-or without fee is hereby granted, provided that the above copyright notice and this
-permission notice appear in all copies.
-
-THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
-SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT
-SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
-DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
-OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
-THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
-
-
-
-JLEX
-
- JLEX COPYRIGHT NOTICE, LICENSE, AND DISCLAIMER
- Copyright 1996-2000 by Elliot Joel Berk and C. Scott Ananian
-
- Permission to use, copy, modify, and distribute this software and its
- documentation for any purpose and without fee is hereby granted,
- provided that the above copyright notice appear in all copies and that
- both the copyright notice and this permission notice and warranty
- disclaimer appear in supporting documentation, and that the name of
- the authors or their employers not be used in advertising or publicity
- pertaining to distribution of the software without specific, written
- prior permission.
-
- The authors and their employers disclaim all warranties with regard to
- this software, including all implied warranties of merchantability and
- fitness. In no event shall the authors or their employers be liable
- for any special, indirect or consequential damages or any damages
- whatsoever resulting from loss of use, data or profits, whether in an
- action of contract, negligence or other tortious action, arising out
- of or in connection with the use or performance of this software.
-
-
-
-LGPL-2.0
-
-GNU LIBRARY GENERAL PUBLIC LICENSE
-
-
-
-Version 2, June 1991
-
-
-
-Copyright (C) 1991 Free Software Foundation, Inc.
-
-51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
-
-Everyone is permitted to copy and distribute verbatim copies
-
-of this license document, but changing it is not allowed.
-
-
-
-[This is the first released version of the library GPL. It is
-
- numbered 2 because it goes with version 2 of the ordinary GPL.]
-
-Preamble
-
-
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public Licenses are intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users.
-
-
-
-This license, the Library General Public License, applies to some specially designated
-Free Software Foundation software, and to any other libraries whose authors decide to
-use it. You can use it for your libraries, too.
-
-
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for this service if you wish), that you receive
-source code or can get it if you want it, that you can change the software or use
-pieces of it in new free programs; and that you know you can do these things.
-
-
-
-To protect your rights, we need to make restrictions that forbid anyone to deny you
-these rights or to ask you to surrender the rights. These restrictions translate to
-certain responsibilities for you if you distribute copies of the library, or if you
-modify it.
-
-
-
-For example, if you distribute copies of the library, whether gratis or for a fee, you
-must give the recipients all the rights that we gave you. You must make sure that
-they, too, receive or can get the source code. If you link a program with the library,
-you must provide complete object files to the recipients so that they can relink them
-with the library, after making changes to the library and recompiling it. And you must
-show them these terms so they know their rights.
-
-
-
-Our method of protecting your rights has two steps: (1) copyright the library, and (2)
-offer you this license which gives you legal permission to copy, distribute and/or
-modify the library.
-
-
-
-Also, for each distributor's protection, we want to make certain that everyone
-understands that there is no warranty for this free library. If the library is
-modified by someone else and passed on, we want its recipients to know that what they
-have is not the original version, so that any problems introduced by others will not
-reflect on the original authors' reputations.
-
-
-
-Finally, any free program is threatened constantly by software patents. We wish to
-avoid the danger that companies distributing free software will individually obtain
-patent licenses, thus in effect transforming the program into proprietary software. To
-prevent this, we have made it clear that any patent must be licensed for everyone's
-free use or not licensed at all.
-
-
-
-Most GNU software, including some libraries, is covered by the ordinary GNU General
-Public License, which was designed for utility programs. This license, the GNU Library
-General Public License, applies to certain designated libraries. This license is quite
-different from the ordinary one; be sure to read it in full, and don't assume that
-anything in it is the same as in the ordinary license.
-
-
-
-The reason we have a separate public license for some libraries is that they blur the
-distinction we usually make between modifying or adding to a program and simply using
-it. Linking a program with a library, without changing the library, is in some sense
-simply using the library, and is analogous to running a utility program or application
-program. However, in a textual and legal sense, the linked executable is a combined
-work, a derivative of the original library, and the ordinary General Public License
-treats it as such.
-
-
-
-Because of this blurred distinction, using the ordinary General Public License for
-libraries did not effectively promote software sharing, because most developers did
-not use the libraries. We concluded that weaker conditions might promote sharing
-better.
-
-
-
-However, unrestricted linking of non-free programs would deprive the users of those
-programs of all benefit from the free status of the libraries themselves. This Library
-General Public License is intended to permit developers of non-free programs to use
-free libraries, while preserving your freedom as a user of such programs to change the
-free libraries that are incorporated in them. (We have not seen how to achieve this as
-regards changes in header files, but we have achieved it as regards changes in the
-actual functions of the Library.) The hope is that this will lead to faster
-development of free libraries.
-
-
-
-The precise terms and conditions for copying, distribution and modification follow.
-Pay close attention to the difference between a "work based on the library" and a
-"work that uses the library". The former contains code derived from the library, while
-the latter only works together with the library.
-
-
-
-Note that it is possible for a library to be covered by the ordinary General Public
-License rather than by this special one.
-
-
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-
-
-0. This License Agreement applies to any software library which contains a notice
-placed by the copyright holder or other authorized party saying it may be distributed
-under the terms of this Library General Public License (also called "this License").
-Each licensee is addressed as "you".
-
-
-
-A "library" means a collection of software functions and/or data prepared so as to be
-conveniently linked with application programs (which use some of those functions and
-data) to form executables.
-
-
-
-The "Library", below, refers to any such software library or work which has been
-distributed under these terms. A "work based on the Library" means either the Library
-or any derivative work under copyright law: that is to say, a work containing the
-Library or a portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is included without
-limitation in the term "modification".)
-
-
-
-"Source code" for a work means the preferred form of the work for making modifications
-to it. For a library, complete source code means all the source code for all modules
-it contains, plus any associated interface definition files, plus the scripts used to
-control compilation and installation of the library.
-
-
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running a program using the Library is
-not restricted, and output from such a program is covered only if its contents
-constitute a work based on the Library (independent of the use of the Library in a
-tool for writing it). Whether that is true depends on what the Library does and what
-the program that uses the Library does.
-
-
-
-1. You may copy and distribute verbatim copies of the Library's complete source code
-as you receive it, in any medium, provided that you conspicuously and appropriately
-publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
-intact all the notices that refer to this License and to the absence of any warranty;
-and distribute a copy of this License along with the Library.
-
-
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-
-
-2. You may modify your copy or copies of the Library or any portion of it, thus
-forming a work based on the Library, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-
-
-a) The modified work must itself be a software library.
-
-b) You must cause the files modified to carry prominent notices stating that you
-changed the files and the date of any change.
-
-c) You must cause the whole of the work to be licensed at no charge to all third
-parties under the terms of this License.
-
-d) If a facility in the modified Library refers to a function or a table of data to be
-supplied by an application program that uses the facility, other than as an argument
-passed when the facility is invoked, then you must make a good faith effort to ensure
-that, in the event an application does not supply such function or table, the facility
-still operates, and performs whatever part of its purpose remains meaningful.
-
-(For example, a function in a library to compute square roots has a purpose that is
-entirely well-defined independent of the application. Therefore, Subsection 2d
-requires that any application-supplied function or table used by this function must be
-optional: if the application does not supply it, the square root function must still
-compute square roots.)
-
-
-
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Library, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Library,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Library.
-
-
-
-In addition, mere aggregation of another work not based on the Library with the
-Library (or with a work based on the Library) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-
-
-3. You may opt to apply the terms of the ordinary GNU General Public License instead
-of this License to a given copy of the Library. To do this, you must alter all the
-notices that refer to this License, so that they refer to the ordinary GNU General
-Public License, version 2, instead of to this License. (If a newer version than
-version 2 of the ordinary GNU General Public License has appeared, then you can
-specify that version instead if you wish.) Do not make any other change in these
-notices.
-
-
-
-Once this change is made in a given copy, it is irreversible for that copy, so the
-ordinary GNU General Public License applies to all subsequent copies and derivative
-works made from that copy.
-
-
-
-This option is useful when you wish to copy part of the code of the Library into a
-program that is not a library.
-
-
-
-4. You may copy and distribute the Library (or a portion or derivative of it, under
-Section 2) in object code or executable form under the terms of Sections 1 and 2 above
-provided that you accompany it with the complete corresponding machine-readable source
-code, which must be distributed under the terms of Sections 1 and 2 above on a medium
-customarily used for software interchange.
-
-
-
-If distribution of object code is made by offering access to copy from a designated
-place, then offering equivalent access to copy the source code from the same place
-satisfies the requirement to distribute the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-
-
-5. A program that contains no derivative of any portion of the Library, but is
-designed to work with the Library by being compiled or linked with it, is called a
-"work that uses the Library". Such a work, in isolation, is not a derivative work of
-the Library, and therefore falls outside the scope of this License.
-
-
-
-However, linking a "work that uses the Library" with the Library creates an executable
-that is a derivative of the Library (because it contains portions of the Library),
-rather than a "work that uses the library". The executable is therefore covered by
-this License. Section 6 states terms for distribution of such executables.
-
-
-
-When a "work that uses the Library" uses material from a header file that is part of
-the Library, the object code for the work may be a derivative work of the Library even
-though the source code is not. Whether this is true is especially significant if the
-work can be linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
-
-
-If such an object file uses only numerical parameters, data structure layouts and
-accessors, and small macros and small inline functions (ten lines or less in length),
-then the use of the object file is unrestricted, regardless of whether it is legally a
-derivative work. (Executables containing this object code plus portions of the Library
-will still fall under Section 6.)
-
-
-
-Otherwise, if the work is a derivative of the Library, you may distribute the object
-code for the work under the terms of Section 6. Any executables containing that work
-also fall under Section 6, whether or not they are linked directly with the Library
-itself.
-
-
-
-6. As an exception to the Sections above, you may also compile or link a "work that
-uses the Library" with the Library to produce a work containing portions of the
-Library, and distribute that work under terms of your choice, provided that the terms
-permit modification of the work for the customer's own use and reverse engineering for
-debugging such modifications.
-
-
-
-You must give prominent notice with each copy of the work that the Library is used in
-it and that the Library and its use are covered by this License. You must supply a
-copy of this License. If the work during execution displays copyright notices, you
-must include the copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one of these things:
-
-
-
-a) Accompany the work with the complete corresponding machine-readable source code for
-the Library including whatever changes were used in the work (which must be
-distributed under Sections 1 and 2 above); and, if the work is an executable linked
-with the Library, with the complete machine-readable "work that uses the Library", as
-object code and/or source code, so that the user can modify the Library and then
-relink to produce a modified executable containing the modified Library. (It is
-understood that the user who changes the contents of definitions files in the Library
-will not necessarily be able to recompile the application to use the modified
-definitions.)
-
-b) Accompany the work with a written offer, valid for at least three years, to give
-the same user the materials specified in Subsection 6a, above, for a charge no more
-than the cost of performing this distribution.
-
-c) If distribution of the work is made by offering access to copy from a designated
-place, offer equivalent access to copy the above specified materials from the same
-place.
-
-d) Verify that the user has already received a copy of these materials or that you
-have already sent this user a copy.
-
-For an executable, the required form of the "work that uses the Library" must include
-any data and utility programs needed for reproducing the executable from it. However,
-as a special exception, the source code distributed need not include anything that is
-normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-
-
-It may happen that this requirement contradicts the license restrictions of other
-proprietary libraries that do not normally accompany the operating system. Such a
-contradiction means you cannot use both them and the Library together in an executable
-that you distribute.
-
-
-
-7. You may place library facilities that are a work based on the Library side-by-side
-in a single library together with other library facilities not covered by this
-License, and distribute such a combined library, provided that the separate
-distribution of the work based on the Library and of the other library facilities is
-otherwise permitted, and provided that you do these two things:
-
-
-
-a) Accompany the combined library with a copy of the same work based on the Library,
-uncombined with any other library facilities. This must be distributed under the terms
-of the Sections above.
-
-b) Give prominent notice with the combined library of the fact that part of it is a
-work based on the Library, and explaining where to find the accompanying uncombined
-form of the same work.
-
-8. You may not copy, modify, sublicense, link with, or distribute the Library except
-as expressly provided under this License. Any attempt otherwise to copy, modify,
-sublicense, link with, or distribute the Library is void, and will automatically
-terminate your rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses terminated so long
-as such parties remain in full compliance.
-
-
-
-9. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Library or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Library or works based on it.
-
-
-
-10. Each time you redistribute the Library (or any work based on the Library), the
-recipient automatically receives a license from the original licensor to copy,
-distribute, link with or modify the Library subject to these terms and conditions. You
-may not impose any further restrictions on the recipients' exercise of the rights
-granted herein. You are not responsible for enforcing compliance by third parties to
-this License.
-
-
-
-11. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Library at all. For example, if a patent license would not permit royalty-free
-redistribution of the Library by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply, and the section as a
-whole is intended to apply in other circumstances.
-
-
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-
-
-12. If the distribution and/or use of the Library is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Library under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-
-
-13. The Free Software Foundation may publish revised and/or new versions of the
-Library General Public License from time to time. Such new versions will be similar in
-spirit to the present version, but may differ in detail to address new problems or
-concerns.
-
-
-
-Each version is given a distinguishing version number. If the Library specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Library does not
-specify a license version number, you may choose any version ever published by the
-Free Software Foundation.
-
-
-
-14. If you wish to incorporate parts of the Library into other free programs whose
-distribution conditions are incompatible with these, write to the author to ask for
-permission. For software which is copyrighted by the Free Software Foundation, write
-to the Free Software Foundation; we sometimes make exceptions for this. Our decision
-will be guided by the two goals of preserving the free status of all derivatives of
-our free software and of promoting the sharing and reuse of software generally.
-
-
-
-NO WARRANTY
-
-
-
-15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-
-
-16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
-WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-
-
-END OF TERMS AND CONDITIONS
-
-
-
-How to Apply These Terms to Your New Libraries
-
-
-
-If you develop a new library, and you want it to be of the greatest possible use to
-the public, we recommend making it free software that everyone can redistribute and
-change. You can do so by permitting redistribution under these terms (or,
-alternatively, under the terms of the ordinary General Public License).
-
-
-
-To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
-where the full notice is found.
-
-
-
-one line to give the library's name and an idea of what it does.
-
-Copyright (C) year name of author
-
-
-
-This library is free software; you can redistribute it and/or
-
-modify it under the terms of the GNU Library General Public
-
-License as published by the Free Software Foundation; either
-
-version 2 of the License, or (at your option) any later version.
-
-
-
-This library is distributed in the hope that it will be useful,
-
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-
-Library General Public License for more details.
-
-
-
-You should have received a copy of the GNU Library General Public
-
-License along with this library; if not, write to the
-
-Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
-
-Boston, MA 02110-1301, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
-alter the names:
-
-
-
-Yoyodyne, Inc., hereby disclaims all copyright interest in
-
-the library `Frob' (a library for tweaking knobs) written
-
-by James Random Hacker.
-
-
-
-signature of Ty Coon, 1 April 1990
-
-Ty Coon, President of Vice
-
-That's all there is to it!
-
-
-
-
-LGPL-2.1
-
-
-GNU LESSER GENERAL PUBLIC LICENSE
-
-Version 2.1, February 1999
-
-Copyright (C) 1991, 1999 Free Software Foundation, Inc.
-51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL. It also counts
- as the successor of the GNU Library Public License, version 2, hence
- the version number 2.1.]
-Preamble
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public Licenses are intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users.
-
-This license, the Lesser General Public License, applies to some specially designated
-software packages--typically libraries--of the Free Software Foundation and other
-authors who decide to use it. You can use it too, but we suggest you first think
-carefully about whether this license or the ordinary General Public License is the
-better strategy to use in any particular case, based on the explanations below.
-
-When we speak of free software, we are referring to freedom of use, not price. Our
-General Public Licenses are designed to make sure that you have the freedom to
-distribute copies of free software (and charge for this service if you wish); that you
-receive source code or can get it if you want it; that you can change the software and
-use pieces of it in new free programs; and that you are informed that you can do these
-things.
-
-To protect your rights, we need to make restrictions that forbid distributors to deny
-you these rights or to ask you to surrender these rights. These restrictions translate
-to certain responsibilities for you if you distribute copies of the library or if you
-modify it.
-
-For example, if you distribute copies of the library, whether gratis or for a fee, you
-must give the recipients all the rights that we gave you. You must make sure that
-they, too, receive or can get the source code. If you link other code with the
-library, you must provide complete object files to the recipients, so that they can
-relink them with the library after making changes to the library and recompiling it.
-And you must show them these terms so they know their rights.
-
-We protect your rights with a two-step method: (1) we copyright the library, and (2)
-we offer you this license, which gives you legal permission to copy, distribute and/or
-modify the library.
-
-To protect each distributor, we want to make it very clear that there is no warranty
-for the free library. Also, if the library is modified by someone else and passed on,
-the recipients should know that what they have is not the original version, so that
-the original author`s reputation will not be affected by problems that might be
-introduced by others.
-
-Finally, software patents pose a constant threat to the existence of any free program.
-We wish to make sure that a company cannot effectively restrict the users of a free
-program by obtaining a restrictive license from a patent holder. Therefore, we insist
-that any patent license obtained for a version of the library must be consistent with
-the full freedom of use specified in this license.
-
-Most GNU software, including some libraries, is covered by the ordinary GNU General
-Public License. This license, the GNU Lesser General Public License, applies to
-certain designated libraries, and is quite different from the ordinary General Public
-License. We use this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
-When a program is linked with a library, whether statically or using a shared library,
-the combination of the two is legally speaking a combined work, a derivative of the
-original library. The ordinary General Public License therefore permits such linking
-only if the entire combination fits its criteria of freedom. The Lesser General Public
-License permits more lax criteria for linking other code with the library.
-
-We call this license the "Lesser" General Public License because it does Less to
-protect the user`s freedom than the ordinary General Public License. It also provides
-other free software developers Less of an advantage over competing non-free programs.
-These disadvantages are the reason we use the ordinary General Public License for many
-libraries. However, the Lesser license provides advantages in certain special
-circumstances.
-
-For example, on rare occasions, there may be a special need to encourage the widest
-possible use of a certain library, so that it becomes a de-facto standard. To achieve
-this, non-free programs must be allowed to use the library. A more frequent case is
-that a free library does the same job as widely used non-free libraries. In this case,
-there is little to gain by limiting the free library to free software only, so we use
-the Lesser General Public License.
-
-In other cases, permission to use a particular library in non-free programs enables a
-greater number of people to use a large body of free software. For example, permission
-to use the GNU C Library in non-free programs enables many more people to use the
-whole GNU operating system, as well as its variant, the GNU/Linux operating system.
-
-Although the Lesser General Public License is Less protective of the users` freedom,
-it does ensure that the user of a program that is linked with the Library has the
-freedom and the wherewithal to run that program using a modified version of the
-Library.
-
-The precise terms and conditions for copying, distribution and modification follow.
-Pay close attention to the difference between a "work based on the library" and a
-"work that uses the library". The former contains code derived from the library,
-whereas the latter must be combined with the library in order to run.
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-0. This License Agreement applies to any software library or other program which
-contains a notice placed by the copyright holder or other authorized party saying it
-may be distributed under the terms of this Lesser General Public License (also called
-"this License"). Each licensee is addressed as "you".
-
-A "library" means a collection of software functions and/or data prepared so as to be
-conveniently linked with application programs (which use some of those functions and
-data) to form executables.
-
-The "Library", below, refers to any such software library or work which has been
-distributed under these terms. A "work based on the Library" means either the Library
-or any derivative work under copyright law: that is to say, a work containing the
-Library or a portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is included without
-limitation in the term "modification".)
-
-"Source code" for a work means the preferred form of the work for making modifications
-to it. For a library, complete source code means all the source code for all modules
-it contains, plus any associated interface definition files, plus the scripts used to
-control compilation and installation of the library.
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running a program using the Library is
-not restricted, and output from such a program is covered only if its contents
-constitute a work based on the Library (independent of the use of the Library in a
-tool for writing it). Whether that is true depends on what the Library does and what
-the program that uses the Library does.
-
-1. You may copy and distribute verbatim copies of the Library`s complete source code
-as you receive it, in any medium, provided that you conspicuously and appropriately
-publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
-intact all the notices that refer to this License and to the absence of any warranty;
-and distribute a copy of this License along with the Library.
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-2. You may modify your copy or copies of the Library or any portion of it, thus
-forming a work based on the Library, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-a) The modified work must itself be a software library.
-b) You must cause the files modified to carry prominent notices stating that you
-changed the files and the date of any change.
-c) You must cause the whole of the work to be licensed at no charge to all third
-parties under the terms of this License.
-d) If a facility in the modified Library refers to a function or a table of data to be
-supplied by an application program that uses the facility, other than as an argument
-passed when the facility is invoked, then you must make a good faith effort to ensure
-that, in the event an application does not supply such function or table, the facility
-still operates, and performs whatever part of its purpose remains meaningful.
-(For example, a function in a library to compute square roots has a purpose that is
-entirely well-defined independent of the application. Therefore, Subsection 2d
-requires that any application-supplied function or table used by this function must be
-optional: if the application does not supply it, the square root function must still
-compute square roots.)
-
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Library, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Library,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library with the
-Library (or with a work based on the Library) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-3. You may opt to apply the terms of the ordinary GNU General Public License instead
-of this License to a given copy of the Library. To do this, you must alter all the
-notices that refer to this License, so that they refer to the ordinary GNU General
-Public License, version 2, instead of to this License. (If a newer version than
-version 2 of the ordinary GNU General Public License has appeared, then you can
-specify that version instead if you wish.) Do not make any other change in these
-notices.
-
-Once this change is made in a given copy, it is irreversible for that copy, so the
-ordinary GNU General Public License applies to all subsequent copies and derivative
-works made from that copy.
-
-This option is useful when you wish to copy part of the code of the Library into a
-program that is not a library.
-
-4. You may copy and distribute the Library (or a portion or derivative of it, under
-Section 2) in object code or executable form under the terms of Sections 1 and 2 above
-provided that you accompany it with the complete corresponding machine-readable source
-code, which must be distributed under the terms of Sections 1 and 2 above on a medium
-customarily used for software interchange.
-
-If distribution of object code is made by offering access to copy from a designated
-place, then offering equivalent access to copy the source code from the same place
-satisfies the requirement to distribute the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-5. A program that contains no derivative of any portion of the Library, but is
-designed to work with the Library by being compiled or linked with it, is called a
-"work that uses the Library". Such a work, in isolation, is not a derivative work of
-the Library, and therefore falls outside the scope of this License.
-
-However, linking a "work that uses the Library" with the Library creates an executable
-that is a derivative of the Library (because it contains portions of the Library),
-rather than a "work that uses the library". The executable is therefore covered by
-this License. Section 6 states terms for distribution of such executables.
-
-When a "work that uses the Library" uses material from a header file that is part of
-the Library, the object code for the work may be a derivative work of the Library even
-though the source code is not. Whether this is true is especially significant if the
-work can be linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
-If such an object file uses only numerical parameters, data structure layouts and
-accessors, and small macros and small inline functions (ten lines or less in length),
-then the use of the object file is unrestricted, regardless of whether it is legally a
-derivative work. (Executables containing this object code plus portions of the Library
-will still fall under Section 6.)
-
-Otherwise, if the work is a derivative of the Library, you may distribute the object
-code for the work under the terms of Section 6. Any executables containing that work
-also fall under Section 6, whether or not they are linked directly with the Library
-itself.
-
-6. As an exception to the Sections above, you may also combine or link a "work that
-uses the Library" with the Library to produce a work containing portions of the
-Library, and distribute that work under terms of your choice, provided that the terms
-permit modification of the work for the customer`s own use and reverse engineering for
-debugging such modifications.
-
-You must give prominent notice with each copy of the work that the Library is used in
-it and that the Library and its use are covered by this License. You must supply a
-copy of this License. If the work during execution displays copyright notices, you
-must include the copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one of these things:
-
-a) Accompany the work with the complete corresponding machine-readable source code for
-the Library including whatever changes were used in the work (which must be
-distributed under Sections 1 and 2 above); and, if the work is an executable linked
-with the Library, with the complete machine-readable "work that uses the Library", as
-object code and/or source code, so that the user can modify the Library and then
-relink to produce a modified executable containing the modified Library. (It is
-understood that the user who changes the contents of definitions files in the Library
-will not necessarily be able to recompile the application to use the modified
-definitions.)
-b) Use a suitable shared library mechanism for linking with the Library. A suitable
-mechanism is one that (1) uses at run time a copy of the library already present on
-the user`s computer system, rather than copying library functions into the executable,
-and (2) will operate properly with a modified version of the library, if the user
-installs one, as long as the modified version is interface-compatible with the version
-that the work was made with.
-c) Accompany the work with a written offer, valid for at least three years, to give
-the same user the materials specified in Subsection 6a, above, for a charge no more
-than the cost of performing this distribution.
-d) If distribution of the work is made by offering access to copy from a designated
-place, offer equivalent access to copy the above specified materials from the same
-place.
-e) Verify that the user has already received a copy of these materials or that you
-have already sent this user a copy.
-For an executable, the required form of the "work that uses the Library" must include
-any data and utility programs needed for reproducing the executable from it. However,
-as a special exception, the materials to be distributed need not include anything that
-is normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-It may happen that this requirement contradicts the license restrictions of other
-proprietary libraries that do not normally accompany the operating system. Such a
-contradiction means you cannot use both them and the Library together in an executable
-that you distribute.
-
-7. You may place library facilities that are a work based on the Library side-by-side
-in a single library together with other library facilities not covered by this
-License, and distribute such a combined library, provided that the separate
-distribution of the work based on the Library and of the other library facilities is
-otherwise permitted, and provided that you do these two things:
-
-a) Accompany the combined library with a copy of the same work based on the Library,
-uncombined with any other library facilities. This must be distributed under the terms
-of the Sections above.
-b) Give prominent notice with the combined library of the fact that part of it is a
-work based on the Library, and explaining where to find the accompanying uncombined
-form of the same work.
-8. You may not copy, modify, sublicense, link with, or distribute the Library except
-as expressly provided under this License. Any attempt otherwise to copy, modify,
-sublicense, link with, or distribute the Library is void, and will automatically
-terminate your rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses terminated so long
-as such parties remain in full compliance.
-
-9. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Library or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Library or works based on it.
-
-10. Each time you redistribute the Library (or any work based on the Library), the
-recipient automatically receives a license from the original licensor to copy,
-distribute, link with or modify the Library subject to these terms and conditions. You
-may not impose any further restrictions on the recipients` exercise of the rights
-granted herein. You are not responsible for enforcing compliance by third parties with
-this License.
-
-11. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Library at all. For example, if a patent license would not permit royalty-free
-redistribution of the Library by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply, and the section as a
-whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-12. If the distribution and/or use of the Library is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Library under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-13. The Free Software Foundation may publish revised and/or new versions of the Lesser
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Library does not
-specify a license version number, you may choose any version ever published by the
-Free Software Foundation.
-
-14. If you wish to incorporate parts of the Library into other free programs whose
-distribution conditions are incompatible with these, write to the author to ask for
-permission. For software which is copyrighted by the Free Software Foundation, write
-to the Free Software Foundation; we sometimes make exceptions for this. Our decision
-will be guided by the two goals of preserving the free status of all derivatives of
-our free software and of promoting the sharing and reuse of software generally.
-
-NO WARRANTY
-
-15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
-WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-END OF TERMS AND CONDITIONS
-
-How to Apply These Terms to Your New Libraries
-
-If you develop a new library, and you want it to be of the greatest possible use to
-the public, we recommend making it free software that everyone can redistribute and
-change. You can do so by permitting redistribution under these terms (or,
-alternatively, under the terms of the ordinary General Public License).
-
-To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
-where the full notice is found.
-
-one line to give the library`s name and an idea of what it does.
-Copyright (C) year name of author
-
-This library is free software; you can redistribute it and/or
-modify it under the terms of the GNU Lesser General Public
-License as published by the Free Software Foundation; either
-version 2.1 of the License, or (at your option) any later version.
-
-This library is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-Lesser General Public License for more details.
-
-You should have received a copy of the GNU Lesser General Public
-License along with this library; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
-Also add information on how to contact you by electronic and paper mail.
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
-alter the names:
-
-Yoyodyne, Inc., hereby disclaims all copyright interest in
-the library `Frob` (a library for tweaking knobs) written
-by James Random Hacker.
-
-signature of Ty Coon, 1 April 1990
-Ty Coon, President of Vice
-That`s all there is to it!
-
-
-
-
-LGPL-3.0
-
-GNU LESSER GENERAL PUBLIC LICENSE
-
-Version 3, 29 June 2007
-
-Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-
-This version of the GNU Lesser General Public License incorporates the terms and
-conditions of version 3 of the GNU General Public License, supplemented by the
-additional permissions listed below.
-0. Additional Definitions.
-
-As used herein, ”this License” refers to version 3 of the GNU Lesser
-General Public License, and the ”GNU GPL” refers to version 3 of the GNU
-General Public License.
-
-”The Library” refers to a covered work governed by this License, other
-than an Application or a Combined Work as defined below.
-
-An ”Application” is any work that makes use of an interface provided by
-the Library, but which is not otherwise based on the Library. Defining a subclass of a
-class defined by the Library is deemed a mode of using an interface provided by the
-Library.
-
-A ”Combined Work” is a work produced by combining or linking an
-Application with the Library. The particular version of the Library with which the
-Combined Work was made is also called the ”Linked Version”.
-
-The ”Minimal Corresponding Source” for a Combined Work means the
-Corresponding Source for the Combined Work, excluding any source code for portions of
-the Combined Work that, considered in isolation, are based on the Application, and not
-on the Linked Version.
-
-The ”Corresponding Application Code” for a Combined Work means the object
-code and/or source code for the Application, including any data and utility programs
-needed for reproducing the Combined Work from the Application, but excluding the
-System Libraries of the Combined Work.
-1. Exception to Section 3 of the GNU GPL.
-
-You may convey a covered work under sections 3 and 4 of this License without being
-bound by section 3 of the GNU GPL.
-2. Conveying Modified Versions.
-
-If you modify a copy of the Library, and, in your modifications, a facility refers to
-a function or data to be supplied by an Application that uses the facility (other than
-as an argument passed when the facility is invoked), then you may convey a copy of the
-modified version:
-
- * a) under this License, provided that you make a good faith effort to ensure
-that, in the event an Application does not supply the function or data, the facility
-still operates, and performs whatever part of its purpose remains meaningful, or
- * b) under the GNU GPL, with none of the additional permissions of this License
-applicable to that copy.
-
-3. Object Code Incorporating Material from Library Header Files.
-
-The object code form of an Application may incorporate material from a header file
-that is part of the Library. You may convey such object code under terms of your
-choice, provided that, if the incorporated material is not limited to numerical
-parameters, data structure layouts and accessors, or small macros, inline functions
-and templates (ten or fewer lines in length), you do both of the following:
-
- * a) Give prominent notice with each copy of the object code that the Library is
-used in it and that the Library and its use are covered by this License.
- * b) Accompany the object code with a copy of the GNU GPL and this license
-document.
-
-4. Combined Works.
-
-You may convey a Combined Work under terms of your choice that, taken together,
-effectively do not restrict modification of the portions of the Library contained in
-the Combined Work and reverse engineering for debugging such modifications, if you
-also do each of the following:
-
- * a) Give prominent notice with each copy of the Combined Work that the Library is
-used in it and that the Library and its use are covered by this License.
- * b) Accompany the Combined Work with a copy of the GNU GPL and this license
-document.
- * c) For a Combined Work that displays copyright notices during execution, include
-the copyright notice for the Library among these notices, as well as a reference
-directing the user to the copies of the GNU GPL and this license document.
- * d) Do one of the following:
- o 0) Convey the Minimal Corresponding Source under the terms of this
-License, and the Corresponding Application Code in a form suitable for, and under
-terms that permit, the user to recombine or relink the Application with a modified
-version of the Linked Version to produce a modified Combined Work, in the manner
-specified by section 6 of the GNU GPL for conveying Corresponding Source.
- o 1) Use a suitable shared library mechanism for linking with the Library. A
-suitable mechanism is one that (a) uses at run time a copy of the Library already
-present on the user's computer system, and (b) will operate properly with a modified
-version of the Library that is interface-compatible with the Linked Version.
- * e) Provide Installation Information, but only if you would otherwise be required
-to provide such information under section 6 of the GNU GPL, and only to the extent
-that such information is necessary to install and execute a modified version of the
-Combined Work produced by recombining or relinking the Application with a modified
-version of the Linked Version. (If you use option 4d0, the Installation Information
-must accompany the Minimal Corresponding Source and Corresponding Application Code. If
-you use option 4d1, you must provide the Installation Information in the manner
-specified by section 6 of the GNU GPL for conveying Corresponding Source.)
-
-5. Combined Libraries.
-
-You may place library facilities that are a work based on the Library side by side in
-a single library together with other library facilities that are not Applications and
-are not covered by this License, and convey such a combined library under terms of
-your choice, if you do both of the following:
-
- * a) Accompany the combined library with a copy of the same work based on the
-Library, uncombined with any other library facilities, conveyed under the terms of
-this License.
- * b) Give prominent notice with the combined library that part of it is a work
-based on the Library, and explaining where to find the accompanying uncombined form of
-the same work.
-
-6. Revised Versions of the GNU Lesser General Public License.
-
-The Free Software Foundation may publish revised and/or new versions of the GNU Lesser
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library as you received
-it specifies that a certain numbered version of the GNU Lesser General Public License
-”or any later version” applies to it, you have the option of following
-the terms and conditions either of that published version or of any later version
-published by the Free Software Foundation. If the Library as you received it does not
-specify a version number of the GNU Lesser General Public License, you may choose any
-version of the GNU Lesser General Public License ever published by the Free Software
-Foundation.
-
-If the Library as you received it specifies that a proxy can decide whether future
-versions of the GNU Lesser General Public License shall apply, that proxy's public
-statement of acceptance of any version is permanent authorization for you to choose
-that version for the Library.
-
-
-
-Libpng
-
-
-This copy of the libpng notices is provided for your convenience. In case of
-any discrepancy between this copy and the notices in the file png.h that is
-included in the libpng distribution, the latter shall prevail.
-
-COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
-
-If you modify libpng you may insert additional notices immediately following
-this sentence.
-
-This code is released under the libpng license.
-
-libpng versions 1.2.6, August 15, 2004, through 1.4.5, December 9, 2010, are
-Copyright (c) 2004, 2006-2010 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-1.2.5
-with the following individual added to the list of Contributing Authors
-
- Cosmin Truta
-
-libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are
-Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-1.0.6
-with the following individuals added to the list of Contributing Authors
-
- Simon-Pierre Cadieux
- Eric S. Raymond
- Gilles Vollant
-
-and with the following additions to the disclaimer:
-
- There is no warranty against interference with your enjoyment of the
- library or against infringement. There is no warranty that our
- efforts or the library will fulfill any of your particular purposes
- or needs. This library is provided with all faults, and the entire
- risk of satisfactory quality, performance, accuracy, and effort is with
- the user.
-
-libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
-Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-0.96,
-with the following individuals added to the list of Contributing Authors:
-
- Tom Lane
- Glenn Randers-Pehrson
- Willem van Schaik
-
-libpng versions 0.89, June 1996, through 0.96, May 1997, are
-Copyright (c) 1996, 1997 Andreas Dilger
-Distributed according to the same disclaimer and license as libpng-0.88,
-with the following individuals added to the list of Contributing Authors:
-
- John Bowler
- Kevin Bracey
- Sam Bushell
- Magnus Holmgren
- Greg Roelofs
- Tom Tanner
-
-libpng versions 0.5, May 1995, through 0.88, January 1996, are
-Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.
-
-For the purposes of this copyright and license, "Contributing Authors"
-is defined as the following set of individuals:
-
- Andreas Dilger
- Dave Martindale
- Guy Eric Schalnat
- Paul Schmidt
- Tim Wegner
-
-The PNG Reference Library is supplied "AS IS". The Contributing Authors
-and Group 42, Inc. disclaim all warranties, expressed or implied,
-including, without limitation, the warranties of merchantability and of
-fitness for any purpose. The Contributing Authors and Group 42, Inc.
-assume no liability for direct, indirect, incidental, special, exemplary,
-or consequential damages, which may result from the use of the PNG
-Reference Library, even if advised of the possibility of such damage.
-
-Permission is hereby granted to use, copy, modify, and distribute this
-source code, or portions hereof, for any purpose, without fee, subject
-to the following restrictions:
-
-1. The origin of this source code must not be misrepresented.
-
-2. Altered versions must be plainly marked as such and must not
- be misrepresented as being the original source.
-
-3. This Copyright notice may not be removed or altered from any
- source or altered source distribution.
-
-The Contributing Authors and Group 42, Inc. specifically permit, without
-fee, and encourage the use of this source code as a component to
-supporting the PNG file format in commercial products. If you use this
-source code in a product, acknowledgment is not required but would be
-appreciated.
-
-
-A "png_get_copyright" function is available, for convenient use in "about"
-boxes and the like:
-
- printf("%s",png_get_copyright(NULL));
-
-Also, the PNG logo (in PNG format, of course) is supplied in the
-files "pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).
-
-Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a
-certification mark of the Open Source Initiative.
-
-Glenn Randers-Pehrson
-glennrp at users.sourceforge.net
-December 9, 2010
-
-
-
-
-MIT
-
-
-MIT License
-
-Copyright (c) <year> <copyright holders>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-
-
-MPL-2.0
-
-Mozilla Public License Version 2.0
-==================================
-
-1. Definitions
---------------
-
-1.1. "Contributor"
- means each individual or legal entity that creates, contributes to
- the creation of, or owns Covered Software.
-
-1.2. "Contributor Version"
- means the combination of the Contributions of others (if any) used
- by a Contributor and that particular Contributor's Contribution.
-
-1.3. "Contribution"
- means Covered Software of a particular Contributor.
-
-1.4. "Covered Software"
- means Source Code Form to which the initial Contributor has attached
- the notice in Exhibit A, the Executable Form of such Source Code
- Form, and Modifications of such Source Code Form, in each case
- including portions thereof.
-
-1.5. "Incompatible With Secondary Licenses"
- means
-
- (a) that the initial Contributor has attached the notice described
- in Exhibit B to the Covered Software; or
-
- (b) that the Covered Software was made available under the terms of
- version 1.1 or earlier of the License, but not also under the
- terms of a Secondary License.
-
-1.6. "Executable Form"
- means any form of the work other than Source Code Form.
-
-1.7. "Larger Work"
- means a work that combines Covered Software with other material, in
- a separate file or files, that is not Covered Software.
-
-1.8. "License"
- means this document.
-
-1.9. "Licensable"
- means having the right to grant, to the maximum extent possible,
- whether at the time of the initial grant or subsequently, any and
- all of the rights conveyed by this License.
-
-1.10. "Modifications"
- means any of the following:
-
- (a) any file in Source Code Form that results from an addition to,
- deletion from, or modification of the contents of Covered
- Software; or
-
- (b) any new file in Source Code Form that contains any Covered
- Software.
-
-1.11. "Patent Claims" of a Contributor
- means any patent claim(s), including without limitation, method,
- process, and apparatus claims, in any patent Licensable by such
- Contributor that would be infringed, but for the grant of the
- License, by the making, using, selling, offering for sale, having
- made, import, or transfer of either its Contributions or its
- Contributor Version.
-
-1.12. "Secondary License"
- means either the GNU General Public License, Version 2.0, the GNU
- Lesser General Public License, Version 2.1, the GNU Affero General
- Public License, Version 3.0, or any later versions of those
- licenses.
-
-1.13. "Source Code Form"
- means the form of the work preferred for making modifications.
-
-1.14. "You" (or "Your")
- means an individual or a legal entity exercising rights under this
- License. For legal entities, "You" includes any entity that
- controls, is controlled by, or is under common control with You. For
- purposes of this definition, "control" means (a) the power, direct
- or indirect, to cause the direction or management of such entity,
- whether by contract or otherwise, or (b) ownership of more than
- fifty percent (50%) of the outstanding shares or beneficial
- ownership of such entity.
-
-2. License Grants and Conditions
---------------------------------
-
-2.1. Grants
-
-Each Contributor hereby grants You a world-wide, royalty-free,
-non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark)
- Licensable by such Contributor to use, reproduce, make available,
- modify, display, perform, distribute, and otherwise exploit its
- Contributions, either on an unmodified basis, with Modifications, or
- as part of a Larger Work; and
-
-(b) under Patent Claims of such Contributor to make, use, sell, offer
- for sale, have made, import, and otherwise transfer either its
- Contributions or its Contributor Version.
-
-2.2. Effective Date
-
-The licenses granted in Section 2.1 with respect to any Contribution
-become effective for each Contribution on the date the Contributor first
-distributes such Contribution.
-
-2.3. Limitations on Grant Scope
-
-The licenses granted in this Section 2 are the only rights granted under
-this License. No additional rights or licenses will be implied from the
-distribution or licensing of Covered Software under this License.
-Notwithstanding Section 2.1(b) above, no patent license is granted by a
-Contributor:
-
-(a) for any code that a Contributor has removed from Covered Software;
- or
-
-(b) for infringements caused by: (i) Your and any other third party's
- modifications of Covered Software, or (ii) the combination of its
- Contributions with other software (except as part of its Contributor
- Version); or
-
-(c) under Patent Claims infringed by Covered Software in the absence of
- its Contributions.
-
-This License does not grant any rights in the trademarks, service marks,
-or logos of any Contributor (except as may be necessary to comply with
-the notice requirements in Section 3.4).
-
-2.4. Subsequent Licenses
-
-No Contributor makes additional grants as a result of Your choice to
-distribute the Covered Software under a subsequent version of this
-License (see Section 10.2) or under the terms of a Secondary License (if
-permitted under the terms of Section 3.3).
-
-2.5. Representation
-
-Each Contributor represents that the Contributor believes its
-Contributions are its original creation(s) or it has sufficient rights
-to grant the rights to its Contributions conveyed by this License.
-
-2.6. Fair Use
-
-This License is not intended to limit any rights You have under
-applicable copyright doctrines of fair use, fair dealing, or other
-equivalents.
-
-2.7. Conditions
-
-Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
-in Section 2.1.
-
-3. Responsibilities
--------------------
-
-3.1. Distribution of Source Form
-
-All distribution of Covered Software in Source Code Form, including any
-Modifications that You create or to which You contribute, must be under
-the terms of this License. You must inform recipients that the Source
-Code Form of the Covered Software is governed by the terms of this
-License, and how they can obtain a copy of this License. You may not
-attempt to alter or restrict the recipients' rights in the Source Code
-Form.
-
-3.2. Distribution of Executable Form
-
-If You distribute Covered Software in Executable Form then:
-
-(a) such Covered Software must also be made available in Source Code
- Form, as described in Section 3.1, and You must inform recipients of
- the Executable Form how they can obtain a copy of such Source Code
- Form by reasonable means in a timely manner, at a charge no more
- than the cost of distribution to the recipient; and
-
-(b) You may distribute such Executable Form under the terms of this
- License, or sublicense it under different terms, provided that the
- license for the Executable Form does not attempt to limit or alter
- the recipients' rights in the Source Code Form under this License.
-
-3.3. Distribution of a Larger Work
-
-You may create and distribute a Larger Work under terms of Your choice,
-provided that You also comply with the requirements of this License for
-the Covered Software. If the Larger Work is a combination of Covered
-Software with a work governed by one or more Secondary Licenses, and the
-Covered Software is not Incompatible With Secondary Licenses, this
-License permits You to additionally distribute such Covered Software
-under the terms of such Secondary License(s), so that the recipient of
-the Larger Work may, at their option, further distribute the Covered
-Software under the terms of either this License or such Secondary
-License(s).
-
-3.4. Notices
-
-You may not remove or alter the substance of any license notices
-(including copyright notices, patent notices, disclaimers of warranty,
-or limitations of liability) contained within the Source Code Form of
-the Covered Software, except that You may alter any license notices to
-the extent required to remedy known factual inaccuracies.
-
-3.5. Application of Additional Terms
-
-You may choose to offer, and to charge a fee for, warranty, support,
-indemnity or liability obligations to one or more recipients of Covered
-Software. However, You may do so only on Your own behalf, and not on
-behalf of any Contributor. You must make it absolutely clear that any
-such warranty, support, indemnity, or liability obligation is offered by
-You alone, and You hereby agree to indemnify every Contributor for any
-liability incurred by such Contributor as a result of warranty, support,
-indemnity or liability terms You offer. You may include additional
-disclaimers of warranty and limitations of liability specific to any
-jurisdiction.
-
-4. Inability to Comply Due to Statute or Regulation
----------------------------------------------------
-
-If it is impossible for You to comply with any of the terms of this
-License with respect to some or all of the Covered Software due to
-statute, judicial order, or regulation then You must: (a) comply with
-the terms of this License to the maximum extent possible; and (b)
-describe the limitations and the code they affect. Such description must
-be placed in a text file included with all distributions of the Covered
-Software under this License. Except to the extent prohibited by statute
-or regulation, such description must be sufficiently detailed for a
-recipient of ordinary skill to be able to understand it.
-
-5. Termination
---------------
-
-5.1. The rights granted under this License will terminate automatically
-if You fail to comply with any of its terms. However, if You become
-compliant, then the rights granted under this License from a particular
-Contributor are reinstated (a) provisionally, unless and until such
-Contributor explicitly and finally terminates Your grants, and (b) on an
-ongoing basis, if such Contributor fails to notify You of the
-non-compliance by some reasonable means prior to 60 days after You have
-come back into compliance. Moreover, Your grants from a particular
-Contributor are reinstated on an ongoing basis if such Contributor
-notifies You of the non-compliance by some reasonable means, this is the
-first time You have received notice of non-compliance with this License
-from such Contributor, and You become compliant prior to 30 days after
-Your receipt of the notice.
-
-5.2. If You initiate litigation against any entity by asserting a patent
-infringement claim (excluding declaratory judgment actions,
-counter-claims, and cross-claims) alleging that a Contributor Version
-directly or indirectly infringes any patent, then the rights granted to
-You by any and all Contributors for the Covered Software under Section
-2.1 of this License shall terminate.
-
-5.3. In the event of termination under Sections 5.1 or 5.2 above, all
-end user license agreements (excluding distributors and resellers) which
-have been validly granted by You or Your distributors under this License
-prior to termination shall survive termination.
-
-************************************************************************
-* *
-* 6. Disclaimer of Warranty *
-* ------------------------- *
-* *
-* Covered Software is provided under this License on an "as is" *
-* basis, without warranty of any kind, either expressed, implied, or *
-* statutory, including, without limitation, warranties that the *
-* Covered Software is free of defects, merchantable, fit for a *
-* particular purpose or non-infringing. The entire risk as to the *
-* quality and performance of the Covered Software is with You. *
-* Should any Covered Software prove defective in any respect, You *
-* (not any Contributor) assume the cost of any necessary servicing, *
-* repair, or correction. This disclaimer of warranty constitutes an *
-* essential part of this License. No use of any Covered Software is *
-* authorized under this License except under this disclaimer. *
-* *
-************************************************************************
-
-************************************************************************
-* *
-* 7. Limitation of Liability *
-* -------------------------- *
-* *
-* Under no circumstances and under no legal theory, whether tort *
-* (including negligence), contract, or otherwise, shall any *
-* Contributor, or anyone who distributes Covered Software as *
-* permitted above, be liable to You for any direct, indirect, *
-* special, incidental, or consequential damages of any character *
-* including, without limitation, damages for lost profits, loss of *
-* goodwill, work stoppage, computer failure or malfunction, or any *
-* and all other commercial damages or losses, even if such party *
-* shall have been informed of the possibility of such damages. This *
-* limitation of liability shall not apply to liability for death or *
-* personal injury resulting from such party's negligence to the *
-* extent applicable law prohibits such limitation. Some *
-* jurisdictions do not allow the exclusion or limitation of *
-* incidental or consequential damages, so this exclusion and *
-* limitation may not apply to You. *
-* *
-************************************************************************
-
-8. Litigation
--------------
-
-Any litigation relating to this License may be brought only in the
-courts of a jurisdiction where the defendant maintains its principal
-place of business and such litigation shall be governed by laws of that
-jurisdiction, without reference to its conflict-of-law provisions.
-Nothing in this Section shall prevent a party's ability to bring
-cross-claims or counter-claims.
-
-9. Miscellaneous
-----------------
-
-This License represents the complete agreement concerning the subject
-matter hereof. If any provision of this License is held to be
-unenforceable, such provision shall be reformed only to the extent
-necessary to make it enforceable. Any law or regulation which provides
-that the language of a contract shall be construed against the drafter
-shall not be used to construe this License against a Contributor.
-
-10. Versions of the License
----------------------------
-
-10.1. New Versions
-
-Mozilla Foundation is the license steward. Except as provided in Section
-10.3, no one other than the license steward has the right to modify or
-publish new versions of this License. Each version will be given a
-distinguishing version number.
-
-10.2. Effect of New Versions
-
-You may distribute the Covered Software under the terms of the version
-of the License under which You originally received the Covered Software,
-or under the terms of any subsequent version published by the license
-steward.
-
-10.3. Modified Versions
-
-If you create software not governed by this License, and you want to
-create a new license for such software, you may create and use a
-modified version of this License if you rename the license and remove
-any references to the name of the license steward (except to note that
-such modified license differs from this License).
-
-10.4. Distributing Source Code Form that is Incompatible With Secondary
-Licenses
-
-If You choose to distribute Source Code Form that is Incompatible With
-Secondary Licenses under the terms of this version of the License, the
-notice described in Exhibit B of this License must be attached.
-
-Exhibit A - Source Code Form License Notice
--------------------------------------------
-
- This Source Code Form is subject to the terms of the Mozilla Public
- License, v. 2.0. If a copy of the MPL was not distributed with this
- file, You can obtain one at http://mozilla.org/MPL/2.0/.
-
-If it is not possible or desirable to put the notice in a particular
-file, then You may include the notice in a location (such as a LICENSE
-file in a relevant directory) where a recipient would be likely to look
-for such a notice.
-
-You may add additional accurate notices of copyright ownership.
-
-Exhibit B - "Incompatible With Secondary Licenses" Notice
----------------------------------------------------------
-
- This Source Code Form is "Incompatible With Secondary Licenses", as
- defined by the Mozilla Public License, v. 2.0.
-
-
-
-OpenSSL
-
-
-OpenSSL License
-
- ====================================================================
- Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the
- distribution.
-
- 3. All advertising materials mentioning features or use of this
- software must display the following acknowledgment:
- "This product includes software developed by the OpenSSL Project
- for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
-
- 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
- endorse or promote products derived from this software without
- prior written permission. For written permission, please contact
- openssl-core@openssl.org.
-
- 5. Products derived from this software may not be called "OpenSSL"
- nor may "OpenSSL" appear in their names without prior written
- permission of the OpenSSL Project.
-
- 6. Redistributions of any form whatsoever must retain the following
- acknowledgment:
- "This product includes software developed by the OpenSSL Project
- for use in the OpenSSL Toolkit (http://www.openssl.org/)"
-
- THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS`` AND ANY
- EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
- PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
- ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
- NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
- LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
- STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
- OF THE POSSIBILITY OF SUCH DAMAGE.
- ====================================================================
-
- This product includes cryptographic software written by Eric Young
- (eay@cryptsoft.com). This product includes software written by Tim
- Hudson (tjh@cryptsoft.com).
-
-
- Original SSLeay License
- -----------------------
-
-Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
-All rights reserved.
-
- This package is an SSL implementation written
- by Eric Young (eay@cryptsoft.com).
- The implementation was written so as to conform with Netscapes SSL.
-
- This library is free for commercial and non-commercial use as long as
- the following conditions are aheared to. The following conditions
- apply to all code found in this distribution, be it the RC4, RSA,
- lhash, DES, etc., code; not just the SSL code. The SSL documentation
- included with this distribution is covered by the same copyright terms
- except that the holder is Tim Hudson (tjh@cryptsoft.com).
-
- Copyright remains Eric Young`s, and as such any Copyright notices in
- the code are not to be removed.
- If this package is used in a product, Eric Young should be given attribution
- as the author of the parts of the library used.
- This can be in the form of a textual message at program startup or
- in documentation (online or textual) provided with the package.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
- 1. Redistributions of source code must retain the copyright
- notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
- 3. All advertising materials mentioning features or use of this software
- must display the following acknowledgement:
- "This product includes cryptographic software written by
- Eric Young (eay@cryptsoft.com)"
- The word `cryptographic` can be left out if the rouines from the library
- being used are not cryptographic related :-).
- 4. If you include any Windows specific code (or a derivative thereof) from
- the apps directory (application code) you must include an acknowledgement:
- "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
-
- THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS`` AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
-CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- The licence and distribution terms for any publically available version or
-derivative of this code cannot be changed. i.e. this code cannot simply be copied and
-put under another distribution licence
- [including the GNU Public Licence.]
-
-
-
-
-
-
-
-PD
-
-This is a placeholder for the Public Domain License
-
-
-
-Python-2.0
-
-
-PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
---------------------------------------------
-
-1. This LICENSE AGREEMENT is between the Python Software Foundation
-("PSF"), and the Individual or Organization ("Licensee") accessing and
-otherwise using this software ("Python") in source or binary form and
-its associated documentation.
-
-2. Subject to the terms and conditions of this License Agreement, PSF
-hereby grants Licensee a nonexclusive, royalty-free, world-wide
-license to reproduce, analyze, test, perform and/or display publicly,
-prepare derivative works, distribute, and otherwise use Python
-alone or in any derivative version, provided, however, that PSF`s
-License Agreement and PSF`s notice of copyright, i.e., "Copyright (c)
-2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights
-Reserved" are retained in Python alone or in any derivative version
-prepared by Licensee.
-
-3. In the event Licensee prepares a derivative work that is based on
-or incorporates Python or any part thereof, and wants to make
-the derivative work available to others as provided herein, then
-Licensee hereby agrees to include in any such work a brief summary of
-the changes made to Python.
-
-4. PSF is making Python available to Licensee on an "AS IS"
-basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
-FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
-A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
-OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-6. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-7. Nothing in this License Agreement shall be deemed to create any
-relationship of agency, partnership, or joint venture between PSF and
-Licensee. This License Agreement does not grant permission to use PSF
-trademarks or trade name in a trademark sense to endorse or promote
-products or services of Licensee, or any third party.
-
-8. By copying, installing or otherwise using Python, Licensee
-agrees to be bound by the terms and conditions of this License
-Agreement.
-
-BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
--------------------------------------------
-
-BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
-
-1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
-office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
-Individual or Organization ("Licensee") accessing and otherwise using
-this software in source or binary form and its associated
-documentation ("the Software").
-
-2. Subject to the terms and conditions of this BeOpen Python License
-Agreement, BeOpen hereby grants Licensee a non-exclusive,
-royalty-free, world-wide license to reproduce, analyze, test, perform
-and/or display publicly, prepare derivative works, distribute, and
-otherwise use the Software alone or in any derivative version,
-provided, however, that the BeOpen Python License is retained in the
-Software, alone or in any derivative version prepared by Licensee.
-
-3. BeOpen is making the Software available to Licensee on an "AS IS"
-basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
-SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
-AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
-DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-5. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-6. This License Agreement shall be governed by and interpreted in all
-respects by the law of the State of California, excluding conflict of
-law provisions. Nothing in this License Agreement shall be deemed to
-create any relationship of agency, partnership, or joint venture
-between BeOpen and Licensee. This License Agreement does not grant
-permission to use BeOpen trademarks or trade names in a trademark
-sense to endorse or promote products or services of Licensee, or any
-third party. As an exception, the "BeOpen Python" logos available at
-http://www.pythonlabs.com/logos.html may be used according to the
-permissions granted on that web page.
-
-7. By copying, installing or otherwise using the software, Licensee
-agrees to be bound by the terms and conditions of this License
-Agreement.
-
-CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
----------------------------------------
-
-1. This LICENSE AGREEMENT is between the Corporation for National
-Research Initiatives, having an office at 1895 Preston White Drive,
-Reston, VA 20191 ("CNRI"), and the Individual or Organization
-("Licensee") accessing and otherwise using Python 1.6.1 software in
-source or binary form and its associated documentation.
-
-2. Subject to the terms and conditions of this License Agreement, CNRI
-hereby grants Licensee a nonexclusive, royalty-free, world-wide
-license to reproduce, analyze, test, perform and/or display publicly,
-prepare derivative works, distribute, and otherwise use Python 1.6.1
-alone or in any derivative version, provided, however, that CNRI`s
-License Agreement and CNRI`s notice of copyright, i.e., "Copyright (c)
-1995-2001 Corporation for National Research Initiatives; All Rights
-Reserved" are retained in Python 1.6.1 alone or in any derivative
-version prepared by Licensee. Alternately, in lieu of CNRI`s License
-Agreement, Licensee may substitute the following text (omitting the
-quotes): "Python 1.6.1 is made available subject to the terms and
-conditions in CNRI`s License Agreement. This Agreement together with
-Python 1.6.1 may be located on the Internet using the following
-unique, persistent identifier (known as a handle): 1895.22/1013. This
-Agreement may also be obtained from a proxy server on the Internet
-using the following URL: http://hdl.handle.net/1895.22/1013".
-
-3. In the event Licensee prepares a derivative work that is based on
-or incorporates Python 1.6.1 or any part thereof, and wants to make
-the derivative work available to others as provided herein, then
-Licensee hereby agrees to include in any such work a brief summary of
-the changes made to Python 1.6.1.
-
-4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
-basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
-1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
-A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
-OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-6. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-7. This License Agreement shall be governed by the federal
-intellectual property law of the United States, including without
-limitation the federal copyright law, and, to the extent such
-U.S. federal law does not apply, by the law of the Commonwealth of
-Virginia, excluding Virginia`s conflict of law provisions.
-Notwithstanding the foregoing, with regard to derivative works based
-on Python 1.6.1 that incorporate non-separable material that was
-previously distributed under the GNU General Public License (GPL), the
-law of the Commonwealth of Virginia shall govern this License
-Agreement only as to issues arising under or with respect to
-Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
-License Agreement shall be deemed to create any relationship of
-agency, partnership, or joint venture between CNRI and Licensee. This
-License Agreement does not grant permission to use CNRI trademarks or
-trade name in a trademark sense to endorse or promote products or
-services of Licensee, or any third party.
-
-8. By clicking on the "ACCEPT" button where indicated, or by copying,
-installing or otherwise using Python 1.6.1, Licensee agrees to be
-bound by the terms and conditions of this License Agreement.
-
-ACCEPT
-
-CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
---------------------------------------------------
-
-Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
-The Netherlands. All rights reserved.
-
-Permission to use, copy, modify, and distribute this software and its
-documentation for any purpose and without fee is hereby granted,
-provided that the above copyright notice appear in all copies and that
-both that copyright notice and this permission notice appear in
-supporting documentation, and that the name of Stichting Mathematisch
-Centrum or CWI not be used in advertising or publicity pertaining to
-distribution of the software without specific, written prior
-permission.
-
-STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
-THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
-FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
-FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
-WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
-ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
-OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
-
-
-
-SAX-PD
-
-
-Copyright Status for SAX
-
-SAX is free!
-
-In fact, it`s not possible to own a license to SAX, since it`s been placed in the
-public domain.
-
-No Warranty
-
-Because SAX is released to the public domain, there is no warranty for the design or
-for the software implementation, to the extent permitted by applicable law. Except
-when otherwise stated in writing the copyright holders and/or other parties provide
-SAX "as is" without warranty of any kind, either expressed or implied, including, but
-not limited to, the implied warranties of merchantability and fitness for a particular
-purpose. The entire risk as to the quality and performance of SAX is with you. Should
-SAX prove defective, you assume the cost of all necessary servicing, repair or
-correction.
-
-In no event unless required by applicable law or agreed to in writing will any
-copyright holder, or any other party who may modify and/or redistribute SAX, be liable
-to you for damages, including any general, special, incidental or consequential
-damages arising out of the use or inability to use SAX (including but not limited to
-loss of data or data being rendered inaccurate or losses sustained by you or third
-parties or a failure of the SAX to operate with any other programs), even if such
-holder or other party has been advised of the possibility of such damages.
-
-Copyright Disclaimers
-
-This page includes statements to that effect by David Megginson, who would have been
-able to claim copyright for the original work.
-
-SAX 1.0
-
-Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of
-the XML-DEV mailing list, is hereby released into the public domain.
-
-No one owns SAX: you may use it freely in both commercial and non-commercial
-applications, bundle it with your software distribution, include it on a CD-ROM, list
-the source code in a book, mirror the documentation at your own web site, or use it in
-any other way you see fit.
-
-David Megginson, Megginson Technologies Ltd.
-1998-05-11
-
-SAX 2.0
-
-I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release
-all of the SAX 2.0 source code, compiled code, and documentation contained in this
-distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of
-fitness for any purpose.
-
-David Megginson, Megginson Technologies Ltd.
-2000-05-05
-
-
-
-
-SMAIL_GPL
-
-This is the Debian GNU/Linux package debianutils.
-
-It is an original Debian package. Programs in it were maintained by
-Guy Maor <maor@debian.org>, and are now maintained by Clint Adams
-<schizo@debian.org>.
-
-All its programs except readlink, savelog, and which may be
-redistributed under the terms of the GNU GPL, Version 2 or later,
-found on Debian systems in the file /usr/share/common-licenses/GPL.
-
-which is in the public domain.
-
-readlink is Copyright (c) 1997 Kenneth Stailey, and may also be
-distributed under the terms of the BSD copyright.
-
-savelog may be redistributed under the following terms: (The rest of
-this file consists of savelog's distribution terms.)
-
-#ident "@(#)smail:RELEASE-3_2:COPYING,v 1.2 1996/06/14 18:59:10 woods Exp"
-
- SMAIL GENERAL PUBLIC LICENSE
- (Clarified 11 Feb 1988)
-
- Copyright (C) 1988 Landon Curt Noll & Ronald S. Karr
- Copyright (C) 1992 Ronald S. Karr
- Copyleft (GNU) 1988 Landon Curt Noll & Ronald S. Karr
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license, but changing it is not allowed. You can also
- use this wording to make the terms for other programs.
-
- The license agreements of most software companies keep you at the
-mercy of those companies. By contrast, our general public license is
-intended to give everyone the right to share SMAIL. To make sure that
-you get the rights we want you to have, we need to make restrictions
-that forbid anyone to deny you these rights or to ask you to surrender
-the rights. Hence this license agreement.
-
- Specifically, we want to make sure that you have the right to give
-away copies of SMAIL, that you receive source code or else can get it
-if you want it, that you can change SMAIL or use pieces of it in new
-free programs, and that you know you can do these things.
-
- To make sure that everyone has such rights, we have to forbid you to
-deprive anyone else of these rights. For example, if you distribute
-copies of SMAIL, you must give the recipients all the rights that you
-have. You must make sure that they, too, receive or can get the
-source code. And you must tell them their rights.
-
- Also, for our own protection, we must make certain that everyone
-finds out that there is no warranty for SMAIL. If SMAIL is modified by
-someone else and passed on, we want its recipients to know that what
-they have is not what we distributed, so that any problems introduced
-by others will not reflect on our reputation.
-
- Therefore we (Landon Curt Noll and Ronald S. Karr) make the following
-terms which say what you must do to be allowed to distribute or change
-SMAIL.
-
-
- COPYING POLICIES
-
- 1. You may copy and distribute verbatim copies of SMAIL source code
-as you receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy a valid copyright notice "Copyright
-(C) 1988 Landon Curt Noll & Ronald S. Karr" (or with whatever year is
-appropriate); keep intact the notices on all files that refer to this
-License Agreement and to the absence of any warranty; and give any
-other recipients of the SMAIL program a copy of this License
-Agreement along with the program. You may charge a distribution fee
-for the physical act of transferring a copy.
-
- 2. You may modify your copy or copies of SMAIL or any portion of it,
-and copy and distribute such modifications under the terms of
-Paragraph 1 above, provided that you also do the following:
-
- a) cause the modified files to carry prominent notices stating
- that you changed the files and the date of any change; and
-
- b) cause the whole of any work that you distribute or publish,
- that in whole or in part contains or is a derivative of SMAIL or
- any part thereof, to be licensed at no charge to all third
- parties on terms identical to those contained in this License
- Agreement (except that you may choose to grant more extensive
- warranty protection to some or all third parties, at your option).
-
- c) You may charge a distribution fee for the physical act of
- transferring a copy, and you may at your option offer warranty
- protection in exchange for a fee.
-
-Mere aggregation of another unrelated program with this program (or its
-derivative) on a volume of a storage or distribution medium does not bring
-the other program under the scope of these terms.
-
- 3. You may copy and distribute SMAIL (or a portion or derivative of it,
-under Paragraph 2) in object code or executable form under the terms of
-Paragraphs 1 and 2 above provided that you also do one of the following:
-
- a) accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- b) accompany it with a written offer, valid for at least three
- years, to give any third party free (except for a nominal
- shipping charge) a complete machine-readable copy of the
- corresponding source code, to be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- c) accompany it with the information you received as to where the
- corresponding source code may be obtained. (This alternative is
- allowed only for non-commercial distribution and only if you
- received the program in object code or executable form alone.)
-
-For an executable file, complete source code means all the source code for
-all modules it contains; but, as a special exception, it need not include
-source code for modules which are standard libraries that accompany the
-operating system on which the executable file runs.
-
- 4. You may not copy, sublicense, distribute or transfer SMAIL
-except as expressly provided under this License Agreement. Any attempt
-otherwise to copy, sublicense, distribute or transfer SMAIL is void and
-your rights to use the program under this License agreement shall be
-automatically terminated. However, parties who have received computer
-software programs from you with this License Agreement will not have
-their licenses terminated so long as such parties remain in full compliance.
-
- 5. If you wish to incorporate parts of SMAIL into other free
-programs whose distribution conditions are different, write to Landon
-Curt Noll & Ronald S. Karr via the Free Software Foundation at 51
-Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. We have not yet
-worked out a simple rule that can be stated here, but we will often
-permit this. We will be guided by the two goals of preserving the
-free status of all derivatives of our free software and of promoting
-the sharing and reuse of software.
-
-Your comments and suggestions about our licensing policies and our
-software are welcome! This contract was based on the contract made by
-the Free Software Foundation. Please contact the Free Software
-Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
-USA, or call (617) 542-5942 for details on copylefted material in
-general.
-
- NO WARRANTY
-
- BECAUSE SMAIL IS LICENSED FREE OF CHARGE, WE PROVIDE ABSOLUTELY NO
-WARRANTY, TO THE EXTENT PERMITTED BY APPLICABLE STATE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING, LANDON CURT NOLL & RONALD S. KARR AND/OR
-OTHER PARTIES PROVIDE SMAIL "AS IS" WITHOUT WARRANTY OF ANY KIND,
-EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
-THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF SMAIL IS WITH
-YOU. SHOULD SMAIL PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
-NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL LANDON CURT NOLL &
-RONALD S. KARR AND/OR ANY OTHER PARTY WHO MAY MODIFY AND REDISTRIBUTE
-SMAIL AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-LOST PROFITS, LOST MONIES, OR OTHER SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
-(INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
-INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE
-PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) SMAIL, EVEN IF YOU HAVE
-BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY
-ANY OTHER PARTY.
-
-
-
-SUN
-
-SUN MICROSYSTEMS, INC. THROUGH ITS SUN MICROSYSTEMS LABORATORIES
-DIVISION ("SUN") WILL LICENSE THIS SOFTWARE AND THE ACCOMPANYING
-DOCUMENTATION TO YOU (a "Licensee") ONLY ON YOUR ACCEPTANCE OF ALL
-THE TERMS SET FORTH BELOW.
-
-Sun grants Licensee a non-exclusive, royalty-free right to download,
-install, compile, use, copy and distribute the Software, modify or
-otherwise create derivative works from the Software (each, a
-"Modification") and distribute any Modification in source code and/or
-binary code form to its customers with a license agreement containing
-these terms and noting that the Software has been modified. The
-Software is copyrighted by Sun and other third parties and Licensee
-shall retain and reproduce all copyright and other notices presently
-on the Software. As between Sun and Licensee, Sun is the sole owner of
-all rights in and to the Software other than the limited rights
-granted to Licensee herein; Licensee will own its Modifications,
-expressly subject to Sun's continuing ownership of the
-Software. Licensee will, at its expense, defend and indemnify Sun and
-its licensors from and against any third party claims, including costs
-and reasonable attorneys' fees, and be wholly responsible for any
-liabilities arising out of or related to Licensee's development, use
-or distribution of the Software or Modifications. Any distribution of
-the Software and Modifications must comply with all applicable United
-States export control laws.
-
-THE SOFTWARE IS BEING PROVIDED TO LICENSEE "AS IS" AND ALL EXPRESS OR
-IMPLIED CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
-ARE DISCLAIMED. IN NO EVENT WILL SUN BE LIABLE HEREUNDER FOR ANY
-DIRECT DAMAGES OR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES OF ANY KIND.
-
-
-
-Sleepycat
-
-
-The Sleepycat License
-Copyright (c) 1990-1999
-Sleepycat Software. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Redistributions in any form must be accompanied by information on
-how to obtain complete source code for the DB software and any
-accompanying software that uses the DB software. The source code
-must either be included in the distribution or be available for no
-more than the cost of distribution plus a nominal fee, and must be
-freely redistributable under reasonable conditions. For an
-executable file, complete source code means the source code for all
-modules it contains. It does not include source code for modules or
-files that typically accompany the major components of the operating
-system on which the executable file runs.
-THIS SOFTWARE IS PROVIDED BY SLEEPYCAT SOFTWARE ``AS IS`` AND ANY EXPRESS
-OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
-NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL SLEEPYCAT SOFTWARE
-BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
-THE POSSIBILITY OF SUCH DAMAGE.
-
-Copyright (c) 1990, 1993, 1994, 1995
-The Regents of the University of California. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Neither the name of the University nor the names of its contributors
-may be used to endorse or promote products derived from this software
-without specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS`` AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-Copyright (c) 1995, 1996
-The President and Fellows of Harvard University. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Neither the name of the University nor the names of its contributors
-may be used to endorse or promote products derived from this software
-without specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY HARVARD AND ITS CONTRIBUTORS ``AS IS`` AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL HARVARD OR ITS CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-
-
-
-UCB
-
- Copyright (c) 1987, 1989, 1990, 1991, 1992, 1993, 1994
- The Regents of the University of California. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
- 3. Neither the name of the University nor the names of its contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
- ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
- ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
- FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
- DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
- OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
- OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
- SUCH DAMAGE.
-
-
-
-Unicode
-
-COPYRIGHT AND PERMISSION NOTICE
-
-Copyright 1991-2015 Unicode, Inc. All rights reserved.
-Distributed under the Terms of Use in
-http://www.unicode.org/copyright.html.
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of the Unicode data files and any associated documentation
-(the "Data Files") or Unicode software and any associated documentation
-(the "Software") to deal in the Data Files or Software
-without restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, and/or sell copies of
-the Data Files or Software, and to permit persons to whom the Data Files
-or Software are furnished to do so, provided that
-(a) this copyright and permission notice appear with all copies
-of the Data Files or Software,
-(b) this copyright and permission notice appear in associated
-documentation, and
-(c) there is clear notice in each modified Data File or in the Software
-as well as in the documentation associated with the Data File(s) or
-Software that the data or software has been modified.
-
-THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
-ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT OF THIRD PARTY RIGHTS.
-IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
-NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
-DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
-DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
-TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
-PERFORMANCE OF THE DATA FILES OR SOFTWARE.
-
-Except as contained in this notice, the name of a copyright holder
-shall not be used in advertising or otherwise to promote the sale,
-use or other dealings in these Data Files or Software without prior
-written authorization of the copyright holder.
-
-
-
-W3C
-
-
-W3C SOFTWARE NOTICE AND LICENSE
-This work (and included software, documentation such as READMEs, or other related
-items) is being provided by the copyright holders under the following license.
-License
-By obtaining, using and/or copying this work, you (the licensee) agree that you have
-read, understood, and will comply with the following terms and conditions.
-Permission to copy, modify, and distribute this software and its documentation, with
-or without modification, for any purpose and without fee or royalty is hereby granted,
-provided that you include the following on ALL copies of the software and
-documentation or portions thereof, including modifications:
-The full text of this NOTICE in a location viewable to users of the redistributed or
-derivative work.
-Any pre-existing intellectual property disclaimers, notices, or terms and conditions.
-If none exist, the W3C Software Short Notice should be included (hypertext is
-preferred, text is permitted) within the body of any redistributed or derivative code.
-Notice of any changes or modifications to the files, including the date changes were
-made. (We recommend you provide URIs to the location from which the code is derived.)
-Disclaimers
-THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
-REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
-WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF
-THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
-TRADEMARKS OR OTHER RIGHTS.
-COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
-The name and trademarks of copyright holders may NOT be used in advertising or
-publicity pertaining to the software without specific, written prior permission. Title
-to copyright in this software and any associated documentation will at all times
-remain with copyright holders.
-Notes
-This version: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
-This formulation of W3C`s notice and license became active on December 31 2002. This
-version removes the copyright ownership notice such that this license can be used with
-materials other than those owned by the W3C, reflects that ERCIM is now a host of the
-W3C, includes references to this specific dated version of the license, and removes
-the ambiguous grant of "use". Otherwise, this version is the same as the previous
-version and is written so as to preserve the Free Software Foundation`s assessment of
-GPL compatibility and OSI`s certification under the Open Source Definition.
-
-
-
-
-ZPL-2.1
-
-
-ZPL 2.1
-Zope Public License (ZPL) Version 2.1
-
-A copyright notice accompanies this license document that identifies the copyright
-holders.
-
-This license has been certified as open source. It has also been designated as GPL
-compatible by the Free Software Foundation (FSF).
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions in source code must retain the accompanying copyright notice, this
-list of conditions, and the following disclaimer.
-Redistributions in binary form must reproduce the accompanying copyright notice, this
-list of conditions, and the following disclaimer in the documentation and/or other
-materials provided with the distribution.
-Names of the copyright holders must not be used to endorse or promote products derived
-from this software without prior written permission from the copyright holders.
-The right to distribute this software or to use it for any purpose does not give you
-the right to use Servicemarks (sm) or Trademarks (tm) of the copyright holders. Use of
-them is covered by separate agreement with the copyright holders.
-If any files are modified, you must cause the modified files to carry prominent
-notices stating that you changed the files and the date of any change.
-Disclaimer
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS`` AND ANY EXPRESSED OR
-IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
-THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-Zlib
-
-
-zlib License
-
-
- This software is provided `as-is`, without any express or implied
- warranty. In no event will the authors be held liable for any damages
- arising from the use of this software.
-
- Permission is granted to anyone to use this software for any purpose,
- including commercial applications, and to alter it and redistribute it
- freely, subject to the following restrictions:
-
- 1. The origin of this software must not be misrepresented; you must not
- claim that you wrote the original software. If you use this software
- in a product, an acknowledgment in the product documentation would be
- appreciated but is not required.
- 2. Altered source versions must be plainly marked as such, and must not be
- misrepresented as being the original software.
- 3. This notice may not be removed or altered from any source distribution.
-
-
-
-
-
-tcl
-
-This software is copyrighted by the Regents of the University of
-California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
-Corporation and other parties. The following terms apply to all files
-associated with the software unless explicitly disclaimed in
-individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7014 (b) (3) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
-
-
-
- Proprietary Licenses
-
-Enea
-
- Copyright (C) 2006 by Enea.
- All rights reserved.
-
- This Software is furnished under a software license agreement and
- may be used only in accordance with the terms of such agreement.
- Any other use or reproduction is prohibited. No title to and
- ownership of the Software is hereby transferred.
-
- PROPRIETARY NOTICE
- This Software consists of confidential information.
- Trade secret law and copyright law protect this Software.
- The above notice of copyright on this Software does not indicate
- any actual or intended publication of such Software.
-
-
-
-
--
cgit v1.2.3-54-g00ecf
From c5332af275a9c17337c348e3a942e2f9c3935a51 Mon Sep 17 00:00:00 2001
From: Adrian Calianu
Date: Mon, 22 Feb 2021 22:18:48 +0100
Subject: Updated licences
manually generated since automatic scripts failed
Change-Id: I5fe2819ec13c4e21bbccc547ae2067d9d0afc05b
Signed-off-by: Adrian Calianu
---
.../doc/licenses.xml | 9936 ++++++++++++++++++++
1 file changed, 9936 insertions(+)
(limited to 'doc/book-enea-nfv-access-platform-open-source')
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
index e69de29..352f820 100644
--- a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
@@ -0,0 +1,9936 @@
+
+
+
+ Packages and Licenses
+
+
+ Packages
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Package Name
+ Version
+ Description
+ License
+
+
+
+
+
+
+ 4g-sierra
+ 1.0
+ Scripts to setup 4G modems from Sierra
+ Enea
+
+
+ acl
+ 2.2.52
+ Utilities for managing POSIX Access Control Lists.
+ LGPL-2.1, GPL-2.0
+
+
+ acpid
+ 2.0.28
+ A daemon for delivering ACPI events.
+ GPL-2.0
+
+
+ alsa-lib
+ 1.1.4.1
+ ALSA sound library.
+ LGPL-2.1, GPL-2.0
+
+
+ ant
+ 1.8.1
+ Another Neat Tool - build system for Java
+ Apache-2.0
+
+
+ antlr
+ 2.7.7
+ Framework for constructing recognizers interpreters compilers and translators
+ PD
+
+
+ apache2
+ 2.4.27
+ The Apache HTTP Server is a powerful efficient and extensible web server.
+ Apache-2.0
+
+
+ apr-util
+ 1.6.0
+ Apache Portable Runtime (APR) companion library.
+ Apache-2.0
+
+
+ apr
+ 1.6.2
+ Apache Portable Runtime (APR) library.
+ Apache-2.0
+
+
+ apt
+ 1.2.24
+ Advanced front-end for dpkg.
+ GPL-2.0
+
+
+ attr
+ 2.4.47
+ Utilities for manipulating filesystem extended attributes.
+ LGPL-2.1, GPL-2.0
+
+
+ aufs-util
+ 4.4
+ Tools for managing AUFS mounts.
+ GPL-2.0
+
+
+ augeas
+ 1.5.0
+ Augeas configuration API.
+ LGPL-2.1
+
+
+ autoconf-archive
+ 2016.09.16
+ a collection of freely re-usable Autoconf macros.
+ GPL-3.0-with-autoconf-exception
+
+
+ autoconf
+ 2.69
+ Autoconf is an extensible package of M4 macros that produce shell scripts to automatically configure software source code packages. Autoconf creates a configuration script for a package from a template file that lists the operating system features that the package can use in the form of M4 macro calls.
+ GPL-2.0, GPL-3.0
+
+
+ automake
+ 1.15.1
+ Automake is a tool for automatically generating `Makefile.in' files compliant with the GNU Coding Standards. Automake requires the use of Autoconf.
+ GPL-2.0
+
+
+ avahi
+ 0.6.32
+ "Avahi is a fully LGPL framework for Multicast DNS Service Discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. This tool implements IPv4LL ""Dynamic Configuration of IPv4 Link-Local Addresses"" (IETF RFC3927) a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server."
+ GPL-2.0, LGPL-2.1
+
+
+ avalon-framework-api
+ 4.3
+ Common way for components to be created initialized configured started. (API-only)
+ Apache-2.0
+
+
+ base-files
+ 3.0.14
+ The base-files package creates the basic system directory structure and provides a small set of key configuration files for the system.
+ GPL-2.0
+
+
+ base-passwd
+ 3.5.29
+ The master copies of the user database files (/etc/passwd and /etc/group). The update-passwd tool is also provided to keep the system databases synchronized with these master files.
+ GPL-2.0
+
+
+ bash-completion
+ 2.7
+ Programmable Completion for Bash 4.
+ GPL-2.0
+
+
+ bash
+ 4.4
+ An sh-compatible command language interpreter.
+ GPL-3.0
+
+
+ bc
+ 1.06
+ Arbitrary precision calculator language.
+ GPL-2.0, LGPL-2.1
+
+
+ bcel
+ 5.2
+ Java Bytecode manipulation library
+ Apache-2.0
+
+
+ bind
+ 9.10.5-P3
+ ISC Internet Domain Name Server.
+ ISC, BSD
+
+
+ binutils-cross-x86_64
+ 2.29.1
+ The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
+ GPL-3.0
+
+
+ binutils
+ 2.29.1
+ The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
+ GPL-3.0
+
+
+ bison
+ 3.0.4
+ Bison is a general-purpose parser generator that converts an annotated context-free grammar into an LALR(1) or GLR parser for that grammar. Bison is upward compatible with Yacc: all properly-written Yacc grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with little trouble.
+ GPL-3.0
+
+
+ bjam
+ 1.64.0
+ Portable Boost.Jam build tool for boost.
+ BSL-1.0, MIT, Python-2.0
+
+
+ bmap-tools
+ 3.4
+ "Bmap-tools - tools to generate block map (AKA bmap) and flash images using bmap. Bmaptool is a generic tool for creating the block map (bmap) for a file and copying files using the block map. The idea is that large file containing unused blocks like raw system image files can be copied or flashed a lot faster with bmaptool than with traditional tools like ""dd"" or ""cp""."
+ GPL-2.0
+
+
+ boost
+ 1.64.0
+ Free peer-reviewed portable C++ source libraries.
+ BSL-1.0, MIT, Python-2.0
+
+
+ bridge-utils
+ 1.5
+ Tools for ethernet bridging.
+ GPL-2.0
+
+
+ bsf
+ 2.4.0
+ Bean Scripting Framework package
+ Apache-2.0
+
+
+ btrfs-tools
+ 4.12
+ Btrfs is a new copy on write filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance repair and easy administration. This package contains utilities (mkfs fsck btrfsctl) used to work with btrfs and an utility (btrfs-convert) to make a btrfs filesystem from an ext3.
+ GPL-2.0
+
+
+ busybox
+ 1.24.1
+ BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for most of the utilities you usually find in GNU fileutils shellutils etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete POSIX environment for any small or embedded system.
+ GPL-2.0, BSD-4-Clause
+
+
+ bzip2
+ 1.0.6
+ bzip2 compresses files using the Burrows-Wheeler block-sorting text compression algorithm and Huffman coding. Compression is generally considerably better than that achieved by more conventional LZ77/LZ78-based compressors and approaches the performance of the PPM family of statistical compressors.
+ BSD-4-Clause
+
+
+ ca-certificates
+ 20170717
+ This package includes PEM files of CA certificates to allow SSL-based applications to check for the authenticity of SSL connections. This derived from Debian's CA Certificates.
+ GPL-2.0, MPL-2.0
+
+
+ cacao-initial
+ 0.98
+ CacaoVM for use as OpenEmbedded's Java VM
+ GPL-2.0
+
+
+ cairo
+ 1.14.10
+ Cairo is a multi-platform library providing anti-aliased vector-based rendering for multiple target backends. Paths consist of line segments and cubic splines and can be rendered at any width with various join and cap styles. All colors may be specified with optional translucence (opacity/alpha) and combined using the extended Porter/Duff compositing algebra as found in the X Render Extension.
+ MPL-1.0, LGPL-2.1, GPL-3.0
+
+
+ cantarell-fonts
+ 0.0.24
+ The Cantarell font typeface is designed as a contemporary Humanist sans serif and was developed for on-screen reading; in particular reading web pages on an HTC Dream mobile phone.
+ OFL-1.1
+
+
+ cdrkit
+ 1.1.11
+ CD/DVD command line tools.
+ GPL-2.0
+
+
+ cdrtools
+ 3.01a31
+ A set of tools for CD recording including cdrecord.
+ GPL-2.0, CDDL-1.0, LGPL-2.1
+
+
+ classpath-initial
+ 0.93
+ Java1.4-compatible GNU Classpath variant that is used as bootclasspath for jikes-native.
+ GPL-2.0, SAX-PD
+
+
+ classpath
+ 0.99
+ GNU Classpath standard Java libraries - For native Java-dependent programs
+ GPL-2.0, SAX-PD
+
+
+ cloud-init
+ 0.7.6
+ Init scripts for use on cloud images
+ GPL-3.0
+
+
+ cmake
+ 3.8.2
+ Cross-platform open-source make system.
+ BSD
+
+
+ collectd
+ 5.12.0
+ collectd is a daemon which collects system performance statistics periodically and provides mechanisms to store the values in a variety of ways for example in RRD files.
+ GPL-2.0, MIT
+
+
+ commons-logging
+ 1.1.1
+ Java Internet protocol suite library
+ Apache-2.0
+
+
+ commons-net
+ 1.4.1
+ Java Internet protocol suite library
+ Apache-2.0
+
+
+ compose-file
+ 3.0
+ Parser for the Compose file format (version 3)
+ Apache-2.0
+
+
+ containerd-docker
+ v0.2.x
+ containerd is a daemon to control runC built for performance and density. containerd leverages runC's advanced features such as seccomp and user namespace support as well as checkpoint and restore for cloning and live migration of containers.
+ Apache-2.0
+
+
+ core-image-minimal-initramfs
+ 1.0
+ Small image capable of booting a device. The kernel includes the Minimal RAM-based Initial Root Filesystem (initramfs) which finds the first 'init' program more efficiently.
+ MIT
+
+
+ coreutils
+ 8.27
+ The GNU Core Utilities provide the basic file shell and text manipulation utilities. These are the core utilities which are expected to exist on every system.
+ GPL-3.0
+
+
+ crda
+ 3.18
+ Wireless Central Regulatory Domain Agent.
+ copyleft-next-0.3.0
+
+
+ cross-localedef
+ 2.26
+ Cross locale generation tool for glibc.
+ LGPL-2.1
+
+
+ cryptodev-linux
+ 1.9
+ A /dev/crypto device driver header file.
+ GPL-2.0
+
+
+ cup
+ 0.10k
+ Lexical analyzer generator for Java
+ CUP
+
+
+ curl
+ 7.58.0
+ Command line tool and library for client-side URL transfers.
+ MIT
+
+
+ cwautomacros
+ 20110201
+ Collection of autoconf m4 macros.
+ GPL-2.0
+
+
+ db
+ 5.3.28
+ Berkeley Database v5.
+ Sleepycat
+
+
+ dbus-glib
+ 0.108
+ GLib bindings for the D-Bus message bus that integrate the D-Bus library with the GLib thread abstraction and main loop.
+ AFL-2.0, GPL-2.0
+
+
+ dbus-test
+ 1.10.20
+ D-Bus test package (for D-bus functionality testing only).
+ AFL-2.0, GPL-2.0
+
+
+ dbus
+ 1.10.20
+ "D-Bus is a message bus system a simple way for applications to talk to one another. In addition to interprocess communication D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a \""single instance\"" application or daemon and to launch applications and daemons on demand when their services are needed."
+ AFL-2.0, GPL-2.0
+
+
+ debianutils
+ 4.8.1.1
+ Miscellaneous utilities specific to Debian.
+ GPL-2.0, SMAIL_GPL
+
+
+ depmodwrapper
+ 1.0
+ Wrapper script for the Linux kernel module dependency indexer.
+ MIT
+
+
+ dhcp
+ 4.3.6
+ DHCP (Dynamic Host Configuration Protocol) is a protocol which allows individual devices on an IP network to get their own network configuration information from a server. DHCP helps make it easier to administer devices.
+ ISC
+
+
+ diffutils
+ 3.6
+ Diffutils contains the GNU diff diff3 sdiff and cmp utilities. These programs are usually used for creating patch files.
+ GPL-3.0
+
+
+ dmidecode
+ 3.1
+ DMI (Desktop Management Interface) table related utilities.
+ GPL-2.0
+
+
+ dnsmasq
+ 2.78
+ Lightweight easy to configure DNS forwarder and DHCP server.
+ GPL-2.0, GPL-3.0
+
+
+ docker
+ 17.06.0
+ Linux container runtime Docker complements kernel namespacing with a high-level API which operates at the process level. It runs unix processes with strong guarantees of isolation and repeatability across servers. . Docker is a great building block for automating distributed systems: large-scale web deployments database clusters continuous deployment systems private PaaS service-oriented architectures etc. . This package contains the daemon and client. Using docker.io is officially supported on x86_64 and arm (32-bit) hosts. Other architectures are considered experimental. . Also note that kernel version 3.10 or above is required for proper operation of the daemon process and that any lower versions may have subtle and/or glaring issues.
+ Apache-2.0
+
+
+ dosfstools
+ 4.1
+ DOS FAT Filesystem Utilities.
+ GPL-3.0
+
+
+ dpdk-dev-libibverbs
+ 1.2.1-3.4-2.0.0.0
+ libibverbs library to support Mellanox config
+ GPL-2.0
+
+
+ dpdk
+ 18.02
+ Intel(r) Data Plane Development Kit
+ BSD, LGPL-2.0, GPL-2.0
+
+
+ dpkg
+ 1.18.24
+ Package maintenance system from Debian.
+ GPL-2.0
+
+
+ dtc
+ 1.4.4
+ The Device Tree Compiler is a tool used to manipulate the Open-Firmware-like device tree used by PowerPC kernels.
+ GPL-2.0, BSD
+
+
+ e2fsprogs
+ 1.43.5
+ The Ext2 Filesystem Utilities (e2fsprogs) contain all of the standard utilities for creating fixing configuring and debugging ext2 filesystems.
+ GPL-2.0, LGPL-2.0, BSD, MIT
+
+
+ ebtables
+ 2.0.10-4
+ Utility for basic Ethernet frame filtering on a Linux bridge advanced logging MAC DNAT/SNAT and brouting.
+ GPL-2.0
+
+
+ ecj-bootstrap
+ 1.0
+ JDT Core Batch Compiler - Bootstrap variant
+ MIT
+
+
+ ecj-initial
+ 1.0
+ JDT Core Batch Compiler - Bootstrap variant
+ MIT
+
+
+ efibootmgr
+ 0.15
+ Linux user-space application to modify the EFI Boot Manager.
+ GPL-2.0
+
+
+ efitools
+ 1.7.0
+ From the EFI Tools package in the Linux user-space it's now possible to read and manipulate the UEFI signatures database via the new efi-readvar and efi-updatevar commands. Aside from needing efitools 1.4 the EFIVARFS file-system is also needed which was only introduced in the Linux 3.8 kernel.
+ GPL-2.0
+
+
+ efivar
+ 0.31
+ efivar provides a simple command line interface to the UEFI variable facility
+ LGPL-2.1
+
+
+ element-vcpe
+ 4.1.3
+ vCPE(based on Element-ODM)
+ Enea, BSD, BSD-2-Clause, GPL-3.0, ISC, LGPL-2.1
+
+
+ elfutils
+ 0.170
+ Utilities and libraries for handling compiled object files.
+ GPL-3.0, Elfutils-Exception
+
+
+ enea-nfv-access-vnf
+ 1.0
+ VNF image of the Enea NFV Access Platform includes kernel rootfs and boot parameters
+ MIT
+
+
+ enea-nfv-access
+ 1.0
+ Image for the host side of the Enea NFV Access Platform with ODM and NETCONF Edgelink customizations
+ MIT
+
+
+ ethtool
+ 4.11
+ A small utility for examining and tuning the settings of your ethernet-based network interfaces.
+ GPL-2.0
+
+
+ expat
+ 2.2.3
+ Expat is an XML parser library written in C. It is a stream-oriented parser in which an application registers handlers for things the parser might find in the XML document (like start tags)
+ MIT
+
+
+ fastjar
+ 0.98
+ jar replacement written in C.
+ GPL-2.0
+
+
+ file
+ 5.31
+ File attempts to classify files depending on their contents and prints a description if a match is found.
+ BSD
+
+
+ findutils
+ 4.6.0
+ The GNU Find Utilities are the basic directory searching utilities of the GNU operating system. These programs are typically used in conjunction with other programs to provide modular and powerful directory search and file locating capabilities to other commands.
+ GPL-3.0
+
+
+ flex
+ 2.6.0
+ Flex is a fast lexical analyser generator. Flex is a tool for generating programs that recognize lexical patterns in text.
+ BSD
+
+
+ fontconfig
+ 2.12.4
+ Fontconfig is a font configuration and customization library which does not depend on the X Window System. It is designed to locate fonts within the system and select them according to requirements specified by applications. Fontconfig is not a rasterization library nor does it impose a particular rasterization library on the application. The X-specific library 'Xft' uses fontconfig along with freetype to specify and rasterize fonts.
+ MIT, PD
+
+
+ freetype
+ 2.8
+ FreeType is a software font engine that is designed to be small efficient highly customizable and portable while capable of producing high-quality output (glyph images). It can be used in graphics libraries display servers font conversion tools text image generation tools and many other products as well.
+ FreeType, GPL-2.0
+
+
+ fuse
+ 2.9.7
+ FUSE (Filesystem in Userspace) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. FUSE also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations.
+ GPL-2.0, LGPL-2.0
+
+
+ gawk
+ 4.1.4
+ The GNU version of awk a text processing utility. Awk interprets a special-purpose programming language to do quick and easy text pattern matching and reformatting jobs.
+ GPL-3.0
+
+
+ gcc-cross-initial-x86_64
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc-cross-x86_64
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc-runtime
+ 7.3.0
+ Runtime libraries from GCC.
+ GPL-3.0-with-GCC-exception
+
+
+ gcc-source-7.3.0
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gdbm
+ 1.13
+ Key/value database library with extensible hashing.
+ GPL-3.0
+
+
+ gettext-minimal
+ 0.19.8.1
+ Contains the m4 macros sufficient to support building autoconf/automake. This provides a significant build time speedup by the removal of gettext-native from most dependency chains (now only needed for gettext for the target).
+ FSF-Unlimited
+
+
+ gettext
+ 0.19.8.1
+ GNU gettext is a set of tools that provides a framework to help other programs produce multi-lingual messages. These tools include a set of conventions about how programs should be written to support message catalogs a directory and file naming organization for the message catalogs themselves a runtime library supporting the retrieval of translated messages and a few stand-alone programs to massage in various ways the sets of translatable and already translated strings.
+ GPL-3.0, LGPL-2.1
+
+
+ giflib
+ 5.1.4
+ shared library for GIF images.
+ MIT
+
+
+ git
+ 2.13.3
+ Distributed version control system.
+ GPL-2.0
+
+
+ glib-2.0
+ 2.52.3
+ GLib is a general-purpose utility library which provides many useful data types macros type conversions string utilities file utilities a main loop abstraction and so on.
+ LGPL-2.0, BSD, PD
+
+
+ glibc-locale
+ 2.26
+ Locale data from glibc.
+ GPL-2.0, LGPL-2.1
+
+
+ glibc
+ 2.26
+ The GNU C Library is used as the system C library in most systems with the Linux kernel.
+ GPL-2.0, LGPL-2.1
+
+
+ gmp
+ 6.1.2
+ GMP is a free library for arbitrary precision arithmetic operating on signed integers rational numbers and floating point numbers
+ GPL-2.0, LGPL-3.0
+
+
+ gnome-desktop-testing
+ 2014.1
+ Test runner for GNOME-style installed tests.
+ LGPL-2.0
+
+
+ gnu-config
+ 20150728
+ Tool that installs the GNU config.guess / config.sub into a directory tree
+ GPL-3.0-with-autoconf-exception
+
+
+ gnu-efi
+ 3.0.6
+ Libraries for producing EFI binaries.
+ GPL-2.0, BSD-2-Clause
+
+
+ gnujaf
+ 1.1.1
+ Provides a mean to type data and locate components suitable for performing various kinds of action on it.
+ GPL-2.0-with-GCC-exception
+
+
+ gnulib
+ 2017-08-20.18
+ A collection of software subroutines which are designed to be usable on many operating systems. The goal of the project is to make it easy for free software authors to make their software run on many operating systems. Since source is designed to be copied from gnulib it is not a library per-se as much as a collection of portable idioms to be used in other projects.
+ LGPL-2.0
+
+
+ gnumail
+ 1.1.2
+ GNU's free implementation of the JavaMail API specification
+ GPL-2.0-with-GCC-exception
+
+
+ gnutls
+ 3.5.13
+ GNU Transport Layer Security Library.
+ GPL-3.0, LGPL-2.1
+
+
+ go-capability
+ 0.0
+ Utilities for manipulating POSIX capabilities in Go.
+ BSD-2-Clause
+
+
+ go-cli
+ 1.1.0
+ A small package for building command line apps in Go
+ MIT
+
+
+ go-connections
+ 0.2.1
+ Utility package to work with network connections
+ Apache-2.0
+
+
+ go-context
+ git
+ A golang registry for global request variables.
+ BSD-3-Clause
+
+
+ go-cross-x86_64
+ 1.9.4
+ The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
+ BSD-3-Clause
+
+
+ go-dbus
+ 4.0.0
+ Native Go bindings for D-Bus
+ BSD-2-Clause
+
+
+ go-distribution
+ 2.6.0
+ The Docker toolset to pack ship store and deliver content
+ Apache-2.0
+
+
+ go-fsnotify
+ 1.2.11
+ A golang registry for global request variables.
+ BSD-3-Clause
+
+
+ go-libtrust
+ 0.0
+ Primitives for identity and authorization
+ Apache-2.0
+
+
+ go-logrus
+ 0.11.0
+ A golang registry for global request variables.
+ MIT
+
+
+ go-mux
+ git
+ A powerful URL router and dispatcher for golang.
+ BSD-3-Clause
+
+
+ go-patricia
+ 2.2.6
+ A generic patricia trie (also called radix tree) implemented in Go (Golang)
+ MIT
+
+
+ go-pty
+ git
+ PTY interface for Go
+ MIT
+
+
+ go-systemd
+ 4
+ Go bindings to systemd socket activation journal D-Bus and unit files
+ Apache-2.0
+
+
+ go
+ 1.9.4
+ The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
+ BSD-3-Clause
+
+
+ gobject-introspection
+ 1.52.1
+ Middleware layer between GObject-using C libraries and language bindings.
+ LGPL-2.0, GPL-2.0
+
+
+ gotty
+ 1.0
+ Run a terminal application as a web service
+ MIT
+
+
+ gperf
+ 3.1
+ GNU gperf is a perfect hash function generator
+ GPL-3.0
+
+
+ gpgme
+ 1.9.0
+ GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a High-Level Crypto API for encryption decryption signing signature verification and key management
+ GPL-2.0, LGPL-2.1
+
+
+ gptfdisk
+ 1.0.3
+ GPT fdisk is a disk partitioning tool loosely modeled on Linux fdisk but used for modifying GUID Partition Table (GPT) disks. The related FixParts utility fixes some common problems on Master Boot Record (MBR) disks.
+ GPL-2.0
+
+
+ grep
+ 3.1
+ GNU grep utility.
+ GPL-3.0
+
+
+ groff
+ 1.22.3
+ The groff (GNU troff) software is a typesetting package which reads plain text mixed with formatting commands and produces formatted output.
+ GPL-3.0
+
+
+ grpc-go
+ 1.4.0
+ The Go language implementation of gRPC. HTTP/2 based RPC
+ BSD
+
+
+ grub-disable-fallback
+ 1.0
+ Enea service to disable grub fallback when boot is successful
+ Enea
+
+
+ grub-efi
+ 2.02
+ GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
+ GPL-3.0
+
+
+ grub
+ 2.02
+ GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
+ GPL-3.0
+
+
+ gtk-doc
+ 1.25
+ Gtk-doc is a set of scripts that extract specially formatted comments from glib-based software and produce a set of html documentation files from them
+ GPL-2.0
+
+
+ gzip
+ 1.8
+ GNU Gzip is a popular data compression program originally written by Jean-loup Gailly for the GNU project. Mark Adler wrote the decompression part
+ GPL-3.0
+
+
+ harfbuzz
+ 1.4.8
+ HarfBuzz is an OpenType text shaping engine.
+ MIT
+
+
+ haveged
+ 1.9.1
+ The haveged project is an attempt to provide an easy-to-use unpredictable random number generator based upon an adaptation of the HAVEGE algorithm. Haveged was created to remedy low-entropy conditions in the Linux random device that can occur under some workloads especially on headless servers.
+ GPL-3.0
+
+
+ help2man
+ 1.47.4
+ Program for creating simple man pages.
+ GPL-3.0
+
+
+ hostapd
+ 2.9
+ User space daemon for extended IEEE 802.11 management.
+ BSD-3-Clause
+
+
+ htop
+ 1.0.3
+ htop process monitor.
+ GPL-2.0
+
+
+ hugepage-reservation
+ 1.0
+ Reserve hugepages on system startup.
+ Enea
+
+
+ icedtea7
+ 2.1.3
+ Harness to build the source code from OpenJDK using Free Software build tools
+ GPL-2.0-with-classpath-exception
+
+
+ icu
+ 59.1
+ The International Component for Unicode (ICU) is a mature portable set of C/C++ and Java libraries for Unicode support software internationalization (I18N) and globalization (G11N) giving applications the same results on all platforms.
+ ICU
+
+
+ inetlib
+ 1.1.1
+ GNU Classpath inetlib is an extension library to provide extra network protocol support for GNU Classpath and ClasspathX project but it can also used standalone to add http imap pop3 and smtp client support applications.
+ GPL-2.0-with-GCC-exception
+
+
+ initramfs-framework
+ 1.0
+ Modular initramfs system.
+ MIT
+
+
+ initramfs-module-install-efi
+ 1.0
+ initramfs-framework module for EFI installation option.
+ MIT
+
+
+ initramfs-module-install
+ 1.0
+ initramfs-framework module for installation option.
+ MIT
+
+
+ initramfs-module-setup-live
+ 1.0
+ initramfs-framework module for live booting.
+ MIT
+
+
+ initramfs-ostree-image
+ 1.0
+ OSTree initramfs image
+ MIT
+
+
+ inputproto
+ 2.3.2
+ This package provides the wire protocol for the X Input extension. The extension supports input devices other then the core X keyboard and pointer.
+ MIT
+
+
+ intltool
+ 0.51.0
+ Utility scripts for internationalizing XML.
+ GPL-2.0
+
+
+ iperf3
+ 3.2
+ iperf is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing protocols and buffers. For each test it reports the bandwidth loss and other parameters.
+ BSD
+
+
+ iproute2
+ 4.11.0
+ Iproute2 is a collection of utilities for controlling TCP / IP networking and traffic control in Linux. Of the utilities ip and tc are the most important. ip controls IPv4 and IPv6 configuration and tc stands for traffic control.
+ GPL-2.0
+
+
+ iptables
+ 1.6.1
+ iptables is the userspace command line program used to configure and control network packet filtering code in Linux.
+ GPL-2.0
+
+
+ iw
+ 4.9
+ iw is a new nl80211 based CLI configuration utility for wireless devices. It supports almost all new drivers that have been added to the kernel recently.
+ BSD
+
+
+ ixgbe
+ 5.10.2
+ The ixgbe driver supports 82598- and 82599-based PCI Express* 10 Gigabit Network Connections.
+ GPL-2.0
+
+
+ ixgbevf
+ 4.10.2
+ This virtual function driver supports kernel versions 2.6.x and newer This driver supports 82599 X540 X550 and X552-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support. The guest OS loading this driver must support MSI-X interrupts.
+ GPL-2.0
+
+
+ jacl
+ 1.4.1
+ Tcl interpreter for Java
+ UCB, SUN, AMD, CDS
+
+
+ jamvm
+ 2.0.0-devel
+ A compact Java Virtual Machine which conforms to the JVM specification version 2.
+ GPL-2.0
+
+
+ jansson
+ 2.9
+ Jansson is a C library for encoding decoding and manipulating JSON data.
+ MIT
+
+
+ jaxp1.3
+ 1.4.01
+ Java XML parser and transformer APIs (DOM SAX JAXP TrAX)
+ Apache-2.0, W3C, PD
+
+
+ jdepend
+ 2.9.1
+ Design quality metrics generator for each Java
+ BSD
+
+
+ jikes-initial
+ 1.0
+ Initial Java 1.4-compatible (and not higher) compiler.
+ MIT
+
+
+ jikes
+ 1.22
+ Java compiler adhering to language and VM specifications
+ IPL-1.0
+
+
+ jlex
+ 1.2.6
+ Lexical analyzer generator for Java
+ JLEX
+
+
+ jq
+ 1.5
+ jq is like sed for JSON data you can use it to slice and filter and map and transform structured data with the same ease that sed awk grep and friends let you play with text.
+ MIT
+
+
+ jsch
+ 0.1.40
+ SSH implementation in Java
+ BSD
+
+
+ junit
+ 3.8.2
+ JUnit is a testing framework for Java
+ CPL-1.0
+
+
+ jzlib
+ 1.0.7
+ zlib implementation in Java
+ BSD
+
+
+ kbd
+ 2.0.4
+ Keytable files and keyboard utilities.
+ GPL-2.0
+
+
+ kbproto
+ 1.0.7
+ This package provides the wire protocol for the X Keyboard extension. This extension is used to control options related to keyboard handling and layout.
+ MIT
+
+
+ kern-tools
+ 0.2
+ Tools for managing Yocto Project style branched kernels.
+ GPL-2.0
+
+
+ keymaps
+ 1.0
+ Keymaps and initscript to set the keymap on bootup.
+ GPL-2.0
+
+
+ keyutils
+ 1.5.10
+ Utilities to control the kernel key management facility and to provide a mechanism by which the kernel call back to userspace to get a key instantiated.
+ LGPL-2.1, GPL-2.0
+
+
+ kmod
+ 24
+ kmod is a set of tools to handle common tasks with Linux kernel modules like insert remove list check properties resolve dependencies and aliases.
+ GPL-2.0, LGPL-2.1
+
+
+ krb5
+ 1.15.1
+ "Kerberos is a system for authenticating users and services on a network. Kerberos is a trusted third-party service. That means that there is a third party (the Kerberos server) that is trusted by all the entities on the network (users and services usually called ""principals""). . This is the MIT reference implementation of Kerberos V5. . This package contains the Kerberos key server (KDC). The KDC manages all authentication credentials for a Kerberos realm holds the master keys for the realm and responds to authentication requests. This package should be installed on both master and slave KDCs."
+ MIT
+
+
+ ldconfig
+ 2.12.1
+ A standalone native ldconfig build.
+ GPL-2.0
+
+
+ less
+ 487
+ Less is a program similar to more i.e. a terminal based program for viewing text files and the output from other programs. Less offers many features beyond those that more does.
+ GPL-3.0, BSD-2-Clause
+
+
+ libaio
+ 0.3.110
+ Asynchronous input/output library that uses the kernels native interface
+ LGPL-2.1
+
+
+ libarchive
+ 3.3.2
+ C library and command-line tools for reading and writing tar cpio zip ISO and other archive formats
+ BSD
+
+
+ libassuan
+ 2.4.3
+ IPC library used by GnuPG and GPGME.
+ GPL-3.0, LGPL-2.1
+
+
+ libbsd
+ 0.8.6
+ This library provides useful functions commonly found on BSD systems and lacking on others like GNU systems thus making it easier to port projects with strong BSD origins without needing to embed the same code over and over again on each project.
+ BSD-4-Clause, ISC, PD
+
+
+ libcap
+ 2.25
+ Library for getting/setting POSIX.1e capabilities.
+ BSD, GPL-2.0
+
+
+ libcgroup
+ 0.41
+ libcgroup is a library that abstracts the control group file system in Linux. Control groups allow you to limit account and isolate resource usage (CPU memory disk I/O etc.) of groups of processes.
+ LGPL-2.1
+
+
+ libcheck
+ 0.10.0
+ Check - unit testing framework for C code.
+ LGPL-2.1
+
+
+ libdaemon
+ 0.14
+ Lightweight C library which eases the writing of UNIX daemons.
+ LGPL-2.1
+
+
+ libdevmapper
+ 2.02.171
+ LVM2 is a set of utilities to manage logical volumes in Linux.
+ GPL-2.0, LGPL-2.0
+
+
+ libecj-bootstrap
+ 3.6.2
+ JDT Core Batch Compiler - Jar only
+ EPL-1.0
+
+
+ liberation-fonts
+ 2.00.1
+ The Liberation(tm) Fonts is a font family originally created by Ascender(c) which aims at metric compatibility with Arial Times New Roman Courier New.
+ OFL-1.1
+
+
+ libffi
+ 3.2.1
+ The `libffi' library provides a portable high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. FFI stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The `libffi' library really only provides the lowest machine dependent layer of a fully featured foreign function interface. A layer must exist above `libffi' that handles type conversions for values passed between the two languages.
+ MIT
+
+
+ libfile-slurp-perl
+ 9999.19
+ This module provides subroutines to read or write entire files with a simple call. It also has a subroutine for reading the list of filenames in a directory.
+ Artistic-1.0, GPL-1.0
+
+
+ libgcc-initial
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception
+
+
+ libgcc
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ libgcrypt
+ 1.8.0
+ General purpose cryptographic library based on the code from GnuPG.
+ GPL-2.0, LGPL-2.1, GPL-3.0
+
+
+ libgpg-error
+ 1.27
+ Small library that defines common error values for all GnuPG components.
+ GPL-2.0, LGPL-2.1
+
+
+ libgudev
+ 231
+ GObject wrapper for libudev.
+ LGPL-2.1
+
+
+ libice
+ 1.0.9
+ The Inter-Client Exchange (ICE) protocol provides a generic framework for building protocols on top of reliable byte-stream transport connections. It provides basic mechanisms for setting up and shutting down connections for performing authentication for negotiating versions and for reporting errors.
+ MIT
+
+
+ libidn
+ 1.33
+ Implementation of the Stringprep Punycode and IDNA specifications defined by the IETF Internationalized Domain Names (IDN) working group.
+ LGPL-2.1, LGPL-3.0, GPL-3.0
+
+
+ libjpeg-turbo
+ 1.5.2
+ libjpeg-turbo is a derivative of libjpeg that uses SIMD instructions (MMX SSE2 NEON) to accelerate baseline JPEG compression and decompression
+ BSD-3-Clause
+
+
+ libmbim
+ 1.16.0
+ libmbim is a glib-based library for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol
+ GPL-2.0, LGPL-2.1
+
+
+ libmnl
+ 1.0.4
+ Minimalistic user-space library oriented to Netlink developers providing functions for common tasks in parsing validating and constructing both the Netlink header and TLVs.
+ LGPL-2.1
+
+
+ libmpc
+ 1.0.3
+ Mpc is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result. It is built upon and follows the same principles as Mpfr
+ LGPL-3.0
+
+
+ libndp
+ 1.6
+ Library for IPv6 Neighbor Discovery Protocol.
+ LGPL-2.1
+
+
+ libnewt
+ 0.52.20
+ Newt is a programming library for color text mode widget based user interfaces. Newt can be used to add stacked windows entry widgets checkboxes radio buttons labels plain text fields scrollbars etc. to text mode user interfaces. This package also contains the shared library needed by programs built with newt as well as a /usr/bin/dialog replacement called whiptail. Newt is based on the slang library.
+ LGPL-2.0
+
+
+ libnl
+ 3.4.0
+ A library for applications dealing with netlink sockets.
+ LGPL-2.1
+
+
+ libnss-mdns
+ 0.10
+ Name Service Switch module for Multicast DNS (zeroconf) name resolution.
+ LGPL-2.1
+
+
+ libpcap
+ 1.8.1
+ Libpcap provides a portable framework for low-level network monitoring. Libpcap can provide network statistics collection security monitoring and network debugging.
+ BSD
+
+
+ libpciaccess
+ 0.13.5
+ libpciaccess provides functionality for X to access the PCI bus and devices in a platform-independent way.
+ MIT
+
+
+ libpcre
+ 8.41
+ The PCRE library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. PCRE has its own native API as well as a set of wrapper functions that correspond to the POSIX regular expression API.
+ BSD
+
+
+ libpng
+ 1.6.31
+ PNG image format decoding library.
+ Libpng
+
+
+ libpthread-stubs
+ 0.4
+ This library provides weak aliases for pthread functions not provided in libc or otherwise available by default.
+ MIT
+
+
+ libqmi
+ 1.20.2
+ libqmi is a glib-based library for talking to WWAN modems and devices which speak the Qualcomm MSM Interface (QMI) protocol
+ GPL-2.0, LGPL-2.1
+
+
+ libsdl
+ 1.2.15
+ Simple DirectMedia Layer is a cross-platform multimedia library designed to provide low level access to audio keyboard mouse joystick 3D hardware via OpenGL and 2D video framebuffer.
+ LGPL-2.1
+
+
+ libsign
+ 0.3.2
+ This project targets to provide a generic signing framework. This framework separates the signing request and signing process and correspondingly forms the so-called signlet and signaturelet. Each signaturelet only concerns about the details about how to construct the layout of a signature format and signlet only cares how to construct the signing request.
+ BSD-3-Clause
+
+
+ libsm
+ 1.2.2
+ "The Session Management Library (SMlib) is a low-level \""C\"" language interface to XSMP. The purpose of the X Session Management Protocol (XSMP) is to provide a uniform mechanism for users to save and restore their sessions. A session is a group of clients each of which has a particular state."
+ MIT
+
+
+ libtasn1
+ 4.12
+ Library for ASN.1 and DER manipulation.
+ GPL-3.0, LGPL-2.1
+
+
+ libtool
+ 2.4.6
+ This is GNU libtool a generic library support script. Libtool hides the complexity of generating special library types (such as shared libraries) behind a consistent interface.
+ GPL-2.0, LGPL-2.1
+
+
+ libunistring
+ 0.9.7
+ Text files are nowadays usually encoded in Unicode and may consist of very different scripts from Latin letters to Chinese Hanzi with many kinds of special characters accents right-to-left writing marks hyphens Roman numbers and much more. But the POSIX platform APIs for text do not contain adequate functions for dealing with particular properties of many Unicode characters. In fact the POSIX APIs for text have several assumptions at their base which don't hold for Unicode text. This library provides functions for manipulating Unicode strings and for manipulating C strings according to the Unicode standard. This package contains documentation.
+ LGPL-3.0, GPL-2.0
+
+
+ libusb1
+ 1.0.21
+ Userspace library to access USB (version 1.0).
+ LGPL-2.1
+
+
+ libvirt
+ 4.2.0
+ A toolkit to interact with the virtualization capabilities of recent versions of Linux.
+ LGPL-2.1, GPL-2.0
+
+
+ libx11
+ 1.6.5
+ This package provides a client interface to the X Window System otherwise known as 'Xlib'. It provides a complete API for the basic functions of the window system.
+ MIT, BSD
+
+
+ libxau
+ 1.0.8
+ libxau provides the main interfaces to the X11 authorisation handling which controls authorisation for X connections both client-side and server-side.
+ MIT
+
+
+ libxcb
+ 1.12
+ The X protocol C-language Binding (XCB) is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
+ MIT
+
+
+ libxdmcp
+ 1.1.2
+ The purpose of the X Display Manager Control Protocol (XDMCP) is to provide a uniform mechanism for an autonomous display to request login service from a remote host. An X terminal (screen keyboard mouse processor network interface) is a prime example of an autonomous display.
+ MIT
+
+
+ libxext
+ 1.3.3
+ libXext provides an X Window System client interface to several extensions to the X protocol. The supported protocol extensions are DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. libXext also provides a small set of utility functions to aid authors of client APIs for X protocol extensions.
+ MIT
+
+
+ libxft
+ 2.3.2
+ Xft was designed to provide good support for scalable fonts and to do so efficiently. Unlike the core fonts system it supports features such as anti-aliasing and sub-pixel rasterisation. Perhaps more importantly it gives applications full control over the way glyphs are rendered making fine typesetting and WYSIWIG display possible. Finally it allows applications to use fonts that are not installed system-wide for displaying documents with embedded fonts. Xft is not compatible with the core fonts system: usage of Xft requires fairly extensive changes to toolkits (user-interface libraries).
+ MIT
+
+
+ libxkbcommon
+ 0.7.1
+ libxkbcommon is a keymap compiler and support library which processes a reduced subset of keymaps as defined by the XKB specification.
+ MIT
+
+
+ libxml-parser-perl
+ 2.44
+ XML::Parser - A perl module for parsing XML documents.
+ Artistic-1.0, GPL-1.0
+
+
+ libxml2
+ 2.9.5
+ The XML Parser Library allows for manipulation of XML files. Libxml2 exports Push and Pull type parser interfaces for both XML and HTML. It can do DTD validation at parse time on a parsed document instance or with an arbitrary DTD. Libxml2 includes complete XPath XPointer and Xinclude implementations. It also has a SAX like interface which is designed to be compatible with Expat.
+ MIT
+
+
+ libxrandr
+ 1.5.1
+ The X Resize Rotate and Reflect Extension called RandR for short brings the ability to resize rotate and reflect the root window of a screen. It is based on the X Resize and Rotate Extension as specified in the Proceedings of the 2001 Usenix Technical Conference [RANDR].
+ MIT
+
+
+ libxrender
+ 0.9.10
+ The X Rendering Extension (Render) introduces digital image composition as the foundation of a new rendering model within the X Window System. Rendering geometric figures is accomplished by client-side tessellation into either triangles or trapezoids. Text is drawn by loading glyphs into the server and rendering sets of them.
+ MIT
+
+
+ libxslt
+ 1.1.29
+ GNOME XSLT library.
+ MIT
+
+
+ libyaml
+ 0.1.7
+ LibYAML is a C library for parsing and emitting data in YAML 1.1 a human-readable data serialization format.
+ MIT
+
+
+ lighttpd
+ 1.4.45
+ Lightweight high-performance web server.
+ BSD
+
+
+ linux-firmware
+ 0.0
+ Firmware files for use with Linux kernel.
+ Redistributable binaries
+
+
+ linux-intel-guest
+ 4.14.123
+ Linux kernel.
+ GPL-2.0
+
+
+ linux-intel-host
+ 4.14.123
+ Linux kernel.
+ GPL-2.0
+
+
+ linux-libc-headers
+ 4.12
+ Sanitized set of kernel headers for the C library's use.
+ GPL-2.0
+
+
+ lmsensors-config
+ 1.0
+ Hardware health monitoring configuration files
+ MIT
+
+
+ lmsensors
+ 3.6.0
+ Hardware health monitoring applications.
+ GPL-2.0, LGPL-2.1
+
+
+ log-collector
+ 1.0
+ Service that collects platform logs
+ Enea
+
+
+ log4j1.2
+ 1.2.17
+ Java library to help the programmer output log statements to a variety of output targets
+ Apache-2.0
+
+
+ logkit
+ 1.2.2
+ Logging toolkit designed for secure performance orientated logging in Java applications
+ Apache-2.0
+
+
+ logrotate
+ 3.12.3
+ Rotates compresses removes and mails system log files.
+ GPL-2.0
+
+
+ lsb
+ 4.1
+ LSB support for OpenEmbedded.
+ GPL-2.0
+
+
+ lsbinitscripts
+ 9.72
+ SysV init scripts which are only used in an LSB image.
+ GPL-2.0
+
+
+ lshw
+ 02.17
+ A small tool to provide detailed information on the hardware configuration of the machine. It can report exact memory configuration firmware version mainboard configuration CPU version and speed cache configuration bus speed etc. on DMI-capable or EFI systems.
+ GPL-2.0
+
+
+ lsof
+ 4.89
+ Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open Files and it does just that.
+ BSD
+
+
+ lvm2
+ 2.02.171
+ LVM2 is a set of utilities to manage logical volumes in Linux.
+ GPL-2.0, LGPL-2.0
+
+
+ lxc
+ 2.0.8
+ lxc aims to use these new functionnalities to provide an userspace container object
+ GPL-2.0
+
+
+ lxd
+ git
+ "LXD is a container ""hypervisor"" and a new user experience for LXC Specifically it's made of three components: - A system-wide daemon (lxd) - A command line client (lxc) - An OpenStack Nova plugin (nova-compute-lxd)"
+ Apache-2.0
+
+
+ lz4
+ 1.7.4
+ LZ4 is a very fast lossless compression algorithm providing compression speed at 400 MB/s per core scalable with multi-cores CPU. It also features an extremely fast decoder with speed in multiple GB/s per core typically reaching RAM speed limits on multi-core systems.
+ BSD, BSD-2-Clause, GPL-2.0
+
+
+ lzo
+ 2.10
+ Lossless data compression library.
+ GPL-2.0
+
+
+ lzop
+ 1.03
+ lzop is a compression utility which is designed to be a companion to gzip. \nIt is based on the LZO data compression library and its main advantages over \ngzip are much higher compression and decompression speed at the cost of some \ncompression ratio. The lzop compression utility was designed with the goals \nof reliability speed portability and with reasonable drop-in compatibility \nto gzip.
+ GPL-2.0
+
+
+ m4
+ 1.4.18
+ GNU m4 is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible although it has some extensions (for example handling more than 9 positional parameters to macros). GNU M4 also has built-in functions for including files running shell commands doing arithmetic etc.
+ GPL-3.0
+
+
+ make
+ 4.2.1
+ Make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. Make gets its knowledge of how to build your program from a file called the makefile which lists each of the non-source files and how to compute it from other files.
+ GPL-3.0, LGPL-2.0
+
+
+ makedepend
+ 1.0.5
+ The makedepend program reads each sourcefile in sequence and parses it like a C-preprocessor processing all #include #define #undef #ifdef #ifndef #endif #if #elif and #else directives so that it can correctly tell which #include directives would be used in a compilation. Any #include directives can reference files having other #include directives and parsing will occur in these files as well.
+ MIT
+
+
+ makedevs
+ 1.0.1
+ Tool for creating device nodes.
+ GPL-2.0
+
+
+ mklibs
+ 0.1.43
+ mklibs produces cut-down shared libraries that contain only the routines required by a particular set of executables.
+ GPL-2.0
+
+
+ modemmanager
+ 1.7.991
+ ModemManager is a DBus-activated daemon which controls mobile broadband (2G/3G/4G) devices and connections
+ GPL-2.0, LGPL-2.1
+
+
+ mokutil
+ 0.3.0
+ The utility to manipulate machines owner keys which managed in shim.
+ GPL-3.0
+
+
+ mozjs
+ 17.0.0
+ SpiderMonkey is Mozilla's JavaScript engine written in C/C++.
+ MPL-2.0
+
+
+ mpfr
+ 3.1.5
+ C library for multiple-precision floating-point computations with exact rounding.
+ GPL-3.0, LGPL-3.0
+
+
+ mtools
+ 4.0.18
+ Mtools is a collection of utilities to access MS-DOS disks from GNU and Unix without mounting them.
+ GPL-3.0
+
+
+ nasm
+ 2.13.01
+ General-purpose x86 assembler.
+ BSD-2-Clause
+
+
+ ncurses
+ 6.0
+ SVr4 and XSI-Curses compatible curses library and terminfo tools including tic infocmp captoinfo. Supports color multiple highlights forms-drawing characters and automatic recognition of keypad and function-key sequences. Extensions include resizable windows and mouse support on both xterm and Linux console using the gpm library.
+ MIT
+
+
+ net-snmp
+ 5.7.3
+ Various tools relating to the Simple Network Management Protocol.
+ BSD
+
+
+ net-tools
+ 1.60-26
+ A collection of programs that form the base set of the NET-3 networking distribution for the Linux operating system
+ GPL-2.0
+
+
+ netbase
+ 5.4
+ This package provides the necessary infrastructure for basic TCP/IP based networking
+ GPL-2.0
+
+
+ netcat-openbsd
+ 1.105
+ A simple Unix utility which reads and writes data across network connections using TCP or UDP protocol. It is designed to be a reliable 'back-end' tool that can be used directly or easily driven by other programs and scripts. At the same time it is a feature-rich network debugging and exploration tool since it can create almost any kind of connection you would need and has several interesting built-in capabilities.
+ BSD-3-Clause
+
+
+ netcf
+ 0.2.8
+ netcf is a cross-platform network configuration library.
+ LGPL-2.1
+
+
+ nettle
+ 3.3
+ A low level cryptographic library.
+ LGPL-3.0, GPL-2.0
+
+
+ networkmanager
+ 1.10.10
+ NetworkManager.
+ GPL-2.0
+
+
+ nfv-init
+ 1.0
+ Enea service expected to be run after cloud-init
+ Enea
+
+
+ nfv-installer
+ 1.0
+ Enea NFV Access installer
+ Enea
+
+
+ nfva-cfgtool
+ 1.0
+ Command line tool to for accessing the Enea NFV Access install configuration json file
+ Enea
+
+
+ nfva-hotfixes
+ 1.0
+ Different hotfixes
+ Enea
+
+
+ nfva-startup
+ 1.0
+ Service that configures the network according to installer settings
+ Enea
+
+
+ nodejs
+ 8.4.0
+ nodeJS Evented I/O for V8 JavaScript
+ MIT, BSD, Artistic-2.0
+
+
+ notary
+ 0.4.2
+ Notary is a Docker project that allows anyone to have trust over arbitrary collections of data
+ Apache-2.0
+
+
+ nspr
+ 4.16
+ Netscape Portable Runtime Library.
+ GPL-2.0, MPL-2.0, LGPL-2.1
+
+
+ nss
+ 3.31.1
+ Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3 TLS PKCS 5 PKCS 7 PKCS 11 PKCS 12 S/MIME X.509 v3 certificates and other security standards.
+ MPL-2.0, GPL-2.0, MPL-2.0, LGPL-2.1
+
+
+ ntp-user-stub
+ 1.0
+ The NTP user/group were added in previous NFVA releases and are needed for OSTree upgrades to ensure backwards compatibility.
+ Enea
+
+
+ numactl
+ 2.0.11
+ Simple NUMA policy support. It consists of a numactl program to run other programs with a specific NUMA policy and a libnuma to do allocations with NUMA policy in applications.
+ GPL-2.0, LGPL-2.1
+
+
+ onig
+ 5.9.6
+ Regular expressions library. The characteristics of this library is that different character encoding for every regular expression object can be specified.
+ BSD
+
+
+ openipmi
+ 2.0.24
+ OpenIPMI is an effort to create a full-function IPMI system to allow full access to all IPMI information on a server and to abstract it to a level that will make it easy to use
+ GPL-2.0, LGPL-2.1, BSD
+
+
+ openjdk-8
+ 102b14
+ Java runtime based upon the OpenJDK Project
+ GPL-2.0-with-classpath-exception
+
+
+ openssh
+ 7.5p1
+ Secure rlogin/rsh/rcp/telnet replacement (OpenSSH) Ssh (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine.
+ BSD
+
+
+ openssl
+ 1.0.2o
+ Secure Socket Layer (SSL) binary and related cryptographic tools.
+ OpenSSL
+
+
+ openvswitch
+ 2.9
+ Open vSwitch is a production quality multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension while still supporting standard management interfaces and protocols (e.g. NetFlow sFlow SPAN RSPAN CLI LACP 802.1ag)
+ Apache-2.0
+
+
+ opkg-utils
+ 0.3.5
+ Additional utilities for the opkg package manager.
+ GPL-2.0
+
+
+ oro
+ 2.0.8
+ Perl5-compatible regular expressions library for Java
+ Apache-2.0
+
+
+ os-release
+ 1.0
+ The /etc/os-release file contains operating system identification data.
+ MIT
+
+
+ ostree-initrd
+ 3
+ Extremely basic live image init script.
+ MIT
+
+
+ ostree-rw
+ 1.0
+ Enea bash script to make current ostree hash writable
+ Enea
+
+
+ ostree
+ v2018.7
+ Tool for managing bootable immutable versioned filesystem trees.
+ LGPL-2.0
+
+
+ packagegroup-core-boot
+ 1.0
+ The minimal set of packages required to boot the system
+ MIT
+
+
+ packagegroup-core-ssh-openssh
+ 1.0
+ OpenSSH SSH client/server.
+ MIT
+
+
+ packagegroup-efi-secure-boot
+ 1.0
+ EFI Secure Boot packages for secure-environment.
+ MIT
+
+
+ packagegroup-enea-telemetry
+ 1.0
+ Packages for Telemetry.
+ MIT
+
+
+ packagegroup-enea-virtualization-4gusb-modems
+ 1.0
+ Packagegroup for 4G usb modems.
+ MIT
+
+
+ packagegroup-enea-virtualization-docker
+ 1.0
+ Packagegroup for Docker.
+ MIT
+
+
+ packagegroup-enea-virtualization-dpdk
+ 1.0
+ Packagegroup for DPDK.
+ MIT
+
+
+ packagegroup-enea-virtualization-guest
+ 1.0
+ This package group includes packages and packagegroups specific to the guest side of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-virtualization-host
+ 1.0
+ This package group includes packages and packagegroups specific to the host side of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-virtualization-libvirt
+ 1.0
+ Package group for libvirt.
+ MIT
+
+
+ packagegroup-enea-virtualization-lxc
+ 1.0
+ Packagegroup for LXC.
+ MIT
+
+
+ packagegroup-enea-virtualization-lxd
+ 1.0
+ Packagegroup for LXD.
+ MIT
+
+
+ packagegroup-enea-virtualization-ovs
+ 1.0
+ Packagegroup for Open vSwitch.
+ MIT
+
+
+ packagegroup-enea-virtualization-qemu
+ 1.0
+ Packagegroup for QEMU.
+ MIT
+
+
+ packagegroup-enea-virtualization
+ 1.0
+ This packagegroup includes packages and packagegroups required for both host and guest images of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-wifi
+ 1.0
+ This package group includes packages and packagegroups that enable WiFi connectivity in the Enea NFV Access platform
+ MIT
+
+
+ pango
+ 1.40.6
+ Pango is a library for laying out and rendering of text with an emphasis on internationalization. Pango can be used anywhere that text layout is needed though most of the work on Pango so far has been done in the context of the GTK+ widget toolkit. Pango forms the core of text and font handling for GTK+-2.x.
+ LGPL-2.0
+
+
+ parted
+ 3.2
+ Disk partition editing/resizing utility.
+ GPL-3.0
+
+
+ partrt
+ 1.1
+ partrt is a tool for dividing a SMP Linux system into a real time domain and a non-real time domain.
+ BSD
+
+
+ pciutils
+ 3.5.5
+ The PCI Utilities package contains a library for portable access to PCI bus configuration space and several utilities based on this library.
+ GPL-2.0
+
+
+ perl
+ 5.24.1
+ Perl scripting language.
+ Artistic-1.0, GPL-1.0
+
+
+ pigz
+ 2.3.4
+ pigz which stands for parallel implementation of gzip is a fully functional replacement for gzip that exploits multiple processors and multiple cores to the hilt when compressing data. pigz was written by Mark Adler and uses the zlib and pthread libraries.
+ Zlib, Apache-2.0
+
+
+ pixman
+ 0.34.0
+ Pixman provides a library for manipulating pixel regions -- a set of Y-X banded rectangles image compositing using the Porter/Duff model and implicit mask generation for geometric primitives including trapezoids triangles and rectangles.
+ MIT, PD
+
+
+ pkgconfig
+ 0.29.2
+ pkg-config is a helper tool used when compiling applications and libraries. It helps determined the correct compiler/link options. It is also language-agnostic.
+ GPL-2.0
+
+
+ pm-utils
+ 1.4.1
+ Simple shell command line tools to suspend and hibernate.
+ GPL-2.0
+
+
+ polkit
+ 0.113
+ The polkit package is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes.
+ LGPL-2.0
+
+
+ popt
+ 1.16
+ Library for parsing command line options.
+ MIT
+
+
+ prelink
+ 1.0
+ The prelink package contains a utility which modifies ELF shared libraries and executables so that far fewer relocations need to be resolved at runtime and thus programs come up faster.
+ GPL-2.0
+
+
+ procps
+ 3.3.12
+ Procps contains a set of system utilities that provide system information about processes using the /proc filesystem. The package includes the programs ps top vmstat w kill and skill.
+ GPL-2.0, LGPL-2.0
+
+
+ pseudo
+ 1.8.2
+ Pseudo gives fake root capabilities to a normal user.
+ LGPL-2.1
+
+
+ ptest-runner
+ 2.1
+ The ptest-runner2 package installs a ptest-runner program which loops through all installed ptest test suites and runs them in sequence.
+ GPL-2.0
+
+
+ python-asn1crypto
+ 0.23.0
+ Python binding to the Networking and Cryptography (NaCl) library
+ Apache-2.0
+
+
+ python-certifi
+ 2017.7.27.1
+ This installable Python package contains a CA Bundle that you can reference in your Python code. This is useful for verifying HTTP requests for example. This is the same CA Bundle which ships with the Requests codebase and is derived from Mozilla Firefox's canonical set.
+ ISC
+
+
+ python-cffi
+ 1.11.2
+ Foreign Function Interface for Python calling C code.
+ MIT
+
+
+ python-chardet
+ 3.0.4
+ Universal encoding detector for Python 2 and 3.
+ LGPL-2.1
+
+
+ python-cryptography-vectors
+ 2.0.3
+ Test vectors for the cryptography package..
+ Apache-2.0, BSD
+
+
+ python-cryptography
+ 2.0.3
+ Provides cryptographic recipes and primitives to python developers.
+ Apache-2.0, BSD
+
+
+ python-cython
+ 0.27.1
+ Cython is a language specially designed for writing Python extension modules. It's designed to bridge the gap between the nice high-level easy-to-use world of Python and the messy low-level world of C.
+ Apache-2.0
+
+
+ python-enum34
+ 1.1.6
+ backport of Python 3.4's enum package.
+ BSD-3-Clause
+
+
+ python-functools32
+ 3.2.3-2
+ Backport of the functools module from Python 3.2.3 for use on 2.7 and PyPy..
+ Python-2.0
+
+
+ python-futures
+ 3.0.5
+ The concurrent.futures module provides a high-level interface for asynchronously executing callables.
+ BSD
+
+
+ python-idna
+ 2.6
+ Internationalised Domain Names in Applications.
+ BSD-3-Clause, Python-2.0, Unicode
+
+
+ python-ipaddress
+ 1.0.18
+ Python 3.3+'s ipaddress for Python 2.6 2.7 3.2..
+ Python-2.0
+
+
+ python-iso8601
+ 0.1.12
+ Simple module to parse ISO 8601 dates.
+ MIT
+
+
+ python-jsonpatch
+ 1.16
+ Appling JSON patches in Python 2.6+ and 3.x.
+ BSD
+
+
+ python-jsonpointer
+ 1.12
+ Resolve JSON Pointers in Python.
+ BSD
+
+
+ python-jsonschema
+ 2.6.0
+ An implementation of JSON Schema validation for Python.
+ MIT
+
+
+ python-m2crypto
+ 0.26.4
+ A Python crypto and SSL toolkit.
+ BSD
+
+
+ python-ndg-httpsclient
+ 0.4.3
+ Provides enhanced HTTPS support for httplib and urllib2 using PyOpenSSL
+ BSD
+
+
+ python-netaddr
+ 0.7.19
+ A network address manipulation library for Python..
+ BSD
+
+
+ python-netifaces
+ 0.10.6
+ Portable network interface information.
+ MIT
+
+
+ python-pip
+ 9.0.1
+ PIP is a tool for installing and managing Python packages.
+ MIT, LGPL-2.1
+
+
+ python-pretend
+ 1.0.8
+ A library for stubbing in Python.
+ BSD
+
+
+ python-prettytable
+ 0.7.2
+ Python library for displaying tabular data in a ASCII table format.
+ BSD
+
+
+ python-psutil
+ 5.3.1
+ A cross-platform process and system utilities module for Python.
+ BSD
+
+
+ python-py
+ 1.4.34
+ Library with cross-python path ini-parsing io code log facilities.
+ MIT
+
+
+ python-pyasn1
+ 0.3.6
+ Python library implementing ASN.1 types..
+ BSD-2-Clause
+
+
+ python-pycparser
+ 2.18
+ Parser of the C language written in pure Python.
+ BSD-3-Clause
+
+
+ python-pyopenssl
+ 17.3.0
+ Simple Python wrapper around the OpenSSL library.
+ Apache-2.0
+
+
+ python-pysocks
+ 1.6.7
+ A Python SOCKS client module
+ BSD
+
+
+ python-pytest-runner
+ 2.12.1
+ Invoke py.test as distutils command with dependency resolution.
+ MIT
+
+
+ python-pytest
+ 3.2.2
+ Simple powerful teting with python.
+ MIT
+
+
+ python-pyyaml
+ 3.11
+ YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. . PyYAML features a complete YAML 1.1 parser Unicode support pickle support capable extension API and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. . PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistance.
+ MIT
+
+
+ python-requests
+ 2.18.4
+ Python HTTP for Humans.
+ Apache-2.0
+
+
+ python-rfc3987
+ 1.3.7
+ Parsing and validation of URIs (RFC 3986) and IRIs (RFC 3987).
+ GPL-3.0
+
+
+ python-setuptools-scm
+ 1.15.6
+ the blessed package to manage your versions by scm tags.
+ MIT
+
+
+ python-setuptools
+ 36.2.7
+ Download build install upgrade and uninstall Python packages.
+ MIT
+
+
+ python-six
+ 1.11.0
+ Python 2 and 3 compatibility library.
+ MIT
+
+
+ python-strict-rfc3339
+ 0.7
+ Strict simple lightweight RFC3339 function.s.
+ GPL-3.0
+
+
+ python-typing
+ 3.6.2
+ Simple Python module defined by PEP 484..
+ Python-2.0
+
+
+ python-urllib3
+ 1.22
+ Python HTTP library with thread-safe connection pooling file post support sanity friendly and more.
+ MIT
+
+
+ python-vcversioner
+ 2.16.0.0
+ Python vcversioner automagically update the project's version.
+ ISC
+
+
+ python
+ 2.7.13
+ The Python Programming Language.
+ Python-2.0
+
+
+ python3-netifaces
+ 0.10.6
+ Portable network interface information.
+ MIT
+
+
+ python3-pip
+ 9.0.1
+ The PyPA recommended tool for installing Python packages.
+ MIT
+
+
+ python3-setuptools
+ 36.2.7
+ Download build install upgrade and uninstall Python packages.
+ MIT
+
+
+ python3-six
+ 1.10.0
+ Python 2 and 3 compatibility library.
+ MIT
+
+
+ python3-twisted
+ 13.2.0
+ Twisted is an event-driven networking framework written in Python and licensed under the LGPL. Twisted supports TCP UDP SSL/TLS multicast Unix sockets a large number of protocols (including HTTP NNTP IMAP SSH IRC FTP and others) and much more.
+ MIT
+
+
+ python3-zopeinterface
+ 4.4.3
+ Interface definitions for Zope products.
+ ZPL-2.1
+
+
+ python3
+ 3.5.3
+ The Python Programming Language.
+ Python-2.0
+
+
+ qemu-helper
+ 1.0
+ Helper utilities needed by the runqemu script.
+ GPL-2.0
+
+
+ qemu
+ 2.11.1
+ Fast open source processor emulator.
+ GPL-2.0, LGPL-2.1
+
+
+ qemuwrapper
+ 1.0
+ QEMU wrapper script.
+ MIT
+
+
+ quilt
+ 0.65
+ Tool for working with series of patches.
+ GPL-2.0
+
+
+ randrproto
+ 1.5.0
+ This package provides the wire protocol for the X Resize Rotate and Reflect extension. This extension provides the ability to resize rotate and reflect the root window of a screen.
+ MIT
+
+
+ readline
+ 7.0
+ The GNU Readline library provides a set of functions for use by applications that allow users to edit command lines as they are typed in. Both Emacs and vi editing modes are available. The Readline library includes additional functions to maintain a list of previously-entered command lines to recall and perhaps reedit those lines and perform csh-like history expansion on previous commands.
+ GPL-3.0
+
+
+ regexp
+ 1.5
+ Java Regular Expression package
+ Apache-2.0
+
+
+ renderproto
+ 0.11.1
+ This package provides the wire protocol for the X Rendering extension. This is the basis the image composition within the X window system.
+ MIT
+
+
+ rhino
+ 1.7r4
+ Lexical analyzer generator for Java
+ MPL-2.0
+
+
+ rpm
+ 4.13.90
+ The RPM Package Manager (RPM) is a powerful command line driven package management system capable of installing uninstalling verifying querying and updating software packages. Each software package consists of an archive of files along with information about the package like its version a description etc.
+ GPL-2.0
+
+
+ rrdtool
+ 1.6.0
+ High performance data logging and graphing system for time series data.
+ GPL-2.0
+
+
+ rsync
+ 3.1.3
+ File synchronization tool.
+ GPL-3.0
+
+
+ run-postinsts
+ 1.0
+ Runs postinstall scripts on first boot of the target device.
+ MIT
+
+
+ runc-docker
+ 1.0.0-rc3
+ runc is a CLI tool for spawning and running containers according to the OCI specification.
+ Apache-2.0
+
+
+ sbsigntool
+ 0.6
+ Utilities for signing UEFI binaries for use with secure boot.
+ GPL-3.0
+
+
+ sed
+ 4.2.2
+ Stream EDitor (text filtering utility).
+ GPL-3.0
+
+
+ seloader
+ 0.4.6
+ The SELoader is designed to authenticate the non-PE files such as grub configuration initrd grub modules which cannot be verified by the MOK Verify Protocol registered by shim loader. In order to conveniently authenticate the PE file with gBS->LoadImage() and gBS->StartImage() the SELoader hooks EFI Security2 Architectural Protocol and employs MOK Verify Protocol to verify the PE file. If only UEFI Secure Boot is enabled the SELoader just simplily calls gBS->LoadImage() and gBS->StartImage() to allow BIOS to verify PE file. The SELoader publishes MOK2 Verify Protocol which provides a flexible interface to allow the bootloader to verify the file file buffer or memory buffer without knowing the file format.
+ BSD-3-Clause
+
+
+ servlet2.3
+ 4.1.37
+ Servlet API 2.3 (from Tomcat 4.1)
+ Apache-2.0
+
+
+ shadow-securetty
+ 4.2.1
+ Provider of the machine specific securetty file.
+ MIT
+
+
+ shadow-sysroot
+ 4.2.1
+ Shadow utils requirements for useradd.bbclass.
+ BSD, Artistic-1.0
+
+
+ shadow
+ 4.2.1
+ Tools to change and administer password and group data.
+ BSD, Artistic-1.0
+
+
+ shared-mime-info
+ 1.8
+ Shared MIME type database and specification.
+ LGPL-2.0
+
+
+ shim
+ 12
+ shim is a trivial EFI application that when run attempts to open and execute another application. It will initially attempt to do this via the standard EFI LoadImage() and StartImage() calls. If these fail (because secure boot is enabled and the binary is not signed with an appropriate key for instance) it will then validate the binary against a built-in certificate. If this succeeds and if the binary or signing key are not blacklisted then shim will relocate and execute the binary.
+ BSD-2-Clause
+
+
+ simpleproxy
+ 1.0
+ Simpleproxy.
+ GPL-2.0
+
+
+ slang
+ 2.3.1a
+ S-Lang is an interpreted language and a programming library. The S-Lang language was designed so that it can be easily embedded into a program to provide the program with a powerful extension language. The S-Lang library provided in this package provides the S-Lang extension language. S-Lang's syntax resembles C which makes it easy to recode S-Lang procedures in C if you need to.
+ GPL-2.0
+
+
+ sqlite3
+ 3.20.0
+ Embeddable SQL database engine.
+ PD
+
+
+ squashfs-tools
+ 4.3
+ Tools for manipulating SquashFS filesystems.
+ GPL-2.0, PD
+
+
+ sshpass
+ 1.06
+ Tool for non-interactivly performing ssh password authentication
+ GPL-2.0
+
+
+ swig
+ 3.0.12
+ SWIG - Simplified Wrapper and Interface Generator.
+ BSD, GPL-3.0
+
+
+ sysfsutils
+ 2.1.0
+ Tools for working with the sysfs virtual filesystem. The tool 'systool' can query devices by bus class and topology.
+ GPL-2.0, LGPL-2.1
+
+
+ sysklogd
+ 1.5.1
+ The sysklogd package implements two system log daemons: syslogd klogd
+ GPL-2.0, BSD
+
+
+ syslinux
+ 6.03
+ Multi-purpose linux bootloader.
+ GPL-2.0
+
+
+ systemd-boot
+ 234
+ systemd is a system and service 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.
+ GPL-2.0, LGPL-2.1
+
+
+ systemd-compat-units
+ 1.0
+ Enhances systemd compatilibity with existing SysVinit scripts.
+ MIT
+
+
+ systemd-serialgetty
+ 1.0
+ Serial terminal support for systemd.
+ GPL-2.0
+
+
+ systemd-systemctl
+ 1.0
+ Wrapper for enabling systemd services.
+ MIT
+
+
+ systemd
+ 234
+ systemd is a system and service 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.
+ GPL-2.0, LGPL-2.1
+
+
+ tar
+ 1.29
+ GNU tar saves many files together into a single tape or disk archive and can restore individual files from the archive.
+ GPL-3.0
+
+
+ tcl
+ 8.6.7
+ Tool Command Language.
+ tcl, BSD-3-Clause
+
+
+ tcpdump
+ 4.9.2
+ A sophisticated network protocol analyzer.
+ BSD
+
+
+ texinfo-dummy
+ 1.0
+ Fake version of the texinfo utility suite.
+ MIT
+
+
+ thin-provisioning-tools
+ 0.6.3
+ A suite of tools for manipulating the metadata of the dm-thin device-mapper target.
+ GPL-3.0
+
+
+ tunctl
+ 1.5
+ Tool for controlling the Linux TUN/TAP driver.
+ GPL-2.0
+
+
+ tzcode
+ 2018c
+ tzcode timezone zoneinfo utils -- zic zdump tzselect.
+ PD, BSD, BSD-3-Clause
+
+
+ tzdata
+ 2018c
+ Timezone data.
+ PD, BSD, BSD-3-Clause
+
+
+ udev-extraconf
+ 1.1
+ Extra machine specific configuration files for udev specifically blacklist information.
+ MIT
+
+
+ unifdef
+ 2.11
+ Selectively remove #ifdef statements from sources.
+ BSD-2-Clause
+
+
+ unzip
+ 6.0
+ Utilities for extracting and viewing files in .zip archives.
+ BSD-3-Clause
+
+
+ update-rc.d
+ 0.7
+ update-rc.d is a utility that allows the management of symlinks to the initscripts in the /etc/rcN.d directory structure.
+ GPL-2.0
+
+
+ usb-modeswitch-data
+ 20170205
+ Data files for usbmodeswitch.
+ GPL-2.0
+
+
+ usb-modeswitch
+ 2.5.0
+ A mode switching tool for controlling 'flip flop' (multiple device) USB gear.
+ GPL-2.0
+
+
+ usbutils
+ 013
+ Contains the lsusb utility for inspecting the devices connected to the USB bus.
+ GPL-2.0, GPL-3.0
+
+
+ util-linux
+ 2.30
+ Util-linux includes a suite of basic system administration utilities commonly found on most Linux systems. Some of the more important utilities include disk partitioning kernel message management filesystem creation and system login.
+ GPL-2.0, LGPL-2.1, BSD
+
+
+ util-macros
+ 1.19.1
+ M4 autotools macros used by various X.org programs.
+ MIT
+
+
+ v86d
+ 0.1.10
+ User support binary for the uvesafb kernel module.
+ GPL-2.0
+
+
+ vala
+ 0.36.4
+ Vala is a C#-like language dedicated to ease GObject programming. Vala compiles to plain C and has no runtime environment nor penalities whatsoever.
+ LGPL-2.1
+
+
+ volatile-binds
+ 1.0
+ Volatile bind mount setup and configuration for read-only-rootfs
+ MIT
+
+
+ web-installer-backend
+ 0.1
+ Web installer go server
+ Enea, BSD-3-Clause
+
+
+ web-installer-frontend
+ 0.1
+ Web installer post-install application
+ Enea, Apache-2.0, BSD, BSD-2-Clause, BSD-3-Clause, CC-BY-4.0, ISC, MIT, Zlib
+
+
+ which
+ 2.21
+ Which is a utility that prints out the full path of the executables that bash(1) would execute when the passed program names would have been entered on the shell prompt. It does this by using the exact same algorithm as bash.
+ GPL-3.0
+
+
+ wireless-regdb
+ 2020.11.20
+ Wireless Central Regulatory Domain Database.
+ ISC
+
+
+ wpa-supplicant
+ 2.6
+ Client for Wi-Fi Protected Access (WPA).
+ BSD
+
+
+ xalan-j
+ 2.7.1
+ Java XSLT processor
+ Apache-2.0
+
+
+ xcb-proto
+ 1.12
+ Function prototypes for the X protocol C-language Binding (XCB). XCB is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
+ MIT
+
+
+ xerces-j
+ 2.11.0
+ Reference implementation of XNI the Xerces Native Interface and also a fully conforming XML Schema processor.
+ Apache-2.0
+
+
+ xextproto
+ 7.3.0
+ This package provides the wire protocol for several X extensions. These protocol extensions include DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. In addition a small set of utility functions are also available.
+ MIT
+
+
+ xkeyboard-config
+ 2.21
+ The non-arch keyboard configuration database for X Window. The goal is to provide the consistent well-structured frequently released open source of X keyboard configuration data for X Window System implementations. The project is targeted to XKB-based systems.
+ MIT
+
+
+ xml-commons-resolver1.1
+ 1.2
+ Library to resolve various public or system identifiers into accessible URLs (Java)
+ Apache-2.0
+
+
+ xproto
+ 7.0.31
+ This package provides the basic headers for the X Window System.
+ MIT
+
+
+ xtrans
+ 1.3.5
+ The X Transport Interface is intended to combine all system and transport specific code into a single place. This API should be used by all libraries clients and servers of the X Window System. Use of this API should allow the addition of new types of transports and support for new platforms without making any changes to the source except in the X Transport Interface code.
+ MIT
+
+
+ xz
+ 5.2.3
+ Utilities for managing LZMA compressed files.
+ GPL-2.0, GPL-3.0-with-autoconf-exception, LGPL-2.1, PD
+
+
+ yajl
+ 2.1.0
+ YAJL is a small event-driven (SAX-style) JSON parser written in ANSI C and a small validating JSON generator.
+ ISC
+
+
+ zip
+ 3.0
+ Compressor/archiver for creating and modifying .zip files.
+ BSD-3-Clause
+
+
+ zisofs-tools
+ 1.0.8
+ Utilities for creating compressed CD-ROM filesystems.
+ GPL-2.0
+
+
+ zlib
+ 1.2.11
+ Zlib is a general-purpose patent-free lossless data compression library which is used by many different programs.
+ Zlib
+
+
+
+
+
+
+ Open Source Licenses
+
+AFL-2.0
+
+
+The Academic Free License
+ v. 2.0
+
+This Academic Free License (the "License") applies to any original work of authorship
+(the "Original Work") whose owner (the "Licensor") has placed the following notice
+immediately following the copyright notice for the Original Work:
+Licensed under the Academic Free License version 2.0
+
+1) Grant of Copyright License. Licensor hereby grants You a world-wide, royalty-free,
+non-exclusive, perpetual, sublicenseable license to do the following:
+a) to reproduce the Original Work in copies;
+
+b) to prepare derivative works ("Derivative Works") based upon the Original Work;
+
+c) to distribute copies of the Original Work and Derivative Works to the public;
+
+d) to perform the Original Work publicly; and
+
+e) to display the Original Work publicly.
+
+2) Grant of Patent License. Licensor hereby grants You a world-wide, royalty-free,
+non-exclusive, perpetual, sublicenseable license, under patent claims owned or
+controlled by the Licensor that are embodied in the Original Work as furnished by the
+Licensor, to make, use, sell and offer for sale the Original Work and Derivative
+Works.
+
+3) Grant of Source Code License. The term "Source Code" means the preferred form of
+the Original Work for making modifications to it and all available documentation
+describing how to modify the Original Work. Licensor hereby agrees to provide a
+machine-readable copy of the Source Code of the Original Work along with each copy of
+the Original Work that Licensor distributes. Licensor reserves the right to satisfy
+this obligation by placing a machine-readable copy of the Source Code in an
+information repository reasonably calculated to permit inexpensive and convenient
+access by You for as long as Licensor continues to distribute the Original Work, and
+by publishing the address of that information repository in a notice immediately
+following the copyright notice that applies to the Original Work.
+
+4) Exclusions From License Grant. Neither the names of Licensor, nor the names of any
+contributors to the Original Work, nor any of their trademarks or service marks, may
+be used to endorse or promote products derived from this Original Work without express
+prior written permission of the Licensor. Nothing in this License shall be deemed to
+grant any rights to trademarks, copyrights, patents, trade secrets or any other
+intellectual property of Licensor except as expressly stated herein. No patent
+license is granted to make, use, sell or offer to sell embodiments of any patent
+claims other than the licensed claims defined in Section 2. No right is granted to
+the trademarks of Licensor even if such marks are included in the Original Work.
+Nothing in this License shall be interpreted to prohibit Licensor from licensing under
+different terms from this License any Original Work that Licensor otherwise would have
+a right to license.
+
+5) This section intentionally omitted.
+
+6) Attribution Rights. You must retain, in the Source Code of any Derivative Works
+that You create, all copyright, patent or trademark notices from the Source Code of
+the Original Work, as well as any notices of licensing and any descriptive text
+identified therein as an "Attribution Notice." You must cause the Source Code for any
+Derivative Works that You create to carry a prominent Attribution Notice reasonably
+calculated to inform recipients that You have modified the Original Work.
+
+7) Warranty of Provenance and Disclaimer of Warranty. Licensor warrants that the
+copyright in and to the Original Work and the patent rights granted herein by Licensor
+are owned by the Licensor or are sublicensed to You under the terms of this License
+with the permission of the contributor(s) of those copyrights and patent rights.
+Except as expressly stated in the immediately proceeding sentence, the Original Work
+is provided under this License on an "AS IS" BASIS and WITHOUT WARRANTY, either
+express or implied, including, without limitation, the warranties of NON-INFRINGEMENT,
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+QUALITY OF THE ORIGINAL WORK IS WITH YOU. This DISCLAIMER OF WARRANTY constitutes an
+essential part of this License. No license to Original Work is granted hereunder
+except under this disclaimer.
+
+8) Limitation of Liability. Under no circumstances and under no legal theory, whether
+in tort (including negligence), contract, or otherwise, shall the Licensor be liable
+to any person for any direct, indirect, special, incidental, or consequential damages
+of any character arising as a result of this License or the use of the Original Work
+including, without limitation, damages for loss of goodwill, work stoppage, computer
+failure or malfunction, or any and all other commercial damages or losses. This
+limitation of liability shall not apply to liability for death or personal injury
+resulting from Licensor`s negligence to the extent applicable law prohibits such
+limitation. Some jurisdictions do not allow the exclusion or limitation of incidental
+or consequential damages, so this exclusion and limitation may not apply to You.
+
+9) Acceptance and Termination. If You distribute copies of the Original Work or a
+Derivative Work, You must make a reasonable effort under the circumstances to obtain
+the express assent of recipients to the terms of this License. Nothing else but this
+License (or another written agreement between Licensor and You) grants You permission
+to create Derivative Works based upon the Original Work or to exercise any of the
+rights granted in Section 1 herein, and any attempt to do so except under the terms of
+this License (or another written agreement between Licensor and You) is expressly
+prohibited by U.S. copyright law, the equivalent laws of other countries, and by
+international treaty. Therefore, by exercising any of the rights granted to You in
+Section 1 herein, You indicate Your acceptance of this License and all of its terms
+and conditions.
+
+10) Termination for Patent Action. This License shall terminate automatically and You
+may no longer exercise any of the rights granted to You by this License as of the date
+You commence an action, including a cross-claim or counterclaim, for patent
+infringement (i) against Licensor with respect to a patent applicable to software or
+(ii) against any entity with respect to a patent applicable to the Original Work (but
+excluding combinations of the Original Work with other software or hardware).
+
+11) Jurisdiction, Venue and Governing Law. Any action or suit relating to this License
+may be brought only in the courts of a jurisdiction wherein the Licensor resides or in
+which Licensor conducts its primary business, and under the laws of that jurisdiction
+excluding its conflict-of-law provisions. The application of the United Nations
+Convention on Contracts for the International Sale of Goods is expressly excluded.
+Any use of the Original Work outside the scope of this License or after its
+termination shall be subject to the requirements and penalties of the U.S. Copyright
+Act, 17 U.S.C. ¤ 101 et seq., the equivalent laws of other countries, and
+international treaty. This section shall survive the termination of this License.
+
+12) Attorneys Fees. In any action to enforce the terms of this License or seeking
+damages relating thereto, the prevailing party shall be entitled to recover its costs
+and expenses, including, without limitation, reasonable attorneys` fees and costs
+incurred in connection with such action, including any appeal of such action. This
+section shall survive the termination of this License.
+
+13) Miscellaneous. This License represents the complete agreement concerning the
+subject matter hereof. If any provision of this License is held to be unenforceable,
+such provision shall be reformed only to the extent necessary to make it enforceable.
+
+14) Definition of "You" in This License. "You" throughout this License, whether in
+upper or lower case, means an individual or a legal entity exercising rights under,
+and complying with all of the terms of, this License. For legal entities, "You"
+includes any entity that controls, is controlled by, or is under common control with
+you. For purposes of this definition, "control" means (i) the power, direct or
+indirect, to cause the direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares,
+or (iii) beneficial ownership of such entity.
+
+15) Right to Use. You may use the Original Work in all ways not otherwise restricted
+or conditioned by this License or by law, and Licensor promises not to interfere with
+or be responsible for such uses by You.
+
+This license is Copyright (C) 2003 Lawrence E. Rosen. All rights reserved.
+Permission is hereby granted to copy and distribute this license without modification.
+This license may not be modified without the express written permission of its
+copyright owner.
+
+
+
+
+AMD
+
+� 2005 Advanced Micro Devices, Inc. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that existing copyright notices
+are retained in all copies, this notice is included verbatim in any
+distributions, and the terms and conditions hererin are met.
+
+Use of the this software manifests acceptance of the terms of this
+license by performance.
+
+The name of Advanced Micro Devices, Inc. may not be used to endorse or
+promote products derived from this software without specific prior
+written permission.
+
+THIS SOFTWARE IS PROVIDED BY ADVANCED MICRO DEVICES, INC. "AS IS" AND ANY
+EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+PURPOSE AND NON-INFRINGEMENT, OR THOSE ARISING FROM CUSTOM OF TRADE OR
+COURSE OF USAGE ARE DISCLAIMED.
+
+IN NO EVENT SHALL ADVANCED MICRO DEVICES, INC. BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED, AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE ITS DOCUMENTATION OR ANY DERIVATIVES
+THEREOF, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BY USING THIS
+SOFTWARE WITHOUT CHARGE, YOU ACCEPT THIS ALLOCATION OF RISK. THIS
+DISCLAIMER OF LIABILITY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE.
+ADVANCED MICRO DEVICES, INC. HAS NO OBLIGATION TO PROVIDE MAINTENANCE,
+SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS OF THIS SOFTWARE.
+
+In the redistribution and use of this software, each party shall at all
+times comply with all applicable governmental laws, statutes, ordinances,
+rules, regulations, orders, and other requirements, including without
+limitation such governmental requirements applicable to environmental
+protection, health, safety, wages, hours, equal employment opportunity,
+nondiscrimination, working conditions, import or export control, and
+transportation. Without limiting the foregoing, each party shall adhere
+to the U.S. Export Administration Regulations (EAR), currently found at
+15 C.F.R. Sections 730 through 744, and, unless properly authorized by
+the U.S. Government, shall not (1) export, re-export or release restricted
+technology, software, or source code to a national of a country in Country
+Groups D:1 or E:1, or (2) export to Country Groups D:1 or E:1 the direct
+product of such technology or software, if such foreign produced direct
+product is subject to national security controls as identified on the
+Commerce Control List (currently found in Supplement 1 to Section 774 of EAR).
+These export requirements shall survive any expiration or termination
+of this agreement.
+
+
+
+Apache-2.0
+
+
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don`t include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+
+
+
+Artistic-1.0
+
+
+The Artistic License
+Preamble
+
+The intent of this document is to state the conditions under which a Package may be
+copied, such that the Copyright Holder maintains some semblance of artistic control
+over the development of the package, while giving the users of the package the right
+to use and distribute the Package in a more-or-less customary fashion, plus the right
+to make reasonable modifications.
+
+Definitions:
+
+"Package" refers to the collection of files distributed by the Copyright Holder, and
+derivatives of that collection of files created through textual modification.
+"Standard Version" refers to such a Package if it has not been modified, or has been
+modified in accordance with the wishes of the Copyright Holder.
+"Copyright Holder" is whoever is named in the copyright or copyrights for the package.
+"You" is you, if you`re thinking about copying or distributing this Package.
+"Reasonable copying fee" is whatever you can justify on the basis of media cost,
+duplication charges, time of people involved, and so on. (You will not be required to
+justify it to the Copyright Holder, but only to the computing community at large as a
+market that must bear the fee.)
+"Freely Available" means that no fee is charged for the item itself, though there may
+be fees involved in handling the item. It also means that recipients of the item may
+redistribute it under the same conditions they received it.
+1. You may make and give away verbatim copies of the source form of the Standard
+Version of this Package without restriction, provided that you duplicate all of the
+original copyright notices and associated disclaimers.
+
+2. You may apply bug fixes, portability fixes and other modifications derived from the
+Public Domain or from the Copyright Holder. A Package modified in such a way shall
+still be considered the Standard Version.
+
+3. You may otherwise modify your copy of this Package in any way, provided that you
+insert a prominent notice in each changed file stating how and when you changed that
+file, and provided that you do at least ONE of the following:
+
+a) place your modifications in the Public Domain or otherwise make them Freely
+Available, such as by posting said modifications to Usenet or an equivalent medium, or
+placing the modifications on a major archive site 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.
+
+4. You may distribute the programs of this Package in object code or executable form,
+provided that you do at least ONE of the following:
+
+a) distribute a Standard Version of the executables and library files, together with
+instructions (in the manual page or equivalent) on where to get the Standard Version.
+
+b) accompany the distribution with the machine-readable source of the Package with
+your modifications.
+
+c) accompany any non-standard executables with their corresponding Standard Version
+executables, giving the non-standard executables non-standard names, and clearly
+documenting the differences in manual pages (or equivalent), together with
+instructions on where to get the Standard Version.
+
+d) make other distribution arrangements with the Copyright Holder.
+
+5. You may charge a reasonable copying fee for any distribution of this Package. You
+may charge any fee you choose for support of this Package. You may not charge a fee
+for this Package itself. However, you may distribute this Package in aggregate with
+other (possibly commercial) programs as part of a larger (possibly commercial)
+software distribution provided that you do not advertise this Package as a product of
+your own.
+
+6. The scripts and library files supplied as input to or produced as output from the
+programs of this Package do not automatically fall under the copyright of this
+Package, but belong to whomever generated them, and may be sold commercially, and may
+be aggregated with this Package.
+
+7. C or perl subroutines supplied by you and linked into this Package shall not be
+considered part of this Package.
+
+8. The name of the Copyright Holder may not be used to endorse or promote products
+derived from this software without specific prior written permission.
+
+9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
+INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS
+FOR A PARTICULAR PURPOSE.
+
+The End
+
+
+
+
+Artistic-2.0
+
+
+ The Artistic License 2.0
+
+ Copyright (c) 2000-2006, The Perl Foundation.
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+Preamble
+
+This license establishes the terms under which a given free software
+Package may be copied, modified, distributed, and/or redistributed.
+The intent is that the Copyright Holder maintains some artistic
+control over the development of that Package while still keeping the
+Package available as open source and free software.
+
+You are always permitted to make arrangements wholly outside of this
+license directly with the Copyright Holder of a given Package. If the
+terms of this license do not permit the full use that you propose to
+make of the Package, you should contact the Copyright Holder and seek
+a different licensing arrangement.
+
+Definitions
+
+ "Copyright Holder" means the individual(s) or organization(s)
+ named in the copyright notice for the entire Package.
+
+ "Contributor" means any party that has contributed code or other
+ material to the Package, in accordance with the Copyright Holder`s
+ procedures.
+
+ "You" and "your" means any person who would like to copy,
+ distribute, or modify the Package.
+
+ "Package" means the collection of files distributed by the
+ Copyright Holder, and derivatives of that collection and/or of
+ those files. A given Package may consist of either the Standard
+ Version, or a Modified Version.
+
+ "Distribute" means providing a copy of the Package or making it
+ accessible to anyone else, or in the case of a company or
+ organization, to others outside of your company or organization.
+
+ "Distributor Fee" means any fee that you charge for Distributing
+ this Package or providing support for this Package to another
+ party. It does not mean licensing fees.
+
+ "Standard Version" refers to the Package if it has not been
+ modified, or has been modified only in ways explicitly requested
+ by the Copyright Holder.
+
+ "Modified Version" means the Package, if it has been changed, and
+ such changes were not explicitly requested by the Copyright
+ Holder.
+
+ "Original License" means this Artistic License as Distributed with
+ the Standard Version of the Package, in its current version or as
+ it may be modified by The Perl Foundation in the future.
+
+ "Source" form means the source code, documentation source, and
+ configuration files for the Package.
+
+ "Compiled" form means the compiled bytecode, object code, binary,
+ or any other form resulting from mechanical transformation or
+ translation of the Source form.
+
+
+Permission for Use and Modification Without Distribution
+
+(1) You are permitted to use the Standard Version and create and use
+Modified Versions for any purpose without restriction, provided that
+you do not Distribute the Modified Version.
+
+
+Permissions for Redistribution of the Standard Version
+
+(2) You may Distribute verbatim copies of the Source form of the
+Standard Version of this Package in any medium without restriction,
+either gratis or for a Distributor Fee, provided that you duplicate
+all of the original copyright notices and associated disclaimers. At
+your discretion, such verbatim copies may or may not include a
+Compiled form of the Package.
+
+(3) You may apply any bug fixes, portability changes, and other
+modifications made available from the Copyright Holder. The resulting
+Package will still be considered the Standard Version, and as such
+will be subject to the Original License.
+
+
+Distribution of Modified Versions of the Package as Source
+
+(4) You may Distribute your Modified Version as Source (either gratis
+or for a Distributor Fee, and with or without a Compiled form of the
+Modified Version) provided that you clearly document how it differs
+from the Standard Version, including, but not limited to, documenting
+any non-standard features, executables, or modules, and provided that
+you do at least ONE of the following:
+
+ (a) make the Modified Version available to the Copyright Holder
+ of the Standard Version, under the Original License, so that the
+ Copyright Holder may include your modifications in the Standard
+ Version.
+
+ (b) ensure that installation of your Modified Version does not
+ prevent the user installing or running the Standard Version. In
+ addition, the Modified Version must bear a name that is different
+ from the name of the Standard Version.
+
+ (c) allow anyone who receives a copy of the Modified Version to
+ make the Source form of the Modified Version available to others
+ under
+
+ (i) the Original License or
+
+ (ii) a license that permits the licensee to freely copy,
+ modify and redistribute the Modified Version using the same
+ licensing terms that apply to the copy that the licensee
+ received, and requires that the Source form of the Modified
+ Version, and of any works derived from it, be made freely
+ available in that license fees are prohibited but Distributor
+ Fees are allowed.
+
+
+Distribution of Compiled Forms of the Standard Version
+or Modified Versions without the Source
+
+(5) You may Distribute Compiled forms of the Standard Version without
+the Source, provided that you include complete instructions on how to
+get the Source of the Standard Version. Such instructions must be
+valid at the time of your distribution. If these instructions, at any
+time while you are carrying out such distribution, become invalid, you
+must provide new instructions on demand or cease further distribution.
+If you provide valid instructions or cease distribution within thirty
+days after you become aware that the instructions are invalid, then
+you do not forfeit any of your rights under this license.
+
+(6) You may Distribute a Modified Version in Compiled form without
+the Source, provided that you comply with Section 4 with respect to
+the Source of the Modified Version.
+
+
+Aggregating or Linking the Package
+
+(7) You may aggregate the Package (either the Standard Version or
+Modified Version) with other packages and Distribute the resulting
+aggregation provided that you do not charge a licensing fee for the
+Package. Distributor Fees are permitted, and licensing fees for other
+components in the aggregation are permitted. The terms of this license
+apply to the use and Distribution of the Standard or Modified Versions
+as included in the aggregation.
+
+(8) You are permitted to link Modified and Standard Versions with
+other works, to embed the Package in a larger work of your own, or to
+build stand-alone binary or bytecode versions of applications that
+include the Package, and Distribute the result without restriction,
+provided the result does not expose a direct interface to the Package.
+
+
+Items That are Not Considered Part of a Modified Version
+
+(9) Works (including, but not limited to, modules and scripts) that
+merely extend or make use of the Package, do not, by themselves, cause
+the Package to be a Modified Version. In addition, such works are not
+considered parts of the Package itself, and are not subject to the
+terms of this license.
+
+
+General Provisions
+
+(10) Any use, modification, and distribution of the Standard or
+Modified Versions is governed by this Artistic License. By using,
+modifying or distributing the Package, you accept this license. Do not
+use, modify, or distribute the Package, if you do not accept this
+license.
+
+(11) If your Modified Version has been derived from a Modified
+Version made by someone other than you, you are nevertheless required
+to ensure that your Modified Version complies with the requirements of
+this license.
+
+(12) This license does not grant you the right to use any trademark,
+service mark, tradename, or logo of the Copyright Holder.
+
+(13) This license includes the non-exclusive, worldwide,
+free-of-charge patent license to make, have made, use, offer to sell,
+sell, import and otherwise transfer the Package with respect to any
+patent claims licensable by the Copyright Holder that are necessarily
+infringed by the Package. If you institute patent litigation
+(including a cross-claim or counterclaim) against any party alleging
+that the Package constitutes direct or contributory patent
+infringement, then this Artistic License to you shall terminate on the
+date that such litigation is filed.
+
+(14) Disclaimer of Warranty:
+THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS
+IS` AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
+NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL
+LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL
+BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+BSD
+
+Copyright (c) The Regents of the University of California.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. Neither the name of the University nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+
+
+BSD-2-Clause
+
+
+The FreeBSD Copyright
+
+Copyright 1992-2010 The FreeBSD Project. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this list of
+conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright notice, this list of
+conditions and the following disclaimer in the documentation and/or other materials
+provided with the distribution.
+THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS`` AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD
+PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+The views and conclusions contained in the software and documentation are those of the
+authors and should not be interpreted as representing official policies, either
+expressed or implied, of the FreeBSD Project.
+
+
+
+
+BSD-3-Clause
+
+
+Copyright (c) <YEAR>, <OWNER>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this list of
+conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright notice, this list of
+conditions and the following disclaimer in the documentation and/or other materials
+provided with the distribution.
+Neither the name of the <ORGANIZATION> nor the names of its contributors may be
+used to endorse or promote products derived from this software without specific prior
+written permission.
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
+SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
+TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
+WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGE.
+
+
+
+
+BSD-4-Clause
+
+
+Copyright (c) <year>, <copyright holder>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. All advertising materials mentioning features or use of this software
+ must display the following acknowledgement:
+ This product includes software developed by the <organization>.
+4. Neither the name of the <organization> nor the
+ names of its contributors may be used to endorse or promote products
+ derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY <COPYRIGHT HOLDER> ``AS IS`` AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+BSL-1.0
+
+
+Boost Software License - Version 1.0 - August 17th, 2003
+
+Permission is hereby granted, free of charge, to any person or organization
+obtaining a copy of the software and accompanying documentation covered by
+this license (the "Software") to use, reproduce, display, distribute,
+execute, and transmit the Software, and to prepare derivative works of the
+Software, and to permit third-parties to whom the Software is furnished to
+do so, all subject to the following:
+
+The copyright notices in the Software and this entire statement, including
+the above license grant, this restriction and the following disclaimer,
+must be included in all copies of the Software, in whole or in part, and
+all derivative works of the Software, unless such copies or derivative
+works are solely in the form of machine-executable object code generated by
+a source language processor.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
+SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
+FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
+ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.
+
+
+
+
+CC-BY-4.0
+
+Attribution 4.0 International
+
+=======================================================================
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and
+does not provide legal services or legal advice. Distribution of
+Creative Commons public licenses does not create a lawyer-client or
+other relationship. Creative Commons makes its licenses and related
+information available on an "as-is" basis. Creative Commons gives no
+warranties regarding its licenses, any material licensed under their
+terms and conditions, or any related information. Creative Commons
+disclaims all liability for damages resulting from their use to the
+fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and
+conditions that creators and other rights holders may use to share
+original works of authorship and other material subject to copyright
+and certain other rights specified in the public license below. The
+following considerations are for informational purposes only, are not
+exhaustive, and do not form part of our licenses.
+
+ Considerations for licensors: Our public licenses are
+ intended for use by those authorized to give the public
+ permission to use material in ways otherwise restricted by
+ copyright and certain other rights. Our licenses are
+ irrevocable. Licensors should read and understand the terms
+ and conditions of the license they choose before applying it.
+ Licensors should also secure all rights necessary before
+ applying our licenses so that the public can reuse the
+ material as expected. Licensors should clearly mark any
+ material not subject to the license. This includes other CC-
+ licensed material, or material used under an exception or
+ limitation to copyright. More considerations for licensors:
+ wiki.creativecommons.org/Considerations_for_licensors
+
+ Considerations for the public: By using one of our public
+ licenses, a licensor grants the public permission to use the
+ licensed material under specified terms and conditions. If
+ the licensor's permission is not necessary for any reason--for
+ example, because of any applicable exception or limitation to
+ copyright--then that use is not regulated by the license. Our
+ licenses grant only permissions under copyright and certain
+ other rights that a licensor has authority to grant. Use of
+ the licensed material may still be restricted for other
+ reasons, including because others have copyright or other
+ rights in the material. A licensor may make special requests,
+ such as asking that all changes be marked or described.
+ Although not required by our licenses, you are encouraged to
+ respect those requests where reasonable. More_considerations
+ for the public:
+ wiki.creativecommons.org/Considerations_for_licensees
+
+=======================================================================
+
+Creative Commons Attribution 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree
+to be bound by the terms and conditions of this Creative Commons
+Attribution 4.0 International Public License ("Public License"). To the
+extent this Public License may be interpreted as a contract, You are
+granted the Licensed Rights in consideration of Your acceptance of
+these terms and conditions, and the Licensor grants You such rights in
+consideration of benefits the Licensor receives from making the
+Licensed Material available under these terms and conditions.
+
+
+Section 1 -- Definitions.
+
+ a. Adapted Material means material subject to Copyright and Similar
+ Rights that is derived from or based upon the Licensed Material
+ and in which the Licensed Material is translated, altered,
+ arranged, transformed, or otherwise modified in a manner requiring
+ permission under the Copyright and Similar Rights held by the
+ Licensor. For purposes of this Public License, where the Licensed
+ Material is a musical work, performance, or sound recording,
+ Adapted Material is always produced where the Licensed Material is
+ synched in timed relation with a moving image.
+
+ b. Adapter's License means the license You apply to Your Copyright
+ and Similar Rights in Your contributions to Adapted Material in
+ accordance with the terms and conditions of this Public License.
+
+ c. Copyright and Similar Rights means copyright and/or similar rights
+ closely related to copyright including, without limitation,
+ performance, broadcast, sound recording, and Sui Generis Database
+ Rights, without regard to how the rights are labeled or
+ categorized. For purposes of this Public License, the rights
+ specified in Section 2(b)(1)-(2) are not Copyright and Similar
+ Rights.
+
+ d. Effective Technological Measures means those measures that, in the
+ absence of proper authority, may not be circumvented under laws
+ fulfilling obligations under Article 11 of the WIPO Copyright
+ Treaty adopted on December 20, 1996, and/or similar international
+ agreements.
+
+ e. Exceptions and Limitations means fair use, fair dealing, and/or
+ any other exception or limitation to Copyright and Similar Rights
+ that applies to Your use of the Licensed Material.
+
+ f. Licensed Material means the artistic or literary work, database,
+ or other material to which the Licensor applied this Public
+ License.
+
+ g. Licensed Rights means the rights granted to You subject to the
+ terms and conditions of this Public License, which are limited to
+ all Copyright and Similar Rights that apply to Your use of the
+ Licensed Material and that the Licensor has authority to license.
+
+ h. Licensor means the individual(s) or entity(ies) granting rights
+ under this Public License.
+
+ i. Share means to provide material to the public by any means or
+ process that requires permission under the Licensed Rights, such
+ as reproduction, public display, public performance, distribution,
+ dissemination, communication, or importation, and to make material
+ available to the public including in ways that members of the
+ public may access the material from a place and at a time
+ individually chosen by them.
+
+ j. Sui Generis Database Rights means rights other than copyright
+ resulting from Directive 96/9/EC of the European Parliament and of
+ the Council of 11 March 1996 on the legal protection of databases,
+ as amended and/or succeeded, as well as other essentially
+ equivalent rights anywhere in the world.
+
+ k. You means the individual or entity exercising the Licensed Rights
+ under this Public License. Your has a corresponding meaning.
+
+
+Section 2 -- Scope.
+
+ a. License grant.
+
+ 1. Subject to the terms and conditions of this Public License,
+ the Licensor hereby grants You a worldwide, royalty-free,
+ non-sublicensable, non-exclusive, irrevocable license to
+ exercise the Licensed Rights in the Licensed Material to:
+
+ a. reproduce and Share the Licensed Material, in whole or
+ in part; and
+
+ b. produce, reproduce, and Share Adapted Material.
+
+ 2. Exceptions and Limitations. For the avoidance of doubt, where
+ Exceptions and Limitations apply to Your use, this Public
+ License does not apply, and You do not need to comply with
+ its terms and conditions.
+
+ 3. Term. The term of this Public License is specified in Section
+ 6(a).
+
+ 4. Media and formats; technical modifications allowed. The
+ Licensor authorizes You to exercise the Licensed Rights in
+ all media and formats whether now known or hereafter created,
+ and to make technical modifications necessary to do so. The
+ Licensor waives and/or agrees not to assert any right or
+ authority to forbid You from making technical modifications
+ necessary to exercise the Licensed Rights, including
+ technical modifications necessary to circumvent Effective
+ Technological Measures. For purposes of this Public License,
+ simply making modifications authorized by this Section 2(a)
+ (4) never produces Adapted Material.
+
+ 5. Downstream recipients.
+
+ a. Offer from the Licensor -- Licensed Material. Every
+ recipient of the Licensed Material automatically
+ receives an offer from the Licensor to exercise the
+ Licensed Rights under the terms and conditions of this
+ Public License.
+
+ b. No downstream restrictions. You may not offer or impose
+ any additional or different terms or conditions on, or
+ apply any Effective Technological Measures to, the
+ Licensed Material if doing so restricts exercise of the
+ Licensed Rights by any recipient of the Licensed
+ Material.
+
+ 6. No endorsement. Nothing in this Public License constitutes or
+ may be construed as permission to assert or imply that You
+ are, or that Your use of the Licensed Material is, connected
+ with, or sponsored, endorsed, or granted official status by,
+ the Licensor or others designated to receive attribution as
+ provided in Section 3(a)(1)(A)(i).
+
+ b. Other rights.
+
+ 1. Moral rights, such as the right of integrity, are not
+ licensed under this Public License, nor are publicity,
+ privacy, and/or other similar personality rights; however, to
+ the extent possible, the Licensor waives and/or agrees not to
+ assert any such rights held by the Licensor to the limited
+ extent necessary to allow You to exercise the Licensed
+ Rights, but not otherwise.
+
+ 2. Patent and trademark rights are not licensed under this
+ Public License.
+
+ 3. To the extent possible, the Licensor waives any right to
+ collect royalties from You for the exercise of the Licensed
+ Rights, whether directly or through a collecting society
+ under any voluntary or waivable statutory or compulsory
+ licensing scheme. In all other cases the Licensor expressly
+ reserves any right to collect such royalties.
+
+
+Section 3 -- License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the
+following conditions.
+
+ a. Attribution.
+
+ 1. If You Share the Licensed Material (including in modified
+ form), You must:
+
+ a. retain the following if it is supplied by the Licensor
+ with the Licensed Material:
+
+ i. identification of the creator(s) of the Licensed
+ Material and any others designated to receive
+ attribution, in any reasonable manner requested by
+ the Licensor (including by pseudonym if
+ designated);
+
+ ii. a copyright notice;
+
+ iii. a notice that refers to this Public License;
+
+ iv. a notice that refers to the disclaimer of
+ warranties;
+
+ v. a URI or hyperlink to the Licensed Material to the
+ extent reasonably practicable;
+
+ b. indicate if You modified the Licensed Material and
+ retain an indication of any previous modifications; and
+
+ c. indicate the Licensed Material is licensed under this
+ Public License, and include the text of, or the URI or
+ hyperlink to, this Public License.
+
+ 2. You may satisfy the conditions in Section 3(a)(1) in any
+ reasonable manner based on the medium, means, and context in
+ which You Share the Licensed Material. For example, it may be
+ reasonable to satisfy the conditions by providing a URI or
+ hyperlink to a resource that includes the required
+ information.
+
+ 3. If requested by the Licensor, You must remove any of the
+ information required by Section 3(a)(1)(A) to the extent
+ reasonably practicable.
+
+ 4. If You Share Adapted Material You produce, the Adapter's
+ License You apply must not prevent recipients of the Adapted
+ Material from complying with this Public License.
+
+
+Section 4 -- Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that
+apply to Your use of the Licensed Material:
+
+ a. for the avoidance of doubt, Section 2(a)(1) grants You the right
+ to extract, reuse, reproduce, and Share all or a substantial
+ portion of the contents of the database;
+
+ b. if You include all or a substantial portion of the database
+ contents in a database in which You have Sui Generis Database
+ Rights, then the database in which You have Sui Generis Database
+ Rights (but not its individual contents) is Adapted Material; and
+
+ c. You must comply with the conditions in Section 3(a) if You Share
+ all or a substantial portion of the contents of the database.
+
+For the avoidance of doubt, this Section 4 supplements and does not
+replace Your obligations under this Public License where the Licensed
+Rights include other Copyright and Similar Rights.
+
+
+Section 5 -- Disclaimer of Warranties and Limitation of Liability.
+
+ a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
+ EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
+ AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
+ ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
+ IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
+ WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
+ PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
+ ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
+ KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
+ ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
+
+ b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
+ TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
+ NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
+ INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
+ COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
+ USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
+ ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
+ DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
+ IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
+
+ c. The disclaimer of warranties and limitation of liability provided
+ above shall be interpreted in a manner that, to the extent
+ possible, most closely approximates an absolute disclaimer and
+ waiver of all liability.
+
+
+Section 6 -- Term and Termination.
+
+ a. This Public License applies for the term of the Copyright and
+ Similar Rights licensed here. However, if You fail to comply with
+ this Public License, then Your rights under this Public License
+ terminate automatically.
+
+ b. Where Your right to use the Licensed Material has terminated under
+ Section 6(a), it reinstates:
+
+ 1. automatically as of the date the violation is cured, provided
+ it is cured within 30 days of Your discovery of the
+ violation; or
+
+ 2. upon express reinstatement by the Licensor.
+
+ For the avoidance of doubt, this Section 6(b) does not affect any
+ right the Licensor may have to seek remedies for Your violations
+ of this Public License.
+
+ c. For the avoidance of doubt, the Licensor may also offer the
+ Licensed Material under separate terms or conditions or stop
+ distributing the Licensed Material at any time; however, doing so
+ will not terminate this Public License.
+
+ d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
+ License.
+
+
+Section 7 -- Other Terms and Conditions.
+
+ a. The Licensor shall not be bound by any additional or different
+ terms or conditions communicated by You unless expressly agreed.
+
+ b. Any arrangements, understandings, or agreements regarding the
+ Licensed Material not stated herein are separate from and
+ independent of the terms and conditions of this Public License.
+
+
+Section 8 -- Interpretation.
+
+ a. For the avoidance of doubt, this Public License does not, and
+ shall not be interpreted to, reduce, limit, restrict, or impose
+ conditions on any use of the Licensed Material that could lawfully
+ be made without permission under this Public License.
+
+ b. To the extent possible, if any provision of this Public License is
+ deemed unenforceable, it shall be automatically reformed to the
+ minimum extent necessary to make it enforceable. If the provision
+ cannot be reformed, it shall be severed from this Public License
+ without affecting the enforceability of the remaining terms and
+ conditions.
+
+ c. No term or condition of this Public License will be waived and no
+ failure to comply consented to unless expressly agreed to by the
+ Licensor.
+
+ d. Nothing in this Public License constitutes or may be interpreted
+ as a limitation upon, or waiver of, any privileges and immunities
+ that apply to the Licensor or You, including from the legal
+ processes of any jurisdiction or authority.
+
+
+=======================================================================
+
+Creative Commons is not a party to its public
+licenses. Notwithstanding, Creative Commons may elect to apply one of
+its public licenses to material it publishes and in those instances
+will be considered the ”Licensor.” The text of the Creative Commons
+public licenses is dedicated to the public domain under the CC0 Public
+Domain Dedication. Except for the limited purpose of indicating that
+material is shared under a Creative Commons public license or as
+otherwise permitted by the Creative Commons policies published at
+creativecommons.org/policies, Creative Commons does not authorize the
+use of the trademark "Creative Commons" or any other trademark or logo
+of Creative Commons without its prior written consent including,
+without limitation, in connection with any unauthorized modifications
+to any of its public licenses or any other arrangements,
+understandings, or agreements concerning use of licensed material. For
+the avoidance of doubt, this paragraph does not form part of the
+public licenses.
+
+Creative Commons may be contacted at creativecommons.org.
+
+
+
+CDDL-1.0
+
+
+COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
+Version 1.0
+1. Definitions.
+
+1.1. “Contributor” means each individual or entity that creates or
+contributes to the creation of Modifications.
+
+1.2. “Contributor Version” means the combination of the Original
+Software, prior Modifications used by a Contributor (if any), and the Modifications
+made by that particular Contributor.
+
+1.3. “Covered Software” means (a) the Original Software, or (b)
+Modifications, or (c) the combination of files containing Original Software with files
+containing Modifications, in each case including portions thereof.
+
+1.4. “Executable” means the Covered Software in any form other
+than Source Code.
+
+1.5. “Initial Developer” means the individual or entity that first
+makes Original Software available under this License.
+
+1.6. “Larger Work” means a work which combines Covered Software or
+portions thereof with code not governed by the terms of this License.
+
+1.7. “License” means this document.
+
+1.8. “Licensable” means having the right to grant, to the maximum
+extent possible, whether at the time of the initial grant or subsequently acquired,
+any and all of the rights conveyed herein.
+
+1.9. “Modifications” means the Source Code and Executable form of
+any of the following:
+
+A. Any file that results from an addition to, deletion from or modification of the
+contents of a file containing Original Software or previous Modifications;
+
+B. Any new file that contains any part of the Original Software or previous
+Modification; or
+
+C. Any new file that is contributed or otherwise made available under the terms of
+this License.
+
+1.10. “Original Software” means the Source Code and Executable
+form of computer software code that is originally released under this License.
+
+1.11. “Patent Claims” means any patent claim(s), now owned or
+hereafter acquired, including without limitation, method, process, and apparatus
+claims, in any patent Licensable by grantor.
+
+1.12. “Source Code” means (a) the common form of computer software
+code in which modifications are made and (b) associated documentation included in or
+with such code.
+
+1.13. “You” (or “Your”) means an individual or
+a legal entity exercising rights under, and complying with all of the terms of, this
+License. For legal entities, “You” includes any entity which
+controls, is controlled by, or is under common control with You. For purposes of this
+definition, “control” means (a) the power, direct or indirect, to
+cause the direction or management of such entity, whether by contract or otherwise, or
+(b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial
+ownership of such entity.
+
+2. License Grants.
+
+2.1. The Initial Developer Grant.
+
+Conditioned upon Your compliance with Section 3.1 below and subject to third party
+intellectual property claims, the Initial Developer hereby grants You a world-wide,
+royalty-free, non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark) Licensable by
+Initial Developer, to use, reproduce, modify, display, perform, sublicense and
+distribute the Original Software (or portions thereof), with or without Modifications,
+and/or as part of a Larger Work; and
+
+(b) under Patent Claims infringed by the making, using or selling of Original
+Software, to make, have made, use, practice, sell, and offer for sale, and/or
+otherwise dispose of the Original Software (or portions thereof).
+
+(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial
+Developer first distributes or otherwise makes the Original Software available to a
+third party under the terms of this License.
+
+(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code
+that You delete from the Original Software, or (2) for infringements caused by: (i)
+the modification of the Original Software, or (ii) the combination of the Original
+Software with other software or devices.
+
+2.2. Contributor Grant.
+
+Conditioned upon Your compliance with Section 3.1 below and subject to third party
+intellectual property claims, each Contributor hereby grants You a world-wide,
+royalty-free, non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark) Licensable by
+Contributor to use, reproduce, modify, display, perform, sublicense and distribute the
+Modifications created by such Contributor (or portions thereof), either on an
+unmodified basis, with other Modifications, as Covered Software and/or as part of a
+Larger Work; and
+
+(b) under Patent Claims infringed by the making, using, or selling of Modifications
+made by that Contributor either alone and/or in combination with its Contributor
+Version (or portions of such combination), to make, use, sell, offer for sale, have
+made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or
+portions thereof); and (2) the combination of Modifications made by that Contributor
+with its Contributor Version (or portions of such combination).
+
+(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
+Contributor first distributes or otherwise makes the Modifications available to a
+third party.
+
+(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any
+code that Contributor has deleted from the Contributor Version; (2) for infringements
+caused by: (i) third party modifications of Contributor Version, or (ii) the
+combination of Modifications made by that Contributor with other software (except as
+part of the Contributor Version) or other devices; or (3) under Patent Claims
+infringed by Covered Software in the absence of Modifications made by that
+Contributor.
+
+3. Distribution Obligations.
+
+3.1. Availability of Source Code.
+
+Any Covered Software that You distribute or otherwise make available in Executable
+form must also be made available in Source Code form and that Source Code form must be
+distributed only under the terms of this License. You must include a copy of this
+License with every copy of the Source Code form of the Covered Software You distribute
+or otherwise make available. You must inform recipients of any such Covered Software
+in Executable form as to how they can obtain such Covered Software in Source Code form
+in a reasonable manner on or through a medium customarily used for software exchange.
+
+3.2. Modifications.
+
+The Modifications that You create or to which You contribute are governed by the terms
+of this License. You represent that You believe Your Modifications are Your original
+creation(s) and/or You have sufficient rights to grant the rights conveyed by this
+License.
+
+3.3. Required Notices.
+
+You must include a notice in each of Your Modifications that identifies You as the
+Contributor of the Modification. You may not remove or alter any copyright, patent or
+trademark notices contained within the Covered Software, or any notices of licensing
+or any descriptive text giving attribution to any Contributor or the Initial
+Developer.
+
+3.4. Application of Additional Terms.
+
+You may not offer or impose any terms on any Covered Software in Source Code form that
+alters or restricts the applicable version of this License or the
+recipients’ rights hereunder. You may choose to offer, and to charge a fee
+for, warranty, support, indemnity or liability obligations to one or more recipients
+of Covered Software. However, you may do so only on Your own behalf, and not on behalf
+of the Initial Developer or any Contributor. You must make it absolutely clear that
+any such warranty, support, indemnity or liability obligation is offered by You alone,
+and You hereby agree to indemnify the Initial Developer and every Contributor for any
+liability incurred by the Initial Developer or such Contributor as a result of
+warranty, support, indemnity or liability terms You offer.
+
+3.5. Distribution of Executable Versions.
+
+You may distribute the Executable form of the Covered Software under the terms of this
+License or under the terms of a license of Your choice, which may contain terms
+different from this License, provided that You are in compliance with the terms of
+this License and that the license for the Executable form does not attempt to limit or
+alter the recipient’s rights in the Source Code form from the rights set
+forth in this License. If You distribute the Covered Software in Executable form under
+a different license, You must make it absolutely clear that any terms which differ
+from this License are offered by You alone, not by the Initial Developer or
+Contributor. You hereby agree to indemnify the Initial Developer and every Contributor
+for any liability incurred by the Initial Developer or such Contributor as a result of
+any such terms You offer.
+
+3.6. Larger Works.
+
+You may create a Larger Work by combining Covered Software with other code not
+governed by the terms of this License and distribute the Larger Work as a single
+product. In such a case, You must make sure the requirements of this License are
+fulfilled for the Covered Software.
+
+4. Versions of the License.
+
+4.1. New Versions.
+
+Sun Microsystems, Inc. is the initial license steward and may publish revised and/or
+new versions of this License from time to time. Each version will be given a
+distinguishing version number. Except as provided in Section 4.3, no one other than
+the license steward has the right to modify this License.
+
+4.2. Effect of New Versions.
+
+You may always continue to use, distribute or otherwise make the Covered Software
+available under the terms of the version of the License under which You originally
+received the Covered Software. If the Initial Developer includes a notice in the
+Original Software prohibiting it from being distributed or otherwise made available
+under any subsequent version of the License, You must distribute and make the Covered
+Software available under the terms of the version of the License under which You
+originally received the Covered Software. Otherwise, You may also choose to use,
+distribute or otherwise make the Covered Software available under the terms of any
+subsequent version of the License published by the license steward.
+
+4.3. Modified Versions.
+
+When You are an Initial Developer and You want to create a new license for Your
+Original Software, You may create and use a modified version of this License if You:
+(a) rename the license and remove any references to the name of the license steward
+(except to note that the license differs from this License); and (b) otherwise make it
+clear that the license contains terms which differ from this License.
+
+5. DISCLAIMER OF WARRANTY.
+
+COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS”
+BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
+LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT
+FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
+PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
+DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR)
+ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
+WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE
+IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
+
+6. TERMINATION.
+
+6.1. This License and the rights granted hereunder will terminate automatically if You
+fail to comply with terms herein and fail to cure such breach within 30 days of
+becoming aware of the breach. Provisions which, by their nature, must remain in effect
+beyond the termination of this License shall survive.
+
+6.2. If You assert a patent infringement claim (excluding declaratory judgment
+actions) against Initial Developer or a Contributor (the Initial Developer or
+Contributor against whom You assert such claim is referred to as
+“Participant”) alleging that the Participant Software (meaning the
+Contributor Version where the Participant is a Contributor or the Original Software
+where the Participant is the Initial Developer) directly or indirectly infringes any
+patent, then any and all rights granted directly or indirectly to You by such
+Participant, the Initial Developer (if the Initial Developer is not the Participant)
+and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days
+notice from Participant terminate prospectively and automatically at the expiration of
+such 60 day notice period, unless if within such 60 day period You withdraw Your claim
+with respect to the Participant Software against such Participant either unilaterally
+or pursuant to a written agreement with Participant.
+
+6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user
+licenses that have been validly granted by You or any distributor hereunder prior to
+termination (excluding licenses granted to You by any distributor) shall survive
+termination.
+
+7. LIMITATION OF LIABILITY.
+
+UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
+CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR
+ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE
+TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
+CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,
+WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL
+DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF
+SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
+PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT
+APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
+EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
+LIMITATION MAY NOT APPLY TO YOU.
+
+8. U.S. GOVERNMENT END USERS.
+
+The Covered Software is a “commercial item,” as that term is
+defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of “commercial computer
+software” (as that term is defined at 48 C.F.R. §
+252.227-7014(a)(1)) and “commercial computer software
+documentation” as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
+Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
+1995), all U.S. Government End Users acquire Covered Software with only those rights
+set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes,
+any other FAR, DFAR, or other clause or provision that addresses Government rights in
+computer software under this License.
+
+9. MISCELLANEOUS.
+
+This License represents the complete agreement concerning subject matter hereof. If
+any provision of this License is held to be unenforceable, such provision shall be
+reformed only to the extent necessary to make it enforceable. This License shall be
+governed by the law of the jurisdiction specified in a notice contained within the
+Original Software (except to the extent applicable law, if any, provides otherwise),
+excluding such jurisdiction’s conflict-of-law provisions. Any litigation
+relating to this License shall be subject to the jurisdiction of the courts located in
+the jurisdiction and venue specified in a notice contained within the Original
+Software, with the losing party responsible for costs, including, without limitation,
+court costs and reasonable attorneys’ fees and expenses. The application of
+the United Nations Convention on Contracts for the International Sale of Goods is
+expressly excluded. Any law or regulation which provides that the language of a
+contract shall be construed against the drafter shall not apply to this License. You
+agree that You alone are responsible for compliance with the United States export
+administration regulations (and the export control laws and regulation of any other
+countries) when You use, distribute or otherwise make available any Covered Software.
+
+10. RESPONSIBILITY FOR CLAIMS.
+
+As between Initial Developer and the Contributors, each party is responsible for
+claims and damages arising, directly or indirectly, out of its utilization of rights
+under this License and You agree to work with Initial Developer and Contributors to
+distribute such responsibility on an equitable basis. Nothing herein is intended or
+shall be deemed to constitute any admission of liability.
+
+
+
+
+CDS
+
+This software is copyrighted by Cadence Design Systems, Inc., and other
+parties. The following terms apply to all files associated with the
+software unless explicitly disclaimed in individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+-----------------------------------------------------------------------
+ Following is the original agreement for the Tcl/Tk software from
+ Sun Microsystems.
+-----------------------------------------------------------------------
+
+This software is copyrighted by the Regents of the University of
+California, Sun Microsystems, Inc., and other parties. The following
+terms apply to all files associated with the software unless explicitly
+disclaimed in individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+
+
+CPL-1.0
+
+
+Common Public License Version 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
+LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
+CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+a) in the case of the initial Contributor, the initial code and
+documentation distributed under this Agreement, and
+
+b) in the case of each subsequent Contributor:
+
+i) changes to the Program, and
+
+ii) additions to the Program;
+
+where such changes and/or additions to the Program originate from and are
+distributed by that particular Contributor. A Contribution `originates` from a
+Contributor if it was added to the Program by such Contributor itself or anyone
+acting on such Contributor`s behalf. Contributions do not include additions to
+the Program which: (i) are separate modules of software distributed in
+conjunction with the Program under their own license agreement, and (ii) are not
+derivative works of the Program.
+
+"Contributor" means any person or entity that distributes the Program.
+
+"Licensed Patents " mean patent claims licensable by a Contributor which are
+necessarily infringed by the use or sale of its Contribution alone or when
+combined with the Program.
+
+"Program" means the Contributions distributed in accordance with this Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement,
+including all Contributors.
+
+2. GRANT OF RIGHTS
+
+a) Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide, royalty-free copyright license to
+reproduce, prepare derivative works of, publicly display, publicly perform,
+distribute and sublicense the Contribution of such Contributor, if any, and such
+derivative works, in source code and object code form.
+
+b) Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
+Patents to make, use, sell, offer to sell, import and otherwise transfer the
+Contribution of such Contributor, if any, in source code and object code form.
+This patent license shall apply to the combination of the Contribution and the
+Program if, at the time the Contribution is added by the Contributor, such
+addition of the Contribution causes such combination to be covered by the
+Licensed Patents. The patent license shall not apply to any other combinations
+which include the Contribution. No hardware per se is licensed hereunder.
+
+c) Recipient understands that although each Contributor grants the licenses
+to its Contributions set forth herein, no assurances are provided by any
+Contributor that the Program does not infringe the patent or other intellectual
+property rights of any other entity. Each Contributor disclaims any liability to
+Recipient for claims brought by any other entity based on infringement of
+intellectual property rights or otherwise. As a condition to exercising the
+rights and licenses granted hereunder, each Recipient hereby assumes sole
+responsibility to secure any other intellectual property rights needed, if any.
+For example, if a third party patent license is required to allow Recipient to
+distribute the Program, it is Recipient`s responsibility to acquire that license
+before distributing the Program.
+
+d) Each Contributor represents that to its knowledge it has sufficient
+copyright rights in its Contribution, if any, to grant the copyright license set
+forth in this Agreement.
+
+3. REQUIREMENTS
+
+A Contributor may choose to distribute the Program in object code form under its
+own license agreement, provided that:
+
+a) it complies with the terms and conditions of this Agreement; and
+
+b) its license agreement:
+
+i) effectively disclaims on behalf of all Contributors all warranties and
+conditions, express and implied, including warranties or conditions of title and
+non-infringement, and implied warranties or conditions of merchantability and
+fitness for a particular purpose;
+
+ii) effectively excludes on behalf of all Contributors all liability for
+damages, including direct, indirect, special, incidental and consequential
+damages, such as lost profits;
+
+iii) states that any provisions which differ from this Agreement are offered
+by that Contributor alone and not by any other party; and
+
+iv) states that source code for the Program is available from such
+Contributor, and informs licensees how to obtain it in a reasonable manner on or
+through a medium customarily used for software exchange.
+
+When the Program is made available in source code form:
+
+a) it must be made available under this Agreement; and
+
+b) a copy of this Agreement must be included with each copy of the Program.
+
+Contributors may not remove or alter any copyright notices contained within the
+Program.
+
+Each Contributor must identify itself as the originator of its Contribution, if
+any, in a manner that reasonably allows subsequent Recipients to identify the
+originator of the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities with
+respect to end users, business partners and the like. While this license is
+intended to facilitate the commercial use of the Program, the Contributor who
+includes the Program in a commercial product offering should do so in a manner
+which does not create potential liability for other Contributors. Therefore, if
+a Contributor includes the Program in a commercial product offering, such
+Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
+every other Contributor ("Indemnified Contributor") against any losses, damages
+and costs (collectively "Losses") arising from claims, lawsuits and other legal
+actions brought by a third party against the Indemnified Contributor to the
+extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product
+offering. The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement. In order
+to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
+Contributor in writing of such claim, and b) allow the Commercial Contributor to
+control, and cooperate with the Commercial Contributor in, the defense and any
+related settlement negotiations. The Indemnified Contributor may participate in
+any such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial product
+offering, Product X. That Contributor is then a Commercial Contributor. If that
+Commercial Contributor then makes performance claims, or offers warranties
+related to Product X, those performance claims and warranties are such
+Commercial Contributor`s responsibility alone. Under this section, the
+Commercial Contributor would have to defend claims against the other
+Contributors related to those performance claims and warranties, and if a court
+requires any other Contributor to pay any damages as a result, the Commercial
+Contributor must pay those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
+IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
+NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
+Recipient is solely responsible for determining the appropriateness of using and
+distributing the Program and assumes all risks associated with its exercise of
+rights under this Agreement, including but not limited to the risks and costs of
+program errors, compliance with applicable laws, damage to or loss of data,
+programs or equipment, and unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
+CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
+PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
+GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under applicable
+law, it shall not affect the validity or enforceability of the remainder of the
+terms of this Agreement, and without further action by the parties hereto, such
+provision shall be reformed to the minimum extent necessary to make such
+provision valid and enforceable.
+
+If Recipient institutes patent litigation against a Contributor with respect to
+a patent applicable to software (including a cross-claim or counterclaim in a
+lawsuit), then any patent licenses granted by that Contributor to such Recipient
+under this Agreement shall terminate as of the date such litigation is filed. In
+addition, if Recipient institutes patent litigation against any entity
+(including a cross-claim or counterclaim in a lawsuit) alleging that the Program
+itself (excluding combinations of the Program with other software or hardware)
+infringes such Recipient`s patent(s), then such Recipient`s rights granted under
+Section 2(b) shall terminate as of the date such litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it fails to
+comply with any of the material terms or conditions of this Agreement and does
+not cure such failure in a reasonable period of time after becoming aware of
+such noncompliance. If all Recipient`s rights under this Agreement terminate,
+Recipient agrees to cease use and distribution of the Program as soon as
+reasonably practicable. However, Recipient`s obligations under this Agreement
+and any licenses granted by Recipient relating to the Program shall continue and
+survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement, but in
+order to avoid inconsistency the Agreement is copyrighted and may only be
+modified in the following manner. The Agreement Steward reserves the right to
+publish new versions (including revisions) of this Agreement from time to time.
+No one other than the Agreement Steward has the right to modify this Agreement.
+IBM is the initial Agreement Steward. IBM may assign the responsibility to serve
+as the Agreement Steward to a suitable separate entity. Each new version of the
+Agreement will be given a distinguishing version number. The Program (including
+Contributions) may always be distributed subject to the version of the Agreement
+under which it was received. In addition, after a new version of the Agreement
+is published, Contributor may elect to distribute the Program (including its
+Contributions) under the new version. Except as expressly stated in Sections
+2(a) and 2(b) above, Recipient receives no rights or licenses to the
+intellectual property of any Contributor under this Agreement, whether
+expressly, by implication, estoppel or otherwise. All rights in the Program not
+expressly granted under this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and the
+intellectual property laws of the United States of America. No party to this
+Agreement will bring a legal action under this Agreement more than one year
+after the cause of action arose. Each party waives its rights to a jury trial in
+any resulting litigation.
+
+
+
+
+CUP
+
+CUP PARSER GENERATOR COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
+
+Copyright 1996 by Scott Hudson, Frank Flannery, C. Scott Ananian
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted,
+provided that the above copyright notice appear in all copies and that
+both the copyright notice and this permission notice and warranty
+disclaimer appear in supporting documentation, and that the names of
+the authors or their employers not be used in advertising or publicity
+pertaining to distribution of the software without specific, written
+prior permission.
+
+The authors and their employers disclaim all warranties with regard to
+this software, including all implied warranties of merchantability and
+fitness. In no event shall the authors or their employers be liable
+for any special, indirect or consequential damages or any damages
+whatsoever resulting from loss of use, data or profits, whether in an
+action of contract, negligence or other tortious action, arising out of
+or in connection with the use or performance of this software.
+
+
+
+EPL-1.0
+
+
+Eclipse Public License - v 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE
+("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES
+RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+a) in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and
+b) in the case of each subsequent Contributor:
+i) changes to the Program, and
+ii) additions to the Program;
+where such changes and/or additions to the Program originate from and are distributed
+by that particular Contributor. A Contribution `originates` from a Contributor if it
+was added to the Program by such Contributor itself or anyone acting on such
+Contributor`s behalf. Contributions do not include additions to the Program which: (i)
+are separate modules of software distributed in conjunction with the Program under
+their own license agreement, and (ii) are not derivative works of the Program.
+"Contributor" means any person or entity that distributes the Program.
+
+"Licensed Patents" mean patent claims licensable by a Contributor which are
+necessarily infringed by the use or sale of its Contribution alone or when combined
+with the Program.
+
+"Program" means the Contributions distributed in accordance with this Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement, including all
+Contributors.
+
+2. GRANT OF RIGHTS
+
+a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
+non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare
+derivative works of, publicly display, publicly perform, distribute and sublicense the
+Contribution of such Contributor, if any, and such derivative works, in source code
+and object code form.
+b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
+non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make,
+use, sell, offer to sell, import and otherwise transfer the Contribution of such
+Contributor, if any, in source code and object code form. This patent license shall
+apply to the combination of the Contribution and the Program if, at the time the
+Contribution is added by the Contributor, such addition of the Contribution causes
+such combination to be covered by the Licensed Patents. The patent license shall not
+apply to any other combinations which include the Contribution. No hardware per se is
+licensed hereunder.
+c) Recipient understands that although each Contributor grants the licenses to its
+Contributions set forth herein, no assurances are provided by any Contributor that the
+Program does not infringe the patent or other intellectual property rights of any
+other entity. Each Contributor disclaims any liability to Recipient for claims brought
+by any other entity based on infringement of intellectual property rights or
+otherwise. As a condition to exercising the rights and licenses granted hereunder,
+each Recipient hereby assumes sole responsibility to secure any other intellectual
+property rights needed, if any. For example, if a third party patent license is
+required to allow Recipient to distribute the Program, it is Recipient`s
+responsibility to acquire that license before distributing the Program.
+d) Each Contributor represents that to its knowledge it has sufficient copyright
+rights in its Contribution, if any, to grant the copyright license set forth in this
+Agreement.
+3. REQUIREMENTS
+
+A Contributor may choose to distribute the Program in object code form under its own
+license agreement, provided that:
+
+a) it complies with the terms and conditions of this Agreement; and
+b) its license agreement:
+i) effectively disclaims on behalf of all Contributors all warranties and conditions,
+express and implied, including warranties or conditions of title and non-infringement,
+and implied warranties or conditions of merchantability and fitness for a particular
+purpose;
+ii) effectively excludes on behalf of all Contributors all liability for damages,
+including direct, indirect, special, incidental and consequential damages, such as
+lost profits;
+iii) states that any provisions which differ from this Agreement are offered by that
+Contributor alone and not by any other party; and
+iv) states that source code for the Program is available from such Contributor, and
+informs licensees how to obtain it in a reasonable manner on or through a medium
+customarily used for software exchange.
+When the Program is made available in source code form:
+
+a) it must be made available under this Agreement; and
+b) a copy of this Agreement must be included with each copy of the Program.
+Contributors may not remove or alter any copyright notices contained within the
+Program.
+
+Each Contributor must identify itself as the originator of its Contribution, if any,
+in a manner that reasonably allows subsequent Recipients to identify the originator of
+the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities with respect
+to end users, business partners and the like. While this license is intended to
+facilitate the commercial use of the Program, the Contributor who includes the Program
+in a commercial product offering should do so in a manner which does not create
+potential liability for other Contributors. Therefore, if a Contributor includes the
+Program in a commercial product offering, such Contributor ("Commercial Contributor")
+hereby agrees to defend and indemnify every other Contributor ("Indemnified
+Contributor") against any losses, damages and costs (collectively "Losses") arising
+from claims, lawsuits and other legal actions brought by a third party against the
+Indemnified Contributor to the extent caused by the acts or omissions of such
+Commercial Contributor in connection with its distribution of the Program in a
+commercial product offering. The obligations in this section do not apply to any
+claims or Losses relating to any actual or alleged intellectual property infringement.
+In order to qualify, an Indemnified Contributor must: a) promptly notify the
+Commercial Contributor in writing of such claim, and b) allow the Commercial
+Contributor to control, and cooperate with the Commercial Contributor in, the defense
+and any related settlement negotiations. The Indemnified Contributor may participate
+in any such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial product offering,
+Product X. That Contributor is then a Commercial Contributor. If that Commercial
+Contributor then makes performance claims, or offers warranties related to Product X,
+those performance claims and warranties are such Commercial Contributor`s
+responsibility alone. Under this section, the Commercial Contributor would have to
+defend claims against the other Contributors related to those performance claims and
+warranties, and if a court requires any other Contributor to pay any damages as a
+result, the Commercial Contributor must pay those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS"
+BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED
+INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
+NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient
+is solely responsible for determining the appropriateness of using and distributing
+the Program and assumes all risks associated with its exercise of rights under this
+Agreement , including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs or equipment, and
+unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
+CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS),
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR
+DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under applicable law,
+it shall not affect the validity or enforceability of the remainder of the terms of
+this Agreement, and without further action by the parties hereto, such provision shall
+be reformed to the minimum extent necessary to make such provision valid and
+enforceable.
+
+If Recipient institutes patent litigation against any entity (including a cross-claim
+or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations
+of the Program with other software or hardware) infringes such Recipient`s patent(s),
+then such Recipient`s rights granted under Section 2(b) shall terminate as of the date
+such litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it fails to comply with
+any of the material terms or conditions of this Agreement and does not cure such
+failure in a reasonable period of time after becoming aware of such noncompliance. If
+all Recipient`s rights under this Agreement terminate, Recipient agrees to cease use
+and distribution of the Program as soon as reasonably practicable. However,
+Recipient`s obligations under this Agreement and any licenses granted by Recipient
+relating to the Program shall continue and survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement, but in order to
+avoid inconsistency the Agreement is copyrighted and may only be modified in the
+following manner. The Agreement Steward reserves the right to publish new versions
+(including revisions) of this Agreement from time to time. No one other than the
+Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is
+the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to
+serve as the Agreement Steward to a suitable separate entity. Each new version of the
+Agreement will be given a distinguishing version number. The Program (including
+Contributions) may always be distributed subject to the version of the Agreement under
+which it was received. In addition, after a new version of the Agreement is published,
+Contributor may elect to distribute the Program (including its Contributions) under
+the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
+receives no rights or licenses to the intellectual property of any Contributor under
+this Agreement, whether expressly, by implication, estoppel or otherwise. All rights
+in the Program not expressly granted under this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and the intellectual
+property laws of the United States of America. No party to this Agreement will bring a
+legal action under this Agreement more than one year after the cause of action arose.
+Each party waives its rights to a jury trial in any resulting litigation.
+
+
+
+
+Elfutils-Exception
+
+ This file describes the limits of the Exception under which you are allowed
+ to distribute Non-GPL Code in linked combination with Red Hat elfutils.
+ For the full text of the license, please see one of the header files
+ included with the source distribution or the file COPYING found in the
+ top level directory of the source.
+
+ The Approved Interfaces are the functions declared in the files:
+
+ libelf.h
+ libdw.h
+ libdwfl.h
+
+
+
+
+FSF-Unlimited
+
+Copyright (C) 1997-2010 Free Software Foundation, Inc.
+This file is free software; the Free Software Foundation
+gives unlimited permission to copy and/or distribute it,
+with or without modifications, as long as this notice is preserved.
+
+
+
+FreeType
+
+ The FreeType Project LICENSE
+ ----------------------------
+
+ 2006-Jan-27
+
+ Copyright 1996-2002, 2006 by
+ David Turner, Robert Wilhelm, and Werner Lemberg
+
+
+
+Introduction
+============
+
+ The FreeType Project is distributed in several archive packages;
+ some of them may contain, in addition to the FreeType font engine,
+ various tools and contributions which rely on, or relate to, the
+ FreeType Project.
+
+ This license applies to all files found in such packages, and
+ which do not fall under their own explicit license. The license
+ affects thus the FreeType font engine, the test programs,
+ documentation and makefiles, at the very least.
+
+ This license was inspired by the BSD, Artistic, and IJG
+ (Independent JPEG Group) licenses, which all encourage inclusion
+ and use of free software in commercial and freeware products
+ alike. As a consequence, its main points are that:
+
+ o We don't promise that this software works. However, we will be
+ interested in any kind of bug reports. (`as is' distribution)
+
+ o You can use this software for whatever you want, in parts or
+ full form, without having to pay us. (`royalty-free' usage)
+
+ o You may not pretend that you wrote this software. If you use
+ it, or only parts of it, in a program, you must acknowledge
+ somewhere in your documentation that you have used the
+ FreeType code. (`credits')
+
+ We specifically permit and encourage the inclusion of this
+ software, with or without modifications, in commercial products.
+ We disclaim all warranties covering The FreeType Project and
+ assume no liability related to The FreeType Project.
+
+
+ Finally, many people asked us for a preferred form for a
+ credit/disclaimer to use in compliance with this license. We thus
+ encourage you to use the following text:
+
+ """
+ Portions of this software are copyright � <year> The FreeType
+ Project (www.freetype.org). All rights reserved.
+ """
+
+ Please replace <year> with the value from the FreeType version you
+ actually use.
+
+
+Legal Terms
+===========
+
+0. Definitions
+--------------
+
+ Throughout this license, the terms `package', `FreeType Project',
+ and `FreeType archive' refer to the set of files originally
+ distributed by the authors (David Turner, Robert Wilhelm, and
+ Werner Lemberg) as the `FreeType Project', be they named as alpha,
+ beta or final release.
+
+ `You' refers to the licensee, or person using the project, where
+ `using' is a generic term including compiling the project's source
+ code as well as linking it to form a `program' or `executable'.
+ This program is referred to as `a program using the FreeType
+ engine'.
+
+ This license applies to all files distributed in the original
+ FreeType Project, including all source code, binaries and
+ documentation, unless otherwise stated in the file in its
+ original, unmodified form as distributed in the original archive.
+ If you are unsure whether or not a particular file is covered by
+ this license, you must contact us to verify this.
+
+ The FreeType Project is copyright (C) 1996-2000 by David Turner,
+ Robert Wilhelm, and Werner Lemberg. All rights reserved except as
+ specified below.
+
+1. No Warranty
+--------------
+
+ THE FREETYPE PROJECT IS PROVIDED `AS IS' WITHOUT WARRANTY OF ANY
+ KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+ WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE. IN NO EVENT WILL ANY OF THE AUTHORS OR COPYRIGHT HOLDERS
+ BE LIABLE FOR ANY DAMAGES CAUSED BY THE USE OR THE INABILITY TO
+ USE, OF THE FREETYPE PROJECT.
+
+2. Redistribution
+-----------------
+
+ This license grants a worldwide, royalty-free, perpetual and
+ irrevocable right and license to use, execute, perform, compile,
+ display, copy, create derivative works of, distribute and
+ sublicense the FreeType Project (in both source and object code
+ forms) and derivative works thereof for any purpose; and to
+ authorize others to exercise some or all of the rights granted
+ herein, subject to the following conditions:
+
+ o Redistribution of source code must retain this license file
+ (`FTL.TXT') unaltered; any additions, deletions or changes to
+ the original files must be clearly indicated in accompanying
+ documentation. The copyright notices of the unaltered,
+ original files must be preserved in all copies of source
+ files.
+
+ o Redistribution in binary form must provide a disclaimer that
+ states that the software is based in part of the work of the
+ FreeType Team, in the distribution documentation. We also
+ encourage you to put an URL to the FreeType web page in your
+ documentation, though this isn't mandatory.
+
+ These conditions apply to any software derived from or based on
+ the FreeType Project, not just the unmodified files. If you use
+ our work, you must acknowledge us. However, no fee need be paid
+ to us.
+
+3. Advertising
+--------------
+
+ Neither the FreeType authors and contributors nor you shall use
+ the name of the other for commercial, advertising, or promotional
+ purposes without specific prior written permission.
+
+ We suggest, but do not require, that you use one or more of the
+ following phrases to refer to this software in your documentation
+ or advertising materials: `FreeType Project', `FreeType Engine',
+ `FreeType library', or `FreeType Distribution'.
+
+ As you have not signed this license, you are not required to
+ accept it. However, as the FreeType Project is copyrighted
+ material, only this license, or another one contracted with the
+ authors, grants you the right to use, distribute, and modify it.
+ Therefore, by using, distributing, or modifying the FreeType
+ Project, you indicate that you understand and accept all the terms
+ of this license.
+
+4. Contacts
+-----------
+
+ There are two mailing lists related to FreeType:
+
+ o freetype@nongnu.org
+
+ Discusses general use and applications of FreeType, as well as
+ future and wanted additions to the library and distribution.
+ If you are looking for support, start in this list if you
+ haven't found anything to help you in the documentation.
+
+ o freetype-devel@nongnu.org
+
+ Discusses bugs, as well as engine internals, design issues,
+ specific licenses, porting, etc.
+
+ Our home page can be found at
+
+ http://www.freetype.org
+
+
+--- end of FTL.TXT ---
+
+
+
+
+GPL-1.0
+
+
+GNU General Public License, version 1
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 1, February 1989
+
+ Copyright (C) 1989 Free Software Foundation, Inc.
+ 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The license agreements of most software companies try to keep users
+at the mercy of those companies. By contrast, our General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. The
+General Public License applies to the Free Software Foundation`s
+software and to any other program whose authors commit to using it.
+You can use it for your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Specifically, the General Public License is designed to make
+sure that you have the freedom to give away or sell copies of free
+software, that you receive source code or can get it if you want it,
+that you can change the software or use pieces of it in new free
+programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of a such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author`s protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors` reputations.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any program or other work which
+contains a notice placed by the copyright holder saying it may be
+distributed under the terms of this General Public License. The
+"Program", below, refers to any such program or work, and a "work based
+on the Program" means either the Program or any work containing the
+Program or a portion of it, either verbatim or with modifications. Each
+licensee is addressed as "you".
+
+ 1. You may copy and distribute verbatim copies of the Program`s source
+code as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice and
+disclaimer of warranty; keep intact all the notices that refer to this
+General Public License and to the absence of any warranty; and give any
+other recipients of the Program a copy of this General Public License
+along with the Program. You may charge a fee for the physical act of
+transferring a copy.
+
+ 2. You may modify your copy or copies of the Program or any portion of
+it, and copy and distribute such modifications under the terms of Paragraph
+1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating that
+ you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish, that
+ in whole or in part contains the Program or any part thereof, either
+ with or without modifications, to be licensed at no charge to all
+ third parties under the terms of this General Public License (except
+ that you may choose to grant warranty protection to some or all
+ third parties, at your option).
+
+ c) If the modified program normally reads commands interactively when
+ run, you must cause it, when started running for such interactive use
+ in the simplest and most usual way, to print or display an
+ announcement including an appropriate copyright notice and a notice
+ that there is no warranty (or else, saying that you provide a
+ warranty) and that users may redistribute the program under these
+ conditions, and telling the user how to view a copy of this General
+ Public License.
+
+ d) You may charge a fee for the physical act of transferring a
+ copy, and you may at your option offer warranty protection in
+ exchange for a fee.
+
+Mere aggregation of another independent work with the Program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other work under the scope of these terms.
+
+ 3. You may copy and distribute the Program (or a portion or derivative of
+it, under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+ a) accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal charge
+ for the cost of distribution) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+Source code for a work means the preferred form of the work for making
+modifications to it. For an executable file, complete source code means
+all the source code for all modules it contains; but, as a special
+exception, it need not include source code for modules which are standard
+libraries that accompany the operating system on which the executable
+file runs, or for standard header files or definitions files that
+accompany that operating system.
+
+ 4. You may not copy, modify, sublicense, distribute or transfer the
+Program except as expressly provided under this General Public License.
+Any attempt otherwise to copy, modify, sublicense, distribute or transfer
+the Program is void, and will automatically terminate your rights to use
+the Program under this License. However, parties who have received
+copies, or rights to use copies, from you under this General Public
+License will not have their licenses terminated so long as such parties
+remain in full compliance.
+
+ 5. By copying, distributing or modifying the Program (or any work based
+on the Program) you indicate your acceptance of this license to do so,
+and all its terms and conditions.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the original
+licensor to copy, distribute or modify the Program subject to these
+terms and conditions. You may not impose any further restrictions on the
+recipients` exercise of the rights granted herein.
+
+ 7. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of the license which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+the license, you may choose any version ever published by the Free Software
+Foundation.
+
+ 8. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ 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
+the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program`s name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 1, or (at your option)
+ any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19xx name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w`.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c` for details.
+
+The hypothetical commands `show w` and `show c` should show the
+appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than `show w` and `show
+c`; they could even be mouse-clicks or menu items--whatever suits your
+program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ program `Gnomovision` (a program to direct compilers to make passes
+ at assemblers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+That`s all there is to it!
+
+
+
+
+GPL-2.0
+
+
+GNU GENERAL PUBLIC LICENSE
+
+Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public License is intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users. This General Public License applies to most of the Free Software
+Foundation`s software and to any other program whose authors commit to using it. (Some
+other Free Software Foundation software is covered by the GNU Lesser General Public
+License instead.) You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for this service if you wish), that you receive
+source code or can get it if you want it, that you can change the software or use
+pieces of it in new free programs; and that you know you can do these things.
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you
+these rights or to ask you to surrender the rights. These restrictions translate to
+certain responsibilities for you if you distribute copies of the software, or if you
+modify it.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee,
+you must give the recipients all the rights that you have. You must make sure that
+they, too, receive or can get the source code. And you must show them these terms so
+they know their rights.
+
+We protect your rights with two steps: (1) copyright the software, and (2) offer you
+this license which gives you legal permission to copy, distribute and/or modify the
+software.
+
+Also, for each author`s protection and ours, we want to make certain that everyone
+understands that there is no warranty for this free software. If the software is
+modified by someone else and passed on, we want its recipients to know that what they
+have is not the original, so that any problems introduced by others will not reflect
+on the original authors` reputations.
+
+Finally, any free program is threatened constantly by software patents. We wish to
+avoid the danger that redistributors of a free program will individually obtain patent
+licenses, in effect making the program proprietary. To prevent this, we have made it
+clear that any patent must be licensed for everyone`s free use or not licensed at all.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License applies to any program or other work which contains a notice placed by
+the copyright holder saying it may be distributed under the terms of this General
+Public License. The "Program", below, refers to any such program or work, and a "work
+based on the Program" means either the Program or any derivative work under copyright
+law: that is to say, a work containing the Program or a portion of it, either verbatim
+or with modifications and/or translated into another language. (Hereinafter,
+translation is included without limitation in the term "modification".) Each licensee
+is addressed as "you".
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running the Program is not restricted,
+and the output from the Program is covered only if its contents constitute a work
+based on the Program (independent of having been made by running the Program). Whether
+that is true depends on what the Program does.
+
+1. You may copy and distribute verbatim copies of the Program`s source code as you
+receive it, in any medium, provided that you conspicuously and appropriately publish
+on each copy an appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any warranty; and
+give any other recipients of the Program a copy of this License along with the
+Program.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Program or any portion of it, thus
+forming a work based on the Program, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+a) You must cause the modified files to carry prominent notices stating that you
+changed the files and the date of any change.
+b) You must cause any work that you distribute or publish, that in whole or in part
+contains or is derived from the Program or any part thereof, to be licensed as a whole
+at no charge to all third parties under the terms of this License.
+c) If the modified program normally reads commands interactively when run, you must
+cause it, when started running for such interactive use in the most ordinary way, to
+print or display an announcement including an appropriate copyright notice and a
+notice that there is no warranty (or else, saying that you provide a warranty) and
+that users may redistribute the program under these conditions, and telling the user
+how to view a copy of this License. (Exception: if the Program itself is interactive
+but does not normally print such an announcement, your work based on the Program is
+not required to print an announcement.)
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Program, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Program,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program with the
+Program (or with a work based on the Program) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+3. You may copy and distribute the Program (or a work based on it, under Section 2) in
+object code or executable form under the terms of Sections 1 and 2 above provided that
+you also do one of the following:
+
+a) Accompany it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a medium customarily
+used for software interchange; or,
+b) Accompany it with a written offer, valid for at least three years, to give any
+third party, for a charge no more than your cost of physically performing source
+distribution, a complete machine-readable copy of the corresponding source code, to be
+distributed under the terms of Sections 1 and 2 above on a medium customarily used for
+software interchange; or,
+c) Accompany it with the information you received as to the offer to distribute
+corresponding source code. (This alternative is allowed only for noncommercial
+distribution and only if you received the program in object code or executable form
+with such an offer, in accord with Subsection b above.)
+The source code for a work means the preferred form of the work for making
+modifications to it. For an executable work, complete source code means all the source
+code for all modules it contains, plus any associated interface definition files, plus
+the scripts used to control compilation and installation of the executable. However,
+as a special exception, the source code distributed need not include anything that is
+normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+If distribution of executable or object code is made by offering access to copy from a
+designated place, then offering equivalent access to copy the source code from the
+same place counts as distribution of the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+4. You may not copy, modify, sublicense, or distribute the Program except as expressly
+provided under this License. Any attempt otherwise to copy, modify, sublicense or
+distribute the Program is void, and will automatically terminate your rights under
+this License. However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such parties remain in
+full compliance.
+
+5. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Program or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Program or works based on it.
+
+6. Each time you redistribute the Program (or any work based on the Program), the
+recipient automatically receives a license from the original licensor to copy,
+distribute or modify the Program subject to these terms and conditions. You may not
+impose any further restrictions on the recipients` exercise of the rights granted
+herein. You are not responsible for enforcing compliance by third parties to this
+License.
+
+7. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Program at all. For example, if a patent license would not permit royalty-free
+redistribution of the Program by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply and the section as a
+whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system,
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+8. If the distribution and/or use of the Program is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Program under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+9. The Free Software Foundation may publish revised and/or new versions of the General
+Public License from time to time. Such new versions will be similar in spirit to the
+present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Program does not
+specify a version number of this License, you may choose any version ever published by
+the Free Software Foundation.
+
+10. If you wish to incorporate parts of the Program into other free programs whose
+distribution conditions are different, write to the author to ask for permission. For
+software which is copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our decision will be
+guided by the two goals of preserving the free status of all derivatives of our free
+software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
+WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+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 the "copyright" line and a pointer to where the
+full notice is found.
+
+one line to give the program`s name and an idea of what it does.
+Copyright (C) yyyy name of author
+
+This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License
+as published by the Free Software Foundation; either version 2
+of the License, or (at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this when it starts
+in an interactive mode:
+
+Gnomovision version 69, Copyright (C) year name of author
+Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
+type `show w`. This is free software, and you are welcome
+to redistribute it under certain conditions; type `show c`
+for details.
+The hypothetical commands `show w` and `show c` should show the appropriate parts of
+the General Public License. Of course, the commands you use may be called something
+other than `show w` and `show c`; they could even be mouse-clicks or menu
+items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample;
+alter the names:
+
+Yoyodyne, Inc., hereby disclaims all copyright
+interest in the program `Gnomovision`
+(which makes passes at compilers) written
+by James Hacker.
+
+signature of Ty Coon, 1 April 1989
+Ty Coon, President of Vice
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may consider it
+more useful to permit linking proprietary applications with the library. If this is
+what you want to do, use the GNU Lesser General Public License instead of this
+License.
+
+
+
+
+GPL-2.0-with-GCC-exception
+
+
+insert GPL v2 text here
+
+GCC Linking Exception
+In addition to the permissions in the GNU General Public License, the Free
+Software Foundation gives you unlimited permission to link the compiled version
+of this file into combinations with other programs, and to distribute those
+combinations without any restriction coming from the use of this file. (The
+General Public License restrictions do apply in other respects; for example,
+they cover modification of the file, and distribution when not linked into a
+combine executable.)
+
+
+
+
+
+
+
+
+
+GPL-2.0-with-classpath-exception
+
+
+insert GPL v2 license text here
+
+Linking this library statically or dynamically with other modules is making a combined
+work based on this library. Thus, the terms and conditions of the GNU General Public
+License cover the whole combination.
+
+As a special exception, the copyright holders of this library give you permission to
+link this library with independent modules to produce an executable, regardless of the
+license terms of these independent modules, and to copy and distribute the resulting
+executable under terms of your choice, provided that you also meet, for each linked
+independent module, the terms and conditions of the license of that module. An
+independent module is a module which is not derived from or based on this library. If
+you modify this library, you may extend this exception to your version of the library,
+but you are not obligated to do so. If you do not wish to do so, delete this exception
+statement from your version.
+
+
+
+
+GPL-3.0
+
+GNU GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+Preamble
+
+The GNU General Public License is a free, copyleft license for software and other
+kinds of works.
+
+The licenses for most software and other practical works are designed to take away
+your freedom to share and change the works. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change all versions of a
+program--to make sure it remains free software for all its users. We, the Free
+Software Foundation, use the GNU General Public License for most of our software; it
+applies also to any other work released this way by its authors. You can apply it to
+your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for them if you wish), that you receive source
+code or can get it if you want it, that you can change the software or use pieces of
+it in new free programs, and that you know you can do these things.
+
+To protect your rights, we need to prevent others from denying you these rights or
+asking you to surrender the rights. Therefore, you have certain responsibilities if
+you distribute copies of the software, or if you modify it: responsibilities to
+respect the freedom of others.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee,
+you must pass on to the recipients the same freedoms that you received. You must make
+sure that they, too, receive or can get the source code. And you must show them these
+terms so they know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps: (1) assert
+copyright on the software, and (2) offer you this License giving you legal permission
+to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains that there is no
+warranty for this free software. For both users' and authors' sake, the GPL requires
+that modified versions be marked as changed, so that their problems will not be
+attributed erroneously to authors of previous versions.
+
+Some devices are designed to deny users access to install or run modified versions of
+the software inside them, although the manufacturer can do so. This is fundamentally
+incompatible with the aim of protecting users' freedom to change the software. The
+systematic pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we have designed
+this version of the GPL to prohibit the practice for those products. If such problems
+arise substantially in other domains, we stand ready to extend this provision to those
+domains in future versions of the GPL, as needed to protect the freedom of users.
+
+Finally, every program is threatened constantly by software patents. States should not
+allow patents to restrict development and use of software on general-purpose
+computers, but in those that do, we wish to avoid the special danger that patents
+applied to a free program could make it effectively proprietary. To prevent this, the
+GPL assures that patents cannot be used to render the program non-free.
+
+The precise terms and conditions for copying, distribution and modification follow.
+TERMS AND CONDITIONS
+0. Definitions.
+
+”This License” refers to version 3 of the GNU General Public License.
+
+”Copyright” also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+”The Program” refers to any copyrightable work licensed under this
+License. Each licensee is addressed as ”you”. ”Licensees”
+and ”recipients” may be individuals or organizations.
+
+To ”modify” a work means to copy from or adapt all or part of the work in
+a fashion requiring copyright permission, other than the making of an exact copy. The
+resulting work is called a ”modified version” of the earlier work or a
+work ”based on” the earlier work.
+
+A ”covered work” means either the unmodified Program or a work based on
+the Program.
+
+To ”propagate” a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for infringement under
+applicable copyright law, except executing it on a computer or modifying a private
+copy. Propagation includes copying, distribution (with or without modification),
+making available to the public, and in some countries other activities as well.
+
+To ”convey” a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through a computer
+network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays ”Appropriate Legal Notices” to the
+extent that it includes a convenient and prominently visible feature that (1) displays
+an appropriate copyright notice, and (2) tells the user that there is no warranty for
+the work (except to the extent that warranties are provided), that licensees may
+convey the work under this License, and how to view a copy of this License. If the
+interface presents a list of user commands or options, such as a menu, a prominent
+item in the list meets this criterion.
+1. Source Code.
+
+The ”source code” for a work means the preferred form of the work for
+making modifications to it. ”Object code” means any non-source form of a
+work.
+
+A ”Standard Interface” means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of interfaces
+specified for a particular programming language, one that is widely used among
+developers working in that language.
+
+The ”System Libraries” of an executable work include anything, other than
+the work as a whole, that (a) is included in the normal form of packaging a Major
+Component, but which is not part of that Major Component, and (b) serves only to
+enable use of the work with that Major Component, or to implement a Standard Interface
+for which an implementation is available to the public in source code form. A
+”Major Component”, in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system (if any) on which
+the executable work runs, or a compiler used to produce the work, or an object code
+interpreter used to run it.
+
+The ”Corresponding Source” for a work in object code form means all the
+source code needed to generate, install, and (for an executable work) run the object
+code and to modify the work, including scripts to control those activities. However,
+it does not include the work's System Libraries, or general-purpose tools or generally
+available free programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source includes interface
+definition files associated with source files for the work, and the source code for
+shared libraries and dynamically linked subprograms that the work is specifically
+designed to require, such as by intimate data communication or control flow between
+those subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate
+automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+2. Basic Permissions.
+
+All rights granted under this License are granted for the term of copyright on the
+Program, and are irrevocable provided the stated conditions are met. This License
+explicitly affirms your unlimited permission to run the unmodified Program. The output
+from running a covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your rights of fair use
+or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without
+conditions so long as your license otherwise remains in force. You may convey covered
+works to others for the sole purpose of having them make modifications exclusively for
+you, or provide you with facilities for running those works, provided that you comply
+with the terms of this License in conveying all material for which you do not control
+copyright. Those thus making or running the covered works for you must do so
+exclusively on your behalf, under your direction and control, on terms that prohibit
+them from making any copies of your copyrighted material outside their relationship
+with you.
+
+Conveying under any other circumstances is permitted solely under the conditions
+stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological measure under any
+applicable law fulfilling obligations under article 11 of the WIPO copyright treaty
+adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention
+of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of
+technological measures to the extent such circumvention is effected by exercising
+rights under this License with respect to the covered work, and you disclaim any
+intention to limit operation or modification of the work as a means of enforcing,
+against the work's users, your or third parties' legal rights to forbid circumvention
+of technological measures.
+4. Conveying Verbatim Copies.
+
+You may convey verbatim copies of the Program's source code as you receive it, in any
+medium, provided that you conspicuously and appropriately publish on each copy an
+appropriate copyright notice; keep intact all notices stating that this License and
+any non-permissive terms added in accord with section 7 apply to the code; keep intact
+all notices of the absence of any warranty; and give all recipients a copy of this
+License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer
+support or warranty protection for a fee.
+5. Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to produce it from
+the Program, in the form of source code under the terms of section 4, provided that
+you also meet all of these conditions:
+
+ * a) The work must carry prominent notices stating that you modified it, and
+giving a relevant date.
+ * b) The work must carry prominent notices stating that it is released under this
+License and any conditions added under section 7. This requirement modifies the
+requirement in section 4 to ”keep intact all notices”.
+ * c) You must license the entire work, as a whole, under this License to anyone
+who comes into possession of a copy. This License will therefore apply, along with any
+applicable section 7 additional terms, to the whole of the work, and all its parts,
+regardless of how they are packaged. This License gives no permission to license the
+work in any other way, but it does not invalidate such permission if you have
+separately received it.
+ * d) If the work has interactive user interfaces, each must display Appropriate
+Legal Notices; however, if the Program has interactive interfaces that do not display
+Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are
+not by their nature extensions of the covered work, and which are not combined with it
+such as to form a larger program, in or on a volume of a storage or distribution
+medium, is called an ”aggregate” if the compilation and its resulting
+copyright are not used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work in an aggregate
+does not cause this License to apply to the other parts of the aggregate.
+6. Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms of sections 4 and 5,
+provided that you also convey the machine-readable Corresponding Source under the
+terms of this License, in one of these ways:
+
+ * a) Convey the object code in, or embodied in, a physical product (including a
+physical distribution medium), accompanied by the Corresponding Source fixed on a
+durable physical medium customarily used for software interchange.
+ * b) Convey the object code in, or embodied in, a physical product (including a
+physical distribution medium), accompanied by a written offer, valid for at least
+three years and valid for as long as you offer spare parts or customer support for
+that product model, to give anyone who possesses the object code either (1) a copy of
+the Corresponding Source for all the software in the product that is covered by this
+License, on a durable physical medium customarily used for software interchange, for a
+price no more than your reasonable cost of physically performing this conveying of
+source, or (2) access to copy the Corresponding Source from a network server at no
+charge.
+ * c) Convey individual copies of the object code with a copy of the written offer
+to provide the Corresponding Source. This alternative is allowed only occasionally and
+noncommercially, and only if you received the object code with such an offer, in
+accord with subsection 6b.
+ * d) Convey the object code by offering access from a designated place (gratis or
+for a charge), and offer equivalent access to the Corresponding Source in the same way
+through the same place at no further charge. You need not require recipients to copy
+the Corresponding Source along with the object code. If the place to copy the object
+code is a network server, the Corresponding Source may be on a different server
+(operated by you or a third party) that supports equivalent copying facilities,
+provided you maintain clear directions next to the object code saying where to find
+the Corresponding Source. Regardless of what server hosts the Corresponding Source,
+you remain obligated to ensure that it is available for as long as needed to satisfy
+these requirements.
+ * e) Convey the object code using peer-to-peer transmission, provided you inform
+other peers where the object code and Corresponding Source of the work are being
+offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the
+Corresponding Source as a System Library, need not be included in conveying the object
+code work.
+
+A ”User Product” is either (1) a ”consumer product”, which
+means any tangible personal property which is normally used for personal, family, or
+household purposes, or (2) anything designed or sold for incorporation into a
+dwelling. In determining whether a product is a consumer product, doubtful cases shall
+be resolved in favor of coverage. For a particular product received by a particular
+user, ”normally used” refers to a typical or common use of that class of
+product, regardless of the status of the particular user or of the way in which the
+particular user actually uses, or expects or is expected to use, the product. A
+product is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent the only
+significant mode of use of the product.
+
+”Installation Information” for a User Product means any methods,
+procedures, authorization keys, or other information required to install and execute
+modified versions of a covered work in that User Product from a modified version of
+its Corresponding Source. The information must suffice to ensure that the continued
+functioning of the modified object code is in no case prevented or interfered with
+solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for
+use in, a User Product, and the conveying occurs as part of a transaction in which the
+right of possession and use of the User Product is transferred to the recipient in
+perpetuity or for a fixed term (regardless of how the transaction is characterized),
+the Corresponding Source conveyed under this section must be accompanied by the
+Installation Information. But this requirement does not apply if neither you nor any
+third party retains the ability to install modified object code on the User Product
+(for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to
+continue to provide support service, warranty, or updates for a work that has been
+modified or installed by the recipient, or for the User Product in which it has been
+modified or installed. Access to a network may be denied when the modification itself
+materially and adversely affects the operation of the network or violates the rules
+and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with
+this section must be in a format that is publicly documented (and with an
+implementation available to the public in source code form), and must require no
+special password or key for unpacking, reading or copying.
+7. Additional Terms.
+
+”Additional permissions” are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions. Additional
+permissions that are applicable to the entire Program shall be treated as though they
+were included in this License, to the extent that they are valid under applicable law.
+If additional permissions apply only to part of the Program, that part may be used
+separately under those permissions, but the entire Program remains governed by this
+License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional
+permissions from that copy, or from any part of it. (Additional permissions may be
+written to require their own removal in certain cases when you modify the work.) You
+may place additional permissions on material, added by you to a covered work, for
+which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered
+work, you may (if authorized by the copyright holders of that material) supplement the
+terms of this License with terms:
+
+ * a) Disclaiming warranty or limiting liability differently from the terms of
+sections 15 and 16 of this License; or
+ * b) Requiring preservation of specified reasonable legal notices or author
+attributions in that material or in the Appropriate Legal Notices displayed by works
+containing it; or
+ * c) Prohibiting misrepresentation of the origin of that material, or requiring
+that modified versions of such material be marked in reasonable ways as different from
+the original version; or
+ * d) Limiting the use for publicity purposes of names of licensors or authors of
+the material; or
+ * e) Declining to grant rights under trademark law for use of some trade names,
+trademarks, or service marks; or
+ * f) Requiring indemnification of licensors and authors of that material by anyone
+who conveys the material (or modified versions of it) with contractual assumptions of
+liability to the recipient, for any liability that these contractual assumptions
+directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered ”further
+restrictions” within the meaning of section 10. If the Program as you received
+it, or any part of it, contains a notice stating that it is governed by this License
+along with a term that is a further restriction, you may remove that term. If a
+license document contains a further restriction but permits relicensing or conveying
+under this License, you may add to a covered work material governed by the terms of
+that license document, provided that the further restriction does not survive such
+relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the
+relevant source files, a statement of the additional terms that apply to those files,
+or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a
+separately written license, or stated as exceptions; the above requirements apply
+either way.
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this
+License. Any attempt otherwise to propagate or modify it is void, and will
+automatically terminate your rights under this License (including any patent licenses
+granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a
+particular copyright holder is reinstated (a) provisionally, unless and until the
+copyright holder explicitly and finally terminates your license, and (b) permanently,
+if the copyright holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if
+the copyright holder notifies you of the violation by some reasonable means, this is
+the first time you have received notice of violation of this License (for any work)
+from that copyright holder, and you cure the violation prior to 30 days after your
+receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of
+parties who have received copies or rights from you under this License. If your rights
+have been terminated and not permanently reinstated, you do not qualify to receive new
+licenses for the same material under section 10.
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the
+Program. Ancillary propagation of a covered work occurring solely as a consequence of
+using peer-to-peer transmission to receive a copy likewise does not require
+acceptance. However, nothing other than this License grants you permission to
+propagate or modify any covered work. These actions infringe copyright if you do not
+accept this License. Therefore, by modifying or propagating a covered work, you
+indicate your acceptance of this License to do so.
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license
+from the original licensors, to run, modify and propagate that work, subject to this
+License. You are not responsible for enforcing compliance by third parties with this
+License.
+
+An ”entity transaction” is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an organization, or
+merging organizations. If propagation of a covered work results from an entity
+transaction, each party to that transaction who receives a copy of the work also
+receives whatever licenses to the work the party's predecessor in interest had or
+could give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if the predecessor
+has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or
+affirmed under this License. For example, you may not impose a license fee, royalty,
+or other charge for exercise of rights granted under this License, and you may not
+initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging
+that any patent claim is infringed by making, using, selling, offering for sale, or
+importing the Program or any portion of it.
+11. Patents.
+
+A ”contributor” is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The work thus licensed
+is called the contributor's ”contributor version”.
+
+A contributor's ”essential patent claims” are all patent claims owned or
+controlled by the contributor, whether already acquired or hereafter acquired, that
+would be infringed by some manner, permitted by this License, of making, using, or
+selling its contributor version, but do not include claims that would be infringed
+only as a consequence of further modification of the contributor version. For purposes
+of this definition, ”control” includes the right to grant patent
+sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license
+under the contributor's essential patent claims, to make, use, sell, offer for sale,
+import and otherwise run, modify and propagate the contents of its contributor
+version.
+
+In the following three paragraphs, a ”patent license” is any express
+agreement or commitment, however denominated, not to enforce a patent (such as an
+express permission to practice a patent or covenant not to sue for patent
+infringement). To ”grant” such a patent license to a party means to make
+such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the
+Corresponding Source of the work is not available for anyone to copy, free of charge
+and under the terms of this License, through a publicly available network server or
+other readily accessible means, then you must either (1) cause the Corresponding
+Source to be so available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner consistent with
+the requirements of this License, to extend the patent license to downstream
+recipients. ”Knowingly relying” means you have actual knowledge that, but
+for the patent license, your conveying the covered work in a country, or your
+recipient's use of the covered work in a country, would infringe one or more
+identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey,
+or propagate by procuring conveyance of, a covered work, and grant a patent license to
+some of the parties receiving the covered work authorizing them to use, propagate,
+modify or convey a specific copy of the covered work, then the patent license you
+grant is automatically extended to all recipients of the covered work and works based
+on it.
+
+A patent license is ”discriminatory” if it does not include within the
+scope of its coverage, prohibits the exercise of, or is conditioned on the
+non-exercise of one or more of the rights that are specifically granted under this
+License. You may not convey a covered work if you are a party to an arrangement with a
+third party that is in the business of distributing software, under which you make
+payment to the third party based on the extent of your activity of conveying the work,
+and under which the third party grants, to any of the parties who would receive the
+covered work from you, a discriminatory patent license (a) in connection with copies
+of the covered work conveyed by you (or copies made from those copies), or (b)
+primarily for and in connection with specific products or compilations that contain
+the covered work, unless you entered into that arrangement, or that patent license was
+granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied
+license or other defenses to infringement that may otherwise be available to you under
+applicable patent law.
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that
+contradict the conditions of this License, they do not excuse you from the conditions
+of this License. If you cannot convey a covered work so as to satisfy simultaneously
+your obligations under this License and any other pertinent obligations, then as a
+consequence you may not convey it at all. For example, if you agree to terms that
+obligate you to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this License would be
+to refrain entirely from conveying the Program.
+13. Use with the GNU Affero General Public License.
+
+Notwithstanding any other provision of this License, you have permission to link or
+combine any covered work with a work licensed under version 3 of the GNU Affero
+General Public License into a single combined work, and to convey the resulting work.
+The terms of this License will continue to apply to the part which is the covered
+work, but the special requirements of the GNU Affero General Public License, section
+13, concerning interaction through a network will apply to the combination as such.
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies that a
+certain numbered version of the GNU General Public License ”or any later
+version” applies to it, you have the option of following the terms and
+conditions either of that numbered version or of any later version published by the
+Free Software Foundation. If the Program does not specify a version number of the GNU
+General Public License, you may choose any version ever published by the Free Software
+Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU
+General Public License can be used, that proxy's public statement of acceptance of a
+version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions. However, no
+additional obligations are imposed on any author or copyright holder as a result of
+your choosing to follow a later version.
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM ”AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
+EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
+DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
+WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be
+given local legal effect according to their terms, reviewing courts shall apply local
+law that most closely approximates an absolute waiver of all civil liability in
+connection with the Program, unless a warranty or assumption of liability accompanies
+a copy of the Program in return for a fee.
+
+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 the ”copyright” line and a pointer to
+where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program does terminal interaction, make it output a short notice like this when
+it starts in an interactive mode:
+
+ <program> Copyright (C) <year> <name of author>
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate parts of
+the General Public License. Of course, your program's commands might be different; for
+a GUI interface, you would use an ”about box”.
+
+You should also get your employer (if you work as a programmer) or school, if any, to
+sign a ”copyright disclaimer” for the program, if necessary. For more
+information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+The GNU General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may consider it
+more useful to permit linking proprietary applications with the library. If this is
+what you want to do, use the GNU Lesser General Public License instead of this
+License. But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
+
+
+
+GPL-3.0-with-GCC-exception
+
+
+insert GPL v3 text here
+
+GCC RUNTIME LIBRARY EXCEPTION
+Version 3.1, 31 March 2009
+
+General information:
+http://www.gnu.org/licenses/gcc-exception.html
+Copyright (C) 2009 Free Software Foundation, Inc. <http://fsf.org/>
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+This GCC Runtime Library Exception ("Exception") is an additional permission under
+section 7 of the GNU General Public License, version 3 ("GPLv3"). It applies to a
+given file (the "Runtime Library") that bears a notice placed by the copyright holder
+of the file stating that the file is governed by GPLv3 along with this Exception.
+When you use GCC to compile a program, GCC may combine portions of certain GCC header
+files and runtime libraries with the compiled program. The purpose of this Exception
+is to allow compilation of non-GPL (including proprietary) programs to use, in this
+way, the header files and runtime libraries covered by this Exception.
+
+0. Definitions.
+A file is an "Independent Module" if it either requires the Runtime Library for
+execution after a Compilation Process, or makes use of an interface provided by the
+Runtime Library, but is not otherwise based on the Runtime Library.
+"GCC" means a version of the GNU Compiler Collection, with or without modifications,
+governed by version 3 (or a specified later version) of the GNU General Public License
+(GPL) with the option of using any subsequent versions published by the FSF.
+"GPL-compatible Software" is software whose conditions of propagation, modification
+and use would permit combination with GCC in accord with the license of GCC.
+"Target Code" refers to output from any compiler for a real or virtual target
+processor architecture, in executable form or suitable for input to an assembler,
+loader, linker and/or execution phase. Notwithstanding that, Target Code does not
+include data in any format that is used as a compiler intermediate representation, or
+used for producing a compiler intermediate representation.
+The "Compilation Process" transforms code entirely represented in non-intermediate
+languages designed for human-written code, and/or in Java Virtual Machine byte code,
+into Target Code. Thus, for example, use of source code generators and preprocessors
+need not be considered part of the Compilation Process, since the Compilation Process
+can be understood as starting with the output of the generators or preprocessors.
+A Compilation Process is "Eligible" if it is done using GCC, alone or with other
+GPL-compatible software, or if it is done without using any work based on GCC. For
+example, using non-GPL-compatible Software to optimize any GCC intermediate
+representations would not qualify as an Eligible Compilation Process.
+
+1. Grant of Additional Permission.
+You have permission to propagate a work of Target Code formed by combining the Runtime
+Library with Independent Modules, even if such propagation would otherwise violate the
+terms of GPLv3, provided that all Target Code was generated by Eligible Compilation
+Processes. You may then convey such a combination under terms of your choice,
+consistent with the licensing of the Independent Modules.
+
+2. No Weakening of GCC Copyleft.
+The availability of this Exception does not imply any general presumption that
+third-party software is unaffected by the copyleft requirements of the license of GCC.
+
+
+
+
+GPL-3.0-with-autoconf-exception
+
+
+insert GPL v3 text here
+
+AUTOCONF CONFIGURE SCRIPT EXCEPTION
+
+Version 3.0, 18 August 2009
+
+Copyright © 2009 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+
+This Exception is an additional permission under section 7 of the GNU General Public
+License, version 3 ("GPLv3"). It applies to a given file that bears a notice placed by
+the copyright holder of the file stating that the file is governed by GPLv3 along with
+this Exception.
+
+The purpose of this Exception is to allow distribution of Autoconf`s typical output
+under terms of the recipient`s choice (including proprietary).
+
+0. Definitions.
+"Covered Code" is the source or object code of a version of Autoconf that is a covered
+work under this License.
+
+"Normally Copied Code" for a version of Autoconf means all parts of its Covered Code
+which that version can copy from its code (i.e., not from its input file) into its
+minimally verbose, non-debugging and non-tracing output.
+
+"Ineligible Code" is Covered Code that is not Normally Copied Code.
+
+1. Grant of Additional Permission.
+You have permission to propagate output of Autoconf, even if such propagation would
+otherwise violate the terms of GPLv3. However, if by modifying Autoconf you cause any
+Ineligible Code of the version you received to become Normally Copied Code of your
+modified version, then you void this Exception for the resulting covered work. If you
+convey that resulting covered work, you must remove this Exception in accordance with
+the second paragraph of Section 7 of GPLv3.
+
+2. No Weakening of Autoconf Copyleft.
+The availability of this Exception does not imply any general presumption that
+third-party software is unaffected by the copyleft requirements of the license of
+Autoconf.
+
+
+
+
+ICU
+
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright (c) 1995-2012 International Business Machines Corporation and others
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this
+software and associated documentation files (the "Software"), to deal in the Software
+without restriction, including without limitation the rights to use, copy, modify,
+merge, publish, distribute, and/or sell copies of the Software, and to permit persons
+to whom the Software is furnished to do so, provided that the above copyright
+notice(s) and this permission notice appear in all copies of the Software and that
+both the above copyright notice(s) and this permission notice appear in supporting
+documentation.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
+PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
+SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
+LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
+SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder shall not be used
+in advertising or otherwise to promote the sale, use or other dealings in this
+Software without prior written authorization of the copyright holder.
+
+All trademarks and registered trademarks mentioned herein are the property of their
+respective owners.
+
+
+
+IPL-1.0
+
+
+IBM Public License Version 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM
+PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
+OF THE PROGRAM CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+"Contribution" means:
+
+in the case of International Business Machines Corporation ("IBM"), the Original
+Program, and
+in the case of each Contributor,
+changes to the Program, and
+additions to the Program;
+where such changes and/or additions to the Program originate from and
+are distributed by that particular Contributor. A Contribution
+`originates` from a Contributor if it was added to the Program by
+such Contributor itself or anyone acting on such Contributor`s
+behalf. Contributions do not include additions to the Program which:
+(i) are separate modules of software distributed in conjunction with
+the Program under their own license agreement, and (ii) are not
+derivative works of the Program.
+
+"Contributor" means IBM and any other entity that distributes the Program.
+
+"Licensed Patents " mean patent claims licensable by a
+Contributor which are necessarily infringed by the use or sale of its
+Contribution alone or when combined with the Program.
+
+"Original Program" means the original version of the software
+accompanying this Agreement as released by IBM, including source
+code, object code and documentation, if any.
+
+"Program" means the Original Program and Contributions.
+
+"Recipient" means anyone who receives the Program under this
+Agreement, including all Contributors.
+
+2. GRANT OF RIGHTS
+Subject to the terms of this Agreement, each Contributor hereby
+grants Recipient a non-exclusive, worldwide, royalty-free copyright
+license to reproduce, prepare derivative works of, publicly display,
+publicly perform, distribute and sublicense the Contribution of such
+Contributor, if any, and such derivative works, in source code and
+object code form.
+Subject to the terms of this Agreement, each Contributor hereby
+grants Recipient a non-exclusive, worldwide, royalty-free patent
+license under Licensed Patents to make, use, sell, offer to sell,
+import and otherwise transfer the Contribution of such Contributor,
+if any, in source code and object code form. This patent license
+shall apply to the combination of the Contribution and the Program
+if, at the time the Contribution is added by the Contributor, such
+addition of the Contribution causes such combination to be covered by
+the Licensed Patents. The patent license shall not apply to any
+other combinations which include the Contribution. No hardware per
+se is licensed hereunder.
+
+Recipient understands that although each Contributor grants the
+licenses to its Contributions set forth herein, no assurances are
+provided by any Contributor that the Program does not infringe the
+patent or other intellectual property rights of any other entity.
+Each Contributor disclaims any liability to Recipient for claims
+brought by any other entity based on infringement of intellectual
+property rights or otherwise. As a condition to exercising the
+rights and licenses granted hereunder, each Recipient hereby assumes
+sole responsibility to secure any other intellectual property rights
+needed, if any. For example, if a third party patent license is
+required to allow Recipient to distribute the Program, it is
+Recipient`s responsibility to acquire that license before
+distributing the Program.
+Each Contributor represents that to its knowledge it has
+sufficient copyright rights in its Contribution, if any, to grant the
+copyright license set forth in this Agreement.
+3. REQUIREMENTS
+A Contributor may choose to distribute
+the Program in object code form under its own license agreement,
+provided that:
+
+it complies with the terms and conditions of this Agreement; and
+its license agreement:
+effectively disclaims on behalf of all Contributors all warranties
+and conditions, express and implied, including warranties or
+conditions of title and non-infringement, and implied warranties or
+conditions of merchantability and fitness for a particular purpose;
+effectively excludes on behalf of all Contributors all liability
+for damages, including direct, indirect, special, incidental and
+consequential damages, such as lost profits;
+states that any provisions which differ from this Agreement are
+offered by that Contributor alone and not by any other party; and
+
+states that source code for the Program is available from such
+Contributor, and informs licensees how to obtain it in a reasonable
+manner on or through a medium customarily used for software exchange.
+When the Program is made available in source code form:
+
+it must be made available under this Agreement; and
+a copy of this Agreement must be included with each copy of the
+Program.
+Each Contributor must include the following in a conspicuous location in the Program:
+
+Copyright (C) 1996, 1999 International Business Machines Corporation and others. All
+Rights Reserved.
+
+In addition, each Contributor must identify itself as the originator
+of its Contribution, if any, in a manner that reasonably allows
+subsequent Recipients to identify the originator of the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+Commercial distributors of software may accept certain
+responsibilities with respect to end users, business partners and the
+like. While this license is intended to facilitate the commercial
+use of the Program, the Contributor who includes the Program in a
+commercial product offering should do so in a manner which does not
+create potential liability for other Contributors. Therefore, if a
+Contributor includes the Program in a commercial product offering,
+such Contributor ("Commercial Contributor") hereby agrees to defend
+and indemnify every other Contributor ("Indemnified Contributor")
+against any losses, damages and costs (collectively "Losses") arising
+from claims, lawsuits and other legal actions brought by a third
+party against the Indemnified Contributor to the extent caused by the
+acts or omissions of such Commercial Contributor in connection with
+its distribution of the Program in a commercial product offering.
+The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement.
+In order to qualify, an Indemnified Contributor must: a) promptly
+notify the Commercial Contributor in writing of such claim, and b)
+allow the Commercial Contributor to control, and cooperate with the
+Commercial Contributor in, the defense and any related settlement
+negotiations. The Indemnified Contributor may participate in any
+such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial
+product offering, Product X. That Contributor is then a Commercial
+Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance
+claims and warranties are such Commercial Contributor`s
+responsibility alone. Under this section, the Commercial Contributor
+would have to defend claims against the other Contributors related to
+those performance claims and warranties, and if a court requires any
+other Contributor to pay any damages as a result, the Commercial
+Contributor must pay those damages.
+
+5. NO WARRANTY
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS
+PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
+WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY
+OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
+responsible for determining the appropriateness of using and
+distributing the Program and assumes all risks associated with its
+exercise of rights under this Agreement, including but not limited to
+the risks and costs of program errors, compliance with applicable
+laws, damage to or loss of data, programs or equipment, and
+unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT
+NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
+TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
+THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
+GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+If any provision of this Agreement is invalid or unenforceable under
+applicable law, it shall not affect the validity or enforceability of
+the remainder of the terms of this Agreement, and without further
+action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.
+
+If Recipient institutes patent litigation against a Contributor with
+respect to a patent applicable to software (including a cross-claim
+or counterclaim in a lawsuit), then any patent licenses granted by
+that Contributor to such Recipient under this Agreement shall
+terminate as of the date such litigation is filed. In addition, if
+Recipient institutes patent litigation against any entity (including
+a cross-claim or counterclaim in a lawsuit) alleging that the Program
+itself (excluding combinations of the Program with other software or
+hardware) infringes such Recipient`s patent(s), then such Recipient`s
+rights granted under Section 2(b) shall terminate as of the date such
+litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it
+fails to comply with any of the material terms or conditions of this
+Agreement and does not cure such failure in a reasonable period of
+time after becoming aware of such noncompliance. If all Recipient`s
+rights under this Agreement terminate, Recipient agrees to cease use
+and distribution of the Program as soon as reasonably practicable.
+However, Recipient`s obligations under this Agreement and any
+licenses granted by Recipient relating to the Program shall continue
+and survive.
+
+IBM may publish new versions (including revisions) of this Agreement
+from time to time. Each new version of the Agreement will be given a
+distinguishing version number. The Program (including Contributions)
+may always be distributed subject to the version of the Agreement
+under which it was received. In addition, after a new version of the
+Agreement is published, Contributor may elect to distribute the
+Program (including its Contributions) under the new version. No one
+other than IBM has the right to modify this Agreement. Except as
+expressly stated in Sections 2(a) and 2(b) above, Recipient receives
+no rights or licenses to the intellectual property of any Contributor
+under this Agreement, whether expressly, by implication, estoppel or
+otherwise. All rights in the Program not expressly granted under
+this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and
+the intellectual property laws of the United States of America. No
+party to this Agreement will bring a legal action under this
+Agreement more than one year after the cause of action arose. Each
+party waives its rights to a jury trial in any resulting litigation.
+
+
+
+
+ISC
+
+
+ISC License:
+
+Copyright © 2004-2010 by Internet Systems Consortium, Inc. ("ISC")
+Copyright © 1995-2003 by Internet Software Consortium
+
+Permission to use, copy, modify, and/or distribute this software for any purpose with
+or without fee is hereby granted, provided that the above copyright notice and this
+permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
+SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT
+SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
+DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
+OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
+THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+
+
+
+JLEX
+
+ JLEX COPYRIGHT NOTICE, LICENSE, AND DISCLAIMER
+ Copyright 1996-2000 by Elliot Joel Berk and C. Scott Ananian
+
+ Permission to use, copy, modify, and distribute this software and its
+ documentation for any purpose and without fee is hereby granted,
+ provided that the above copyright notice appear in all copies and that
+ both the copyright notice and this permission notice and warranty
+ disclaimer appear in supporting documentation, and that the name of
+ the authors or their employers not be used in advertising or publicity
+ pertaining to distribution of the software without specific, written
+ prior permission.
+
+ The authors and their employers disclaim all warranties with regard to
+ this software, including all implied warranties of merchantability and
+ fitness. In no event shall the authors or their employers be liable
+ for any special, indirect or consequential damages or any damages
+ whatsoever resulting from loss of use, data or profits, whether in an
+ action of contract, negligence or other tortious action, arising out
+ of or in connection with the use or performance of this software.
+
+
+
+LGPL-2.0
+
+GNU LIBRARY GENERAL PUBLIC LICENSE
+
+
+
+Version 2, June 1991
+
+
+
+Copyright (C) 1991 Free Software Foundation, Inc.
+
+51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+
+of this license document, but changing it is not allowed.
+
+
+
+[This is the first released version of the library GPL. It is
+
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+Preamble
+
+
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public Licenses are intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users.
+
+
+
+This license, the Library General Public License, applies to some specially designated
+Free Software Foundation software, and to any other libraries whose authors decide to
+use it. You can use it for your libraries, too.
+
+
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for this service if you wish), that you receive
+source code or can get it if you want it, that you can change the software or use
+pieces of it in new free programs; and that you know you can do these things.
+
+
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you
+these rights or to ask you to surrender the rights. These restrictions translate to
+certain responsibilities for you if you distribute copies of the library, or if you
+modify it.
+
+
+
+For example, if you distribute copies of the library, whether gratis or for a fee, you
+must give the recipients all the rights that we gave you. You must make sure that
+they, too, receive or can get the source code. If you link a program with the library,
+you must provide complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling it. And you must
+show them these terms so they know their rights.
+
+
+
+Our method of protecting your rights has two steps: (1) copyright the library, and (2)
+offer you this license which gives you legal permission to copy, distribute and/or
+modify the library.
+
+
+
+Also, for each distributor's protection, we want to make certain that everyone
+understands that there is no warranty for this free library. If the library is
+modified by someone else and passed on, we want its recipients to know that what they
+have is not the original version, so that any problems introduced by others will not
+reflect on the original authors' reputations.
+
+
+
+Finally, any free program is threatened constantly by software patents. We wish to
+avoid the danger that companies distributing free software will individually obtain
+patent licenses, thus in effect transforming the program into proprietary software. To
+prevent this, we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+
+
+Most GNU software, including some libraries, is covered by the ordinary GNU General
+Public License, which was designed for utility programs. This license, the GNU Library
+General Public License, applies to certain designated libraries. This license is quite
+different from the ordinary one; be sure to read it in full, and don't assume that
+anything in it is the same as in the ordinary license.
+
+
+
+The reason we have a separate public license for some libraries is that they blur the
+distinction we usually make between modifying or adding to a program and simply using
+it. Linking a program with a library, without changing the library, is in some sense
+simply using the library, and is analogous to running a utility program or application
+program. However, in a textual and legal sense, the linked executable is a combined
+work, a derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+
+
+Because of this blurred distinction, using the ordinary General Public License for
+libraries did not effectively promote software sharing, because most developers did
+not use the libraries. We concluded that weaker conditions might promote sharing
+better.
+
+
+
+However, unrestricted linking of non-free programs would deprive the users of those
+programs of all benefit from the free status of the libraries themselves. This Library
+General Public License is intended to permit developers of non-free programs to use
+free libraries, while preserving your freedom as a user of such programs to change the
+free libraries that are incorporated in them. (We have not seen how to achieve this as
+regards changes in header files, but we have achieved it as regards changes in the
+actual functions of the Library.) The hope is that this will lead to faster
+development of free libraries.
+
+
+
+The precise terms and conditions for copying, distribution and modification follow.
+Pay close attention to the difference between a "work based on the library" and a
+"work that uses the library". The former contains code derived from the library, while
+the latter only works together with the library.
+
+
+
+Note that it is possible for a library to be covered by the ordinary General Public
+License rather than by this special one.
+
+
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+
+
+0. This License Agreement applies to any software library which contains a notice
+placed by the copyright holder or other authorized party saying it may be distributed
+under the terms of this Library General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+
+
+A "library" means a collection of software functions and/or data prepared so as to be
+conveniently linked with application programs (which use some of those functions and
+data) to form executables.
+
+
+
+The "Library", below, refers to any such software library or work which has been
+distributed under these terms. A "work based on the Library" means either the Library
+or any derivative work under copyright law: that is to say, a work containing the
+Library or a portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is included without
+limitation in the term "modification".)
+
+
+
+"Source code" for a work means the preferred form of the work for making modifications
+to it. For a library, complete source code means all the source code for all modules
+it contains, plus any associated interface definition files, plus the scripts used to
+control compilation and installation of the library.
+
+
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running a program using the Library is
+not restricted, and output from such a program is covered only if its contents
+constitute a work based on the Library (independent of the use of the Library in a
+tool for writing it). Whether that is true depends on what the Library does and what
+the program that uses the Library does.
+
+
+
+1. You may copy and distribute verbatim copies of the Library's complete source code
+as you receive it, in any medium, provided that you conspicuously and appropriately
+publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
+intact all the notices that refer to this License and to the absence of any warranty;
+and distribute a copy of this License along with the Library.
+
+
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+
+
+2. You may modify your copy or copies of the Library or any portion of it, thus
+forming a work based on the Library, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+
+
+a) The modified work must itself be a software library.
+
+b) You must cause the files modified to carry prominent notices stating that you
+changed the files and the date of any change.
+
+c) You must cause the whole of the work to be licensed at no charge to all third
+parties under the terms of this License.
+
+d) If a facility in the modified Library refers to a function or a table of data to be
+supplied by an application program that uses the facility, other than as an argument
+passed when the facility is invoked, then you must make a good faith effort to ensure
+that, in the event an application does not supply such function or table, the facility
+still operates, and performs whatever part of its purpose remains meaningful.
+
+(For example, a function in a library to compute square roots has a purpose that is
+entirely well-defined independent of the application. Therefore, Subsection 2d
+requires that any application-supplied function or table used by this function must be
+optional: if the application does not supply it, the square root function must still
+compute square roots.)
+
+
+
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Library, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Library,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Library.
+
+
+
+In addition, mere aggregation of another work not based on the Library with the
+Library (or with a work based on the Library) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+
+
+3. You may opt to apply the terms of the ordinary GNU General Public License instead
+of this License to a given copy of the Library. To do this, you must alter all the
+notices that refer to this License, so that they refer to the ordinary GNU General
+Public License, version 2, instead of to this License. (If a newer version than
+version 2 of the ordinary GNU General Public License has appeared, then you can
+specify that version instead if you wish.) Do not make any other change in these
+notices.
+
+
+
+Once this change is made in a given copy, it is irreversible for that copy, so the
+ordinary GNU General Public License applies to all subsequent copies and derivative
+works made from that copy.
+
+
+
+This option is useful when you wish to copy part of the code of the Library into a
+program that is not a library.
+
+
+
+4. You may copy and distribute the Library (or a portion or derivative of it, under
+Section 2) in object code or executable form under the terms of Sections 1 and 2 above
+provided that you accompany it with the complete corresponding machine-readable source
+code, which must be distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange.
+
+
+
+If distribution of object code is made by offering access to copy from a designated
+place, then offering equivalent access to copy the source code from the same place
+satisfies the requirement to distribute the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+
+
+5. A program that contains no derivative of any portion of the Library, but is
+designed to work with the Library by being compiled or linked with it, is called a
+"work that uses the Library". Such a work, in isolation, is not a derivative work of
+the Library, and therefore falls outside the scope of this License.
+
+
+
+However, linking a "work that uses the Library" with the Library creates an executable
+that is a derivative of the Library (because it contains portions of the Library),
+rather than a "work that uses the library". The executable is therefore covered by
+this License. Section 6 states terms for distribution of such executables.
+
+
+
+When a "work that uses the Library" uses material from a header file that is part of
+the Library, the object code for the work may be a derivative work of the Library even
+though the source code is not. Whether this is true is especially significant if the
+work can be linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+
+
+If such an object file uses only numerical parameters, data structure layouts and
+accessors, and small macros and small inline functions (ten lines or less in length),
+then the use of the object file is unrestricted, regardless of whether it is legally a
+derivative work. (Executables containing this object code plus portions of the Library
+will still fall under Section 6.)
+
+
+
+Otherwise, if the work is a derivative of the Library, you may distribute the object
+code for the work under the terms of Section 6. Any executables containing that work
+also fall under Section 6, whether or not they are linked directly with the Library
+itself.
+
+
+
+6. As an exception to the Sections above, you may also compile or link a "work that
+uses the Library" with the Library to produce a work containing portions of the
+Library, and distribute that work under terms of your choice, provided that the terms
+permit modification of the work for the customer's own use and reverse engineering for
+debugging such modifications.
+
+
+
+You must give prominent notice with each copy of the work that the Library is used in
+it and that the Library and its use are covered by this License. You must supply a
+copy of this License. If the work during execution displays copyright notices, you
+must include the copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one of these things:
+
+
+
+a) Accompany the work with the complete corresponding machine-readable source code for
+the Library including whatever changes were used in the work (which must be
+distributed under Sections 1 and 2 above); and, if the work is an executable linked
+with the Library, with the complete machine-readable "work that uses the Library", as
+object code and/or source code, so that the user can modify the Library and then
+relink to produce a modified executable containing the modified Library. (It is
+understood that the user who changes the contents of definitions files in the Library
+will not necessarily be able to recompile the application to use the modified
+definitions.)
+
+b) Accompany the work with a written offer, valid for at least three years, to give
+the same user the materials specified in Subsection 6a, above, for a charge no more
+than the cost of performing this distribution.
+
+c) If distribution of the work is made by offering access to copy from a designated
+place, offer equivalent access to copy the above specified materials from the same
+place.
+
+d) Verify that the user has already received a copy of these materials or that you
+have already sent this user a copy.
+
+For an executable, the required form of the "work that uses the Library" must include
+any data and utility programs needed for reproducing the executable from it. However,
+as a special exception, the source code distributed need not include anything that is
+normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+
+
+It may happen that this requirement contradicts the license restrictions of other
+proprietary libraries that do not normally accompany the operating system. Such a
+contradiction means you cannot use both them and the Library together in an executable
+that you distribute.
+
+
+
+7. You may place library facilities that are a work based on the Library side-by-side
+in a single library together with other library facilities not covered by this
+License, and distribute such a combined library, provided that the separate
+distribution of the work based on the Library and of the other library facilities is
+otherwise permitted, and provided that you do these two things:
+
+
+
+a) Accompany the combined library with a copy of the same work based on the Library,
+uncombined with any other library facilities. This must be distributed under the terms
+of the Sections above.
+
+b) Give prominent notice with the combined library of the fact that part of it is a
+work based on the Library, and explaining where to find the accompanying uncombined
+form of the same work.
+
+8. You may not copy, modify, sublicense, link with, or distribute the Library except
+as expressly provided under this License. Any attempt otherwise to copy, modify,
+sublicense, link with, or distribute the Library is void, and will automatically
+terminate your rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses terminated so long
+as such parties remain in full compliance.
+
+
+
+9. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Library or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Library or works based on it.
+
+
+
+10. Each time you redistribute the Library (or any work based on the Library), the
+recipient automatically receives a license from the original licensor to copy,
+distribute, link with or modify the Library subject to these terms and conditions. You
+may not impose any further restrictions on the recipients' exercise of the rights
+granted herein. You are not responsible for enforcing compliance by third parties to
+this License.
+
+
+
+11. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Library at all. For example, if a patent license would not permit royalty-free
+redistribution of the Library by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply, and the section as a
+whole is intended to apply in other circumstances.
+
+
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+
+
+12. If the distribution and/or use of the Library is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Library under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+
+
+13. The Free Software Foundation may publish revised and/or new versions of the
+Library General Public License from time to time. Such new versions will be similar in
+spirit to the present version, but may differ in detail to address new problems or
+concerns.
+
+
+
+Each version is given a distinguishing version number. If the Library specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Library does not
+specify a license version number, you may choose any version ever published by the
+Free Software Foundation.
+
+
+
+14. If you wish to incorporate parts of the Library into other free programs whose
+distribution conditions are incompatible with these, write to the author to ask for
+permission. For software which is copyrighted by the Free Software Foundation, write
+to the Free Software Foundation; we sometimes make exceptions for this. Our decision
+will be guided by the two goals of preserving the free status of all derivatives of
+our free software and of promoting the sharing and reuse of software generally.
+
+
+
+NO WARRANTY
+
+
+
+15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+
+
+16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
+WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+
+
+END OF TERMS AND CONDITIONS
+
+
+
+How to Apply These Terms to Your New Libraries
+
+
+
+If you develop a new library, and you want it to be of the greatest possible use to
+the public, we recommend making it free software that everyone can redistribute and
+change. You can do so by permitting redistribution under these terms (or,
+alternatively, under the terms of the ordinary General Public License).
+
+
+
+To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
+where the full notice is found.
+
+
+
+one line to give the library's name and an idea of what it does.
+
+Copyright (C) year name of author
+
+
+
+This library is free software; you can redistribute it and/or
+
+modify it under the terms of the GNU Library General Public
+
+License as published by the Free Software Foundation; either
+
+version 2 of the License, or (at your option) any later version.
+
+
+
+This library is distributed in the hope that it will be useful,
+
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+
+Library General Public License for more details.
+
+
+
+You should have received a copy of the GNU Library General Public
+
+License along with this library; if not, write to the
+
+Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+
+Boston, MA 02110-1301, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
+alter the names:
+
+
+
+Yoyodyne, Inc., hereby disclaims all copyright interest in
+
+the library `Frob' (a library for tweaking knobs) written
+
+by James Random Hacker.
+
+
+
+signature of Ty Coon, 1 April 1990
+
+Ty Coon, President of Vice
+
+That's all there is to it!
+
+
+
+
+LGPL-2.1
+
+
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 2.1, February 1999
+
+Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public Licenses are intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users.
+
+This license, the Lesser General Public License, applies to some specially designated
+software packages--typically libraries--of the Free Software Foundation and other
+authors who decide to use it. You can use it too, but we suggest you first think
+carefully about whether this license or the ordinary General Public License is the
+better strategy to use in any particular case, based on the explanations below.
+
+When we speak of free software, we are referring to freedom of use, not price. Our
+General Public Licenses are designed to make sure that you have the freedom to
+distribute copies of free software (and charge for this service if you wish); that you
+receive source code or can get it if you want it; that you can change the software and
+use pieces of it in new free programs; and that you are informed that you can do these
+things.
+
+To protect your rights, we need to make restrictions that forbid distributors to deny
+you these rights or to ask you to surrender these rights. These restrictions translate
+to certain responsibilities for you if you distribute copies of the library or if you
+modify it.
+
+For example, if you distribute copies of the library, whether gratis or for a fee, you
+must give the recipients all the rights that we gave you. You must make sure that
+they, too, receive or can get the source code. If you link other code with the
+library, you must provide complete object files to the recipients, so that they can
+relink them with the library after making changes to the library and recompiling it.
+And you must show them these terms so they know their rights.
+
+We protect your rights with a two-step method: (1) we copyright the library, and (2)
+we offer you this license, which gives you legal permission to copy, distribute and/or
+modify the library.
+
+To protect each distributor, we want to make it very clear that there is no warranty
+for the free library. Also, if the library is modified by someone else and passed on,
+the recipients should know that what they have is not the original version, so that
+the original author`s reputation will not be affected by problems that might be
+introduced by others.
+
+Finally, software patents pose a constant threat to the existence of any free program.
+We wish to make sure that a company cannot effectively restrict the users of a free
+program by obtaining a restrictive license from a patent holder. Therefore, we insist
+that any patent license obtained for a version of the library must be consistent with
+the full freedom of use specified in this license.
+
+Most GNU software, including some libraries, is covered by the ordinary GNU General
+Public License. This license, the GNU Lesser General Public License, applies to
+certain designated libraries, and is quite different from the ordinary General Public
+License. We use this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+When a program is linked with a library, whether statically or using a shared library,
+the combination of the two is legally speaking a combined work, a derivative of the
+original library. The ordinary General Public License therefore permits such linking
+only if the entire combination fits its criteria of freedom. The Lesser General Public
+License permits more lax criteria for linking other code with the library.
+
+We call this license the "Lesser" General Public License because it does Less to
+protect the user`s freedom than the ordinary General Public License. It also provides
+other free software developers Less of an advantage over competing non-free programs.
+These disadvantages are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain special
+circumstances.
+
+For example, on rare occasions, there may be a special need to encourage the widest
+possible use of a certain library, so that it becomes a de-facto standard. To achieve
+this, non-free programs must be allowed to use the library. A more frequent case is
+that a free library does the same job as widely used non-free libraries. In this case,
+there is little to gain by limiting the free library to free software only, so we use
+the Lesser General Public License.
+
+In other cases, permission to use a particular library in non-free programs enables a
+greater number of people to use a large body of free software. For example, permission
+to use the GNU C Library in non-free programs enables many more people to use the
+whole GNU operating system, as well as its variant, the GNU/Linux operating system.
+
+Although the Lesser General Public License is Less protective of the users` freedom,
+it does ensure that the user of a program that is linked with the Library has the
+freedom and the wherewithal to run that program using a modified version of the
+Library.
+
+The precise terms and conditions for copying, distribution and modification follow.
+Pay close attention to the difference between a "work based on the library" and a
+"work that uses the library". The former contains code derived from the library,
+whereas the latter must be combined with the library in order to run.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License Agreement applies to any software library or other program which
+contains a notice placed by the copyright holder or other authorized party saying it
+may be distributed under the terms of this Lesser General Public License (also called
+"this License"). Each licensee is addressed as "you".
+
+A "library" means a collection of software functions and/or data prepared so as to be
+conveniently linked with application programs (which use some of those functions and
+data) to form executables.
+
+The "Library", below, refers to any such software library or work which has been
+distributed under these terms. A "work based on the Library" means either the Library
+or any derivative work under copyright law: that is to say, a work containing the
+Library or a portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is included without
+limitation in the term "modification".)
+
+"Source code" for a work means the preferred form of the work for making modifications
+to it. For a library, complete source code means all the source code for all modules
+it contains, plus any associated interface definition files, plus the scripts used to
+control compilation and installation of the library.
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running a program using the Library is
+not restricted, and output from such a program is covered only if its contents
+constitute a work based on the Library (independent of the use of the Library in a
+tool for writing it). Whether that is true depends on what the Library does and what
+the program that uses the Library does.
+
+1. You may copy and distribute verbatim copies of the Library`s complete source code
+as you receive it, in any medium, provided that you conspicuously and appropriately
+publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
+intact all the notices that refer to this License and to the absence of any warranty;
+and distribute a copy of this License along with the Library.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Library or any portion of it, thus
+forming a work based on the Library, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+a) The modified work must itself be a software library.
+b) You must cause the files modified to carry prominent notices stating that you
+changed the files and the date of any change.
+c) You must cause the whole of the work to be licensed at no charge to all third
+parties under the terms of this License.
+d) If a facility in the modified Library refers to a function or a table of data to be
+supplied by an application program that uses the facility, other than as an argument
+passed when the facility is invoked, then you must make a good faith effort to ensure
+that, in the event an application does not supply such function or table, the facility
+still operates, and performs whatever part of its purpose remains meaningful.
+(For example, a function in a library to compute square roots has a purpose that is
+entirely well-defined independent of the application. Therefore, Subsection 2d
+requires that any application-supplied function or table used by this function must be
+optional: if the application does not supply it, the square root function must still
+compute square roots.)
+
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Library, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Library,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library with the
+Library (or with a work based on the Library) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+3. You may opt to apply the terms of the ordinary GNU General Public License instead
+of this License to a given copy of the Library. To do this, you must alter all the
+notices that refer to this License, so that they refer to the ordinary GNU General
+Public License, version 2, instead of to this License. (If a newer version than
+version 2 of the ordinary GNU General Public License has appeared, then you can
+specify that version instead if you wish.) Do not make any other change in these
+notices.
+
+Once this change is made in a given copy, it is irreversible for that copy, so the
+ordinary GNU General Public License applies to all subsequent copies and derivative
+works made from that copy.
+
+This option is useful when you wish to copy part of the code of the Library into a
+program that is not a library.
+
+4. You may copy and distribute the Library (or a portion or derivative of it, under
+Section 2) in object code or executable form under the terms of Sections 1 and 2 above
+provided that you accompany it with the complete corresponding machine-readable source
+code, which must be distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange.
+
+If distribution of object code is made by offering access to copy from a designated
+place, then offering equivalent access to copy the source code from the same place
+satisfies the requirement to distribute the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+5. A program that contains no derivative of any portion of the Library, but is
+designed to work with the Library by being compiled or linked with it, is called a
+"work that uses the Library". Such a work, in isolation, is not a derivative work of
+the Library, and therefore falls outside the scope of this License.
+
+However, linking a "work that uses the Library" with the Library creates an executable
+that is a derivative of the Library (because it contains portions of the Library),
+rather than a "work that uses the library". The executable is therefore covered by
+this License. Section 6 states terms for distribution of such executables.
+
+When a "work that uses the Library" uses material from a header file that is part of
+the Library, the object code for the work may be a derivative work of the Library even
+though the source code is not. Whether this is true is especially significant if the
+work can be linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+If such an object file uses only numerical parameters, data structure layouts and
+accessors, and small macros and small inline functions (ten lines or less in length),
+then the use of the object file is unrestricted, regardless of whether it is legally a
+derivative work. (Executables containing this object code plus portions of the Library
+will still fall under Section 6.)
+
+Otherwise, if the work is a derivative of the Library, you may distribute the object
+code for the work under the terms of Section 6. Any executables containing that work
+also fall under Section 6, whether or not they are linked directly with the Library
+itself.
+
+6. As an exception to the Sections above, you may also combine or link a "work that
+uses the Library" with the Library to produce a work containing portions of the
+Library, and distribute that work under terms of your choice, provided that the terms
+permit modification of the work for the customer`s own use and reverse engineering for
+debugging such modifications.
+
+You must give prominent notice with each copy of the work that the Library is used in
+it and that the Library and its use are covered by this License. You must supply a
+copy of this License. If the work during execution displays copyright notices, you
+must include the copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one of these things:
+
+a) Accompany the work with the complete corresponding machine-readable source code for
+the Library including whatever changes were used in the work (which must be
+distributed under Sections 1 and 2 above); and, if the work is an executable linked
+with the Library, with the complete machine-readable "work that uses the Library", as
+object code and/or source code, so that the user can modify the Library and then
+relink to produce a modified executable containing the modified Library. (It is
+understood that the user who changes the contents of definitions files in the Library
+will not necessarily be able to recompile the application to use the modified
+definitions.)
+b) Use a suitable shared library mechanism for linking with the Library. A suitable
+mechanism is one that (1) uses at run time a copy of the library already present on
+the user`s computer system, rather than copying library functions into the executable,
+and (2) will operate properly with a modified version of the library, if the user
+installs one, as long as the modified version is interface-compatible with the version
+that the work was made with.
+c) Accompany the work with a written offer, valid for at least three years, to give
+the same user the materials specified in Subsection 6a, above, for a charge no more
+than the cost of performing this distribution.
+d) If distribution of the work is made by offering access to copy from a designated
+place, offer equivalent access to copy the above specified materials from the same
+place.
+e) Verify that the user has already received a copy of these materials or that you
+have already sent this user a copy.
+For an executable, the required form of the "work that uses the Library" must include
+any data and utility programs needed for reproducing the executable from it. However,
+as a special exception, the materials to be distributed need not include anything that
+is normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+It may happen that this requirement contradicts the license restrictions of other
+proprietary libraries that do not normally accompany the operating system. Such a
+contradiction means you cannot use both them and the Library together in an executable
+that you distribute.
+
+7. You may place library facilities that are a work based on the Library side-by-side
+in a single library together with other library facilities not covered by this
+License, and distribute such a combined library, provided that the separate
+distribution of the work based on the Library and of the other library facilities is
+otherwise permitted, and provided that you do these two things:
+
+a) Accompany the combined library with a copy of the same work based on the Library,
+uncombined with any other library facilities. This must be distributed under the terms
+of the Sections above.
+b) Give prominent notice with the combined library of the fact that part of it is a
+work based on the Library, and explaining where to find the accompanying uncombined
+form of the same work.
+8. You may not copy, modify, sublicense, link with, or distribute the Library except
+as expressly provided under this License. Any attempt otherwise to copy, modify,
+sublicense, link with, or distribute the Library is void, and will automatically
+terminate your rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses terminated so long
+as such parties remain in full compliance.
+
+9. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Library or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Library or works based on it.
+
+10. Each time you redistribute the Library (or any work based on the Library), the
+recipient automatically receives a license from the original licensor to copy,
+distribute, link with or modify the Library subject to these terms and conditions. You
+may not impose any further restrictions on the recipients` exercise of the rights
+granted herein. You are not responsible for enforcing compliance by third parties with
+this License.
+
+11. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Library at all. For example, if a patent license would not permit royalty-free
+redistribution of the Library by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply, and the section as a
+whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+12. If the distribution and/or use of the Library is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Library under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+13. The Free Software Foundation may publish revised and/or new versions of the Lesser
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Library does not
+specify a license version number, you may choose any version ever published by the
+Free Software Foundation.
+
+14. If you wish to incorporate parts of the Library into other free programs whose
+distribution conditions are incompatible with these, write to the author to ask for
+permission. For software which is copyrighted by the Free Software Foundation, write
+to the Free Software Foundation; we sometimes make exceptions for this. Our decision
+will be guided by the two goals of preserving the free status of all derivatives of
+our free software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
+WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Libraries
+
+If you develop a new library, and you want it to be of the greatest possible use to
+the public, we recommend making it free software that everyone can redistribute and
+change. You can do so by permitting redistribution under these terms (or,
+alternatively, under the terms of the ordinary General Public License).
+
+To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
+where the full notice is found.
+
+one line to give the library`s name and an idea of what it does.
+Copyright (C) year name of author
+
+This library is free software; you can redistribute it and/or
+modify it under the terms of the GNU Lesser General Public
+License as published by the Free Software Foundation; either
+version 2.1 of the License, or (at your option) any later version.
+
+This library is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public
+License along with this library; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
+alter the names:
+
+Yoyodyne, Inc., hereby disclaims all copyright interest in
+the library `Frob` (a library for tweaking knobs) written
+by James Random Hacker.
+
+signature of Ty Coon, 1 April 1990
+Ty Coon, President of Vice
+That`s all there is to it!
+
+
+
+
+LGPL-3.0
+
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the terms and
+conditions of version 3 of the GNU General Public License, supplemented by the
+additional permissions listed below.
+0. Additional Definitions.
+
+As used herein, ”this License” refers to version 3 of the GNU Lesser
+General Public License, and the ”GNU GPL” refers to version 3 of the GNU
+General Public License.
+
+”The Library” refers to a covered work governed by this License, other
+than an Application or a Combined Work as defined below.
+
+An ”Application” is any work that makes use of an interface provided by
+the Library, but which is not otherwise based on the Library. Defining a subclass of a
+class defined by the Library is deemed a mode of using an interface provided by the
+Library.
+
+A ”Combined Work” is a work produced by combining or linking an
+Application with the Library. The particular version of the Library with which the
+Combined Work was made is also called the ”Linked Version”.
+
+The ”Minimal Corresponding Source” for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code for portions of
+the Combined Work that, considered in isolation, are based on the Application, and not
+on the Linked Version.
+
+The ”Corresponding Application Code” for a Combined Work means the object
+code and/or source code for the Application, including any data and utility programs
+needed for reproducing the Combined Work from the Application, but excluding the
+System Libraries of the Combined Work.
+1. Exception to Section 3 of the GNU GPL.
+
+You may convey a covered work under sections 3 and 4 of this License without being
+bound by section 3 of the GNU GPL.
+2. Conveying Modified Versions.
+
+If you modify a copy of the Library, and, in your modifications, a facility refers to
+a function or data to be supplied by an Application that uses the facility (other than
+as an argument passed when the facility is invoked), then you may convey a copy of the
+modified version:
+
+ * a) under this License, provided that you make a good faith effort to ensure
+that, in the event an Application does not supply the function or data, the facility
+still operates, and performs whatever part of its purpose remains meaningful, or
+ * b) under the GNU GPL, with none of the additional permissions of this License
+applicable to that copy.
+
+3. Object Code Incorporating Material from Library Header Files.
+
+The object code form of an Application may incorporate material from a header file
+that is part of the Library. You may convey such object code under terms of your
+choice, provided that, if the incorporated material is not limited to numerical
+parameters, data structure layouts and accessors, or small macros, inline functions
+and templates (ten or fewer lines in length), you do both of the following:
+
+ * a) Give prominent notice with each copy of the object code that the Library is
+used in it and that the Library and its use are covered by this License.
+ * b) Accompany the object code with a copy of the GNU GPL and this license
+document.
+
+4. Combined Works.
+
+You may convey a Combined Work under terms of your choice that, taken together,
+effectively do not restrict modification of the portions of the Library contained in
+the Combined Work and reverse engineering for debugging such modifications, if you
+also do each of the following:
+
+ * a) Give prominent notice with each copy of the Combined Work that the Library is
+used in it and that the Library and its use are covered by this License.
+ * b) Accompany the Combined Work with a copy of the GNU GPL and this license
+document.
+ * c) For a Combined Work that displays copyright notices during execution, include
+the copyright notice for the Library among these notices, as well as a reference
+directing the user to the copies of the GNU GPL and this license document.
+ * d) Do one of the following:
+ o 0) Convey the Minimal Corresponding Source under the terms of this
+License, and the Corresponding Application Code in a form suitable for, and under
+terms that permit, the user to recombine or relink the Application with a modified
+version of the Linked Version to produce a modified Combined Work, in the manner
+specified by section 6 of the GNU GPL for conveying Corresponding Source.
+ o 1) Use a suitable shared library mechanism for linking with the Library. A
+suitable mechanism is one that (a) uses at run time a copy of the Library already
+present on the user's computer system, and (b) will operate properly with a modified
+version of the Library that is interface-compatible with the Linked Version.
+ * e) Provide Installation Information, but only if you would otherwise be required
+to provide such information under section 6 of the GNU GPL, and only to the extent
+that such information is necessary to install and execute a modified version of the
+Combined Work produced by recombining or relinking the Application with a modified
+version of the Linked Version. (If you use option 4d0, the Installation Information
+must accompany the Minimal Corresponding Source and Corresponding Application Code. If
+you use option 4d1, you must provide the Installation Information in the manner
+specified by section 6 of the GNU GPL for conveying Corresponding Source.)
+
+5. Combined Libraries.
+
+You may place library facilities that are a work based on the Library side by side in
+a single library together with other library facilities that are not Applications and
+are not covered by this License, and convey such a combined library under terms of
+your choice, if you do both of the following:
+
+ * a) Accompany the combined library with a copy of the same work based on the
+Library, uncombined with any other library facilities, conveyed under the terms of
+this License.
+ * b) Give prominent notice with the combined library that part of it is a work
+based on the Library, and explaining where to find the accompanying uncombined form of
+the same work.
+
+6. Revised Versions of the GNU Lesser General Public License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Lesser
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library as you received
+it specifies that a certain numbered version of the GNU Lesser General Public License
+”or any later version” applies to it, you have the option of following
+the terms and conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you received it does not
+specify a version number of the GNU Lesser General Public License, you may choose any
+version of the GNU Lesser General Public License ever published by the Free Software
+Foundation.
+
+If the Library as you received it specifies that a proxy can decide whether future
+versions of the GNU Lesser General Public License shall apply, that proxy's public
+statement of acceptance of any version is permanent authorization for you to choose
+that version for the Library.
+
+
+
+Libpng
+
+
+This copy of the libpng notices is provided for your convenience. In case of
+any discrepancy between this copy and the notices in the file png.h that is
+included in the libpng distribution, the latter shall prevail.
+
+COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
+
+If you modify libpng you may insert additional notices immediately following
+this sentence.
+
+This code is released under the libpng license.
+
+libpng versions 1.2.6, August 15, 2004, through 1.4.5, December 9, 2010, are
+Copyright (c) 2004, 2006-2010 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-1.2.5
+with the following individual added to the list of Contributing Authors
+
+ Cosmin Truta
+
+libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are
+Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-1.0.6
+with the following individuals added to the list of Contributing Authors
+
+ Simon-Pierre Cadieux
+ Eric S. Raymond
+ Gilles Vollant
+
+and with the following additions to the disclaimer:
+
+ There is no warranty against interference with your enjoyment of the
+ library or against infringement. There is no warranty that our
+ efforts or the library will fulfill any of your particular purposes
+ or needs. This library is provided with all faults, and the entire
+ risk of satisfactory quality, performance, accuracy, and effort is with
+ the user.
+
+libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
+Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-0.96,
+with the following individuals added to the list of Contributing Authors:
+
+ Tom Lane
+ Glenn Randers-Pehrson
+ Willem van Schaik
+
+libpng versions 0.89, June 1996, through 0.96, May 1997, are
+Copyright (c) 1996, 1997 Andreas Dilger
+Distributed according to the same disclaimer and license as libpng-0.88,
+with the following individuals added to the list of Contributing Authors:
+
+ John Bowler
+ Kevin Bracey
+ Sam Bushell
+ Magnus Holmgren
+ Greg Roelofs
+ Tom Tanner
+
+libpng versions 0.5, May 1995, through 0.88, January 1996, are
+Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.
+
+For the purposes of this copyright and license, "Contributing Authors"
+is defined as the following set of individuals:
+
+ Andreas Dilger
+ Dave Martindale
+ Guy Eric Schalnat
+ Paul Schmidt
+ Tim Wegner
+
+The PNG Reference Library is supplied "AS IS". The Contributing Authors
+and Group 42, Inc. disclaim all warranties, expressed or implied,
+including, without limitation, the warranties of merchantability and of
+fitness for any purpose. The Contributing Authors and Group 42, Inc.
+assume no liability for direct, indirect, incidental, special, exemplary,
+or consequential damages, which may result from the use of the PNG
+Reference Library, even if advised of the possibility of such damage.
+
+Permission is hereby granted to use, copy, modify, and distribute this
+source code, or portions hereof, for any purpose, without fee, subject
+to the following restrictions:
+
+1. The origin of this source code must not be misrepresented.
+
+2. Altered versions must be plainly marked as such and must not
+ be misrepresented as being the original source.
+
+3. This Copyright notice may not be removed or altered from any
+ source or altered source distribution.
+
+The Contributing Authors and Group 42, Inc. specifically permit, without
+fee, and encourage the use of this source code as a component to
+supporting the PNG file format in commercial products. If you use this
+source code in a product, acknowledgment is not required but would be
+appreciated.
+
+
+A "png_get_copyright" function is available, for convenient use in "about"
+boxes and the like:
+
+ printf("%s",png_get_copyright(NULL));
+
+Also, the PNG logo (in PNG format, of course) is supplied in the
+files "pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).
+
+Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a
+certification mark of the Open Source Initiative.
+
+Glenn Randers-Pehrson
+glennrp at users.sourceforge.net
+December 9, 2010
+
+
+
+
+MIT
+
+
+MIT License
+
+Copyright (c) <year> <copyright holders>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+
+
+MPL-1.0
+
+
+MOZILLA PUBLIC LICENSE
+Version 1.0
+
+1. Definitions.
+
+1.1. ``Contributor`` means each entity that creates or contributes to the creation of
+Modifications.
+1.2. ``Contributor Version`` means the combination of the Original Code, prior
+Modifications used by a Contributor, and the Modifications made by that particular
+Contributor.
+
+1.3. ``Covered Code`` means the Original Code or Modifications or the combination of
+the Original Code and Modifications, in each case including portions thereof.
+
+1.4. ``Electronic Distribution Mechanism`` means a mechanism generally accepted in the
+software development community for the electronic transfer of data.
+
+1.5. ``Executable`` means Covered Code in any form other than Source Code.
+
+1.6. ``Initial Developer`` means the individual or entity identified as the Initial
+Developer in the Source Code notice required by Exhibit A.
+
+1.7. ``Larger Work`` means a work which combines Covered Code or portions thereof with
+code not governed by the terms of this License.
+
+1.8. ``License`` means this document.
+
+1.9. ``Modifications`` means any addition to or deletion from the substance or
+structure of either the Original Code or any previous Modifications. When Covered Code
+is released as a series of files, a Modification is:
+
+A. Any addition to or deletion from the contents of a file containing Original Code or
+previous Modifications.
+
+B. Any new file that contains any part of the Original Code or previous Modifications.
+
+1.10. ``Original Code`` means Source Code of computer software code which is described
+in the Source Code notice required by Exhibit A as Original Code, and which, at the
+time of its release under this License is not already Covered Code governed by this
+License.
+
+1.11. ``Source Code`` means the preferred form of the Covered Code for making
+modifications to it, including all modules it contains, plus any associated interface
+definition files, scripts used to control compilation and installation of an
+Executable, or a list of source code differential comparisons against either the
+Original Code or another well known, available Covered Code of the Contributor`s
+choice. The Source Code can be in a compressed or archival form, provided the
+appropriate decompression or de-archiving software is widely available for no charge.
+
+1.12. ``You`` means an individual or a legal entity exercising rights under, and
+complying with all of the terms of, this License or a future version of this License
+issued under Section 6.1. For legal entities, ``You`` includes any entity which
+controls, is controlled by, or is under common control with You. For purposes of this
+definition, ``control`` means (a) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or otherwise, or (b)
+ownership of fifty percent (50%) or more of the outstanding shares or beneficial
+ownership of such entity.
+
+2. Source Code License.
+2.1. The Initial Developer Grant.
+The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive
+license, subject to third party intellectual property claims:
+(a) to use, reproduce, modify, display, perform, sublicense and distribute the
+Original Code (or portions thereof) with or without Modifications, or as part of a
+Larger Work; and
+
+(b) under patents now or hereafter owned or controlled by Initial Developer, to make,
+have made, use and sell (``Utilize``) the Original Code (or portions thereof), but
+solely to the extent that any such patent is reasonably necessary to enable You to
+Utilize the Original Code (or portions thereof) and not to any greater extent that may
+be necessary to Utilize further Modifications or combinations.
+
+2.2. Contributor Grant.
+Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license,
+subject to third party intellectual property claims:
+
+(a) to use, reproduce, modify, display, perform, sublicense and distribute the
+Modifications created by such Contributor (or portions thereof) either on an
+unmodified basis, with other Modifications, as Covered Code or as part of a Larger
+Work; and
+
+(b) under patents now or hereafter owned or controlled by Contributor, to Utilize the
+Contributor Version (or portions thereof), but solely to the extent that any such
+patent is reasonably necessary to enable You to Utilize the Contributor Version (or
+portions thereof), and not to any greater extent that may be necessary to Utilize
+further Modifications or combinations.
+
+3. Distribution Obligations.
+3.1. Application of License.
+The Modifications which You create or to which You contribute are governed by the
+terms of this License, including without limitation Section 2.2. The Source Code
+version of Covered Code may be distributed only under the terms of this License or a
+future version of this License released under Section 6.1, and You must include a copy
+of this License with every copy of the Source Code You distribute. You may not offer
+or impose any terms on any Source Code version that alters or restricts the applicable
+version of this License or the recipients` rights hereunder. However, You may include
+an additional document offering the additional rights described in Section 3.5.
+3.2. Availability of Source Code.
+Any Modification which You create or to which You contribute must be made available in
+Source Code form under the terms of this License either on the same media as an
+Executable version or via an accepted Electronic Distribution Mechanism to anyone to
+whom you made an Executable version available; and if made available via Electronic
+Distribution Mechanism, must remain available for at least twelve (12) months after
+the date it initially became available, or at least six (6) months after a subsequent
+version of that particular Modification has been made available to such recipients.
+You are responsible for ensuring that the Source Code version remains available even
+if the Electronic Distribution Mechanism is maintained by a third party.
+
+3.3. Description of Modifications.
+You must cause all Covered Code to which you contribute to contain a file documenting
+the changes You made to create that Covered Code and the date of any change. You must
+include a prominent statement that the Modification is derived, directly or
+indirectly, from Original Code provided by the Initial Developer and including the
+name of the Initial Developer in (a) the Source Code, and (b) in any notice in an
+Executable version or related documentation in which You describe the origin or
+ownership of the Covered Code.
+
+3.4. Intellectual Property Matters
+
+(a) Third Party Claims.
+If You have knowledge that a party claims an intellectual property right in particular
+functionality or code (or its utilization under this License), you must include a text
+file with the source code distribution titled ``LEGAL`` which describes the claim and
+the party making the claim in sufficient detail that a recipient will know whom to
+contact. If you obtain such knowledge after You make Your Modification available as
+described in Section 3.2, You shall promptly modify the LEGAL file in all copies You
+make available thereafter and shall take other steps (such as notifying appropriate
+mailing lists or newsgroups) reasonably calculated to inform those who received the
+Covered Code that new knowledge has been obtained.
+
+(b) Contributor APIs.
+If Your Modification is an application programming interface and You own or control
+patents which are reasonably necessary to implement that API, you must also include
+this information in the LEGAL file.
+
+3.5. Required Notices.
+You must duplicate the notice in Exhibit A in each file of the Source Code, and this
+License in any documentation for the Source Code, where You describe recipients`
+rights relating to Covered Code. If You created one or more Modification(s), You may
+add your name as a Contributor to the notice described in Exhibit A. If it is not
+possible to put such notice in a particular Source Code file due to its structure,
+then you must include such notice in a location (such as a relevant directory file)
+where a user would be likely to look for such a notice. You may choose to offer, and
+to charge a fee for, warranty, support, indemnity or liability obligations to one or
+more recipients of Covered Code. However, You may do so only on Your own behalf, and
+not on behalf of the Initial Developer or any Contributor. You must make it absolutely
+clear than any such warranty, support, indemnity or liability obligation is offered by
+You alone, and You hereby agree to indemnify the Initial Developer and every
+Contributor for any liability incurred by the Initial Developer or such Contributor as
+a result of warranty, support, indemnity or liability terms You offer.
+
+3.6. Distribution of Executable Versions.
+You may distribute Covered Code in Executable form only if the requirements of Section
+3.1-3.5 have been met for that Covered Code, and if You include a notice stating that
+the Source Code version of the Covered Code is available under the terms of this
+License, including a description of how and where You have fulfilled the obligations
+of Section 3.2. The notice must be conspicuously included in any notice in an
+Executable version, related documentation or collateral in which You describe
+recipients` rights relating to the Covered Code. You may distribute the Executable
+version of Covered Code under a license of Your choice, which may contain terms
+different from this License, provided that You are in compliance with the terms of
+this License and that the license for the Executable version does not attempt to limit
+or alter the recipient`s rights in the Source Code version from the rights set forth
+in this License. If You distribute the Executable version under a different license
+You must make it absolutely clear that any terms which differ from this License are
+offered by You alone, not by the Initial Developer or any Contributor. You hereby
+agree to indemnify the Initial Developer and every Contributor for any liability
+incurred by the Initial Developer or such Contributor as a result of any such terms
+You offer.
+
+3.7. Larger Works.
+You may create a Larger Work by combining Covered Code with other code not governed by
+the terms of this License and distribute the Larger Work as a single product. In such
+a case, You must make sure the requirements of this License are fulfilled for the
+Covered Code.
+
+4. Inability to Comply Due to Statute or Regulation.
+If it is impossible for You to comply with any of the terms of this License with
+respect to some or all of the Covered Code due to statute or regulation then You must:
+(a) comply with the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must be included
+in the LEGAL file described in Section 3.4 and must be included with all distributions
+of the Source Code. Except to the extent prohibited by statute or regulation, such
+description must be sufficiently detailed for a recipient of ordinary skill to be able
+to understand it.
+
+5. Application of this License.
+This License applies to code to which the Initial Developer has attached the notice in
+Exhibit A, and to related Covered Code.
+6. Versions of the License.
+6.1. New Versions.
+Netscape Communications Corporation (``Netscape``) may publish revised and/or new
+versions of the License from time to time. Each version will be given a distinguishing
+version number.
+6.2. Effect of New Versions.
+Once Covered Code has been published under a particular version of the License, You
+may always continue to use it under the terms of that version. You may also choose to
+use such Covered Code under the terms of any subsequent version of the License
+published by Netscape. No one other than Netscape has the right to modify the terms
+applicable to Covered Code created under this License.
+
+6.3. Derivative Works.
+If you create or use a modified version of this License (which you may only do in
+order to apply it to code which is not already Covered Code governed by this License),
+you must (a) rename Your license so that the phrases ``Mozilla``, ``MOZILLAPL``,
+``MOZPL``, ``Netscape``, ``NPL`` or any confusingly similar phrase do not appear
+anywhere in your license and (b) otherwise make it clear that your version of the
+license contains terms which differ from the Mozilla Public License and Netscape
+Public License. (Filling in the name of the Initial Developer, Original Code or
+Contributor in the notice described in Exhibit A shall not of themselves be deemed to
+be modifications of this License.)
+
+7. DISCLAIMER OF WARRANTY.
+COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS`` BASIS, WITHOUT WARRANTY OF
+ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT
+THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
+NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
+IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE
+INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
+SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL
+PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER
+THIS DISCLAIMER.
+8. TERMINATION.
+This License and the rights granted hereunder will terminate automatically if You fail
+to comply with terms herein and fail to cure such breach within 30 days of becoming
+aware of the breach. All sublicenses to the Covered Code which are properly granted
+shall survive any termination of this License. Provisions which, by their nature, must
+remain in effect beyond the termination of this License shall survive.
+9. LIMITATION OF LIABILITY.
+UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
+CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY
+DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU
+OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF
+ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK
+STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
+LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH
+DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
+PERSONAL INJURY RESULTING FROM SUCH PARTY`S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
+PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION
+OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY
+TO YOU.
+10. U.S. GOVERNMENT END USERS.
+The Covered Code is a ``commercial item,`` as that term is defined in 48 C.F.R. 2.101
+(Oct. 1995), consisting of ``commercial computer software`` and ``commercial computer
+software documentation,`` as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
+Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
+1995), all U.S. Government End Users acquire Covered Code with only those rights set
+forth herein.
+11. MISCELLANEOUS.
+This License represents the complete agreement concerning subject matter hereof. If
+any provision of this License is held to be unenforceable, such provision shall be
+reformed only to the extent necessary to make it enforceable. This License shall be
+governed by California law provisions (except to the extent applicable law, if any,
+provides otherwise), excluding its conflict-of-law provisions. With respect to
+disputes in which at least one party is a citizen of, or an entity chartered or
+registered to do business in, the United States of America: (a) unless otherwise
+agreed in writing, all disputes relating to this License (excepting any dispute
+relating to intellectual property rights) shall be subject to final and binding
+arbitration, with the losing party paying all costs of arbitration; (b) any
+arbitration relating to this Agreement shall be held in Santa Clara County,
+California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to
+this Agreement shall be subject to the jurisdiction of the Federal Courts of the
+Northern District of California, with venue lying in Santa Clara County, California,
+with the losing party responsible for costs, including without limitation, court costs
+and reasonable attorneys fees and expenses. The application of the United Nations
+Convention on Contracts for the International Sale of Goods is expressly excluded. Any
+law or regulation which provides that the language of a contract shall be construed
+against the drafter shall not apply to this License.
+12. RESPONSIBILITY FOR CLAIMS.
+Except in cases where another Contributor has failed to comply with Section 3.4, You
+are responsible for damages arising, directly or indirectly, out of Your utilization
+of rights under this License, based on the number of copies of Covered Code you made
+available, the revenues you received from utilizing such rights, and other relevant
+factors. You agree to work with affected parties to distribute responsibility on an
+equitable basis.
+EXHIBIT A.
+``The contents of this file are subject to the Mozilla Public License Version 1.0 (the
+"License"); you may not use this file except in compliance with the License. You may
+obtain a copy of the License at http://www.mozilla.org/MPL/
+Software distributed under the License is distributed on an "AS IS" basis, WITHOUT
+WARRANTY OF ANY KIND, either express or implied. See the License for the specific
+language governing rights and limitations under the License.
+
+The Original Code is ______________________________________.
+
+The Initial Developer of the Original Code is ________________________. Portions
+created by ______________________ are Copyright (C) ______ _______________________.
+All Rights Reserved.
+
+Contributor(s): ______________________________________.``
+
+
+
+
+MPL-2.0
+
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+ means each individual or legal entity that creates, contributes to
+ the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+ means the combination of the Contributions of others (if any) used
+ by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+ means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+ means Source Code Form to which the initial Contributor has attached
+ the notice in Exhibit A, the Executable Form of such Source Code
+ Form, and Modifications of such Source Code Form, in each case
+ including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+ means
+
+ (a) that the initial Contributor has attached the notice described
+ in Exhibit B to the Covered Software; or
+
+ (b) that the Covered Software was made available under the terms of
+ version 1.1 or earlier of the License, but not also under the
+ terms of a Secondary License.
+
+1.6. "Executable Form"
+ means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+ means a work that combines Covered Software with other material, in
+ a separate file or files, that is not Covered Software.
+
+1.8. "License"
+ means this document.
+
+1.9. "Licensable"
+ means having the right to grant, to the maximum extent possible,
+ whether at the time of the initial grant or subsequently, any and
+ all of the rights conveyed by this License.
+
+1.10. "Modifications"
+ means any of the following:
+
+ (a) any file in Source Code Form that results from an addition to,
+ deletion from, or modification of the contents of Covered
+ Software; or
+
+ (b) any new file in Source Code Form that contains any Covered
+ Software.
+
+1.11. "Patent Claims" of a Contributor
+ means any patent claim(s), including without limitation, method,
+ process, and apparatus claims, in any patent Licensable by such
+ Contributor that would be infringed, but for the grant of the
+ License, by the making, using, selling, offering for sale, having
+ made, import, or transfer of either its Contributions or its
+ Contributor Version.
+
+1.12. "Secondary License"
+ means either the GNU General Public License, Version 2.0, the GNU
+ Lesser General Public License, Version 2.1, the GNU Affero General
+ Public License, Version 3.0, or any later versions of those
+ licenses.
+
+1.13. "Source Code Form"
+ means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+ means an individual or a legal entity exercising rights under this
+ License. For legal entities, "You" includes any entity that
+ controls, is controlled by, or is under common control with You. For
+ purposes of this definition, "control" means (a) the power, direct
+ or indirect, to cause the direction or management of such entity,
+ whether by contract or otherwise, or (b) ownership of more than
+ fifty percent (50%) of the outstanding shares or beneficial
+ ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+ Licensable by such Contributor to use, reproduce, make available,
+ modify, display, perform, distribute, and otherwise exploit its
+ Contributions, either on an unmodified basis, with Modifications, or
+ as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+ for sale, have made, import, and otherwise transfer either its
+ Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+ or
+
+(b) for infringements caused by: (i) Your and any other third party's
+ modifications of Covered Software, or (ii) the combination of its
+ Contributions with other software (except as part of its Contributor
+ Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+ its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+ Form, as described in Section 3.1, and You must inform recipients of
+ the Executable Form how they can obtain a copy of such Source Code
+ Form by reasonable means in a timely manner, at a charge no more
+ than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+ License, or sublicense it under different terms, provided that the
+ license for the Executable Form does not attempt to limit or alter
+ the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+* *
+* 6. Disclaimer of Warranty *
+* ------------------------- *
+* *
+* Covered Software is provided under this License on an "as is" *
+* basis, without warranty of any kind, either expressed, implied, or *
+* statutory, including, without limitation, warranties that the *
+* Covered Software is free of defects, merchantable, fit for a *
+* particular purpose or non-infringing. The entire risk as to the *
+* quality and performance of the Covered Software is with You. *
+* Should any Covered Software prove defective in any respect, You *
+* (not any Contributor) assume the cost of any necessary servicing, *
+* repair, or correction. This disclaimer of warranty constitutes an *
+* essential part of this License. No use of any Covered Software is *
+* authorized under this License except under this disclaimer. *
+* *
+************************************************************************
+
+************************************************************************
+* *
+* 7. Limitation of Liability *
+* -------------------------- *
+* *
+* Under no circumstances and under no legal theory, whether tort *
+* (including negligence), contract, or otherwise, shall any *
+* Contributor, or anyone who distributes Covered Software as *
+* permitted above, be liable to You for any direct, indirect, *
+* special, incidental, or consequential damages of any character *
+* including, without limitation, damages for lost profits, loss of *
+* goodwill, work stoppage, computer failure or malfunction, or any *
+* and all other commercial damages or losses, even if such party *
+* shall have been informed of the possibility of such damages. This *
+* limitation of liability shall not apply to liability for death or *
+* personal injury resulting from such party's negligence to the *
+* extent applicable law prohibits such limitation. Some *
+* jurisdictions do not allow the exclusion or limitation of *
+* incidental or consequential damages, so this exclusion and *
+* limitation may not apply to You. *
+* *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+ This Source Code Form is subject to the terms of the Mozilla Public
+ License, v. 2.0. If a copy of the MPL was not distributed with this
+ file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+ This Source Code Form is "Incompatible With Secondary Licenses", as
+ defined by the Mozilla Public License, v. 2.0.
+
+
+
+OFL-1.1
+
+
+SIL OPEN FONT LICENSE
+
+Version 1.1 - 26 February 2007
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
+
+
+
+
+OpenSSL
+
+
+OpenSSL License
+
+ ====================================================================
+ Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ 1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the
+ distribution.
+
+ 3. All advertising materials mentioning features or use of this
+ software must display the following acknowledgment:
+ "This product includes software developed by the OpenSSL Project
+ for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
+
+ 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
+ endorse or promote products derived from this software without
+ prior written permission. For written permission, please contact
+ openssl-core@openssl.org.
+
+ 5. Products derived from this software may not be called "OpenSSL"
+ nor may "OpenSSL" appear in their names without prior written
+ permission of the OpenSSL Project.
+
+ 6. Redistributions of any form whatsoever must retain the following
+ acknowledgment:
+ "This product includes software developed by the OpenSSL Project
+ for use in the OpenSSL Toolkit (http://www.openssl.org/)"
+
+ THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS`` AND ANY
+ EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
+ ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+ NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+ OF THE POSSIBILITY OF SUCH DAMAGE.
+ ====================================================================
+
+ This product includes cryptographic software written by Eric Young
+ (eay@cryptsoft.com). This product includes software written by Tim
+ Hudson (tjh@cryptsoft.com).
+
+
+ Original SSLeay License
+ -----------------------
+
+Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
+All rights reserved.
+
+ This package is an SSL implementation written
+ by Eric Young (eay@cryptsoft.com).
+ The implementation was written so as to conform with Netscapes SSL.
+
+ This library is free for commercial and non-commercial use as long as
+ the following conditions are aheared to. The following conditions
+ apply to all code found in this distribution, be it the RC4, RSA,
+ lhash, DES, etc., code; not just the SSL code. The SSL documentation
+ included with this distribution is covered by the same copyright terms
+ except that the holder is Tim Hudson (tjh@cryptsoft.com).
+
+ Copyright remains Eric Young`s, and as such any Copyright notices in
+ the code are not to be removed.
+ If this package is used in a product, Eric Young should be given attribution
+ as the author of the parts of the library used.
+ This can be in the form of a textual message at program startup or
+ in documentation (online or textual) provided with the package.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the copyright
+ notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ 3. All advertising materials mentioning features or use of this software
+ must display the following acknowledgement:
+ "This product includes cryptographic software written by
+ Eric Young (eay@cryptsoft.com)"
+ The word `cryptographic` can be left out if the rouines from the library
+ being used are not cryptographic related :-).
+ 4. If you include any Windows specific code (or a derivative thereof) from
+ the apps directory (application code) you must include an acknowledgement:
+ "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
+
+ THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS`` AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
+CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+ The licence and distribution terms for any publically available version or
+derivative of this code cannot be changed. i.e. this code cannot simply be copied and
+put under another distribution licence
+ [including the GNU Public Licence.]
+
+
+
+
+
+
+
+PD
+
+This is a placeholder for the Public Domain License
+
+
+
+Python-2.0
+
+
+PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
+--------------------------------------------
+
+1. This LICENSE AGREEMENT is between the Python Software Foundation
+("PSF"), and the Individual or Organization ("Licensee") accessing and
+otherwise using this software ("Python") in source or binary form and
+its associated documentation.
+
+2. Subject to the terms and conditions of this License Agreement, PSF
+hereby grants Licensee a nonexclusive, royalty-free, world-wide
+license to reproduce, analyze, test, perform and/or display publicly,
+prepare derivative works, distribute, and otherwise use Python
+alone or in any derivative version, provided, however, that PSF`s
+License Agreement and PSF`s notice of copyright, i.e., "Copyright (c)
+2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights
+Reserved" are retained in Python alone or in any derivative version
+prepared by Licensee.
+
+3. In the event Licensee prepares a derivative work that is based on
+or incorporates Python or any part thereof, and wants to make
+the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to Python.
+
+4. PSF is making Python available to Licensee on an "AS IS"
+basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
+FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
+A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
+OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+7. Nothing in this License Agreement shall be deemed to create any
+relationship of agency, partnership, or joint venture between PSF and
+Licensee. This License Agreement does not grant permission to use PSF
+trademarks or trade name in a trademark sense to endorse or promote
+products or services of Licensee, or any third party.
+
+8. By copying, installing or otherwise using Python, Licensee
+agrees to be bound by the terms and conditions of this License
+Agreement.
+
+BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
+-------------------------------------------
+
+BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
+
+1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
+office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
+Individual or Organization ("Licensee") accessing and otherwise using
+this software in source or binary form and its associated
+documentation ("the Software").
+
+2. Subject to the terms and conditions of this BeOpen Python License
+Agreement, BeOpen hereby grants Licensee a non-exclusive,
+royalty-free, world-wide license to reproduce, analyze, test, perform
+and/or display publicly, prepare derivative works, distribute, and
+otherwise use the Software alone or in any derivative version,
+provided, however, that the BeOpen Python License is retained in the
+Software, alone or in any derivative version prepared by Licensee.
+
+3. BeOpen is making the Software available to Licensee on an "AS IS"
+basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
+SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
+AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
+DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+5. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+6. This License Agreement shall be governed by and interpreted in all
+respects by the law of the State of California, excluding conflict of
+law provisions. Nothing in this License Agreement shall be deemed to
+create any relationship of agency, partnership, or joint venture
+between BeOpen and Licensee. This License Agreement does not grant
+permission to use BeOpen trademarks or trade names in a trademark
+sense to endorse or promote products or services of Licensee, or any
+third party. As an exception, the "BeOpen Python" logos available at
+http://www.pythonlabs.com/logos.html may be used according to the
+permissions granted on that web page.
+
+7. By copying, installing or otherwise using the software, Licensee
+agrees to be bound by the terms and conditions of this License
+Agreement.
+
+CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
+---------------------------------------
+
+1. This LICENSE AGREEMENT is between the Corporation for National
+Research Initiatives, having an office at 1895 Preston White Drive,
+Reston, VA 20191 ("CNRI"), and the Individual or Organization
+("Licensee") accessing and otherwise using Python 1.6.1 software in
+source or binary form and its associated documentation.
+
+2. Subject to the terms and conditions of this License Agreement, CNRI
+hereby grants Licensee a nonexclusive, royalty-free, world-wide
+license to reproduce, analyze, test, perform and/or display publicly,
+prepare derivative works, distribute, and otherwise use Python 1.6.1
+alone or in any derivative version, provided, however, that CNRI`s
+License Agreement and CNRI`s notice of copyright, i.e., "Copyright (c)
+1995-2001 Corporation for National Research Initiatives; All Rights
+Reserved" are retained in Python 1.6.1 alone or in any derivative
+version prepared by Licensee. Alternately, in lieu of CNRI`s License
+Agreement, Licensee may substitute the following text (omitting the
+quotes): "Python 1.6.1 is made available subject to the terms and
+conditions in CNRI`s License Agreement. This Agreement together with
+Python 1.6.1 may be located on the Internet using the following
+unique, persistent identifier (known as a handle): 1895.22/1013. This
+Agreement may also be obtained from a proxy server on the Internet
+using the following URL: http://hdl.handle.net/1895.22/1013".
+
+3. In the event Licensee prepares a derivative work that is based on
+or incorporates Python 1.6.1 or any part thereof, and wants to make
+the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to Python 1.6.1.
+
+4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
+basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
+1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
+A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
+OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+7. This License Agreement shall be governed by the federal
+intellectual property law of the United States, including without
+limitation the federal copyright law, and, to the extent such
+U.S. federal law does not apply, by the law of the Commonwealth of
+Virginia, excluding Virginia`s conflict of law provisions.
+Notwithstanding the foregoing, with regard to derivative works based
+on Python 1.6.1 that incorporate non-separable material that was
+previously distributed under the GNU General Public License (GPL), the
+law of the Commonwealth of Virginia shall govern this License
+Agreement only as to issues arising under or with respect to
+Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
+License Agreement shall be deemed to create any relationship of
+agency, partnership, or joint venture between CNRI and Licensee. This
+License Agreement does not grant permission to use CNRI trademarks or
+trade name in a trademark sense to endorse or promote products or
+services of Licensee, or any third party.
+
+8. By clicking on the "ACCEPT" button where indicated, or by copying,
+installing or otherwise using Python 1.6.1, Licensee agrees to be
+bound by the terms and conditions of this License Agreement.
+
+ACCEPT
+
+CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
+--------------------------------------------------
+
+Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
+The Netherlands. All rights reserved.
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted,
+provided that the above copyright notice appear in all copies and that
+both that copyright notice and this permission notice appear in
+supporting documentation, and that the name of Stichting Mathematisch
+Centrum or CWI not be used in advertising or publicity pertaining to
+distribution of the software without specific, written prior
+permission.
+
+STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
+THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
+FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
+OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+
+
+
+SAX-PD
+
+
+Copyright Status for SAX
+
+SAX is free!
+
+In fact, it`s not possible to own a license to SAX, since it`s been placed in the
+public domain.
+
+No Warranty
+
+Because SAX is released to the public domain, there is no warranty for the design or
+for the software implementation, to the extent permitted by applicable law. Except
+when otherwise stated in writing the copyright holders and/or other parties provide
+SAX "as is" without warranty of any kind, either expressed or implied, including, but
+not limited to, the implied warranties of merchantability and fitness for a particular
+purpose. The entire risk as to the quality and performance of SAX is with you. Should
+SAX prove defective, you assume the cost of all necessary servicing, repair or
+correction.
+
+In no event unless required by applicable law or agreed to in writing will any
+copyright holder, or any other party who may modify and/or redistribute SAX, be liable
+to you for damages, including any general, special, incidental or consequential
+damages arising out of the use or inability to use SAX (including but not limited to
+loss of data or data being rendered inaccurate or losses sustained by you or third
+parties or a failure of the SAX to operate with any other programs), even if such
+holder or other party has been advised of the possibility of such damages.
+
+Copyright Disclaimers
+
+This page includes statements to that effect by David Megginson, who would have been
+able to claim copyright for the original work.
+
+SAX 1.0
+
+Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of
+the XML-DEV mailing list, is hereby released into the public domain.
+
+No one owns SAX: you may use it freely in both commercial and non-commercial
+applications, bundle it with your software distribution, include it on a CD-ROM, list
+the source code in a book, mirror the documentation at your own web site, or use it in
+any other way you see fit.
+
+David Megginson, Megginson Technologies Ltd.
+1998-05-11
+
+SAX 2.0
+
+I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release
+all of the SAX 2.0 source code, compiled code, and documentation contained in this
+distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of
+fitness for any purpose.
+
+David Megginson, Megginson Technologies Ltd.
+2000-05-05
+
+
+
+
+SMAIL_GPL
+
+This is the Debian GNU/Linux package debianutils.
+
+It is an original Debian package. Programs in it were maintained by
+Guy Maor <maor@debian.org>, and are now maintained by Clint Adams
+<schizo@debian.org>.
+
+All its programs except readlink, savelog, and which may be
+redistributed under the terms of the GNU GPL, Version 2 or later,
+found on Debian systems in the file /usr/share/common-licenses/GPL.
+
+which is in the public domain.
+
+readlink is Copyright (c) 1997 Kenneth Stailey, and may also be
+distributed under the terms of the BSD copyright.
+
+savelog may be redistributed under the following terms: (The rest of
+this file consists of savelog's distribution terms.)
+
+#ident "@(#)smail:RELEASE-3_2:COPYING,v 1.2 1996/06/14 18:59:10 woods Exp"
+
+ SMAIL GENERAL PUBLIC LICENSE
+ (Clarified 11 Feb 1988)
+
+ Copyright (C) 1988 Landon Curt Noll & Ronald S. Karr
+ Copyright (C) 1992 Ronald S. Karr
+ Copyleft (GNU) 1988 Landon Curt Noll & Ronald S. Karr
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license, but changing it is not allowed. You can also
+ use this wording to make the terms for other programs.
+
+ The license agreements of most software companies keep you at the
+mercy of those companies. By contrast, our general public license is
+intended to give everyone the right to share SMAIL. To make sure that
+you get the rights we want you to have, we need to make restrictions
+that forbid anyone to deny you these rights or to ask you to surrender
+the rights. Hence this license agreement.
+
+ Specifically, we want to make sure that you have the right to give
+away copies of SMAIL, that you receive source code or else can get it
+if you want it, that you can change SMAIL or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To make sure that everyone has such rights, we have to forbid you to
+deprive anyone else of these rights. For example, if you distribute
+copies of SMAIL, you must give the recipients all the rights that you
+have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+ Also, for our own protection, we must make certain that everyone
+finds out that there is no warranty for SMAIL. If SMAIL is modified by
+someone else and passed on, we want its recipients to know that what
+they have is not what we distributed, so that any problems introduced
+by others will not reflect on our reputation.
+
+ Therefore we (Landon Curt Noll and Ronald S. Karr) make the following
+terms which say what you must do to be allowed to distribute or change
+SMAIL.
+
+
+ COPYING POLICIES
+
+ 1. You may copy and distribute verbatim copies of SMAIL source code
+as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy a valid copyright notice "Copyright
+(C) 1988 Landon Curt Noll & Ronald S. Karr" (or with whatever year is
+appropriate); keep intact the notices on all files that refer to this
+License Agreement and to the absence of any warranty; and give any
+other recipients of the SMAIL program a copy of this License
+Agreement along with the program. You may charge a distribution fee
+for the physical act of transferring a copy.
+
+ 2. You may modify your copy or copies of SMAIL or any portion of it,
+and copy and distribute such modifications under the terms of
+Paragraph 1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating
+ that you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish,
+ that in whole or in part contains or is a derivative of SMAIL or
+ any part thereof, to be licensed at no charge to all third
+ parties on terms identical to those contained in this License
+ Agreement (except that you may choose to grant more extensive
+ warranty protection to some or all third parties, at your option).
+
+ c) You may charge a distribution fee for the physical act of
+ transferring a copy, and you may at your option offer warranty
+ protection in exchange for a fee.
+
+Mere aggregation of another unrelated program with this program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other program under the scope of these terms.
+
+ 3. You may copy and distribute SMAIL (or a portion or derivative of it,
+under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+ a) accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal
+ shipping charge) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for non-commercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+For an executable file, complete source code means all the source code for
+all modules it contains; but, as a special exception, it need not include
+source code for modules which are standard libraries that accompany the
+operating system on which the executable file runs.
+
+ 4. You may not copy, sublicense, distribute or transfer SMAIL
+except as expressly provided under this License Agreement. Any attempt
+otherwise to copy, sublicense, distribute or transfer SMAIL is void and
+your rights to use the program under this License agreement shall be
+automatically terminated. However, parties who have received computer
+software programs from you with this License Agreement will not have
+their licenses terminated so long as such parties remain in full compliance.
+
+ 5. If you wish to incorporate parts of SMAIL into other free
+programs whose distribution conditions are different, write to Landon
+Curt Noll & Ronald S. Karr via the Free Software Foundation at 51
+Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. We have not yet
+worked out a simple rule that can be stated here, but we will often
+permit this. We will be guided by the two goals of preserving the
+free status of all derivatives of our free software and of promoting
+the sharing and reuse of software.
+
+Your comments and suggestions about our licensing policies and our
+software are welcome! This contract was based on the contract made by
+the Free Software Foundation. Please contact the Free Software
+Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
+USA, or call (617) 542-5942 for details on copylefted material in
+general.
+
+ NO WARRANTY
+
+ BECAUSE SMAIL IS LICENSED FREE OF CHARGE, WE PROVIDE ABSOLUTELY NO
+WARRANTY, TO THE EXTENT PERMITTED BY APPLICABLE STATE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING, LANDON CURT NOLL & RONALD S. KARR AND/OR
+OTHER PARTIES PROVIDE SMAIL "AS IS" WITHOUT WARRANTY OF ANY KIND,
+EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF SMAIL IS WITH
+YOU. SHOULD SMAIL PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
+NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL LANDON CURT NOLL &
+RONALD S. KARR AND/OR ANY OTHER PARTY WHO MAY MODIFY AND REDISTRIBUTE
+SMAIL AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+LOST PROFITS, LOST MONIES, OR OTHER SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
+(INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
+INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE
+PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) SMAIL, EVEN IF YOU HAVE
+BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY
+ANY OTHER PARTY.
+
+
+
+SUN
+
+SUN MICROSYSTEMS, INC. THROUGH ITS SUN MICROSYSTEMS LABORATORIES
+DIVISION ("SUN") WILL LICENSE THIS SOFTWARE AND THE ACCOMPANYING
+DOCUMENTATION TO YOU (a "Licensee") ONLY ON YOUR ACCEPTANCE OF ALL
+THE TERMS SET FORTH BELOW.
+
+Sun grants Licensee a non-exclusive, royalty-free right to download,
+install, compile, use, copy and distribute the Software, modify or
+otherwise create derivative works from the Software (each, a
+"Modification") and distribute any Modification in source code and/or
+binary code form to its customers with a license agreement containing
+these terms and noting that the Software has been modified. The
+Software is copyrighted by Sun and other third parties and Licensee
+shall retain and reproduce all copyright and other notices presently
+on the Software. As between Sun and Licensee, Sun is the sole owner of
+all rights in and to the Software other than the limited rights
+granted to Licensee herein; Licensee will own its Modifications,
+expressly subject to Sun's continuing ownership of the
+Software. Licensee will, at its expense, defend and indemnify Sun and
+its licensors from and against any third party claims, including costs
+and reasonable attorneys' fees, and be wholly responsible for any
+liabilities arising out of or related to Licensee's development, use
+or distribution of the Software or Modifications. Any distribution of
+the Software and Modifications must comply with all applicable United
+States export control laws.
+
+THE SOFTWARE IS BEING PROVIDED TO LICENSEE "AS IS" AND ALL EXPRESS OR
+IMPLIED CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
+ARE DISCLAIMED. IN NO EVENT WILL SUN BE LIABLE HEREUNDER FOR ANY
+DIRECT DAMAGES OR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES OF ANY KIND.
+
+
+
+Sleepycat
+
+
+The Sleepycat License
+Copyright (c) 1990-1999
+Sleepycat Software. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Redistributions in any form must be accompanied by information on
+how to obtain complete source code for the DB software and any
+accompanying software that uses the DB software. The source code
+must either be included in the distribution or be available for no
+more than the cost of distribution plus a nominal fee, and must be
+freely redistributable under reasonable conditions. For an
+executable file, complete source code means the source code for all
+modules it contains. It does not include source code for modules or
+files that typically accompany the major components of the operating
+system on which the executable file runs.
+THIS SOFTWARE IS PROVIDED BY SLEEPYCAT SOFTWARE ``AS IS`` AND ANY EXPRESS
+OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
+NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL SLEEPYCAT SOFTWARE
+BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGE.
+
+Copyright (c) 1990, 1993, 1994, 1995
+The Regents of the University of California. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Neither the name of the University nor the names of its contributors
+may be used to endorse or promote products derived from this software
+without specific prior written permission.
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS`` AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+Copyright (c) 1995, 1996
+The President and Fellows of Harvard University. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Neither the name of the University nor the names of its contributors
+may be used to endorse or promote products derived from this software
+without specific prior written permission.
+THIS SOFTWARE IS PROVIDED BY HARVARD AND ITS CONTRIBUTORS ``AS IS`` AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL HARVARD OR ITS CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+
+
+
+UCB
+
+ Copyright (c) 1987, 1989, 1990, 1991, 1992, 1993, 1994
+ The Regents of the University of California. All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ 3. Neither the name of the University nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ SUCH DAMAGE.
+
+
+
+Unicode
+
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright 1991-2015 Unicode, Inc. All rights reserved.
+Distributed under the Terms of Use in
+http://www.unicode.org/copyright.html.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Unicode data files and any associated documentation
+(the "Data Files") or Unicode software and any associated documentation
+(the "Software") to deal in the Data Files or Software
+without restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, and/or sell copies of
+the Data Files or Software, and to permit persons to whom the Data Files
+or Software are furnished to do so, provided that
+(a) this copyright and permission notice appear with all copies
+of the Data Files or Software,
+(b) this copyright and permission notice appear in associated
+documentation, and
+(c) there is clear notice in each modified Data File or in the Software
+as well as in the documentation associated with the Data File(s) or
+Software that the data or software has been modified.
+
+THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
+ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT OF THIRD PARTY RIGHTS.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
+NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
+DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
+DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+PERFORMANCE OF THE DATA FILES OR SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder
+shall not be used in advertising or otherwise to promote the sale,
+use or other dealings in these Data Files or Software without prior
+written authorization of the copyright holder.
+
+
+
+W3C
+
+
+W3C SOFTWARE NOTICE AND LICENSE
+This work (and included software, documentation such as READMEs, or other related
+items) is being provided by the copyright holders under the following license.
+License
+By obtaining, using and/or copying this work, you (the licensee) agree that you have
+read, understood, and will comply with the following terms and conditions.
+Permission to copy, modify, and distribute this software and its documentation, with
+or without modification, for any purpose and without fee or royalty is hereby granted,
+provided that you include the following on ALL copies of the software and
+documentation or portions thereof, including modifications:
+The full text of this NOTICE in a location viewable to users of the redistributed or
+derivative work.
+Any pre-existing intellectual property disclaimers, notices, or terms and conditions.
+If none exist, the W3C Software Short Notice should be included (hypertext is
+preferred, text is permitted) within the body of any redistributed or derivative code.
+Notice of any changes or modifications to the files, including the date changes were
+made. (We recommend you provide URIs to the location from which the code is derived.)
+Disclaimers
+THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
+REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
+WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF
+THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
+TRADEMARKS OR OTHER RIGHTS.
+COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
+The name and trademarks of copyright holders may NOT be used in advertising or
+publicity pertaining to the software without specific, written prior permission. Title
+to copyright in this software and any associated documentation will at all times
+remain with copyright holders.
+Notes
+This version: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
+This formulation of W3C`s notice and license became active on December 31 2002. This
+version removes the copyright ownership notice such that this license can be used with
+materials other than those owned by the W3C, reflects that ERCIM is now a host of the
+W3C, includes references to this specific dated version of the license, and removes
+the ambiguous grant of "use". Otherwise, this version is the same as the previous
+version and is written so as to preserve the Free Software Foundation`s assessment of
+GPL compatibility and OSI`s certification under the Open Source Definition.
+
+
+
+
+ZPL-2.1
+
+
+ZPL 2.1
+Zope Public License (ZPL) Version 2.1
+
+A copyright notice accompanies this license document that identifies the copyright
+holders.
+
+This license has been certified as open source. It has also been designated as GPL
+compatible by the Free Software Foundation (FSF).
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions in source code must retain the accompanying copyright notice, this
+list of conditions, and the following disclaimer.
+Redistributions in binary form must reproduce the accompanying copyright notice, this
+list of conditions, and the following disclaimer in the documentation and/or other
+materials provided with the distribution.
+Names of the copyright holders must not be used to endorse or promote products derived
+from this software without prior written permission from the copyright holders.
+The right to distribute this software or to use it for any purpose does not give you
+the right to use Servicemarks (sm) or Trademarks (tm) of the copyright holders. Use of
+them is covered by separate agreement with the copyright holders.
+If any files are modified, you must cause the modified files to carry prominent
+notices stating that you changed the files and the date of any change.
+Disclaimer
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS`` AND ANY EXPRESSED OR
+IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
+THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+Zlib
+
+
+zlib License
+
+
+ This software is provided `as-is`, without any express or implied
+ warranty. In no event will the authors be held liable for any damages
+ arising from the use of this software.
+
+ Permission is granted to anyone to use this software for any purpose,
+ including commercial applications, and to alter it and redistribute it
+ freely, subject to the following restrictions:
+
+ 1. The origin of this software must not be misrepresented; you must not
+ claim that you wrote the original software. If you use this software
+ in a product, an acknowledgment in the product documentation would be
+ appreciated but is not required.
+ 2. Altered source versions must be plainly marked as such, and must not be
+ misrepresented as being the original software.
+ 3. This notice may not be removed or altered from any source distribution.
+
+
+
+
+
+copyleft-next-0.3.0
+
+ copyleft-next 0.3.0 ("this License")
+ Release date: 2013-05-16
+
+1. License Grants; No Trademark License
+
+ Subject to the terms of this License, I grant You:
+
+ a) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
+ copyright license, to reproduce, Distribute, prepare derivative works
+ of, publicly perform and publicly display My Work.
+
+ b) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
+ patent license under Licensed Patents to make, have made, use, sell,
+ offer for sale, and import Covered Works.
+
+ This License does not grant any rights in My name, trademarks, service
+ marks, or logos.
+
+2. Distribution: General Conditions
+
+ You may Distribute Covered Works, provided that You (i) inform
+ recipients how they can obtain a copy of this License; (ii) satisfy the
+ applicable conditions of sections 3 through 6; and (iii) preserve all
+ Legal Notices contained in My Work (to the extent they remain
+ pertinent). "Legal Notices" means copyright notices, license notices,
+ license texts, and author attributions, but does not include logos,
+ other graphical images, trademarks or trademark legends.
+
+3. Conditions for Distributing Derived Works; Outbound GPL Compatibility
+
+ If You Distribute a Derived Work, You must license the entire Derived
+ Work as a whole under this License, with prominent notice of such
+ licensing. This condition may not be avoided through such means as
+ separate Distribution of portions of the Derived Work. You may
+ additionally license the Derived Work under the GPL, so that the
+ recipient may further Distribute the Derived Work under either this
+ License or the GPL.
+
+4. Condition Against Further Restrictions; Inbound License Compatibility
+
+ When Distributing a Covered Work, You may not impose further
+ restrictions on the exercise of rights in the Covered Work granted under
+ this License. This condition is not excused merely because such
+ restrictions result from Your compliance with conditions or obligations
+ extrinsic to this License (such as a court order or an agreement with a
+ third party).
+
+ However, You may Distribute a Covered Work incorporating material
+ governed by a license that is both OSI-Approved and FSF-Free as of the
+ release date of this License, provided that Your Distribution complies
+ with such other license.
+
+5. Conditions for Distributing Object Code
+
+ You may Distribute an Object Code form of a Covered Work, provided that
+ you accompany the Object Code with a URL through which the Corresponding
+ Source is made available, at no charge, by some standard or customary
+ means of providing network access to source code.
+
+ If you Distribute the Object Code in a physical product or tangible
+ storage medium ("Product"), the Corresponding Source must be available
+ through such URL for two years from the date of Your most recent
+ Distribution of the Object Code in the Product. However, if the Product
+ itself contains or is accompanied by the Corresponding Source (made
+ available in a customarily accessible manner), You need not also comply
+ with the first paragraph of this section.
+
+ Each recipient of the Covered Work from You is an intended third-party
+ beneficiary of this License solely as to this section 5, with the right
+ to enforce its terms.
+
+6. Symmetrical Licensing Condition for Upstream Contributions
+
+ If You Distribute a work to Me specifically for inclusion in or
+ modification of a Covered Work (a "Patch"), and no explicit licensing
+ terms apply to the Patch, You license the Patch under this License, to
+ the extent of Your copyright in the Patch. This condition does not
+ negate the other conditions of this License, if applicable to the Patch.
+
+7. Nullification of Copyleft/Proprietary Dual Licensing
+
+ If I offer to license, for a fee, a Covered Work under terms other than
+ a license that is OSI-Approved or FSF-Free as of the release date of this
+ License or a numbered version of copyleft-next released by the
+ Copyleft-Next Project, then the license I grant You under section 1 is no
+ longer subject to the conditions in sections 2 through 5.
+
+8. Copyleft Sunset
+
+ The conditions in sections 2 through 5 no longer apply once fifteen
+ years have elapsed from the date of My first Distribution of My Work
+ under this License.
+
+9. Pass-Through
+
+ When You Distribute a Covered Work, the recipient automatically receives
+ a license to My Work from Me, subject to the terms of this License.
+
+10. Termination
+
+ Your license grants under section 1 are automatically terminated if You
+
+ a) fail to comply with the conditions of this License, unless You cure
+ such noncompliance within thirty days after becoming aware of it, or
+
+ b) initiate a patent infringement litigation claim (excluding
+ declaratory judgment actions, counterclaims, and cross-claims)
+ alleging that any part of My Work directly or indirectly infringes
+ any patent.
+
+ Termination of Your license grants extends to all copies of Covered
+ Works You subsequently obtain. Termination does not terminate the
+ rights of those who have received copies or rights from You subject to
+ this License.
+
+ To the extent permission to make copies of a Covered Work is necessary
+ merely for running it, such permission is not terminable.
+
+11. Later License Versions
+
+ The Copyleft-Next Project may release new versions of copyleft-next,
+ designated by a distinguishing version number ("Later Versions").
+ Unless I explicitly remove the option of Distributing Covered Works
+ under Later Versions, You may Distribute Covered Works under any Later
+ Version.
+
+** 12. No Warranty **
+** **
+** My Work is provided "as-is", without warranty. You bear the risk **
+** of using it. To the extent permitted by applicable law, each **
+** Distributor of My Work excludes the implied warranties of title, **
+** merchantability, fitness for a particular purpose and **
+** non-infringement. **
+
+** 13. Limitation of Liability **
+** **
+** To the extent permitted by applicable law, in no event will any **
+** Distributor of My Work be liable to You for any damages **
+** whatsoever, whether direct, indirect, special, incidental, or **
+** consequential damages, whether arising under contract, tort **
+** (including negligence), or otherwise, even where the Distributor **
+** knew or should have known about the possibility of such damages. **
+
+14. Severability
+
+ The invalidity or unenforceability of any provision of this License
+ does not affect the validity or enforceability of the remainder of
+ this License. Such provision is to be reformed to the minimum extent
+ necessary to make it valid and enforceable.
+
+15. Definitions
+
+ "Copyleft-Next Project" means the project that maintains the source
+ code repository at <https://gitorious.org/copyleft-next/> as of the
+ release date of this License.
+
+ "Corresponding Source" of a Covered Work in Object Code form means (i)
+ the Source Code form of the Covered Work; (ii) all scripts,
+ instructions and similar information that are reasonably necessary for
+ a skilled developer to generate such Object Code from the Source Code
+ provided under (i); and (iii) a list clearly identifying all Separate
+ Works (other than those provided in compliance with (ii)) that were
+ specifically used in building and (if applicable) installing the
+ Covered Work (for example, a specified proprietary compiler including
+ its version number). Corresponding Source must be machine-readable.
+
+ "Covered Work" means My Work or a Derived Work.
+
+ "Derived Work" means a work of authorship that copies from, modifies,
+ adapts, is based on, is a derivative work of, transforms, translates or
+ contains all or part of My Work, such that copyright permission is
+ required. The following are not Derived Works: (i) Mere Aggregation;
+ (ii) a mere reproduction of My Work; and (iii) if My Work fails to
+ explicitly state an expectation otherwise, a work that merely makes
+ reference to My Work.
+
+ "Distribute" means to distribute, transfer or make a copy available to
+ someone else, such that copyright permission is required.
+
+ "Distributor" means Me and anyone else who Distributes a Covered Work.
+
+ "FSF-Free" means classified as 'free' by the Free Software Foundation.
+
+ "GPL" means a version of the GNU General Public License or the GNU
+ Affero General Public License.
+
+ "I"/"Me"/"My" refers to the individual or legal entity that places My
+ Work under this License. "You"/"Your" refers to the individual or legal
+ entity exercising rights in My Work under this License. A legal entity
+ includes each entity that controls, is controlled by, or is under
+ common control with such legal entity. "Control" means (a) the power to
+ direct the actions of such legal entity, whether by contract or
+ otherwise, or (b) ownership of more than fifty percent of the
+ outstanding shares or beneficial ownership of such legal entity.
+
+ "Licensed Patents" means all patent claims licensable royalty-free by
+ Me, now or in the future, that are necessarily infringed by making,
+ using, or selling My Work, and excludes claims that would be infringed
+ only as a consequence of further modification of My Work.
+
+ "Mere Aggregation" means an aggregation of a Covered Work with a
+ Separate Work.
+
+ "My Work" means the particular work of authorship I license to You
+ under this License.
+
+ "Object Code" means any form of a work that is not Source Code.
+
+ "OSI-Approved" means approved as 'Open Source' by the Open Source
+ Initiative.
+
+ "Separate Work" means a work that is separate from and independent of a
+ particular Covered Work and is not by its nature an extension or
+ enhancement of the Covered Work, and/or a runtime library, standard
+ library or similar component that is used to generate an Object Code
+ form of a Covered Work.
+
+ "Source Code" means the preferred form of a work for making
+ modifications to it.
+
+
+
+tcl
+
+This software is copyrighted by the Regents of the University of
+California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
+Corporation and other parties. The following terms apply to all files
+associated with the software unless explicitly disclaimed in
+individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7014 (b) (3) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+
+
+
+ Proprietary Licenses
+
+Enea
+
+ Copyright (C) 2006 by Enea.
+ All rights reserved.
+
+ This Software is furnished under a software license agreement and
+ may be used only in accordance with the terms of such agreement.
+ Any other use or reproduction is prohibited. No title to and
+ ownership of the Software is hereby transferred.
+
+ PROPRIETARY NOTICE
+ This Software consists of confidential information.
+ Trade secret law and copyright law protect this Software.
+ The above notice of copyright on this Software does not indicate
+ any actual or intended publication of such Software.
+
+
+
+
--
cgit v1.2.3-54-g00ecf
From e58fc620a21759ccaae0caf24f7bbe55512b73c2 Mon Sep 17 00:00:00 2001
From: Jenkins for Enea Linux Test Framework
Date: Wed, 24 Feb 2021 00:36:07 +0100
Subject: Updated licenses.xml
---
.../doc/licenses.xml | 9936 --------------------
1 file changed, 9936 deletions(-)
(limited to 'doc/book-enea-nfv-access-platform-open-source')
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
index 352f820..e69de29 100644
--- a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
@@ -1,9936 +0,0 @@
-
-
-
- Packages and Licenses
-
-
- Packages
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Package Name
- Version
- Description
- License
-
-
-
-
-
-
- 4g-sierra
- 1.0
- Scripts to setup 4G modems from Sierra
- Enea
-
-
- acl
- 2.2.52
- Utilities for managing POSIX Access Control Lists.
- LGPL-2.1, GPL-2.0
-
-
- acpid
- 2.0.28
- A daemon for delivering ACPI events.
- GPL-2.0
-
-
- alsa-lib
- 1.1.4.1
- ALSA sound library.
- LGPL-2.1, GPL-2.0
-
-
- ant
- 1.8.1
- Another Neat Tool - build system for Java
- Apache-2.0
-
-
- antlr
- 2.7.7
- Framework for constructing recognizers interpreters compilers and translators
- PD
-
-
- apache2
- 2.4.27
- The Apache HTTP Server is a powerful efficient and extensible web server.
- Apache-2.0
-
-
- apr-util
- 1.6.0
- Apache Portable Runtime (APR) companion library.
- Apache-2.0
-
-
- apr
- 1.6.2
- Apache Portable Runtime (APR) library.
- Apache-2.0
-
-
- apt
- 1.2.24
- Advanced front-end for dpkg.
- GPL-2.0
-
-
- attr
- 2.4.47
- Utilities for manipulating filesystem extended attributes.
- LGPL-2.1, GPL-2.0
-
-
- aufs-util
- 4.4
- Tools for managing AUFS mounts.
- GPL-2.0
-
-
- augeas
- 1.5.0
- Augeas configuration API.
- LGPL-2.1
-
-
- autoconf-archive
- 2016.09.16
- a collection of freely re-usable Autoconf macros.
- GPL-3.0-with-autoconf-exception
-
-
- autoconf
- 2.69
- Autoconf is an extensible package of M4 macros that produce shell scripts to automatically configure software source code packages. Autoconf creates a configuration script for a package from a template file that lists the operating system features that the package can use in the form of M4 macro calls.
- GPL-2.0, GPL-3.0
-
-
- automake
- 1.15.1
- Automake is a tool for automatically generating `Makefile.in' files compliant with the GNU Coding Standards. Automake requires the use of Autoconf.
- GPL-2.0
-
-
- avahi
- 0.6.32
- "Avahi is a fully LGPL framework for Multicast DNS Service Discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. This tool implements IPv4LL ""Dynamic Configuration of IPv4 Link-Local Addresses"" (IETF RFC3927) a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server."
- GPL-2.0, LGPL-2.1
-
-
- avalon-framework-api
- 4.3
- Common way for components to be created initialized configured started. (API-only)
- Apache-2.0
-
-
- base-files
- 3.0.14
- The base-files package creates the basic system directory structure and provides a small set of key configuration files for the system.
- GPL-2.0
-
-
- base-passwd
- 3.5.29
- The master copies of the user database files (/etc/passwd and /etc/group). The update-passwd tool is also provided to keep the system databases synchronized with these master files.
- GPL-2.0
-
-
- bash-completion
- 2.7
- Programmable Completion for Bash 4.
- GPL-2.0
-
-
- bash
- 4.4
- An sh-compatible command language interpreter.
- GPL-3.0
-
-
- bc
- 1.06
- Arbitrary precision calculator language.
- GPL-2.0, LGPL-2.1
-
-
- bcel
- 5.2
- Java Bytecode manipulation library
- Apache-2.0
-
-
- bind
- 9.10.5-P3
- ISC Internet Domain Name Server.
- ISC, BSD
-
-
- binutils-cross-x86_64
- 2.29.1
- The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
- GPL-3.0
-
-
- binutils
- 2.29.1
- The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
- GPL-3.0
-
-
- bison
- 3.0.4
- Bison is a general-purpose parser generator that converts an annotated context-free grammar into an LALR(1) or GLR parser for that grammar. Bison is upward compatible with Yacc: all properly-written Yacc grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with little trouble.
- GPL-3.0
-
-
- bjam
- 1.64.0
- Portable Boost.Jam build tool for boost.
- BSL-1.0, MIT, Python-2.0
-
-
- bmap-tools
- 3.4
- "Bmap-tools - tools to generate block map (AKA bmap) and flash images using bmap. Bmaptool is a generic tool for creating the block map (bmap) for a file and copying files using the block map. The idea is that large file containing unused blocks like raw system image files can be copied or flashed a lot faster with bmaptool than with traditional tools like ""dd"" or ""cp""."
- GPL-2.0
-
-
- boost
- 1.64.0
- Free peer-reviewed portable C++ source libraries.
- BSL-1.0, MIT, Python-2.0
-
-
- bridge-utils
- 1.5
- Tools for ethernet bridging.
- GPL-2.0
-
-
- bsf
- 2.4.0
- Bean Scripting Framework package
- Apache-2.0
-
-
- btrfs-tools
- 4.12
- Btrfs is a new copy on write filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance repair and easy administration. This package contains utilities (mkfs fsck btrfsctl) used to work with btrfs and an utility (btrfs-convert) to make a btrfs filesystem from an ext3.
- GPL-2.0
-
-
- busybox
- 1.24.1
- BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for most of the utilities you usually find in GNU fileutils shellutils etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete POSIX environment for any small or embedded system.
- GPL-2.0, BSD-4-Clause
-
-
- bzip2
- 1.0.6
- bzip2 compresses files using the Burrows-Wheeler block-sorting text compression algorithm and Huffman coding. Compression is generally considerably better than that achieved by more conventional LZ77/LZ78-based compressors and approaches the performance of the PPM family of statistical compressors.
- BSD-4-Clause
-
-
- ca-certificates
- 20170717
- This package includes PEM files of CA certificates to allow SSL-based applications to check for the authenticity of SSL connections. This derived from Debian's CA Certificates.
- GPL-2.0, MPL-2.0
-
-
- cacao-initial
- 0.98
- CacaoVM for use as OpenEmbedded's Java VM
- GPL-2.0
-
-
- cairo
- 1.14.10
- Cairo is a multi-platform library providing anti-aliased vector-based rendering for multiple target backends. Paths consist of line segments and cubic splines and can be rendered at any width with various join and cap styles. All colors may be specified with optional translucence (opacity/alpha) and combined using the extended Porter/Duff compositing algebra as found in the X Render Extension.
- MPL-1.0, LGPL-2.1, GPL-3.0
-
-
- cantarell-fonts
- 0.0.24
- The Cantarell font typeface is designed as a contemporary Humanist sans serif and was developed for on-screen reading; in particular reading web pages on an HTC Dream mobile phone.
- OFL-1.1
-
-
- cdrkit
- 1.1.11
- CD/DVD command line tools.
- GPL-2.0
-
-
- cdrtools
- 3.01a31
- A set of tools for CD recording including cdrecord.
- GPL-2.0, CDDL-1.0, LGPL-2.1
-
-
- classpath-initial
- 0.93
- Java1.4-compatible GNU Classpath variant that is used as bootclasspath for jikes-native.
- GPL-2.0, SAX-PD
-
-
- classpath
- 0.99
- GNU Classpath standard Java libraries - For native Java-dependent programs
- GPL-2.0, SAX-PD
-
-
- cloud-init
- 0.7.6
- Init scripts for use on cloud images
- GPL-3.0
-
-
- cmake
- 3.8.2
- Cross-platform open-source make system.
- BSD
-
-
- collectd
- 5.12.0
- collectd is a daemon which collects system performance statistics periodically and provides mechanisms to store the values in a variety of ways for example in RRD files.
- GPL-2.0, MIT
-
-
- commons-logging
- 1.1.1
- Java Internet protocol suite library
- Apache-2.0
-
-
- commons-net
- 1.4.1
- Java Internet protocol suite library
- Apache-2.0
-
-
- compose-file
- 3.0
- Parser for the Compose file format (version 3)
- Apache-2.0
-
-
- containerd-docker
- v0.2.x
- containerd is a daemon to control runC built for performance and density. containerd leverages runC's advanced features such as seccomp and user namespace support as well as checkpoint and restore for cloning and live migration of containers.
- Apache-2.0
-
-
- core-image-minimal-initramfs
- 1.0
- Small image capable of booting a device. The kernel includes the Minimal RAM-based Initial Root Filesystem (initramfs) which finds the first 'init' program more efficiently.
- MIT
-
-
- coreutils
- 8.27
- The GNU Core Utilities provide the basic file shell and text manipulation utilities. These are the core utilities which are expected to exist on every system.
- GPL-3.0
-
-
- crda
- 3.18
- Wireless Central Regulatory Domain Agent.
- copyleft-next-0.3.0
-
-
- cross-localedef
- 2.26
- Cross locale generation tool for glibc.
- LGPL-2.1
-
-
- cryptodev-linux
- 1.9
- A /dev/crypto device driver header file.
- GPL-2.0
-
-
- cup
- 0.10k
- Lexical analyzer generator for Java
- CUP
-
-
- curl
- 7.58.0
- Command line tool and library for client-side URL transfers.
- MIT
-
-
- cwautomacros
- 20110201
- Collection of autoconf m4 macros.
- GPL-2.0
-
-
- db
- 5.3.28
- Berkeley Database v5.
- Sleepycat
-
-
- dbus-glib
- 0.108
- GLib bindings for the D-Bus message bus that integrate the D-Bus library with the GLib thread abstraction and main loop.
- AFL-2.0, GPL-2.0
-
-
- dbus-test
- 1.10.20
- D-Bus test package (for D-bus functionality testing only).
- AFL-2.0, GPL-2.0
-
-
- dbus
- 1.10.20
- "D-Bus is a message bus system a simple way for applications to talk to one another. In addition to interprocess communication D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a \""single instance\"" application or daemon and to launch applications and daemons on demand when their services are needed."
- AFL-2.0, GPL-2.0
-
-
- debianutils
- 4.8.1.1
- Miscellaneous utilities specific to Debian.
- GPL-2.0, SMAIL_GPL
-
-
- depmodwrapper
- 1.0
- Wrapper script for the Linux kernel module dependency indexer.
- MIT
-
-
- dhcp
- 4.3.6
- DHCP (Dynamic Host Configuration Protocol) is a protocol which allows individual devices on an IP network to get their own network configuration information from a server. DHCP helps make it easier to administer devices.
- ISC
-
-
- diffutils
- 3.6
- Diffutils contains the GNU diff diff3 sdiff and cmp utilities. These programs are usually used for creating patch files.
- GPL-3.0
-
-
- dmidecode
- 3.1
- DMI (Desktop Management Interface) table related utilities.
- GPL-2.0
-
-
- dnsmasq
- 2.78
- Lightweight easy to configure DNS forwarder and DHCP server.
- GPL-2.0, GPL-3.0
-
-
- docker
- 17.06.0
- Linux container runtime Docker complements kernel namespacing with a high-level API which operates at the process level. It runs unix processes with strong guarantees of isolation and repeatability across servers. . Docker is a great building block for automating distributed systems: large-scale web deployments database clusters continuous deployment systems private PaaS service-oriented architectures etc. . This package contains the daemon and client. Using docker.io is officially supported on x86_64 and arm (32-bit) hosts. Other architectures are considered experimental. . Also note that kernel version 3.10 or above is required for proper operation of the daemon process and that any lower versions may have subtle and/or glaring issues.
- Apache-2.0
-
-
- dosfstools
- 4.1
- DOS FAT Filesystem Utilities.
- GPL-3.0
-
-
- dpdk-dev-libibverbs
- 1.2.1-3.4-2.0.0.0
- libibverbs library to support Mellanox config
- GPL-2.0
-
-
- dpdk
- 18.02
- Intel(r) Data Plane Development Kit
- BSD, LGPL-2.0, GPL-2.0
-
-
- dpkg
- 1.18.24
- Package maintenance system from Debian.
- GPL-2.0
-
-
- dtc
- 1.4.4
- The Device Tree Compiler is a tool used to manipulate the Open-Firmware-like device tree used by PowerPC kernels.
- GPL-2.0, BSD
-
-
- e2fsprogs
- 1.43.5
- The Ext2 Filesystem Utilities (e2fsprogs) contain all of the standard utilities for creating fixing configuring and debugging ext2 filesystems.
- GPL-2.0, LGPL-2.0, BSD, MIT
-
-
- ebtables
- 2.0.10-4
- Utility for basic Ethernet frame filtering on a Linux bridge advanced logging MAC DNAT/SNAT and brouting.
- GPL-2.0
-
-
- ecj-bootstrap
- 1.0
- JDT Core Batch Compiler - Bootstrap variant
- MIT
-
-
- ecj-initial
- 1.0
- JDT Core Batch Compiler - Bootstrap variant
- MIT
-
-
- efibootmgr
- 0.15
- Linux user-space application to modify the EFI Boot Manager.
- GPL-2.0
-
-
- efitools
- 1.7.0
- From the EFI Tools package in the Linux user-space it's now possible to read and manipulate the UEFI signatures database via the new efi-readvar and efi-updatevar commands. Aside from needing efitools 1.4 the EFIVARFS file-system is also needed which was only introduced in the Linux 3.8 kernel.
- GPL-2.0
-
-
- efivar
- 0.31
- efivar provides a simple command line interface to the UEFI variable facility
- LGPL-2.1
-
-
- element-vcpe
- 4.1.3
- vCPE(based on Element-ODM)
- Enea, BSD, BSD-2-Clause, GPL-3.0, ISC, LGPL-2.1
-
-
- elfutils
- 0.170
- Utilities and libraries for handling compiled object files.
- GPL-3.0, Elfutils-Exception
-
-
- enea-nfv-access-vnf
- 1.0
- VNF image of the Enea NFV Access Platform includes kernel rootfs and boot parameters
- MIT
-
-
- enea-nfv-access
- 1.0
- Image for the host side of the Enea NFV Access Platform with ODM and NETCONF Edgelink customizations
- MIT
-
-
- ethtool
- 4.11
- A small utility for examining and tuning the settings of your ethernet-based network interfaces.
- GPL-2.0
-
-
- expat
- 2.2.3
- Expat is an XML parser library written in C. It is a stream-oriented parser in which an application registers handlers for things the parser might find in the XML document (like start tags)
- MIT
-
-
- fastjar
- 0.98
- jar replacement written in C.
- GPL-2.0
-
-
- file
- 5.31
- File attempts to classify files depending on their contents and prints a description if a match is found.
- BSD
-
-
- findutils
- 4.6.0
- The GNU Find Utilities are the basic directory searching utilities of the GNU operating system. These programs are typically used in conjunction with other programs to provide modular and powerful directory search and file locating capabilities to other commands.
- GPL-3.0
-
-
- flex
- 2.6.0
- Flex is a fast lexical analyser generator. Flex is a tool for generating programs that recognize lexical patterns in text.
- BSD
-
-
- fontconfig
- 2.12.4
- Fontconfig is a font configuration and customization library which does not depend on the X Window System. It is designed to locate fonts within the system and select them according to requirements specified by applications. Fontconfig is not a rasterization library nor does it impose a particular rasterization library on the application. The X-specific library 'Xft' uses fontconfig along with freetype to specify and rasterize fonts.
- MIT, PD
-
-
- freetype
- 2.8
- FreeType is a software font engine that is designed to be small efficient highly customizable and portable while capable of producing high-quality output (glyph images). It can be used in graphics libraries display servers font conversion tools text image generation tools and many other products as well.
- FreeType, GPL-2.0
-
-
- fuse
- 2.9.7
- FUSE (Filesystem in Userspace) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. FUSE also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations.
- GPL-2.0, LGPL-2.0
-
-
- gawk
- 4.1.4
- The GNU version of awk a text processing utility. Awk interprets a special-purpose programming language to do quick and easy text pattern matching and reformatting jobs.
- GPL-3.0
-
-
- gcc-cross-initial-x86_64
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc-cross-x86_64
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc-runtime
- 7.3.0
- Runtime libraries from GCC.
- GPL-3.0-with-GCC-exception
-
-
- gcc-source-7.3.0
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gdbm
- 1.13
- Key/value database library with extensible hashing.
- GPL-3.0
-
-
- gettext-minimal
- 0.19.8.1
- Contains the m4 macros sufficient to support building autoconf/automake. This provides a significant build time speedup by the removal of gettext-native from most dependency chains (now only needed for gettext for the target).
- FSF-Unlimited
-
-
- gettext
- 0.19.8.1
- GNU gettext is a set of tools that provides a framework to help other programs produce multi-lingual messages. These tools include a set of conventions about how programs should be written to support message catalogs a directory and file naming organization for the message catalogs themselves a runtime library supporting the retrieval of translated messages and a few stand-alone programs to massage in various ways the sets of translatable and already translated strings.
- GPL-3.0, LGPL-2.1
-
-
- giflib
- 5.1.4
- shared library for GIF images.
- MIT
-
-
- git
- 2.13.3
- Distributed version control system.
- GPL-2.0
-
-
- glib-2.0
- 2.52.3
- GLib is a general-purpose utility library which provides many useful data types macros type conversions string utilities file utilities a main loop abstraction and so on.
- LGPL-2.0, BSD, PD
-
-
- glibc-locale
- 2.26
- Locale data from glibc.
- GPL-2.0, LGPL-2.1
-
-
- glibc
- 2.26
- The GNU C Library is used as the system C library in most systems with the Linux kernel.
- GPL-2.0, LGPL-2.1
-
-
- gmp
- 6.1.2
- GMP is a free library for arbitrary precision arithmetic operating on signed integers rational numbers and floating point numbers
- GPL-2.0, LGPL-3.0
-
-
- gnome-desktop-testing
- 2014.1
- Test runner for GNOME-style installed tests.
- LGPL-2.0
-
-
- gnu-config
- 20150728
- Tool that installs the GNU config.guess / config.sub into a directory tree
- GPL-3.0-with-autoconf-exception
-
-
- gnu-efi
- 3.0.6
- Libraries for producing EFI binaries.
- GPL-2.0, BSD-2-Clause
-
-
- gnujaf
- 1.1.1
- Provides a mean to type data and locate components suitable for performing various kinds of action on it.
- GPL-2.0-with-GCC-exception
-
-
- gnulib
- 2017-08-20.18
- A collection of software subroutines which are designed to be usable on many operating systems. The goal of the project is to make it easy for free software authors to make their software run on many operating systems. Since source is designed to be copied from gnulib it is not a library per-se as much as a collection of portable idioms to be used in other projects.
- LGPL-2.0
-
-
- gnumail
- 1.1.2
- GNU's free implementation of the JavaMail API specification
- GPL-2.0-with-GCC-exception
-
-
- gnutls
- 3.5.13
- GNU Transport Layer Security Library.
- GPL-3.0, LGPL-2.1
-
-
- go-capability
- 0.0
- Utilities for manipulating POSIX capabilities in Go.
- BSD-2-Clause
-
-
- go-cli
- 1.1.0
- A small package for building command line apps in Go
- MIT
-
-
- go-connections
- 0.2.1
- Utility package to work with network connections
- Apache-2.0
-
-
- go-context
- git
- A golang registry for global request variables.
- BSD-3-Clause
-
-
- go-cross-x86_64
- 1.9.4
- The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
- BSD-3-Clause
-
-
- go-dbus
- 4.0.0
- Native Go bindings for D-Bus
- BSD-2-Clause
-
-
- go-distribution
- 2.6.0
- The Docker toolset to pack ship store and deliver content
- Apache-2.0
-
-
- go-fsnotify
- 1.2.11
- A golang registry for global request variables.
- BSD-3-Clause
-
-
- go-libtrust
- 0.0
- Primitives for identity and authorization
- Apache-2.0
-
-
- go-logrus
- 0.11.0
- A golang registry for global request variables.
- MIT
-
-
- go-mux
- git
- A powerful URL router and dispatcher for golang.
- BSD-3-Clause
-
-
- go-patricia
- 2.2.6
- A generic patricia trie (also called radix tree) implemented in Go (Golang)
- MIT
-
-
- go-pty
- git
- PTY interface for Go
- MIT
-
-
- go-systemd
- 4
- Go bindings to systemd socket activation journal D-Bus and unit files
- Apache-2.0
-
-
- go
- 1.9.4
- The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
- BSD-3-Clause
-
-
- gobject-introspection
- 1.52.1
- Middleware layer between GObject-using C libraries and language bindings.
- LGPL-2.0, GPL-2.0
-
-
- gotty
- 1.0
- Run a terminal application as a web service
- MIT
-
-
- gperf
- 3.1
- GNU gperf is a perfect hash function generator
- GPL-3.0
-
-
- gpgme
- 1.9.0
- GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a High-Level Crypto API for encryption decryption signing signature verification and key management
- GPL-2.0, LGPL-2.1
-
-
- gptfdisk
- 1.0.3
- GPT fdisk is a disk partitioning tool loosely modeled on Linux fdisk but used for modifying GUID Partition Table (GPT) disks. The related FixParts utility fixes some common problems on Master Boot Record (MBR) disks.
- GPL-2.0
-
-
- grep
- 3.1
- GNU grep utility.
- GPL-3.0
-
-
- groff
- 1.22.3
- The groff (GNU troff) software is a typesetting package which reads plain text mixed with formatting commands and produces formatted output.
- GPL-3.0
-
-
- grpc-go
- 1.4.0
- The Go language implementation of gRPC. HTTP/2 based RPC
- BSD
-
-
- grub-disable-fallback
- 1.0
- Enea service to disable grub fallback when boot is successful
- Enea
-
-
- grub-efi
- 2.02
- GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
- GPL-3.0
-
-
- grub
- 2.02
- GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
- GPL-3.0
-
-
- gtk-doc
- 1.25
- Gtk-doc is a set of scripts that extract specially formatted comments from glib-based software and produce a set of html documentation files from them
- GPL-2.0
-
-
- gzip
- 1.8
- GNU Gzip is a popular data compression program originally written by Jean-loup Gailly for the GNU project. Mark Adler wrote the decompression part
- GPL-3.0
-
-
- harfbuzz
- 1.4.8
- HarfBuzz is an OpenType text shaping engine.
- MIT
-
-
- haveged
- 1.9.1
- The haveged project is an attempt to provide an easy-to-use unpredictable random number generator based upon an adaptation of the HAVEGE algorithm. Haveged was created to remedy low-entropy conditions in the Linux random device that can occur under some workloads especially on headless servers.
- GPL-3.0
-
-
- help2man
- 1.47.4
- Program for creating simple man pages.
- GPL-3.0
-
-
- hostapd
- 2.9
- User space daemon for extended IEEE 802.11 management.
- BSD-3-Clause
-
-
- htop
- 1.0.3
- htop process monitor.
- GPL-2.0
-
-
- hugepage-reservation
- 1.0
- Reserve hugepages on system startup.
- Enea
-
-
- icedtea7
- 2.1.3
- Harness to build the source code from OpenJDK using Free Software build tools
- GPL-2.0-with-classpath-exception
-
-
- icu
- 59.1
- The International Component for Unicode (ICU) is a mature portable set of C/C++ and Java libraries for Unicode support software internationalization (I18N) and globalization (G11N) giving applications the same results on all platforms.
- ICU
-
-
- inetlib
- 1.1.1
- GNU Classpath inetlib is an extension library to provide extra network protocol support for GNU Classpath and ClasspathX project but it can also used standalone to add http imap pop3 and smtp client support applications.
- GPL-2.0-with-GCC-exception
-
-
- initramfs-framework
- 1.0
- Modular initramfs system.
- MIT
-
-
- initramfs-module-install-efi
- 1.0
- initramfs-framework module for EFI installation option.
- MIT
-
-
- initramfs-module-install
- 1.0
- initramfs-framework module for installation option.
- MIT
-
-
- initramfs-module-setup-live
- 1.0
- initramfs-framework module for live booting.
- MIT
-
-
- initramfs-ostree-image
- 1.0
- OSTree initramfs image
- MIT
-
-
- inputproto
- 2.3.2
- This package provides the wire protocol for the X Input extension. The extension supports input devices other then the core X keyboard and pointer.
- MIT
-
-
- intltool
- 0.51.0
- Utility scripts for internationalizing XML.
- GPL-2.0
-
-
- iperf3
- 3.2
- iperf is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing protocols and buffers. For each test it reports the bandwidth loss and other parameters.
- BSD
-
-
- iproute2
- 4.11.0
- Iproute2 is a collection of utilities for controlling TCP / IP networking and traffic control in Linux. Of the utilities ip and tc are the most important. ip controls IPv4 and IPv6 configuration and tc stands for traffic control.
- GPL-2.0
-
-
- iptables
- 1.6.1
- iptables is the userspace command line program used to configure and control network packet filtering code in Linux.
- GPL-2.0
-
-
- iw
- 4.9
- iw is a new nl80211 based CLI configuration utility for wireless devices. It supports almost all new drivers that have been added to the kernel recently.
- BSD
-
-
- ixgbe
- 5.10.2
- The ixgbe driver supports 82598- and 82599-based PCI Express* 10 Gigabit Network Connections.
- GPL-2.0
-
-
- ixgbevf
- 4.10.2
- This virtual function driver supports kernel versions 2.6.x and newer This driver supports 82599 X540 X550 and X552-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support. The guest OS loading this driver must support MSI-X interrupts.
- GPL-2.0
-
-
- jacl
- 1.4.1
- Tcl interpreter for Java
- UCB, SUN, AMD, CDS
-
-
- jamvm
- 2.0.0-devel
- A compact Java Virtual Machine which conforms to the JVM specification version 2.
- GPL-2.0
-
-
- jansson
- 2.9
- Jansson is a C library for encoding decoding and manipulating JSON data.
- MIT
-
-
- jaxp1.3
- 1.4.01
- Java XML parser and transformer APIs (DOM SAX JAXP TrAX)
- Apache-2.0, W3C, PD
-
-
- jdepend
- 2.9.1
- Design quality metrics generator for each Java
- BSD
-
-
- jikes-initial
- 1.0
- Initial Java 1.4-compatible (and not higher) compiler.
- MIT
-
-
- jikes
- 1.22
- Java compiler adhering to language and VM specifications
- IPL-1.0
-
-
- jlex
- 1.2.6
- Lexical analyzer generator for Java
- JLEX
-
-
- jq
- 1.5
- jq is like sed for JSON data you can use it to slice and filter and map and transform structured data with the same ease that sed awk grep and friends let you play with text.
- MIT
-
-
- jsch
- 0.1.40
- SSH implementation in Java
- BSD
-
-
- junit
- 3.8.2
- JUnit is a testing framework for Java
- CPL-1.0
-
-
- jzlib
- 1.0.7
- zlib implementation in Java
- BSD
-
-
- kbd
- 2.0.4
- Keytable files and keyboard utilities.
- GPL-2.0
-
-
- kbproto
- 1.0.7
- This package provides the wire protocol for the X Keyboard extension. This extension is used to control options related to keyboard handling and layout.
- MIT
-
-
- kern-tools
- 0.2
- Tools for managing Yocto Project style branched kernels.
- GPL-2.0
-
-
- keymaps
- 1.0
- Keymaps and initscript to set the keymap on bootup.
- GPL-2.0
-
-
- keyutils
- 1.5.10
- Utilities to control the kernel key management facility and to provide a mechanism by which the kernel call back to userspace to get a key instantiated.
- LGPL-2.1, GPL-2.0
-
-
- kmod
- 24
- kmod is a set of tools to handle common tasks with Linux kernel modules like insert remove list check properties resolve dependencies and aliases.
- GPL-2.0, LGPL-2.1
-
-
- krb5
- 1.15.1
- "Kerberos is a system for authenticating users and services on a network. Kerberos is a trusted third-party service. That means that there is a third party (the Kerberos server) that is trusted by all the entities on the network (users and services usually called ""principals""). . This is the MIT reference implementation of Kerberos V5. . This package contains the Kerberos key server (KDC). The KDC manages all authentication credentials for a Kerberos realm holds the master keys for the realm and responds to authentication requests. This package should be installed on both master and slave KDCs."
- MIT
-
-
- ldconfig
- 2.12.1
- A standalone native ldconfig build.
- GPL-2.0
-
-
- less
- 487
- Less is a program similar to more i.e. a terminal based program for viewing text files and the output from other programs. Less offers many features beyond those that more does.
- GPL-3.0, BSD-2-Clause
-
-
- libaio
- 0.3.110
- Asynchronous input/output library that uses the kernels native interface
- LGPL-2.1
-
-
- libarchive
- 3.3.2
- C library and command-line tools for reading and writing tar cpio zip ISO and other archive formats
- BSD
-
-
- libassuan
- 2.4.3
- IPC library used by GnuPG and GPGME.
- GPL-3.0, LGPL-2.1
-
-
- libbsd
- 0.8.6
- This library provides useful functions commonly found on BSD systems and lacking on others like GNU systems thus making it easier to port projects with strong BSD origins without needing to embed the same code over and over again on each project.
- BSD-4-Clause, ISC, PD
-
-
- libcap
- 2.25
- Library for getting/setting POSIX.1e capabilities.
- BSD, GPL-2.0
-
-
- libcgroup
- 0.41
- libcgroup is a library that abstracts the control group file system in Linux. Control groups allow you to limit account and isolate resource usage (CPU memory disk I/O etc.) of groups of processes.
- LGPL-2.1
-
-
- libcheck
- 0.10.0
- Check - unit testing framework for C code.
- LGPL-2.1
-
-
- libdaemon
- 0.14
- Lightweight C library which eases the writing of UNIX daemons.
- LGPL-2.1
-
-
- libdevmapper
- 2.02.171
- LVM2 is a set of utilities to manage logical volumes in Linux.
- GPL-2.0, LGPL-2.0
-
-
- libecj-bootstrap
- 3.6.2
- JDT Core Batch Compiler - Jar only
- EPL-1.0
-
-
- liberation-fonts
- 2.00.1
- The Liberation(tm) Fonts is a font family originally created by Ascender(c) which aims at metric compatibility with Arial Times New Roman Courier New.
- OFL-1.1
-
-
- libffi
- 3.2.1
- The `libffi' library provides a portable high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. FFI stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The `libffi' library really only provides the lowest machine dependent layer of a fully featured foreign function interface. A layer must exist above `libffi' that handles type conversions for values passed between the two languages.
- MIT
-
-
- libfile-slurp-perl
- 9999.19
- This module provides subroutines to read or write entire files with a simple call. It also has a subroutine for reading the list of filenames in a directory.
- Artistic-1.0, GPL-1.0
-
-
- libgcc-initial
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception
-
-
- libgcc
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- libgcrypt
- 1.8.0
- General purpose cryptographic library based on the code from GnuPG.
- GPL-2.0, LGPL-2.1, GPL-3.0
-
-
- libgpg-error
- 1.27
- Small library that defines common error values for all GnuPG components.
- GPL-2.0, LGPL-2.1
-
-
- libgudev
- 231
- GObject wrapper for libudev.
- LGPL-2.1
-
-
- libice
- 1.0.9
- The Inter-Client Exchange (ICE) protocol provides a generic framework for building protocols on top of reliable byte-stream transport connections. It provides basic mechanisms for setting up and shutting down connections for performing authentication for negotiating versions and for reporting errors.
- MIT
-
-
- libidn
- 1.33
- Implementation of the Stringprep Punycode and IDNA specifications defined by the IETF Internationalized Domain Names (IDN) working group.
- LGPL-2.1, LGPL-3.0, GPL-3.0
-
-
- libjpeg-turbo
- 1.5.2
- libjpeg-turbo is a derivative of libjpeg that uses SIMD instructions (MMX SSE2 NEON) to accelerate baseline JPEG compression and decompression
- BSD-3-Clause
-
-
- libmbim
- 1.16.0
- libmbim is a glib-based library for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol
- GPL-2.0, LGPL-2.1
-
-
- libmnl
- 1.0.4
- Minimalistic user-space library oriented to Netlink developers providing functions for common tasks in parsing validating and constructing both the Netlink header and TLVs.
- LGPL-2.1
-
-
- libmpc
- 1.0.3
- Mpc is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result. It is built upon and follows the same principles as Mpfr
- LGPL-3.0
-
-
- libndp
- 1.6
- Library for IPv6 Neighbor Discovery Protocol.
- LGPL-2.1
-
-
- libnewt
- 0.52.20
- Newt is a programming library for color text mode widget based user interfaces. Newt can be used to add stacked windows entry widgets checkboxes radio buttons labels plain text fields scrollbars etc. to text mode user interfaces. This package also contains the shared library needed by programs built with newt as well as a /usr/bin/dialog replacement called whiptail. Newt is based on the slang library.
- LGPL-2.0
-
-
- libnl
- 3.4.0
- A library for applications dealing with netlink sockets.
- LGPL-2.1
-
-
- libnss-mdns
- 0.10
- Name Service Switch module for Multicast DNS (zeroconf) name resolution.
- LGPL-2.1
-
-
- libpcap
- 1.8.1
- Libpcap provides a portable framework for low-level network monitoring. Libpcap can provide network statistics collection security monitoring and network debugging.
- BSD
-
-
- libpciaccess
- 0.13.5
- libpciaccess provides functionality for X to access the PCI bus and devices in a platform-independent way.
- MIT
-
-
- libpcre
- 8.41
- The PCRE library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. PCRE has its own native API as well as a set of wrapper functions that correspond to the POSIX regular expression API.
- BSD
-
-
- libpng
- 1.6.31
- PNG image format decoding library.
- Libpng
-
-
- libpthread-stubs
- 0.4
- This library provides weak aliases for pthread functions not provided in libc or otherwise available by default.
- MIT
-
-
- libqmi
- 1.20.2
- libqmi is a glib-based library for talking to WWAN modems and devices which speak the Qualcomm MSM Interface (QMI) protocol
- GPL-2.0, LGPL-2.1
-
-
- libsdl
- 1.2.15
- Simple DirectMedia Layer is a cross-platform multimedia library designed to provide low level access to audio keyboard mouse joystick 3D hardware via OpenGL and 2D video framebuffer.
- LGPL-2.1
-
-
- libsign
- 0.3.2
- This project targets to provide a generic signing framework. This framework separates the signing request and signing process and correspondingly forms the so-called signlet and signaturelet. Each signaturelet only concerns about the details about how to construct the layout of a signature format and signlet only cares how to construct the signing request.
- BSD-3-Clause
-
-
- libsm
- 1.2.2
- "The Session Management Library (SMlib) is a low-level \""C\"" language interface to XSMP. The purpose of the X Session Management Protocol (XSMP) is to provide a uniform mechanism for users to save and restore their sessions. A session is a group of clients each of which has a particular state."
- MIT
-
-
- libtasn1
- 4.12
- Library for ASN.1 and DER manipulation.
- GPL-3.0, LGPL-2.1
-
-
- libtool
- 2.4.6
- This is GNU libtool a generic library support script. Libtool hides the complexity of generating special library types (such as shared libraries) behind a consistent interface.
- GPL-2.0, LGPL-2.1
-
-
- libunistring
- 0.9.7
- Text files are nowadays usually encoded in Unicode and may consist of very different scripts from Latin letters to Chinese Hanzi with many kinds of special characters accents right-to-left writing marks hyphens Roman numbers and much more. But the POSIX platform APIs for text do not contain adequate functions for dealing with particular properties of many Unicode characters. In fact the POSIX APIs for text have several assumptions at their base which don't hold for Unicode text. This library provides functions for manipulating Unicode strings and for manipulating C strings according to the Unicode standard. This package contains documentation.
- LGPL-3.0, GPL-2.0
-
-
- libusb1
- 1.0.21
- Userspace library to access USB (version 1.0).
- LGPL-2.1
-
-
- libvirt
- 4.2.0
- A toolkit to interact with the virtualization capabilities of recent versions of Linux.
- LGPL-2.1, GPL-2.0
-
-
- libx11
- 1.6.5
- This package provides a client interface to the X Window System otherwise known as 'Xlib'. It provides a complete API for the basic functions of the window system.
- MIT, BSD
-
-
- libxau
- 1.0.8
- libxau provides the main interfaces to the X11 authorisation handling which controls authorisation for X connections both client-side and server-side.
- MIT
-
-
- libxcb
- 1.12
- The X protocol C-language Binding (XCB) is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
- MIT
-
-
- libxdmcp
- 1.1.2
- The purpose of the X Display Manager Control Protocol (XDMCP) is to provide a uniform mechanism for an autonomous display to request login service from a remote host. An X terminal (screen keyboard mouse processor network interface) is a prime example of an autonomous display.
- MIT
-
-
- libxext
- 1.3.3
- libXext provides an X Window System client interface to several extensions to the X protocol. The supported protocol extensions are DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. libXext also provides a small set of utility functions to aid authors of client APIs for X protocol extensions.
- MIT
-
-
- libxft
- 2.3.2
- Xft was designed to provide good support for scalable fonts and to do so efficiently. Unlike the core fonts system it supports features such as anti-aliasing and sub-pixel rasterisation. Perhaps more importantly it gives applications full control over the way glyphs are rendered making fine typesetting and WYSIWIG display possible. Finally it allows applications to use fonts that are not installed system-wide for displaying documents with embedded fonts. Xft is not compatible with the core fonts system: usage of Xft requires fairly extensive changes to toolkits (user-interface libraries).
- MIT
-
-
- libxkbcommon
- 0.7.1
- libxkbcommon is a keymap compiler and support library which processes a reduced subset of keymaps as defined by the XKB specification.
- MIT
-
-
- libxml-parser-perl
- 2.44
- XML::Parser - A perl module for parsing XML documents.
- Artistic-1.0, GPL-1.0
-
-
- libxml2
- 2.9.5
- The XML Parser Library allows for manipulation of XML files. Libxml2 exports Push and Pull type parser interfaces for both XML and HTML. It can do DTD validation at parse time on a parsed document instance or with an arbitrary DTD. Libxml2 includes complete XPath XPointer and Xinclude implementations. It also has a SAX like interface which is designed to be compatible with Expat.
- MIT
-
-
- libxrandr
- 1.5.1
- The X Resize Rotate and Reflect Extension called RandR for short brings the ability to resize rotate and reflect the root window of a screen. It is based on the X Resize and Rotate Extension as specified in the Proceedings of the 2001 Usenix Technical Conference [RANDR].
- MIT
-
-
- libxrender
- 0.9.10
- The X Rendering Extension (Render) introduces digital image composition as the foundation of a new rendering model within the X Window System. Rendering geometric figures is accomplished by client-side tessellation into either triangles or trapezoids. Text is drawn by loading glyphs into the server and rendering sets of them.
- MIT
-
-
- libxslt
- 1.1.29
- GNOME XSLT library.
- MIT
-
-
- libyaml
- 0.1.7
- LibYAML is a C library for parsing and emitting data in YAML 1.1 a human-readable data serialization format.
- MIT
-
-
- lighttpd
- 1.4.45
- Lightweight high-performance web server.
- BSD
-
-
- linux-firmware
- 0.0
- Firmware files for use with Linux kernel.
- Redistributable binaries
-
-
- linux-intel-guest
- 4.14.123
- Linux kernel.
- GPL-2.0
-
-
- linux-intel-host
- 4.14.123
- Linux kernel.
- GPL-2.0
-
-
- linux-libc-headers
- 4.12
- Sanitized set of kernel headers for the C library's use.
- GPL-2.0
-
-
- lmsensors-config
- 1.0
- Hardware health monitoring configuration files
- MIT
-
-
- lmsensors
- 3.6.0
- Hardware health monitoring applications.
- GPL-2.0, LGPL-2.1
-
-
- log-collector
- 1.0
- Service that collects platform logs
- Enea
-
-
- log4j1.2
- 1.2.17
- Java library to help the programmer output log statements to a variety of output targets
- Apache-2.0
-
-
- logkit
- 1.2.2
- Logging toolkit designed for secure performance orientated logging in Java applications
- Apache-2.0
-
-
- logrotate
- 3.12.3
- Rotates compresses removes and mails system log files.
- GPL-2.0
-
-
- lsb
- 4.1
- LSB support for OpenEmbedded.
- GPL-2.0
-
-
- lsbinitscripts
- 9.72
- SysV init scripts which are only used in an LSB image.
- GPL-2.0
-
-
- lshw
- 02.17
- A small tool to provide detailed information on the hardware configuration of the machine. It can report exact memory configuration firmware version mainboard configuration CPU version and speed cache configuration bus speed etc. on DMI-capable or EFI systems.
- GPL-2.0
-
-
- lsof
- 4.89
- Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open Files and it does just that.
- BSD
-
-
- lvm2
- 2.02.171
- LVM2 is a set of utilities to manage logical volumes in Linux.
- GPL-2.0, LGPL-2.0
-
-
- lxc
- 2.0.8
- lxc aims to use these new functionnalities to provide an userspace container object
- GPL-2.0
-
-
- lxd
- git
- "LXD is a container ""hypervisor"" and a new user experience for LXC Specifically it's made of three components: - A system-wide daemon (lxd) - A command line client (lxc) - An OpenStack Nova plugin (nova-compute-lxd)"
- Apache-2.0
-
-
- lz4
- 1.7.4
- LZ4 is a very fast lossless compression algorithm providing compression speed at 400 MB/s per core scalable with multi-cores CPU. It also features an extremely fast decoder with speed in multiple GB/s per core typically reaching RAM speed limits on multi-core systems.
- BSD, BSD-2-Clause, GPL-2.0
-
-
- lzo
- 2.10
- Lossless data compression library.
- GPL-2.0
-
-
- lzop
- 1.03
- lzop is a compression utility which is designed to be a companion to gzip. \nIt is based on the LZO data compression library and its main advantages over \ngzip are much higher compression and decompression speed at the cost of some \ncompression ratio. The lzop compression utility was designed with the goals \nof reliability speed portability and with reasonable drop-in compatibility \nto gzip.
- GPL-2.0
-
-
- m4
- 1.4.18
- GNU m4 is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible although it has some extensions (for example handling more than 9 positional parameters to macros). GNU M4 also has built-in functions for including files running shell commands doing arithmetic etc.
- GPL-3.0
-
-
- make
- 4.2.1
- Make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. Make gets its knowledge of how to build your program from a file called the makefile which lists each of the non-source files and how to compute it from other files.
- GPL-3.0, LGPL-2.0
-
-
- makedepend
- 1.0.5
- The makedepend program reads each sourcefile in sequence and parses it like a C-preprocessor processing all #include #define #undef #ifdef #ifndef #endif #if #elif and #else directives so that it can correctly tell which #include directives would be used in a compilation. Any #include directives can reference files having other #include directives and parsing will occur in these files as well.
- MIT
-
-
- makedevs
- 1.0.1
- Tool for creating device nodes.
- GPL-2.0
-
-
- mklibs
- 0.1.43
- mklibs produces cut-down shared libraries that contain only the routines required by a particular set of executables.
- GPL-2.0
-
-
- modemmanager
- 1.7.991
- ModemManager is a DBus-activated daemon which controls mobile broadband (2G/3G/4G) devices and connections
- GPL-2.0, LGPL-2.1
-
-
- mokutil
- 0.3.0
- The utility to manipulate machines owner keys which managed in shim.
- GPL-3.0
-
-
- mozjs
- 17.0.0
- SpiderMonkey is Mozilla's JavaScript engine written in C/C++.
- MPL-2.0
-
-
- mpfr
- 3.1.5
- C library for multiple-precision floating-point computations with exact rounding.
- GPL-3.0, LGPL-3.0
-
-
- mtools
- 4.0.18
- Mtools is a collection of utilities to access MS-DOS disks from GNU and Unix without mounting them.
- GPL-3.0
-
-
- nasm
- 2.13.01
- General-purpose x86 assembler.
- BSD-2-Clause
-
-
- ncurses
- 6.0
- SVr4 and XSI-Curses compatible curses library and terminfo tools including tic infocmp captoinfo. Supports color multiple highlights forms-drawing characters and automatic recognition of keypad and function-key sequences. Extensions include resizable windows and mouse support on both xterm and Linux console using the gpm library.
- MIT
-
-
- net-snmp
- 5.7.3
- Various tools relating to the Simple Network Management Protocol.
- BSD
-
-
- net-tools
- 1.60-26
- A collection of programs that form the base set of the NET-3 networking distribution for the Linux operating system
- GPL-2.0
-
-
- netbase
- 5.4
- This package provides the necessary infrastructure for basic TCP/IP based networking
- GPL-2.0
-
-
- netcat-openbsd
- 1.105
- A simple Unix utility which reads and writes data across network connections using TCP or UDP protocol. It is designed to be a reliable 'back-end' tool that can be used directly or easily driven by other programs and scripts. At the same time it is a feature-rich network debugging and exploration tool since it can create almost any kind of connection you would need and has several interesting built-in capabilities.
- BSD-3-Clause
-
-
- netcf
- 0.2.8
- netcf is a cross-platform network configuration library.
- LGPL-2.1
-
-
- nettle
- 3.3
- A low level cryptographic library.
- LGPL-3.0, GPL-2.0
-
-
- networkmanager
- 1.10.10
- NetworkManager.
- GPL-2.0
-
-
- nfv-init
- 1.0
- Enea service expected to be run after cloud-init
- Enea
-
-
- nfv-installer
- 1.0
- Enea NFV Access installer
- Enea
-
-
- nfva-cfgtool
- 1.0
- Command line tool to for accessing the Enea NFV Access install configuration json file
- Enea
-
-
- nfva-hotfixes
- 1.0
- Different hotfixes
- Enea
-
-
- nfva-startup
- 1.0
- Service that configures the network according to installer settings
- Enea
-
-
- nodejs
- 8.4.0
- nodeJS Evented I/O for V8 JavaScript
- MIT, BSD, Artistic-2.0
-
-
- notary
- 0.4.2
- Notary is a Docker project that allows anyone to have trust over arbitrary collections of data
- Apache-2.0
-
-
- nspr
- 4.16
- Netscape Portable Runtime Library.
- GPL-2.0, MPL-2.0, LGPL-2.1
-
-
- nss
- 3.31.1
- Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3 TLS PKCS 5 PKCS 7 PKCS 11 PKCS 12 S/MIME X.509 v3 certificates and other security standards.
- MPL-2.0, GPL-2.0, MPL-2.0, LGPL-2.1
-
-
- ntp-user-stub
- 1.0
- The NTP user/group were added in previous NFVA releases and are needed for OSTree upgrades to ensure backwards compatibility.
- Enea
-
-
- numactl
- 2.0.11
- Simple NUMA policy support. It consists of a numactl program to run other programs with a specific NUMA policy and a libnuma to do allocations with NUMA policy in applications.
- GPL-2.0, LGPL-2.1
-
-
- onig
- 5.9.6
- Regular expressions library. The characteristics of this library is that different character encoding for every regular expression object can be specified.
- BSD
-
-
- openipmi
- 2.0.24
- OpenIPMI is an effort to create a full-function IPMI system to allow full access to all IPMI information on a server and to abstract it to a level that will make it easy to use
- GPL-2.0, LGPL-2.1, BSD
-
-
- openjdk-8
- 102b14
- Java runtime based upon the OpenJDK Project
- GPL-2.0-with-classpath-exception
-
-
- openssh
- 7.5p1
- Secure rlogin/rsh/rcp/telnet replacement (OpenSSH) Ssh (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine.
- BSD
-
-
- openssl
- 1.0.2o
- Secure Socket Layer (SSL) binary and related cryptographic tools.
- OpenSSL
-
-
- openvswitch
- 2.9
- Open vSwitch is a production quality multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension while still supporting standard management interfaces and protocols (e.g. NetFlow sFlow SPAN RSPAN CLI LACP 802.1ag)
- Apache-2.0
-
-
- opkg-utils
- 0.3.5
- Additional utilities for the opkg package manager.
- GPL-2.0
-
-
- oro
- 2.0.8
- Perl5-compatible regular expressions library for Java
- Apache-2.0
-
-
- os-release
- 1.0
- The /etc/os-release file contains operating system identification data.
- MIT
-
-
- ostree-initrd
- 3
- Extremely basic live image init script.
- MIT
-
-
- ostree-rw
- 1.0
- Enea bash script to make current ostree hash writable
- Enea
-
-
- ostree
- v2018.7
- Tool for managing bootable immutable versioned filesystem trees.
- LGPL-2.0
-
-
- packagegroup-core-boot
- 1.0
- The minimal set of packages required to boot the system
- MIT
-
-
- packagegroup-core-ssh-openssh
- 1.0
- OpenSSH SSH client/server.
- MIT
-
-
- packagegroup-efi-secure-boot
- 1.0
- EFI Secure Boot packages for secure-environment.
- MIT
-
-
- packagegroup-enea-telemetry
- 1.0
- Packages for Telemetry.
- MIT
-
-
- packagegroup-enea-virtualization-4gusb-modems
- 1.0
- Packagegroup for 4G usb modems.
- MIT
-
-
- packagegroup-enea-virtualization-docker
- 1.0
- Packagegroup for Docker.
- MIT
-
-
- packagegroup-enea-virtualization-dpdk
- 1.0
- Packagegroup for DPDK.
- MIT
-
-
- packagegroup-enea-virtualization-guest
- 1.0
- This package group includes packages and packagegroups specific to the guest side of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-virtualization-host
- 1.0
- This package group includes packages and packagegroups specific to the host side of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-virtualization-libvirt
- 1.0
- Package group for libvirt.
- MIT
-
-
- packagegroup-enea-virtualization-lxc
- 1.0
- Packagegroup for LXC.
- MIT
-
-
- packagegroup-enea-virtualization-lxd
- 1.0
- Packagegroup for LXD.
- MIT
-
-
- packagegroup-enea-virtualization-ovs
- 1.0
- Packagegroup for Open vSwitch.
- MIT
-
-
- packagegroup-enea-virtualization-qemu
- 1.0
- Packagegroup for QEMU.
- MIT
-
-
- packagegroup-enea-virtualization
- 1.0
- This packagegroup includes packages and packagegroups required for both host and guest images of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-wifi
- 1.0
- This package group includes packages and packagegroups that enable WiFi connectivity in the Enea NFV Access platform
- MIT
-
-
- pango
- 1.40.6
- Pango is a library for laying out and rendering of text with an emphasis on internationalization. Pango can be used anywhere that text layout is needed though most of the work on Pango so far has been done in the context of the GTK+ widget toolkit. Pango forms the core of text and font handling for GTK+-2.x.
- LGPL-2.0
-
-
- parted
- 3.2
- Disk partition editing/resizing utility.
- GPL-3.0
-
-
- partrt
- 1.1
- partrt is a tool for dividing a SMP Linux system into a real time domain and a non-real time domain.
- BSD
-
-
- pciutils
- 3.5.5
- The PCI Utilities package contains a library for portable access to PCI bus configuration space and several utilities based on this library.
- GPL-2.0
-
-
- perl
- 5.24.1
- Perl scripting language.
- Artistic-1.0, GPL-1.0
-
-
- pigz
- 2.3.4
- pigz which stands for parallel implementation of gzip is a fully functional replacement for gzip that exploits multiple processors and multiple cores to the hilt when compressing data. pigz was written by Mark Adler and uses the zlib and pthread libraries.
- Zlib, Apache-2.0
-
-
- pixman
- 0.34.0
- Pixman provides a library for manipulating pixel regions -- a set of Y-X banded rectangles image compositing using the Porter/Duff model and implicit mask generation for geometric primitives including trapezoids triangles and rectangles.
- MIT, PD
-
-
- pkgconfig
- 0.29.2
- pkg-config is a helper tool used when compiling applications and libraries. It helps determined the correct compiler/link options. It is also language-agnostic.
- GPL-2.0
-
-
- pm-utils
- 1.4.1
- Simple shell command line tools to suspend and hibernate.
- GPL-2.0
-
-
- polkit
- 0.113
- The polkit package is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes.
- LGPL-2.0
-
-
- popt
- 1.16
- Library for parsing command line options.
- MIT
-
-
- prelink
- 1.0
- The prelink package contains a utility which modifies ELF shared libraries and executables so that far fewer relocations need to be resolved at runtime and thus programs come up faster.
- GPL-2.0
-
-
- procps
- 3.3.12
- Procps contains a set of system utilities that provide system information about processes using the /proc filesystem. The package includes the programs ps top vmstat w kill and skill.
- GPL-2.0, LGPL-2.0
-
-
- pseudo
- 1.8.2
- Pseudo gives fake root capabilities to a normal user.
- LGPL-2.1
-
-
- ptest-runner
- 2.1
- The ptest-runner2 package installs a ptest-runner program which loops through all installed ptest test suites and runs them in sequence.
- GPL-2.0
-
-
- python-asn1crypto
- 0.23.0
- Python binding to the Networking and Cryptography (NaCl) library
- Apache-2.0
-
-
- python-certifi
- 2017.7.27.1
- This installable Python package contains a CA Bundle that you can reference in your Python code. This is useful for verifying HTTP requests for example. This is the same CA Bundle which ships with the Requests codebase and is derived from Mozilla Firefox's canonical set.
- ISC
-
-
- python-cffi
- 1.11.2
- Foreign Function Interface for Python calling C code.
- MIT
-
-
- python-chardet
- 3.0.4
- Universal encoding detector for Python 2 and 3.
- LGPL-2.1
-
-
- python-cryptography-vectors
- 2.0.3
- Test vectors for the cryptography package..
- Apache-2.0, BSD
-
-
- python-cryptography
- 2.0.3
- Provides cryptographic recipes and primitives to python developers.
- Apache-2.0, BSD
-
-
- python-cython
- 0.27.1
- Cython is a language specially designed for writing Python extension modules. It's designed to bridge the gap between the nice high-level easy-to-use world of Python and the messy low-level world of C.
- Apache-2.0
-
-
- python-enum34
- 1.1.6
- backport of Python 3.4's enum package.
- BSD-3-Clause
-
-
- python-functools32
- 3.2.3-2
- Backport of the functools module from Python 3.2.3 for use on 2.7 and PyPy..
- Python-2.0
-
-
- python-futures
- 3.0.5
- The concurrent.futures module provides a high-level interface for asynchronously executing callables.
- BSD
-
-
- python-idna
- 2.6
- Internationalised Domain Names in Applications.
- BSD-3-Clause, Python-2.0, Unicode
-
-
- python-ipaddress
- 1.0.18
- Python 3.3+'s ipaddress for Python 2.6 2.7 3.2..
- Python-2.0
-
-
- python-iso8601
- 0.1.12
- Simple module to parse ISO 8601 dates.
- MIT
-
-
- python-jsonpatch
- 1.16
- Appling JSON patches in Python 2.6+ and 3.x.
- BSD
-
-
- python-jsonpointer
- 1.12
- Resolve JSON Pointers in Python.
- BSD
-
-
- python-jsonschema
- 2.6.0
- An implementation of JSON Schema validation for Python.
- MIT
-
-
- python-m2crypto
- 0.26.4
- A Python crypto and SSL toolkit.
- BSD
-
-
- python-ndg-httpsclient
- 0.4.3
- Provides enhanced HTTPS support for httplib and urllib2 using PyOpenSSL
- BSD
-
-
- python-netaddr
- 0.7.19
- A network address manipulation library for Python..
- BSD
-
-
- python-netifaces
- 0.10.6
- Portable network interface information.
- MIT
-
-
- python-pip
- 9.0.1
- PIP is a tool for installing and managing Python packages.
- MIT, LGPL-2.1
-
-
- python-pretend
- 1.0.8
- A library for stubbing in Python.
- BSD
-
-
- python-prettytable
- 0.7.2
- Python library for displaying tabular data in a ASCII table format.
- BSD
-
-
- python-psutil
- 5.3.1
- A cross-platform process and system utilities module for Python.
- BSD
-
-
- python-py
- 1.4.34
- Library with cross-python path ini-parsing io code log facilities.
- MIT
-
-
- python-pyasn1
- 0.3.6
- Python library implementing ASN.1 types..
- BSD-2-Clause
-
-
- python-pycparser
- 2.18
- Parser of the C language written in pure Python.
- BSD-3-Clause
-
-
- python-pyopenssl
- 17.3.0
- Simple Python wrapper around the OpenSSL library.
- Apache-2.0
-
-
- python-pysocks
- 1.6.7
- A Python SOCKS client module
- BSD
-
-
- python-pytest-runner
- 2.12.1
- Invoke py.test as distutils command with dependency resolution.
- MIT
-
-
- python-pytest
- 3.2.2
- Simple powerful teting with python.
- MIT
-
-
- python-pyyaml
- 3.11
- YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. . PyYAML features a complete YAML 1.1 parser Unicode support pickle support capable extension API and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. . PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistance.
- MIT
-
-
- python-requests
- 2.18.4
- Python HTTP for Humans.
- Apache-2.0
-
-
- python-rfc3987
- 1.3.7
- Parsing and validation of URIs (RFC 3986) and IRIs (RFC 3987).
- GPL-3.0
-
-
- python-setuptools-scm
- 1.15.6
- the blessed package to manage your versions by scm tags.
- MIT
-
-
- python-setuptools
- 36.2.7
- Download build install upgrade and uninstall Python packages.
- MIT
-
-
- python-six
- 1.11.0
- Python 2 and 3 compatibility library.
- MIT
-
-
- python-strict-rfc3339
- 0.7
- Strict simple lightweight RFC3339 function.s.
- GPL-3.0
-
-
- python-typing
- 3.6.2
- Simple Python module defined by PEP 484..
- Python-2.0
-
-
- python-urllib3
- 1.22
- Python HTTP library with thread-safe connection pooling file post support sanity friendly and more.
- MIT
-
-
- python-vcversioner
- 2.16.0.0
- Python vcversioner automagically update the project's version.
- ISC
-
-
- python
- 2.7.13
- The Python Programming Language.
- Python-2.0
-
-
- python3-netifaces
- 0.10.6
- Portable network interface information.
- MIT
-
-
- python3-pip
- 9.0.1
- The PyPA recommended tool for installing Python packages.
- MIT
-
-
- python3-setuptools
- 36.2.7
- Download build install upgrade and uninstall Python packages.
- MIT
-
-
- python3-six
- 1.10.0
- Python 2 and 3 compatibility library.
- MIT
-
-
- python3-twisted
- 13.2.0
- Twisted is an event-driven networking framework written in Python and licensed under the LGPL. Twisted supports TCP UDP SSL/TLS multicast Unix sockets a large number of protocols (including HTTP NNTP IMAP SSH IRC FTP and others) and much more.
- MIT
-
-
- python3-zopeinterface
- 4.4.3
- Interface definitions for Zope products.
- ZPL-2.1
-
-
- python3
- 3.5.3
- The Python Programming Language.
- Python-2.0
-
-
- qemu-helper
- 1.0
- Helper utilities needed by the runqemu script.
- GPL-2.0
-
-
- qemu
- 2.11.1
- Fast open source processor emulator.
- GPL-2.0, LGPL-2.1
-
-
- qemuwrapper
- 1.0
- QEMU wrapper script.
- MIT
-
-
- quilt
- 0.65
- Tool for working with series of patches.
- GPL-2.0
-
-
- randrproto
- 1.5.0
- This package provides the wire protocol for the X Resize Rotate and Reflect extension. This extension provides the ability to resize rotate and reflect the root window of a screen.
- MIT
-
-
- readline
- 7.0
- The GNU Readline library provides a set of functions for use by applications that allow users to edit command lines as they are typed in. Both Emacs and vi editing modes are available. The Readline library includes additional functions to maintain a list of previously-entered command lines to recall and perhaps reedit those lines and perform csh-like history expansion on previous commands.
- GPL-3.0
-
-
- regexp
- 1.5
- Java Regular Expression package
- Apache-2.0
-
-
- renderproto
- 0.11.1
- This package provides the wire protocol for the X Rendering extension. This is the basis the image composition within the X window system.
- MIT
-
-
- rhino
- 1.7r4
- Lexical analyzer generator for Java
- MPL-2.0
-
-
- rpm
- 4.13.90
- The RPM Package Manager (RPM) is a powerful command line driven package management system capable of installing uninstalling verifying querying and updating software packages. Each software package consists of an archive of files along with information about the package like its version a description etc.
- GPL-2.0
-
-
- rrdtool
- 1.6.0
- High performance data logging and graphing system for time series data.
- GPL-2.0
-
-
- rsync
- 3.1.3
- File synchronization tool.
- GPL-3.0
-
-
- run-postinsts
- 1.0
- Runs postinstall scripts on first boot of the target device.
- MIT
-
-
- runc-docker
- 1.0.0-rc3
- runc is a CLI tool for spawning and running containers according to the OCI specification.
- Apache-2.0
-
-
- sbsigntool
- 0.6
- Utilities for signing UEFI binaries for use with secure boot.
- GPL-3.0
-
-
- sed
- 4.2.2
- Stream EDitor (text filtering utility).
- GPL-3.0
-
-
- seloader
- 0.4.6
- The SELoader is designed to authenticate the non-PE files such as grub configuration initrd grub modules which cannot be verified by the MOK Verify Protocol registered by shim loader. In order to conveniently authenticate the PE file with gBS->LoadImage() and gBS->StartImage() the SELoader hooks EFI Security2 Architectural Protocol and employs MOK Verify Protocol to verify the PE file. If only UEFI Secure Boot is enabled the SELoader just simplily calls gBS->LoadImage() and gBS->StartImage() to allow BIOS to verify PE file. The SELoader publishes MOK2 Verify Protocol which provides a flexible interface to allow the bootloader to verify the file file buffer or memory buffer without knowing the file format.
- BSD-3-Clause
-
-
- servlet2.3
- 4.1.37
- Servlet API 2.3 (from Tomcat 4.1)
- Apache-2.0
-
-
- shadow-securetty
- 4.2.1
- Provider of the machine specific securetty file.
- MIT
-
-
- shadow-sysroot
- 4.2.1
- Shadow utils requirements for useradd.bbclass.
- BSD, Artistic-1.0
-
-
- shadow
- 4.2.1
- Tools to change and administer password and group data.
- BSD, Artistic-1.0
-
-
- shared-mime-info
- 1.8
- Shared MIME type database and specification.
- LGPL-2.0
-
-
- shim
- 12
- shim is a trivial EFI application that when run attempts to open and execute another application. It will initially attempt to do this via the standard EFI LoadImage() and StartImage() calls. If these fail (because secure boot is enabled and the binary is not signed with an appropriate key for instance) it will then validate the binary against a built-in certificate. If this succeeds and if the binary or signing key are not blacklisted then shim will relocate and execute the binary.
- BSD-2-Clause
-
-
- simpleproxy
- 1.0
- Simpleproxy.
- GPL-2.0
-
-
- slang
- 2.3.1a
- S-Lang is an interpreted language and a programming library. The S-Lang language was designed so that it can be easily embedded into a program to provide the program with a powerful extension language. The S-Lang library provided in this package provides the S-Lang extension language. S-Lang's syntax resembles C which makes it easy to recode S-Lang procedures in C if you need to.
- GPL-2.0
-
-
- sqlite3
- 3.20.0
- Embeddable SQL database engine.
- PD
-
-
- squashfs-tools
- 4.3
- Tools for manipulating SquashFS filesystems.
- GPL-2.0, PD
-
-
- sshpass
- 1.06
- Tool for non-interactivly performing ssh password authentication
- GPL-2.0
-
-
- swig
- 3.0.12
- SWIG - Simplified Wrapper and Interface Generator.
- BSD, GPL-3.0
-
-
- sysfsutils
- 2.1.0
- Tools for working with the sysfs virtual filesystem. The tool 'systool' can query devices by bus class and topology.
- GPL-2.0, LGPL-2.1
-
-
- sysklogd
- 1.5.1
- The sysklogd package implements two system log daemons: syslogd klogd
- GPL-2.0, BSD
-
-
- syslinux
- 6.03
- Multi-purpose linux bootloader.
- GPL-2.0
-
-
- systemd-boot
- 234
- systemd is a system and service 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.
- GPL-2.0, LGPL-2.1
-
-
- systemd-compat-units
- 1.0
- Enhances systemd compatilibity with existing SysVinit scripts.
- MIT
-
-
- systemd-serialgetty
- 1.0
- Serial terminal support for systemd.
- GPL-2.0
-
-
- systemd-systemctl
- 1.0
- Wrapper for enabling systemd services.
- MIT
-
-
- systemd
- 234
- systemd is a system and service 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.
- GPL-2.0, LGPL-2.1
-
-
- tar
- 1.29
- GNU tar saves many files together into a single tape or disk archive and can restore individual files from the archive.
- GPL-3.0
-
-
- tcl
- 8.6.7
- Tool Command Language.
- tcl, BSD-3-Clause
-
-
- tcpdump
- 4.9.2
- A sophisticated network protocol analyzer.
- BSD
-
-
- texinfo-dummy
- 1.0
- Fake version of the texinfo utility suite.
- MIT
-
-
- thin-provisioning-tools
- 0.6.3
- A suite of tools for manipulating the metadata of the dm-thin device-mapper target.
- GPL-3.0
-
-
- tunctl
- 1.5
- Tool for controlling the Linux TUN/TAP driver.
- GPL-2.0
-
-
- tzcode
- 2018c
- tzcode timezone zoneinfo utils -- zic zdump tzselect.
- PD, BSD, BSD-3-Clause
-
-
- tzdata
- 2018c
- Timezone data.
- PD, BSD, BSD-3-Clause
-
-
- udev-extraconf
- 1.1
- Extra machine specific configuration files for udev specifically blacklist information.
- MIT
-
-
- unifdef
- 2.11
- Selectively remove #ifdef statements from sources.
- BSD-2-Clause
-
-
- unzip
- 6.0
- Utilities for extracting and viewing files in .zip archives.
- BSD-3-Clause
-
-
- update-rc.d
- 0.7
- update-rc.d is a utility that allows the management of symlinks to the initscripts in the /etc/rcN.d directory structure.
- GPL-2.0
-
-
- usb-modeswitch-data
- 20170205
- Data files for usbmodeswitch.
- GPL-2.0
-
-
- usb-modeswitch
- 2.5.0
- A mode switching tool for controlling 'flip flop' (multiple device) USB gear.
- GPL-2.0
-
-
- usbutils
- 013
- Contains the lsusb utility for inspecting the devices connected to the USB bus.
- GPL-2.0, GPL-3.0
-
-
- util-linux
- 2.30
- Util-linux includes a suite of basic system administration utilities commonly found on most Linux systems. Some of the more important utilities include disk partitioning kernel message management filesystem creation and system login.
- GPL-2.0, LGPL-2.1, BSD
-
-
- util-macros
- 1.19.1
- M4 autotools macros used by various X.org programs.
- MIT
-
-
- v86d
- 0.1.10
- User support binary for the uvesafb kernel module.
- GPL-2.0
-
-
- vala
- 0.36.4
- Vala is a C#-like language dedicated to ease GObject programming. Vala compiles to plain C and has no runtime environment nor penalities whatsoever.
- LGPL-2.1
-
-
- volatile-binds
- 1.0
- Volatile bind mount setup and configuration for read-only-rootfs
- MIT
-
-
- web-installer-backend
- 0.1
- Web installer go server
- Enea, BSD-3-Clause
-
-
- web-installer-frontend
- 0.1
- Web installer post-install application
- Enea, Apache-2.0, BSD, BSD-2-Clause, BSD-3-Clause, CC-BY-4.0, ISC, MIT, Zlib
-
-
- which
- 2.21
- Which is a utility that prints out the full path of the executables that bash(1) would execute when the passed program names would have been entered on the shell prompt. It does this by using the exact same algorithm as bash.
- GPL-3.0
-
-
- wireless-regdb
- 2020.11.20
- Wireless Central Regulatory Domain Database.
- ISC
-
-
- wpa-supplicant
- 2.6
- Client for Wi-Fi Protected Access (WPA).
- BSD
-
-
- xalan-j
- 2.7.1
- Java XSLT processor
- Apache-2.0
-
-
- xcb-proto
- 1.12
- Function prototypes for the X protocol C-language Binding (XCB). XCB is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
- MIT
-
-
- xerces-j
- 2.11.0
- Reference implementation of XNI the Xerces Native Interface and also a fully conforming XML Schema processor.
- Apache-2.0
-
-
- xextproto
- 7.3.0
- This package provides the wire protocol for several X extensions. These protocol extensions include DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. In addition a small set of utility functions are also available.
- MIT
-
-
- xkeyboard-config
- 2.21
- The non-arch keyboard configuration database for X Window. The goal is to provide the consistent well-structured frequently released open source of X keyboard configuration data for X Window System implementations. The project is targeted to XKB-based systems.
- MIT
-
-
- xml-commons-resolver1.1
- 1.2
- Library to resolve various public or system identifiers into accessible URLs (Java)
- Apache-2.0
-
-
- xproto
- 7.0.31
- This package provides the basic headers for the X Window System.
- MIT
-
-
- xtrans
- 1.3.5
- The X Transport Interface is intended to combine all system and transport specific code into a single place. This API should be used by all libraries clients and servers of the X Window System. Use of this API should allow the addition of new types of transports and support for new platforms without making any changes to the source except in the X Transport Interface code.
- MIT
-
-
- xz
- 5.2.3
- Utilities for managing LZMA compressed files.
- GPL-2.0, GPL-3.0-with-autoconf-exception, LGPL-2.1, PD
-
-
- yajl
- 2.1.0
- YAJL is a small event-driven (SAX-style) JSON parser written in ANSI C and a small validating JSON generator.
- ISC
-
-
- zip
- 3.0
- Compressor/archiver for creating and modifying .zip files.
- BSD-3-Clause
-
-
- zisofs-tools
- 1.0.8
- Utilities for creating compressed CD-ROM filesystems.
- GPL-2.0
-
-
- zlib
- 1.2.11
- Zlib is a general-purpose patent-free lossless data compression library which is used by many different programs.
- Zlib
-
-
-
-
-
-
- Open Source Licenses
-
-AFL-2.0
-
-
-The Academic Free License
- v. 2.0
-
-This Academic Free License (the "License") applies to any original work of authorship
-(the "Original Work") whose owner (the "Licensor") has placed the following notice
-immediately following the copyright notice for the Original Work:
-Licensed under the Academic Free License version 2.0
-
-1) Grant of Copyright License. Licensor hereby grants You a world-wide, royalty-free,
-non-exclusive, perpetual, sublicenseable license to do the following:
-a) to reproduce the Original Work in copies;
-
-b) to prepare derivative works ("Derivative Works") based upon the Original Work;
-
-c) to distribute copies of the Original Work and Derivative Works to the public;
-
-d) to perform the Original Work publicly; and
-
-e) to display the Original Work publicly.
-
-2) Grant of Patent License. Licensor hereby grants You a world-wide, royalty-free,
-non-exclusive, perpetual, sublicenseable license, under patent claims owned or
-controlled by the Licensor that are embodied in the Original Work as furnished by the
-Licensor, to make, use, sell and offer for sale the Original Work and Derivative
-Works.
-
-3) Grant of Source Code License. The term "Source Code" means the preferred form of
-the Original Work for making modifications to it and all available documentation
-describing how to modify the Original Work. Licensor hereby agrees to provide a
-machine-readable copy of the Source Code of the Original Work along with each copy of
-the Original Work that Licensor distributes. Licensor reserves the right to satisfy
-this obligation by placing a machine-readable copy of the Source Code in an
-information repository reasonably calculated to permit inexpensive and convenient
-access by You for as long as Licensor continues to distribute the Original Work, and
-by publishing the address of that information repository in a notice immediately
-following the copyright notice that applies to the Original Work.
-
-4) Exclusions From License Grant. Neither the names of Licensor, nor the names of any
-contributors to the Original Work, nor any of their trademarks or service marks, may
-be used to endorse or promote products derived from this Original Work without express
-prior written permission of the Licensor. Nothing in this License shall be deemed to
-grant any rights to trademarks, copyrights, patents, trade secrets or any other
-intellectual property of Licensor except as expressly stated herein. No patent
-license is granted to make, use, sell or offer to sell embodiments of any patent
-claims other than the licensed claims defined in Section 2. No right is granted to
-the trademarks of Licensor even if such marks are included in the Original Work.
-Nothing in this License shall be interpreted to prohibit Licensor from licensing under
-different terms from this License any Original Work that Licensor otherwise would have
-a right to license.
-
-5) This section intentionally omitted.
-
-6) Attribution Rights. You must retain, in the Source Code of any Derivative Works
-that You create, all copyright, patent or trademark notices from the Source Code of
-the Original Work, as well as any notices of licensing and any descriptive text
-identified therein as an "Attribution Notice." You must cause the Source Code for any
-Derivative Works that You create to carry a prominent Attribution Notice reasonably
-calculated to inform recipients that You have modified the Original Work.
-
-7) Warranty of Provenance and Disclaimer of Warranty. Licensor warrants that the
-copyright in and to the Original Work and the patent rights granted herein by Licensor
-are owned by the Licensor or are sublicensed to You under the terms of this License
-with the permission of the contributor(s) of those copyrights and patent rights.
-Except as expressly stated in the immediately proceeding sentence, the Original Work
-is provided under this License on an "AS IS" BASIS and WITHOUT WARRANTY, either
-express or implied, including, without limitation, the warranties of NON-INFRINGEMENT,
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
-QUALITY OF THE ORIGINAL WORK IS WITH YOU. This DISCLAIMER OF WARRANTY constitutes an
-essential part of this License. No license to Original Work is granted hereunder
-except under this disclaimer.
-
-8) Limitation of Liability. Under no circumstances and under no legal theory, whether
-in tort (including negligence), contract, or otherwise, shall the Licensor be liable
-to any person for any direct, indirect, special, incidental, or consequential damages
-of any character arising as a result of this License or the use of the Original Work
-including, without limitation, damages for loss of goodwill, work stoppage, computer
-failure or malfunction, or any and all other commercial damages or losses. This
-limitation of liability shall not apply to liability for death or personal injury
-resulting from Licensor`s negligence to the extent applicable law prohibits such
-limitation. Some jurisdictions do not allow the exclusion or limitation of incidental
-or consequential damages, so this exclusion and limitation may not apply to You.
-
-9) Acceptance and Termination. If You distribute copies of the Original Work or a
-Derivative Work, You must make a reasonable effort under the circumstances to obtain
-the express assent of recipients to the terms of this License. Nothing else but this
-License (or another written agreement between Licensor and You) grants You permission
-to create Derivative Works based upon the Original Work or to exercise any of the
-rights granted in Section 1 herein, and any attempt to do so except under the terms of
-this License (or another written agreement between Licensor and You) is expressly
-prohibited by U.S. copyright law, the equivalent laws of other countries, and by
-international treaty. Therefore, by exercising any of the rights granted to You in
-Section 1 herein, You indicate Your acceptance of this License and all of its terms
-and conditions.
-
-10) Termination for Patent Action. This License shall terminate automatically and You
-may no longer exercise any of the rights granted to You by this License as of the date
-You commence an action, including a cross-claim or counterclaim, for patent
-infringement (i) against Licensor with respect to a patent applicable to software or
-(ii) against any entity with respect to a patent applicable to the Original Work (but
-excluding combinations of the Original Work with other software or hardware).
-
-11) Jurisdiction, Venue and Governing Law. Any action or suit relating to this License
-may be brought only in the courts of a jurisdiction wherein the Licensor resides or in
-which Licensor conducts its primary business, and under the laws of that jurisdiction
-excluding its conflict-of-law provisions. The application of the United Nations
-Convention on Contracts for the International Sale of Goods is expressly excluded.
-Any use of the Original Work outside the scope of this License or after its
-termination shall be subject to the requirements and penalties of the U.S. Copyright
-Act, 17 U.S.C. ¤ 101 et seq., the equivalent laws of other countries, and
-international treaty. This section shall survive the termination of this License.
-
-12) Attorneys Fees. In any action to enforce the terms of this License or seeking
-damages relating thereto, the prevailing party shall be entitled to recover its costs
-and expenses, including, without limitation, reasonable attorneys` fees and costs
-incurred in connection with such action, including any appeal of such action. This
-section shall survive the termination of this License.
-
-13) Miscellaneous. This License represents the complete agreement concerning the
-subject matter hereof. If any provision of this License is held to be unenforceable,
-such provision shall be reformed only to the extent necessary to make it enforceable.
-
-14) Definition of "You" in This License. "You" throughout this License, whether in
-upper or lower case, means an individual or a legal entity exercising rights under,
-and complying with all of the terms of, this License. For legal entities, "You"
-includes any entity that controls, is controlled by, or is under common control with
-you. For purposes of this definition, "control" means (i) the power, direct or
-indirect, to cause the direction or management of such entity, whether by contract or
-otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares,
-or (iii) beneficial ownership of such entity.
-
-15) Right to Use. You may use the Original Work in all ways not otherwise restricted
-or conditioned by this License or by law, and Licensor promises not to interfere with
-or be responsible for such uses by You.
-
-This license is Copyright (C) 2003 Lawrence E. Rosen. All rights reserved.
-Permission is hereby granted to copy and distribute this license without modification.
-This license may not be modified without the express written permission of its
-copyright owner.
-
-
-
-
-AMD
-
-� 2005 Advanced Micro Devices, Inc. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that existing copyright notices
-are retained in all copies, this notice is included verbatim in any
-distributions, and the terms and conditions hererin are met.
-
-Use of the this software manifests acceptance of the terms of this
-license by performance.
-
-The name of Advanced Micro Devices, Inc. may not be used to endorse or
-promote products derived from this software without specific prior
-written permission.
-
-THIS SOFTWARE IS PROVIDED BY ADVANCED MICRO DEVICES, INC. "AS IS" AND ANY
-EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
-PURPOSE AND NON-INFRINGEMENT, OR THOSE ARISING FROM CUSTOM OF TRADE OR
-COURSE OF USAGE ARE DISCLAIMED.
-
-IN NO EVENT SHALL ADVANCED MICRO DEVICES, INC. BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED, AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE ITS DOCUMENTATION OR ANY DERIVATIVES
-THEREOF, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BY USING THIS
-SOFTWARE WITHOUT CHARGE, YOU ACCEPT THIS ALLOCATION OF RISK. THIS
-DISCLAIMER OF LIABILITY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE.
-ADVANCED MICRO DEVICES, INC. HAS NO OBLIGATION TO PROVIDE MAINTENANCE,
-SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS OF THIS SOFTWARE.
-
-In the redistribution and use of this software, each party shall at all
-times comply with all applicable governmental laws, statutes, ordinances,
-rules, regulations, orders, and other requirements, including without
-limitation such governmental requirements applicable to environmental
-protection, health, safety, wages, hours, equal employment opportunity,
-nondiscrimination, working conditions, import or export control, and
-transportation. Without limiting the foregoing, each party shall adhere
-to the U.S. Export Administration Regulations (EAR), currently found at
-15 C.F.R. Sections 730 through 744, and, unless properly authorized by
-the U.S. Government, shall not (1) export, re-export or release restricted
-technology, software, or source code to a national of a country in Country
-Groups D:1 or E:1, or (2) export to Country Groups D:1 or E:1 the direct
-product of such technology or software, if such foreign produced direct
-product is subject to national security controls as identified on the
-Commerce Control List (currently found in Supplement 1 to Section 774 of EAR).
-These export requirements shall survive any expiration or termination
-of this agreement.
-
-
-
-Apache-2.0
-
-
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don`t include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
-
-Artistic-1.0
-
-
-The Artistic License
-Preamble
-
-The intent of this document is to state the conditions under which a Package may be
-copied, such that the Copyright Holder maintains some semblance of artistic control
-over the development of the package, while giving the users of the package the right
-to use and distribute the Package in a more-or-less customary fashion, plus the right
-to make reasonable modifications.
-
-Definitions:
-
-"Package" refers to the collection of files distributed by the Copyright Holder, and
-derivatives of that collection of files created through textual modification.
-"Standard Version" refers to such a Package if it has not been modified, or has been
-modified in accordance with the wishes of the Copyright Holder.
-"Copyright Holder" is whoever is named in the copyright or copyrights for the package.
-"You" is you, if you`re thinking about copying or distributing this Package.
-"Reasonable copying fee" is whatever you can justify on the basis of media cost,
-duplication charges, time of people involved, and so on. (You will not be required to
-justify it to the Copyright Holder, but only to the computing community at large as a
-market that must bear the fee.)
-"Freely Available" means that no fee is charged for the item itself, though there may
-be fees involved in handling the item. It also means that recipients of the item may
-redistribute it under the same conditions they received it.
-1. You may make and give away verbatim copies of the source form of the Standard
-Version of this Package without restriction, provided that you duplicate all of the
-original copyright notices and associated disclaimers.
-
-2. You may apply bug fixes, portability fixes and other modifications derived from the
-Public Domain or from the Copyright Holder. A Package modified in such a way shall
-still be considered the Standard Version.
-
-3. You may otherwise modify your copy of this Package in any way, provided that you
-insert a prominent notice in each changed file stating how and when you changed that
-file, and provided that you do at least ONE of the following:
-
-a) place your modifications in the Public Domain or otherwise make them Freely
-Available, such as by posting said modifications to Usenet or an equivalent medium, or
-placing the modifications on a major archive site 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.
-
-4. You may distribute the programs of this Package in object code or executable form,
-provided that you do at least ONE of the following:
-
-a) distribute a Standard Version of the executables and library files, together with
-instructions (in the manual page or equivalent) on where to get the Standard Version.
-
-b) accompany the distribution with the machine-readable source of the Package with
-your modifications.
-
-c) accompany any non-standard executables with their corresponding Standard Version
-executables, giving the non-standard executables non-standard names, and clearly
-documenting the differences in manual pages (or equivalent), together with
-instructions on where to get the Standard Version.
-
-d) make other distribution arrangements with the Copyright Holder.
-
-5. You may charge a reasonable copying fee for any distribution of this Package. You
-may charge any fee you choose for support of this Package. You may not charge a fee
-for this Package itself. However, you may distribute this Package in aggregate with
-other (possibly commercial) programs as part of a larger (possibly commercial)
-software distribution provided that you do not advertise this Package as a product of
-your own.
-
-6. The scripts and library files supplied as input to or produced as output from the
-programs of this Package do not automatically fall under the copyright of this
-Package, but belong to whomever generated them, and may be sold commercially, and may
-be aggregated with this Package.
-
-7. C or perl subroutines supplied by you and linked into this Package shall not be
-considered part of this Package.
-
-8. The name of the Copyright Holder may not be used to endorse or promote products
-derived from this software without specific prior written permission.
-
-9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
-INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS
-FOR A PARTICULAR PURPOSE.
-
-The End
-
-
-
-
-Artistic-2.0
-
-
- The Artistic License 2.0
-
- Copyright (c) 2000-2006, The Perl Foundation.
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-Preamble
-
-This license establishes the terms under which a given free software
-Package may be copied, modified, distributed, and/or redistributed.
-The intent is that the Copyright Holder maintains some artistic
-control over the development of that Package while still keeping the
-Package available as open source and free software.
-
-You are always permitted to make arrangements wholly outside of this
-license directly with the Copyright Holder of a given Package. If the
-terms of this license do not permit the full use that you propose to
-make of the Package, you should contact the Copyright Holder and seek
-a different licensing arrangement.
-
-Definitions
-
- "Copyright Holder" means the individual(s) or organization(s)
- named in the copyright notice for the entire Package.
-
- "Contributor" means any party that has contributed code or other
- material to the Package, in accordance with the Copyright Holder`s
- procedures.
-
- "You" and "your" means any person who would like to copy,
- distribute, or modify the Package.
-
- "Package" means the collection of files distributed by the
- Copyright Holder, and derivatives of that collection and/or of
- those files. A given Package may consist of either the Standard
- Version, or a Modified Version.
-
- "Distribute" means providing a copy of the Package or making it
- accessible to anyone else, or in the case of a company or
- organization, to others outside of your company or organization.
-
- "Distributor Fee" means any fee that you charge for Distributing
- this Package or providing support for this Package to another
- party. It does not mean licensing fees.
-
- "Standard Version" refers to the Package if it has not been
- modified, or has been modified only in ways explicitly requested
- by the Copyright Holder.
-
- "Modified Version" means the Package, if it has been changed, and
- such changes were not explicitly requested by the Copyright
- Holder.
-
- "Original License" means this Artistic License as Distributed with
- the Standard Version of the Package, in its current version or as
- it may be modified by The Perl Foundation in the future.
-
- "Source" form means the source code, documentation source, and
- configuration files for the Package.
-
- "Compiled" form means the compiled bytecode, object code, binary,
- or any other form resulting from mechanical transformation or
- translation of the Source form.
-
-
-Permission for Use and Modification Without Distribution
-
-(1) You are permitted to use the Standard Version and create and use
-Modified Versions for any purpose without restriction, provided that
-you do not Distribute the Modified Version.
-
-
-Permissions for Redistribution of the Standard Version
-
-(2) You may Distribute verbatim copies of the Source form of the
-Standard Version of this Package in any medium without restriction,
-either gratis or for a Distributor Fee, provided that you duplicate
-all of the original copyright notices and associated disclaimers. At
-your discretion, such verbatim copies may or may not include a
-Compiled form of the Package.
-
-(3) You may apply any bug fixes, portability changes, and other
-modifications made available from the Copyright Holder. The resulting
-Package will still be considered the Standard Version, and as such
-will be subject to the Original License.
-
-
-Distribution of Modified Versions of the Package as Source
-
-(4) You may Distribute your Modified Version as Source (either gratis
-or for a Distributor Fee, and with or without a Compiled form of the
-Modified Version) provided that you clearly document how it differs
-from the Standard Version, including, but not limited to, documenting
-any non-standard features, executables, or modules, and provided that
-you do at least ONE of the following:
-
- (a) make the Modified Version available to the Copyright Holder
- of the Standard Version, under the Original License, so that the
- Copyright Holder may include your modifications in the Standard
- Version.
-
- (b) ensure that installation of your Modified Version does not
- prevent the user installing or running the Standard Version. In
- addition, the Modified Version must bear a name that is different
- from the name of the Standard Version.
-
- (c) allow anyone who receives a copy of the Modified Version to
- make the Source form of the Modified Version available to others
- under
-
- (i) the Original License or
-
- (ii) a license that permits the licensee to freely copy,
- modify and redistribute the Modified Version using the same
- licensing terms that apply to the copy that the licensee
- received, and requires that the Source form of the Modified
- Version, and of any works derived from it, be made freely
- available in that license fees are prohibited but Distributor
- Fees are allowed.
-
-
-Distribution of Compiled Forms of the Standard Version
-or Modified Versions without the Source
-
-(5) You may Distribute Compiled forms of the Standard Version without
-the Source, provided that you include complete instructions on how to
-get the Source of the Standard Version. Such instructions must be
-valid at the time of your distribution. If these instructions, at any
-time while you are carrying out such distribution, become invalid, you
-must provide new instructions on demand or cease further distribution.
-If you provide valid instructions or cease distribution within thirty
-days after you become aware that the instructions are invalid, then
-you do not forfeit any of your rights under this license.
-
-(6) You may Distribute a Modified Version in Compiled form without
-the Source, provided that you comply with Section 4 with respect to
-the Source of the Modified Version.
-
-
-Aggregating or Linking the Package
-
-(7) You may aggregate the Package (either the Standard Version or
-Modified Version) with other packages and Distribute the resulting
-aggregation provided that you do not charge a licensing fee for the
-Package. Distributor Fees are permitted, and licensing fees for other
-components in the aggregation are permitted. The terms of this license
-apply to the use and Distribution of the Standard or Modified Versions
-as included in the aggregation.
-
-(8) You are permitted to link Modified and Standard Versions with
-other works, to embed the Package in a larger work of your own, or to
-build stand-alone binary or bytecode versions of applications that
-include the Package, and Distribute the result without restriction,
-provided the result does not expose a direct interface to the Package.
-
-
-Items That are Not Considered Part of a Modified Version
-
-(9) Works (including, but not limited to, modules and scripts) that
-merely extend or make use of the Package, do not, by themselves, cause
-the Package to be a Modified Version. In addition, such works are not
-considered parts of the Package itself, and are not subject to the
-terms of this license.
-
-
-General Provisions
-
-(10) Any use, modification, and distribution of the Standard or
-Modified Versions is governed by this Artistic License. By using,
-modifying or distributing the Package, you accept this license. Do not
-use, modify, or distribute the Package, if you do not accept this
-license.
-
-(11) If your Modified Version has been derived from a Modified
-Version made by someone other than you, you are nevertheless required
-to ensure that your Modified Version complies with the requirements of
-this license.
-
-(12) This license does not grant you the right to use any trademark,
-service mark, tradename, or logo of the Copyright Holder.
-
-(13) This license includes the non-exclusive, worldwide,
-free-of-charge patent license to make, have made, use, offer to sell,
-sell, import and otherwise transfer the Package with respect to any
-patent claims licensable by the Copyright Holder that are necessarily
-infringed by the Package. If you institute patent litigation
-(including a cross-claim or counterclaim) against any party alleging
-that the Package constitutes direct or contributory patent
-infringement, then this Artistic License to you shall terminate on the
-date that such litigation is filed.
-
-(14) Disclaimer of Warranty:
-THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS
-IS` AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
-NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL
-LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL
-BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
-DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-BSD
-
-Copyright (c) The Regents of the University of California.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. Neither the name of the University nor the names of its contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-
-
-BSD-2-Clause
-
-
-The FreeBSD Copyright
-
-Copyright 1992-2010 The FreeBSD Project. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions of source code must retain the above copyright notice, this list of
-conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright notice, this list of
-conditions and the following disclaimer in the documentation and/or other materials
-provided with the distribution.
-THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS`` AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD
-PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-The views and conclusions contained in the software and documentation are those of the
-authors and should not be interpreted as representing official policies, either
-expressed or implied, of the FreeBSD Project.
-
-
-
-
-BSD-3-Clause
-
-
-Copyright (c) <YEAR>, <OWNER>
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions of source code must retain the above copyright notice, this list of
-conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright notice, this list of
-conditions and the following disclaimer in the documentation and/or other materials
-provided with the distribution.
-Neither the name of the <ORGANIZATION> nor the names of its contributors may be
-used to endorse or promote products derived from this software without specific prior
-written permission.
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
-EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
-SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
-TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
-WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGE.
-
-
-
-
-BSD-4-Clause
-
-
-Copyright (c) <year>, <copyright holder>
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. All advertising materials mentioning features or use of this software
- must display the following acknowledgement:
- This product includes software developed by the <organization>.
-4. Neither the name of the <organization> nor the
- names of its contributors may be used to endorse or promote products
- derived from this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY <COPYRIGHT HOLDER> ``AS IS`` AND ANY
-EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
-DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
-ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-BSL-1.0
-
-
-Boost Software License - Version 1.0 - August 17th, 2003
-
-Permission is hereby granted, free of charge, to any person or organization
-obtaining a copy of the software and accompanying documentation covered by
-this license (the "Software") to use, reproduce, display, distribute,
-execute, and transmit the Software, and to prepare derivative works of the
-Software, and to permit third-parties to whom the Software is furnished to
-do so, all subject to the following:
-
-The copyright notices in the Software and this entire statement, including
-the above license grant, this restriction and the following disclaimer,
-must be included in all copies of the Software, in whole or in part, and
-all derivative works of the Software, unless such copies or derivative
-works are solely in the form of machine-executable object code generated by
-a source language processor.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
-SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
-FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
-ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
-DEALINGS IN THE SOFTWARE.
-
-
-
-
-CC-BY-4.0
-
-Attribution 4.0 International
-
-=======================================================================
-
-Creative Commons Corporation ("Creative Commons") is not a law firm and
-does not provide legal services or legal advice. Distribution of
-Creative Commons public licenses does not create a lawyer-client or
-other relationship. Creative Commons makes its licenses and related
-information available on an "as-is" basis. Creative Commons gives no
-warranties regarding its licenses, any material licensed under their
-terms and conditions, or any related information. Creative Commons
-disclaims all liability for damages resulting from their use to the
-fullest extent possible.
-
-Using Creative Commons Public Licenses
-
-Creative Commons public licenses provide a standard set of terms and
-conditions that creators and other rights holders may use to share
-original works of authorship and other material subject to copyright
-and certain other rights specified in the public license below. The
-following considerations are for informational purposes only, are not
-exhaustive, and do not form part of our licenses.
-
- Considerations for licensors: Our public licenses are
- intended for use by those authorized to give the public
- permission to use material in ways otherwise restricted by
- copyright and certain other rights. Our licenses are
- irrevocable. Licensors should read and understand the terms
- and conditions of the license they choose before applying it.
- Licensors should also secure all rights necessary before
- applying our licenses so that the public can reuse the
- material as expected. Licensors should clearly mark any
- material not subject to the license. This includes other CC-
- licensed material, or material used under an exception or
- limitation to copyright. More considerations for licensors:
- wiki.creativecommons.org/Considerations_for_licensors
-
- Considerations for the public: By using one of our public
- licenses, a licensor grants the public permission to use the
- licensed material under specified terms and conditions. If
- the licensor's permission is not necessary for any reason--for
- example, because of any applicable exception or limitation to
- copyright--then that use is not regulated by the license. Our
- licenses grant only permissions under copyright and certain
- other rights that a licensor has authority to grant. Use of
- the licensed material may still be restricted for other
- reasons, including because others have copyright or other
- rights in the material. A licensor may make special requests,
- such as asking that all changes be marked or described.
- Although not required by our licenses, you are encouraged to
- respect those requests where reasonable. More_considerations
- for the public:
- wiki.creativecommons.org/Considerations_for_licensees
-
-=======================================================================
-
-Creative Commons Attribution 4.0 International Public License
-
-By exercising the Licensed Rights (defined below), You accept and agree
-to be bound by the terms and conditions of this Creative Commons
-Attribution 4.0 International Public License ("Public License"). To the
-extent this Public License may be interpreted as a contract, You are
-granted the Licensed Rights in consideration of Your acceptance of
-these terms and conditions, and the Licensor grants You such rights in
-consideration of benefits the Licensor receives from making the
-Licensed Material available under these terms and conditions.
-
-
-Section 1 -- Definitions.
-
- a. Adapted Material means material subject to Copyright and Similar
- Rights that is derived from or based upon the Licensed Material
- and in which the Licensed Material is translated, altered,
- arranged, transformed, or otherwise modified in a manner requiring
- permission under the Copyright and Similar Rights held by the
- Licensor. For purposes of this Public License, where the Licensed
- Material is a musical work, performance, or sound recording,
- Adapted Material is always produced where the Licensed Material is
- synched in timed relation with a moving image.
-
- b. Adapter's License means the license You apply to Your Copyright
- and Similar Rights in Your contributions to Adapted Material in
- accordance with the terms and conditions of this Public License.
-
- c. Copyright and Similar Rights means copyright and/or similar rights
- closely related to copyright including, without limitation,
- performance, broadcast, sound recording, and Sui Generis Database
- Rights, without regard to how the rights are labeled or
- categorized. For purposes of this Public License, the rights
- specified in Section 2(b)(1)-(2) are not Copyright and Similar
- Rights.
-
- d. Effective Technological Measures means those measures that, in the
- absence of proper authority, may not be circumvented under laws
- fulfilling obligations under Article 11 of the WIPO Copyright
- Treaty adopted on December 20, 1996, and/or similar international
- agreements.
-
- e. Exceptions and Limitations means fair use, fair dealing, and/or
- any other exception or limitation to Copyright and Similar Rights
- that applies to Your use of the Licensed Material.
-
- f. Licensed Material means the artistic or literary work, database,
- or other material to which the Licensor applied this Public
- License.
-
- g. Licensed Rights means the rights granted to You subject to the
- terms and conditions of this Public License, which are limited to
- all Copyright and Similar Rights that apply to Your use of the
- Licensed Material and that the Licensor has authority to license.
-
- h. Licensor means the individual(s) or entity(ies) granting rights
- under this Public License.
-
- i. Share means to provide material to the public by any means or
- process that requires permission under the Licensed Rights, such
- as reproduction, public display, public performance, distribution,
- dissemination, communication, or importation, and to make material
- available to the public including in ways that members of the
- public may access the material from a place and at a time
- individually chosen by them.
-
- j. Sui Generis Database Rights means rights other than copyright
- resulting from Directive 96/9/EC of the European Parliament and of
- the Council of 11 March 1996 on the legal protection of databases,
- as amended and/or succeeded, as well as other essentially
- equivalent rights anywhere in the world.
-
- k. You means the individual or entity exercising the Licensed Rights
- under this Public License. Your has a corresponding meaning.
-
-
-Section 2 -- Scope.
-
- a. License grant.
-
- 1. Subject to the terms and conditions of this Public License,
- the Licensor hereby grants You a worldwide, royalty-free,
- non-sublicensable, non-exclusive, irrevocable license to
- exercise the Licensed Rights in the Licensed Material to:
-
- a. reproduce and Share the Licensed Material, in whole or
- in part; and
-
- b. produce, reproduce, and Share Adapted Material.
-
- 2. Exceptions and Limitations. For the avoidance of doubt, where
- Exceptions and Limitations apply to Your use, this Public
- License does not apply, and You do not need to comply with
- its terms and conditions.
-
- 3. Term. The term of this Public License is specified in Section
- 6(a).
-
- 4. Media and formats; technical modifications allowed. The
- Licensor authorizes You to exercise the Licensed Rights in
- all media and formats whether now known or hereafter created,
- and to make technical modifications necessary to do so. The
- Licensor waives and/or agrees not to assert any right or
- authority to forbid You from making technical modifications
- necessary to exercise the Licensed Rights, including
- technical modifications necessary to circumvent Effective
- Technological Measures. For purposes of this Public License,
- simply making modifications authorized by this Section 2(a)
- (4) never produces Adapted Material.
-
- 5. Downstream recipients.
-
- a. Offer from the Licensor -- Licensed Material. Every
- recipient of the Licensed Material automatically
- receives an offer from the Licensor to exercise the
- Licensed Rights under the terms and conditions of this
- Public License.
-
- b. No downstream restrictions. You may not offer or impose
- any additional or different terms or conditions on, or
- apply any Effective Technological Measures to, the
- Licensed Material if doing so restricts exercise of the
- Licensed Rights by any recipient of the Licensed
- Material.
-
- 6. No endorsement. Nothing in this Public License constitutes or
- may be construed as permission to assert or imply that You
- are, or that Your use of the Licensed Material is, connected
- with, or sponsored, endorsed, or granted official status by,
- the Licensor or others designated to receive attribution as
- provided in Section 3(a)(1)(A)(i).
-
- b. Other rights.
-
- 1. Moral rights, such as the right of integrity, are not
- licensed under this Public License, nor are publicity,
- privacy, and/or other similar personality rights; however, to
- the extent possible, the Licensor waives and/or agrees not to
- assert any such rights held by the Licensor to the limited
- extent necessary to allow You to exercise the Licensed
- Rights, but not otherwise.
-
- 2. Patent and trademark rights are not licensed under this
- Public License.
-
- 3. To the extent possible, the Licensor waives any right to
- collect royalties from You for the exercise of the Licensed
- Rights, whether directly or through a collecting society
- under any voluntary or waivable statutory or compulsory
- licensing scheme. In all other cases the Licensor expressly
- reserves any right to collect such royalties.
-
-
-Section 3 -- License Conditions.
-
-Your exercise of the Licensed Rights is expressly made subject to the
-following conditions.
-
- a. Attribution.
-
- 1. If You Share the Licensed Material (including in modified
- form), You must:
-
- a. retain the following if it is supplied by the Licensor
- with the Licensed Material:
-
- i. identification of the creator(s) of the Licensed
- Material and any others designated to receive
- attribution, in any reasonable manner requested by
- the Licensor (including by pseudonym if
- designated);
-
- ii. a copyright notice;
-
- iii. a notice that refers to this Public License;
-
- iv. a notice that refers to the disclaimer of
- warranties;
-
- v. a URI or hyperlink to the Licensed Material to the
- extent reasonably practicable;
-
- b. indicate if You modified the Licensed Material and
- retain an indication of any previous modifications; and
-
- c. indicate the Licensed Material is licensed under this
- Public License, and include the text of, or the URI or
- hyperlink to, this Public License.
-
- 2. You may satisfy the conditions in Section 3(a)(1) in any
- reasonable manner based on the medium, means, and context in
- which You Share the Licensed Material. For example, it may be
- reasonable to satisfy the conditions by providing a URI or
- hyperlink to a resource that includes the required
- information.
-
- 3. If requested by the Licensor, You must remove any of the
- information required by Section 3(a)(1)(A) to the extent
- reasonably practicable.
-
- 4. If You Share Adapted Material You produce, the Adapter's
- License You apply must not prevent recipients of the Adapted
- Material from complying with this Public License.
-
-
-Section 4 -- Sui Generis Database Rights.
-
-Where the Licensed Rights include Sui Generis Database Rights that
-apply to Your use of the Licensed Material:
-
- a. for the avoidance of doubt, Section 2(a)(1) grants You the right
- to extract, reuse, reproduce, and Share all or a substantial
- portion of the contents of the database;
-
- b. if You include all or a substantial portion of the database
- contents in a database in which You have Sui Generis Database
- Rights, then the database in which You have Sui Generis Database
- Rights (but not its individual contents) is Adapted Material; and
-
- c. You must comply with the conditions in Section 3(a) if You Share
- all or a substantial portion of the contents of the database.
-
-For the avoidance of doubt, this Section 4 supplements and does not
-replace Your obligations under this Public License where the Licensed
-Rights include other Copyright and Similar Rights.
-
-
-Section 5 -- Disclaimer of Warranties and Limitation of Liability.
-
- a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
- EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
- AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
- ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
- IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
- WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
- PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
- ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
- KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
- ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
-
- b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
- TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
- NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
- INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
- COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
- USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
- ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
- DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
- IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
-
- c. The disclaimer of warranties and limitation of liability provided
- above shall be interpreted in a manner that, to the extent
- possible, most closely approximates an absolute disclaimer and
- waiver of all liability.
-
-
-Section 6 -- Term and Termination.
-
- a. This Public License applies for the term of the Copyright and
- Similar Rights licensed here. However, if You fail to comply with
- this Public License, then Your rights under this Public License
- terminate automatically.
-
- b. Where Your right to use the Licensed Material has terminated under
- Section 6(a), it reinstates:
-
- 1. automatically as of the date the violation is cured, provided
- it is cured within 30 days of Your discovery of the
- violation; or
-
- 2. upon express reinstatement by the Licensor.
-
- For the avoidance of doubt, this Section 6(b) does not affect any
- right the Licensor may have to seek remedies for Your violations
- of this Public License.
-
- c. For the avoidance of doubt, the Licensor may also offer the
- Licensed Material under separate terms or conditions or stop
- distributing the Licensed Material at any time; however, doing so
- will not terminate this Public License.
-
- d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
- License.
-
-
-Section 7 -- Other Terms and Conditions.
-
- a. The Licensor shall not be bound by any additional or different
- terms or conditions communicated by You unless expressly agreed.
-
- b. Any arrangements, understandings, or agreements regarding the
- Licensed Material not stated herein are separate from and
- independent of the terms and conditions of this Public License.
-
-
-Section 8 -- Interpretation.
-
- a. For the avoidance of doubt, this Public License does not, and
- shall not be interpreted to, reduce, limit, restrict, or impose
- conditions on any use of the Licensed Material that could lawfully
- be made without permission under this Public License.
-
- b. To the extent possible, if any provision of this Public License is
- deemed unenforceable, it shall be automatically reformed to the
- minimum extent necessary to make it enforceable. If the provision
- cannot be reformed, it shall be severed from this Public License
- without affecting the enforceability of the remaining terms and
- conditions.
-
- c. No term or condition of this Public License will be waived and no
- failure to comply consented to unless expressly agreed to by the
- Licensor.
-
- d. Nothing in this Public License constitutes or may be interpreted
- as a limitation upon, or waiver of, any privileges and immunities
- that apply to the Licensor or You, including from the legal
- processes of any jurisdiction or authority.
-
-
-=======================================================================
-
-Creative Commons is not a party to its public
-licenses. Notwithstanding, Creative Commons may elect to apply one of
-its public licenses to material it publishes and in those instances
-will be considered the ”Licensor.” The text of the Creative Commons
-public licenses is dedicated to the public domain under the CC0 Public
-Domain Dedication. Except for the limited purpose of indicating that
-material is shared under a Creative Commons public license or as
-otherwise permitted by the Creative Commons policies published at
-creativecommons.org/policies, Creative Commons does not authorize the
-use of the trademark "Creative Commons" or any other trademark or logo
-of Creative Commons without its prior written consent including,
-without limitation, in connection with any unauthorized modifications
-to any of its public licenses or any other arrangements,
-understandings, or agreements concerning use of licensed material. For
-the avoidance of doubt, this paragraph does not form part of the
-public licenses.
-
-Creative Commons may be contacted at creativecommons.org.
-
-
-
-CDDL-1.0
-
-
-COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
-Version 1.0
-1. Definitions.
-
-1.1. “Contributor” means each individual or entity that creates or
-contributes to the creation of Modifications.
-
-1.2. “Contributor Version” means the combination of the Original
-Software, prior Modifications used by a Contributor (if any), and the Modifications
-made by that particular Contributor.
-
-1.3. “Covered Software” means (a) the Original Software, or (b)
-Modifications, or (c) the combination of files containing Original Software with files
-containing Modifications, in each case including portions thereof.
-
-1.4. “Executable” means the Covered Software in any form other
-than Source Code.
-
-1.5. “Initial Developer” means the individual or entity that first
-makes Original Software available under this License.
-
-1.6. “Larger Work” means a work which combines Covered Software or
-portions thereof with code not governed by the terms of this License.
-
-1.7. “License” means this document.
-
-1.8. “Licensable” means having the right to grant, to the maximum
-extent possible, whether at the time of the initial grant or subsequently acquired,
-any and all of the rights conveyed herein.
-
-1.9. “Modifications” means the Source Code and Executable form of
-any of the following:
-
-A. Any file that results from an addition to, deletion from or modification of the
-contents of a file containing Original Software or previous Modifications;
-
-B. Any new file that contains any part of the Original Software or previous
-Modification; or
-
-C. Any new file that is contributed or otherwise made available under the terms of
-this License.
-
-1.10. “Original Software” means the Source Code and Executable
-form of computer software code that is originally released under this License.
-
-1.11. “Patent Claims” means any patent claim(s), now owned or
-hereafter acquired, including without limitation, method, process, and apparatus
-claims, in any patent Licensable by grantor.
-
-1.12. “Source Code” means (a) the common form of computer software
-code in which modifications are made and (b) associated documentation included in or
-with such code.
-
-1.13. “You” (or “Your”) means an individual or
-a legal entity exercising rights under, and complying with all of the terms of, this
-License. For legal entities, “You” includes any entity which
-controls, is controlled by, or is under common control with You. For purposes of this
-definition, “control” means (a) the power, direct or indirect, to
-cause the direction or management of such entity, whether by contract or otherwise, or
-(b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial
-ownership of such entity.
-
-2. License Grants.
-
-2.1. The Initial Developer Grant.
-
-Conditioned upon Your compliance with Section 3.1 below and subject to third party
-intellectual property claims, the Initial Developer hereby grants You a world-wide,
-royalty-free, non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark) Licensable by
-Initial Developer, to use, reproduce, modify, display, perform, sublicense and
-distribute the Original Software (or portions thereof), with or without Modifications,
-and/or as part of a Larger Work; and
-
-(b) under Patent Claims infringed by the making, using or selling of Original
-Software, to make, have made, use, practice, sell, and offer for sale, and/or
-otherwise dispose of the Original Software (or portions thereof).
-
-(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial
-Developer first distributes or otherwise makes the Original Software available to a
-third party under the terms of this License.
-
-(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code
-that You delete from the Original Software, or (2) for infringements caused by: (i)
-the modification of the Original Software, or (ii) the combination of the Original
-Software with other software or devices.
-
-2.2. Contributor Grant.
-
-Conditioned upon Your compliance with Section 3.1 below and subject to third party
-intellectual property claims, each Contributor hereby grants You a world-wide,
-royalty-free, non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark) Licensable by
-Contributor to use, reproduce, modify, display, perform, sublicense and distribute the
-Modifications created by such Contributor (or portions thereof), either on an
-unmodified basis, with other Modifications, as Covered Software and/or as part of a
-Larger Work; and
-
-(b) under Patent Claims infringed by the making, using, or selling of Modifications
-made by that Contributor either alone and/or in combination with its Contributor
-Version (or portions of such combination), to make, use, sell, offer for sale, have
-made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or
-portions thereof); and (2) the combination of Modifications made by that Contributor
-with its Contributor Version (or portions of such combination).
-
-(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
-Contributor first distributes or otherwise makes the Modifications available to a
-third party.
-
-(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any
-code that Contributor has deleted from the Contributor Version; (2) for infringements
-caused by: (i) third party modifications of Contributor Version, or (ii) the
-combination of Modifications made by that Contributor with other software (except as
-part of the Contributor Version) or other devices; or (3) under Patent Claims
-infringed by Covered Software in the absence of Modifications made by that
-Contributor.
-
-3. Distribution Obligations.
-
-3.1. Availability of Source Code.
-
-Any Covered Software that You distribute or otherwise make available in Executable
-form must also be made available in Source Code form and that Source Code form must be
-distributed only under the terms of this License. You must include a copy of this
-License with every copy of the Source Code form of the Covered Software You distribute
-or otherwise make available. You must inform recipients of any such Covered Software
-in Executable form as to how they can obtain such Covered Software in Source Code form
-in a reasonable manner on or through a medium customarily used for software exchange.
-
-3.2. Modifications.
-
-The Modifications that You create or to which You contribute are governed by the terms
-of this License. You represent that You believe Your Modifications are Your original
-creation(s) and/or You have sufficient rights to grant the rights conveyed by this
-License.
-
-3.3. Required Notices.
-
-You must include a notice in each of Your Modifications that identifies You as the
-Contributor of the Modification. You may not remove or alter any copyright, patent or
-trademark notices contained within the Covered Software, or any notices of licensing
-or any descriptive text giving attribution to any Contributor or the Initial
-Developer.
-
-3.4. Application of Additional Terms.
-
-You may not offer or impose any terms on any Covered Software in Source Code form that
-alters or restricts the applicable version of this License or the
-recipients’ rights hereunder. You may choose to offer, and to charge a fee
-for, warranty, support, indemnity or liability obligations to one or more recipients
-of Covered Software. However, you may do so only on Your own behalf, and not on behalf
-of the Initial Developer or any Contributor. You must make it absolutely clear that
-any such warranty, support, indemnity or liability obligation is offered by You alone,
-and You hereby agree to indemnify the Initial Developer and every Contributor for any
-liability incurred by the Initial Developer or such Contributor as a result of
-warranty, support, indemnity or liability terms You offer.
-
-3.5. Distribution of Executable Versions.
-
-You may distribute the Executable form of the Covered Software under the terms of this
-License or under the terms of a license of Your choice, which may contain terms
-different from this License, provided that You are in compliance with the terms of
-this License and that the license for the Executable form does not attempt to limit or
-alter the recipient’s rights in the Source Code form from the rights set
-forth in this License. If You distribute the Covered Software in Executable form under
-a different license, You must make it absolutely clear that any terms which differ
-from this License are offered by You alone, not by the Initial Developer or
-Contributor. You hereby agree to indemnify the Initial Developer and every Contributor
-for any liability incurred by the Initial Developer or such Contributor as a result of
-any such terms You offer.
-
-3.6. Larger Works.
-
-You may create a Larger Work by combining Covered Software with other code not
-governed by the terms of this License and distribute the Larger Work as a single
-product. In such a case, You must make sure the requirements of this License are
-fulfilled for the Covered Software.
-
-4. Versions of the License.
-
-4.1. New Versions.
-
-Sun Microsystems, Inc. is the initial license steward and may publish revised and/or
-new versions of this License from time to time. Each version will be given a
-distinguishing version number. Except as provided in Section 4.3, no one other than
-the license steward has the right to modify this License.
-
-4.2. Effect of New Versions.
-
-You may always continue to use, distribute or otherwise make the Covered Software
-available under the terms of the version of the License under which You originally
-received the Covered Software. If the Initial Developer includes a notice in the
-Original Software prohibiting it from being distributed or otherwise made available
-under any subsequent version of the License, You must distribute and make the Covered
-Software available under the terms of the version of the License under which You
-originally received the Covered Software. Otherwise, You may also choose to use,
-distribute or otherwise make the Covered Software available under the terms of any
-subsequent version of the License published by the license steward.
-
-4.3. Modified Versions.
-
-When You are an Initial Developer and You want to create a new license for Your
-Original Software, You may create and use a modified version of this License if You:
-(a) rename the license and remove any references to the name of the license steward
-(except to note that the license differs from this License); and (b) otherwise make it
-clear that the license contains terms which differ from this License.
-
-5. DISCLAIMER OF WARRANTY.
-
-COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS”
-BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
-LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT
-FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
-PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
-DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR)
-ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
-WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE
-IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
-
-6. TERMINATION.
-
-6.1. This License and the rights granted hereunder will terminate automatically if You
-fail to comply with terms herein and fail to cure such breach within 30 days of
-becoming aware of the breach. Provisions which, by their nature, must remain in effect
-beyond the termination of this License shall survive.
-
-6.2. If You assert a patent infringement claim (excluding declaratory judgment
-actions) against Initial Developer or a Contributor (the Initial Developer or
-Contributor against whom You assert such claim is referred to as
-“Participant”) alleging that the Participant Software (meaning the
-Contributor Version where the Participant is a Contributor or the Original Software
-where the Participant is the Initial Developer) directly or indirectly infringes any
-patent, then any and all rights granted directly or indirectly to You by such
-Participant, the Initial Developer (if the Initial Developer is not the Participant)
-and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days
-notice from Participant terminate prospectively and automatically at the expiration of
-such 60 day notice period, unless if within such 60 day period You withdraw Your claim
-with respect to the Participant Software against such Participant either unilaterally
-or pursuant to a written agreement with Participant.
-
-6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user
-licenses that have been validly granted by You or any distributor hereunder prior to
-termination (excluding licenses granted to You by any distributor) shall survive
-termination.
-
-7. LIMITATION OF LIABILITY.
-
-UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
-CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR
-ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE
-TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
-CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,
-WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL
-DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF
-SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
-PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT
-APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
-EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
-LIMITATION MAY NOT APPLY TO YOU.
-
-8. U.S. GOVERNMENT END USERS.
-
-The Covered Software is a “commercial item,” as that term is
-defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of “commercial computer
-software” (as that term is defined at 48 C.F.R. §
-252.227-7014(a)(1)) and “commercial computer software
-documentation” as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
-Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
-1995), all U.S. Government End Users acquire Covered Software with only those rights
-set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes,
-any other FAR, DFAR, or other clause or provision that addresses Government rights in
-computer software under this License.
-
-9. MISCELLANEOUS.
-
-This License represents the complete agreement concerning subject matter hereof. If
-any provision of this License is held to be unenforceable, such provision shall be
-reformed only to the extent necessary to make it enforceable. This License shall be
-governed by the law of the jurisdiction specified in a notice contained within the
-Original Software (except to the extent applicable law, if any, provides otherwise),
-excluding such jurisdiction’s conflict-of-law provisions. Any litigation
-relating to this License shall be subject to the jurisdiction of the courts located in
-the jurisdiction and venue specified in a notice contained within the Original
-Software, with the losing party responsible for costs, including, without limitation,
-court costs and reasonable attorneys’ fees and expenses. The application of
-the United Nations Convention on Contracts for the International Sale of Goods is
-expressly excluded. Any law or regulation which provides that the language of a
-contract shall be construed against the drafter shall not apply to this License. You
-agree that You alone are responsible for compliance with the United States export
-administration regulations (and the export control laws and regulation of any other
-countries) when You use, distribute or otherwise make available any Covered Software.
-
-10. RESPONSIBILITY FOR CLAIMS.
-
-As between Initial Developer and the Contributors, each party is responsible for
-claims and damages arising, directly or indirectly, out of its utilization of rights
-under this License and You agree to work with Initial Developer and Contributors to
-distribute such responsibility on an equitable basis. Nothing herein is intended or
-shall be deemed to constitute any admission of liability.
-
-
-
-
-CDS
-
-This software is copyrighted by Cadence Design Systems, Inc., and other
-parties. The following terms apply to all files associated with the
-software unless explicitly disclaimed in individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
------------------------------------------------------------------------
- Following is the original agreement for the Tcl/Tk software from
- Sun Microsystems.
------------------------------------------------------------------------
-
-This software is copyrighted by the Regents of the University of
-California, Sun Microsystems, Inc., and other parties. The following
-terms apply to all files associated with the software unless explicitly
-disclaimed in individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
-
-
-CPL-1.0
-
-
-Common Public License Version 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
-LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
-CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-
-"Contribution" means:
-
-a) in the case of the initial Contributor, the initial code and
-documentation distributed under this Agreement, and
-
-b) in the case of each subsequent Contributor:
-
-i) changes to the Program, and
-
-ii) additions to the Program;
-
-where such changes and/or additions to the Program originate from and are
-distributed by that particular Contributor. A Contribution `originates` from a
-Contributor if it was added to the Program by such Contributor itself or anyone
-acting on such Contributor`s behalf. Contributions do not include additions to
-the Program which: (i) are separate modules of software distributed in
-conjunction with the Program under their own license agreement, and (ii) are not
-derivative works of the Program.
-
-"Contributor" means any person or entity that distributes the Program.
-
-"Licensed Patents " mean patent claims licensable by a Contributor which are
-necessarily infringed by the use or sale of its Contribution alone or when
-combined with the Program.
-
-"Program" means the Contributions distributed in accordance with this Agreement.
-
-"Recipient" means anyone who receives the Program under this Agreement,
-including all Contributors.
-
-2. GRANT OF RIGHTS
-
-a) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free copyright license to
-reproduce, prepare derivative works of, publicly display, publicly perform,
-distribute and sublicense the Contribution of such Contributor, if any, and such
-derivative works, in source code and object code form.
-
-b) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
-Patents to make, use, sell, offer to sell, import and otherwise transfer the
-Contribution of such Contributor, if any, in source code and object code form.
-This patent license shall apply to the combination of the Contribution and the
-Program if, at the time the Contribution is added by the Contributor, such
-addition of the Contribution causes such combination to be covered by the
-Licensed Patents. The patent license shall not apply to any other combinations
-which include the Contribution. No hardware per se is licensed hereunder.
-
-c) Recipient understands that although each Contributor grants the licenses
-to its Contributions set forth herein, no assurances are provided by any
-Contributor that the Program does not infringe the patent or other intellectual
-property rights of any other entity. Each Contributor disclaims any liability to
-Recipient for claims brought by any other entity based on infringement of
-intellectual property rights or otherwise. As a condition to exercising the
-rights and licenses granted hereunder, each Recipient hereby assumes sole
-responsibility to secure any other intellectual property rights needed, if any.
-For example, if a third party patent license is required to allow Recipient to
-distribute the Program, it is Recipient`s responsibility to acquire that license
-before distributing the Program.
-
-d) Each Contributor represents that to its knowledge it has sufficient
-copyright rights in its Contribution, if any, to grant the copyright license set
-forth in this Agreement.
-
-3. REQUIREMENTS
-
-A Contributor may choose to distribute the Program in object code form under its
-own license agreement, provided that:
-
-a) it complies with the terms and conditions of this Agreement; and
-
-b) its license agreement:
-
-i) effectively disclaims on behalf of all Contributors all warranties and
-conditions, express and implied, including warranties or conditions of title and
-non-infringement, and implied warranties or conditions of merchantability and
-fitness for a particular purpose;
-
-ii) effectively excludes on behalf of all Contributors all liability for
-damages, including direct, indirect, special, incidental and consequential
-damages, such as lost profits;
-
-iii) states that any provisions which differ from this Agreement are offered
-by that Contributor alone and not by any other party; and
-
-iv) states that source code for the Program is available from such
-Contributor, and informs licensees how to obtain it in a reasonable manner on or
-through a medium customarily used for software exchange.
-
-When the Program is made available in source code form:
-
-a) it must be made available under this Agreement; and
-
-b) a copy of this Agreement must be included with each copy of the Program.
-
-Contributors may not remove or alter any copyright notices contained within the
-Program.
-
-Each Contributor must identify itself as the originator of its Contribution, if
-any, in a manner that reasonably allows subsequent Recipients to identify the
-originator of the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-
-Commercial distributors of software may accept certain responsibilities with
-respect to end users, business partners and the like. While this license is
-intended to facilitate the commercial use of the Program, the Contributor who
-includes the Program in a commercial product offering should do so in a manner
-which does not create potential liability for other Contributors. Therefore, if
-a Contributor includes the Program in a commercial product offering, such
-Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
-every other Contributor ("Indemnified Contributor") against any losses, damages
-and costs (collectively "Losses") arising from claims, lawsuits and other legal
-actions brought by a third party against the Indemnified Contributor to the
-extent caused by the acts or omissions of such Commercial Contributor in
-connection with its distribution of the Program in a commercial product
-offering. The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement. In order
-to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
-Contributor in writing of such claim, and b) allow the Commercial Contributor to
-control, and cooperate with the Commercial Contributor in, the defense and any
-related settlement negotiations. The Indemnified Contributor may participate in
-any such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial product
-offering, Product X. That Contributor is then a Commercial Contributor. If that
-Commercial Contributor then makes performance claims, or offers warranties
-related to Product X, those performance claims and warranties are such
-Commercial Contributor`s responsibility alone. Under this section, the
-Commercial Contributor would have to defend claims against the other
-Contributors related to those performance claims and warranties, and if a court
-requires any other Contributor to pay any damages as a result, the Commercial
-Contributor must pay those damages.
-
-5. NO WARRANTY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
-IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
-NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
-Recipient is solely responsible for determining the appropriateness of using and
-distributing the Program and assumes all risks associated with its exercise of
-rights under this Agreement, including but not limited to the risks and costs of
-program errors, compliance with applicable laws, damage to or loss of data,
-programs or equipment, and unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
-CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
-PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
-STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
-GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-
-If any provision of this Agreement is invalid or unenforceable under applicable
-law, it shall not affect the validity or enforceability of the remainder of the
-terms of this Agreement, and without further action by the parties hereto, such
-provision shall be reformed to the minimum extent necessary to make such
-provision valid and enforceable.
-
-If Recipient institutes patent litigation against a Contributor with respect to
-a patent applicable to software (including a cross-claim or counterclaim in a
-lawsuit), then any patent licenses granted by that Contributor to such Recipient
-under this Agreement shall terminate as of the date such litigation is filed. In
-addition, if Recipient institutes patent litigation against any entity
-(including a cross-claim or counterclaim in a lawsuit) alleging that the Program
-itself (excluding combinations of the Program with other software or hardware)
-infringes such Recipient`s patent(s), then such Recipient`s rights granted under
-Section 2(b) shall terminate as of the date such litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it fails to
-comply with any of the material terms or conditions of this Agreement and does
-not cure such failure in a reasonable period of time after becoming aware of
-such noncompliance. If all Recipient`s rights under this Agreement terminate,
-Recipient agrees to cease use and distribution of the Program as soon as
-reasonably practicable. However, Recipient`s obligations under this Agreement
-and any licenses granted by Recipient relating to the Program shall continue and
-survive.
-
-Everyone is permitted to copy and distribute copies of this Agreement, but in
-order to avoid inconsistency the Agreement is copyrighted and may only be
-modified in the following manner. The Agreement Steward reserves the right to
-publish new versions (including revisions) of this Agreement from time to time.
-No one other than the Agreement Steward has the right to modify this Agreement.
-IBM is the initial Agreement Steward. IBM may assign the responsibility to serve
-as the Agreement Steward to a suitable separate entity. Each new version of the
-Agreement will be given a distinguishing version number. The Program (including
-Contributions) may always be distributed subject to the version of the Agreement
-under which it was received. In addition, after a new version of the Agreement
-is published, Contributor may elect to distribute the Program (including its
-Contributions) under the new version. Except as expressly stated in Sections
-2(a) and 2(b) above, Recipient receives no rights or licenses to the
-intellectual property of any Contributor under this Agreement, whether
-expressly, by implication, estoppel or otherwise. All rights in the Program not
-expressly granted under this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and the
-intellectual property laws of the United States of America. No party to this
-Agreement will bring a legal action under this Agreement more than one year
-after the cause of action arose. Each party waives its rights to a jury trial in
-any resulting litigation.
-
-
-
-
-CUP
-
-CUP PARSER GENERATOR COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
-
-Copyright 1996 by Scott Hudson, Frank Flannery, C. Scott Ananian
-
-Permission to use, copy, modify, and distribute this software and its
-documentation for any purpose and without fee is hereby granted,
-provided that the above copyright notice appear in all copies and that
-both the copyright notice and this permission notice and warranty
-disclaimer appear in supporting documentation, and that the names of
-the authors or their employers not be used in advertising or publicity
-pertaining to distribution of the software without specific, written
-prior permission.
-
-The authors and their employers disclaim all warranties with regard to
-this software, including all implied warranties of merchantability and
-fitness. In no event shall the authors or their employers be liable
-for any special, indirect or consequential damages or any damages
-whatsoever resulting from loss of use, data or profits, whether in an
-action of contract, negligence or other tortious action, arising out of
-or in connection with the use or performance of this software.
-
-
-
-EPL-1.0
-
-
-Eclipse Public License - v 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE
-("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES
-RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-
-"Contribution" means:
-
-a) in the case of the initial Contributor, the initial code and documentation
-distributed under this Agreement, and
-b) in the case of each subsequent Contributor:
-i) changes to the Program, and
-ii) additions to the Program;
-where such changes and/or additions to the Program originate from and are distributed
-by that particular Contributor. A Contribution `originates` from a Contributor if it
-was added to the Program by such Contributor itself or anyone acting on such
-Contributor`s behalf. Contributions do not include additions to the Program which: (i)
-are separate modules of software distributed in conjunction with the Program under
-their own license agreement, and (ii) are not derivative works of the Program.
-"Contributor" means any person or entity that distributes the Program.
-
-"Licensed Patents" mean patent claims licensable by a Contributor which are
-necessarily infringed by the use or sale of its Contribution alone or when combined
-with the Program.
-
-"Program" means the Contributions distributed in accordance with this Agreement.
-
-"Recipient" means anyone who receives the Program under this Agreement, including all
-Contributors.
-
-2. GRANT OF RIGHTS
-
-a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
-non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare
-derivative works of, publicly display, publicly perform, distribute and sublicense the
-Contribution of such Contributor, if any, and such derivative works, in source code
-and object code form.
-b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
-non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make,
-use, sell, offer to sell, import and otherwise transfer the Contribution of such
-Contributor, if any, in source code and object code form. This patent license shall
-apply to the combination of the Contribution and the Program if, at the time the
-Contribution is added by the Contributor, such addition of the Contribution causes
-such combination to be covered by the Licensed Patents. The patent license shall not
-apply to any other combinations which include the Contribution. No hardware per se is
-licensed hereunder.
-c) Recipient understands that although each Contributor grants the licenses to its
-Contributions set forth herein, no assurances are provided by any Contributor that the
-Program does not infringe the patent or other intellectual property rights of any
-other entity. Each Contributor disclaims any liability to Recipient for claims brought
-by any other entity based on infringement of intellectual property rights or
-otherwise. As a condition to exercising the rights and licenses granted hereunder,
-each Recipient hereby assumes sole responsibility to secure any other intellectual
-property rights needed, if any. For example, if a third party patent license is
-required to allow Recipient to distribute the Program, it is Recipient`s
-responsibility to acquire that license before distributing the Program.
-d) Each Contributor represents that to its knowledge it has sufficient copyright
-rights in its Contribution, if any, to grant the copyright license set forth in this
-Agreement.
-3. REQUIREMENTS
-
-A Contributor may choose to distribute the Program in object code form under its own
-license agreement, provided that:
-
-a) it complies with the terms and conditions of this Agreement; and
-b) its license agreement:
-i) effectively disclaims on behalf of all Contributors all warranties and conditions,
-express and implied, including warranties or conditions of title and non-infringement,
-and implied warranties or conditions of merchantability and fitness for a particular
-purpose;
-ii) effectively excludes on behalf of all Contributors all liability for damages,
-including direct, indirect, special, incidental and consequential damages, such as
-lost profits;
-iii) states that any provisions which differ from this Agreement are offered by that
-Contributor alone and not by any other party; and
-iv) states that source code for the Program is available from such Contributor, and
-informs licensees how to obtain it in a reasonable manner on or through a medium
-customarily used for software exchange.
-When the Program is made available in source code form:
-
-a) it must be made available under this Agreement; and
-b) a copy of this Agreement must be included with each copy of the Program.
-Contributors may not remove or alter any copyright notices contained within the
-Program.
-
-Each Contributor must identify itself as the originator of its Contribution, if any,
-in a manner that reasonably allows subsequent Recipients to identify the originator of
-the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-
-Commercial distributors of software may accept certain responsibilities with respect
-to end users, business partners and the like. While this license is intended to
-facilitate the commercial use of the Program, the Contributor who includes the Program
-in a commercial product offering should do so in a manner which does not create
-potential liability for other Contributors. Therefore, if a Contributor includes the
-Program in a commercial product offering, such Contributor ("Commercial Contributor")
-hereby agrees to defend and indemnify every other Contributor ("Indemnified
-Contributor") against any losses, damages and costs (collectively "Losses") arising
-from claims, lawsuits and other legal actions brought by a third party against the
-Indemnified Contributor to the extent caused by the acts or omissions of such
-Commercial Contributor in connection with its distribution of the Program in a
-commercial product offering. The obligations in this section do not apply to any
-claims or Losses relating to any actual or alleged intellectual property infringement.
-In order to qualify, an Indemnified Contributor must: a) promptly notify the
-Commercial Contributor in writing of such claim, and b) allow the Commercial
-Contributor to control, and cooperate with the Commercial Contributor in, the defense
-and any related settlement negotiations. The Indemnified Contributor may participate
-in any such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial product offering,
-Product X. That Contributor is then a Commercial Contributor. If that Commercial
-Contributor then makes performance claims, or offers warranties related to Product X,
-those performance claims and warranties are such Commercial Contributor`s
-responsibility alone. Under this section, the Commercial Contributor would have to
-defend claims against the other Contributors related to those performance claims and
-warranties, and if a court requires any other Contributor to pay any damages as a
-result, the Commercial Contributor must pay those damages.
-
-5. NO WARRANTY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS"
-BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED
-INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
-NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient
-is solely responsible for determining the appropriateness of using and distributing
-the Program and assumes all risks associated with its exercise of rights under this
-Agreement , including but not limited to the risks and costs of program errors,
-compliance with applicable laws, damage to or loss of data, programs or equipment, and
-unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
-CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS),
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR
-DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-
-If any provision of this Agreement is invalid or unenforceable under applicable law,
-it shall not affect the validity or enforceability of the remainder of the terms of
-this Agreement, and without further action by the parties hereto, such provision shall
-be reformed to the minimum extent necessary to make such provision valid and
-enforceable.
-
-If Recipient institutes patent litigation against any entity (including a cross-claim
-or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations
-of the Program with other software or hardware) infringes such Recipient`s patent(s),
-then such Recipient`s rights granted under Section 2(b) shall terminate as of the date
-such litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it fails to comply with
-any of the material terms or conditions of this Agreement and does not cure such
-failure in a reasonable period of time after becoming aware of such noncompliance. If
-all Recipient`s rights under this Agreement terminate, Recipient agrees to cease use
-and distribution of the Program as soon as reasonably practicable. However,
-Recipient`s obligations under this Agreement and any licenses granted by Recipient
-relating to the Program shall continue and survive.
-
-Everyone is permitted to copy and distribute copies of this Agreement, but in order to
-avoid inconsistency the Agreement is copyrighted and may only be modified in the
-following manner. The Agreement Steward reserves the right to publish new versions
-(including revisions) of this Agreement from time to time. No one other than the
-Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is
-the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to
-serve as the Agreement Steward to a suitable separate entity. Each new version of the
-Agreement will be given a distinguishing version number. The Program (including
-Contributions) may always be distributed subject to the version of the Agreement under
-which it was received. In addition, after a new version of the Agreement is published,
-Contributor may elect to distribute the Program (including its Contributions) under
-the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
-receives no rights or licenses to the intellectual property of any Contributor under
-this Agreement, whether expressly, by implication, estoppel or otherwise. All rights
-in the Program not expressly granted under this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and the intellectual
-property laws of the United States of America. No party to this Agreement will bring a
-legal action under this Agreement more than one year after the cause of action arose.
-Each party waives its rights to a jury trial in any resulting litigation.
-
-
-
-
-Elfutils-Exception
-
- This file describes the limits of the Exception under which you are allowed
- to distribute Non-GPL Code in linked combination with Red Hat elfutils.
- For the full text of the license, please see one of the header files
- included with the source distribution or the file COPYING found in the
- top level directory of the source.
-
- The Approved Interfaces are the functions declared in the files:
-
- libelf.h
- libdw.h
- libdwfl.h
-
-
-
-
-FSF-Unlimited
-
-Copyright (C) 1997-2010 Free Software Foundation, Inc.
-This file is free software; the Free Software Foundation
-gives unlimited permission to copy and/or distribute it,
-with or without modifications, as long as this notice is preserved.
-
-
-
-FreeType
-
- The FreeType Project LICENSE
- ----------------------------
-
- 2006-Jan-27
-
- Copyright 1996-2002, 2006 by
- David Turner, Robert Wilhelm, and Werner Lemberg
-
-
-
-Introduction
-============
-
- The FreeType Project is distributed in several archive packages;
- some of them may contain, in addition to the FreeType font engine,
- various tools and contributions which rely on, or relate to, the
- FreeType Project.
-
- This license applies to all files found in such packages, and
- which do not fall under their own explicit license. The license
- affects thus the FreeType font engine, the test programs,
- documentation and makefiles, at the very least.
-
- This license was inspired by the BSD, Artistic, and IJG
- (Independent JPEG Group) licenses, which all encourage inclusion
- and use of free software in commercial and freeware products
- alike. As a consequence, its main points are that:
-
- o We don't promise that this software works. However, we will be
- interested in any kind of bug reports. (`as is' distribution)
-
- o You can use this software for whatever you want, in parts or
- full form, without having to pay us. (`royalty-free' usage)
-
- o You may not pretend that you wrote this software. If you use
- it, or only parts of it, in a program, you must acknowledge
- somewhere in your documentation that you have used the
- FreeType code. (`credits')
-
- We specifically permit and encourage the inclusion of this
- software, with or without modifications, in commercial products.
- We disclaim all warranties covering The FreeType Project and
- assume no liability related to The FreeType Project.
-
-
- Finally, many people asked us for a preferred form for a
- credit/disclaimer to use in compliance with this license. We thus
- encourage you to use the following text:
-
- """
- Portions of this software are copyright � <year> The FreeType
- Project (www.freetype.org). All rights reserved.
- """
-
- Please replace <year> with the value from the FreeType version you
- actually use.
-
-
-Legal Terms
-===========
-
-0. Definitions
---------------
-
- Throughout this license, the terms `package', `FreeType Project',
- and `FreeType archive' refer to the set of files originally
- distributed by the authors (David Turner, Robert Wilhelm, and
- Werner Lemberg) as the `FreeType Project', be they named as alpha,
- beta or final release.
-
- `You' refers to the licensee, or person using the project, where
- `using' is a generic term including compiling the project's source
- code as well as linking it to form a `program' or `executable'.
- This program is referred to as `a program using the FreeType
- engine'.
-
- This license applies to all files distributed in the original
- FreeType Project, including all source code, binaries and
- documentation, unless otherwise stated in the file in its
- original, unmodified form as distributed in the original archive.
- If you are unsure whether or not a particular file is covered by
- this license, you must contact us to verify this.
-
- The FreeType Project is copyright (C) 1996-2000 by David Turner,
- Robert Wilhelm, and Werner Lemberg. All rights reserved except as
- specified below.
-
-1. No Warranty
---------------
-
- THE FREETYPE PROJECT IS PROVIDED `AS IS' WITHOUT WARRANTY OF ANY
- KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
- WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
- PURPOSE. IN NO EVENT WILL ANY OF THE AUTHORS OR COPYRIGHT HOLDERS
- BE LIABLE FOR ANY DAMAGES CAUSED BY THE USE OR THE INABILITY TO
- USE, OF THE FREETYPE PROJECT.
-
-2. Redistribution
------------------
-
- This license grants a worldwide, royalty-free, perpetual and
- irrevocable right and license to use, execute, perform, compile,
- display, copy, create derivative works of, distribute and
- sublicense the FreeType Project (in both source and object code
- forms) and derivative works thereof for any purpose; and to
- authorize others to exercise some or all of the rights granted
- herein, subject to the following conditions:
-
- o Redistribution of source code must retain this license file
- (`FTL.TXT') unaltered; any additions, deletions or changes to
- the original files must be clearly indicated in accompanying
- documentation. The copyright notices of the unaltered,
- original files must be preserved in all copies of source
- files.
-
- o Redistribution in binary form must provide a disclaimer that
- states that the software is based in part of the work of the
- FreeType Team, in the distribution documentation. We also
- encourage you to put an URL to the FreeType web page in your
- documentation, though this isn't mandatory.
-
- These conditions apply to any software derived from or based on
- the FreeType Project, not just the unmodified files. If you use
- our work, you must acknowledge us. However, no fee need be paid
- to us.
-
-3. Advertising
---------------
-
- Neither the FreeType authors and contributors nor you shall use
- the name of the other for commercial, advertising, or promotional
- purposes without specific prior written permission.
-
- We suggest, but do not require, that you use one or more of the
- following phrases to refer to this software in your documentation
- or advertising materials: `FreeType Project', `FreeType Engine',
- `FreeType library', or `FreeType Distribution'.
-
- As you have not signed this license, you are not required to
- accept it. However, as the FreeType Project is copyrighted
- material, only this license, or another one contracted with the
- authors, grants you the right to use, distribute, and modify it.
- Therefore, by using, distributing, or modifying the FreeType
- Project, you indicate that you understand and accept all the terms
- of this license.
-
-4. Contacts
------------
-
- There are two mailing lists related to FreeType:
-
- o freetype@nongnu.org
-
- Discusses general use and applications of FreeType, as well as
- future and wanted additions to the library and distribution.
- If you are looking for support, start in this list if you
- haven't found anything to help you in the documentation.
-
- o freetype-devel@nongnu.org
-
- Discusses bugs, as well as engine internals, design issues,
- specific licenses, porting, etc.
-
- Our home page can be found at
-
- http://www.freetype.org
-
-
---- end of FTL.TXT ---
-
-
-
-
-GPL-1.0
-
-
-GNU General Public License, version 1
-
- GNU GENERAL PUBLIC LICENSE
- Version 1, February 1989
-
- Copyright (C) 1989 Free Software Foundation, Inc.
- 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The license agreements of most software companies try to keep users
-at the mercy of those companies. By contrast, our General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. The
-General Public License applies to the Free Software Foundation`s
-software and to any other program whose authors commit to using it.
-You can use it for your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Specifically, the General Public License is designed to make
-sure that you have the freedom to give away or sell copies of free
-software, that you receive source code or can get it if you want it,
-that you can change the software or use pieces of it in new free
-programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of a such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must tell them their rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author`s protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors` reputations.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License Agreement applies to any program or other work which
-contains a notice placed by the copyright holder saying it may be
-distributed under the terms of this General Public License. The
-"Program", below, refers to any such program or work, and a "work based
-on the Program" means either the Program or any work containing the
-Program or a portion of it, either verbatim or with modifications. Each
-licensee is addressed as "you".
-
- 1. You may copy and distribute verbatim copies of the Program`s source
-code as you receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice and
-disclaimer of warranty; keep intact all the notices that refer to this
-General Public License and to the absence of any warranty; and give any
-other recipients of the Program a copy of this General Public License
-along with the Program. You may charge a fee for the physical act of
-transferring a copy.
-
- 2. You may modify your copy or copies of the Program or any portion of
-it, and copy and distribute such modifications under the terms of Paragraph
-1 above, provided that you also do the following:
-
- a) cause the modified files to carry prominent notices stating that
- you changed the files and the date of any change; and
-
- b) cause the whole of any work that you distribute or publish, that
- in whole or in part contains the Program or any part thereof, either
- with or without modifications, to be licensed at no charge to all
- third parties under the terms of this General Public License (except
- that you may choose to grant warranty protection to some or all
- third parties, at your option).
-
- c) If the modified program normally reads commands interactively when
- run, you must cause it, when started running for such interactive use
- in the simplest and most usual way, to print or display an
- announcement including an appropriate copyright notice and a notice
- that there is no warranty (or else, saying that you provide a
- warranty) and that users may redistribute the program under these
- conditions, and telling the user how to view a copy of this General
- Public License.
-
- d) You may charge a fee for the physical act of transferring a
- copy, and you may at your option offer warranty protection in
- exchange for a fee.
-
-Mere aggregation of another independent work with the Program (or its
-derivative) on a volume of a storage or distribution medium does not bring
-the other work under the scope of these terms.
-
- 3. You may copy and distribute the Program (or a portion or derivative of
-it, under Paragraph 2) in object code or executable form under the terms of
-Paragraphs 1 and 2 above provided that you also do one of the following:
-
- a) accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- b) accompany it with a written offer, valid for at least three
- years, to give any third party free (except for a nominal charge
- for the cost of distribution) a complete machine-readable copy of the
- corresponding source code, to be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- c) accompany it with the information you received as to where the
- corresponding source code may be obtained. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form alone.)
-
-Source code for a work means the preferred form of the work for making
-modifications to it. For an executable file, complete source code means
-all the source code for all modules it contains; but, as a special
-exception, it need not include source code for modules which are standard
-libraries that accompany the operating system on which the executable
-file runs, or for standard header files or definitions files that
-accompany that operating system.
-
- 4. You may not copy, modify, sublicense, distribute or transfer the
-Program except as expressly provided under this General Public License.
-Any attempt otherwise to copy, modify, sublicense, distribute or transfer
-the Program is void, and will automatically terminate your rights to use
-the Program under this License. However, parties who have received
-copies, or rights to use copies, from you under this General Public
-License will not have their licenses terminated so long as such parties
-remain in full compliance.
-
- 5. By copying, distributing or modifying the Program (or any work based
-on the Program) you indicate your acceptance of this license to do so,
-and all its terms and conditions.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the original
-licensor to copy, distribute or modify the Program subject to these
-terms and conditions. You may not impose any further restrictions on the
-recipients` exercise of the rights granted herein.
-
- 7. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of the license which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-the license, you may choose any version ever published by the Free Software
-Foundation.
-
- 8. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- 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
-the exclusion of warranty; and each file should have at least the
-"copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program`s name and a brief idea of what it does.>
- Copyright (C) 19yy <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 1, or (at your option)
- any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) 19xx name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w`.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c` for details.
-
-The hypothetical commands `show w` and `show c` should show the
-appropriate parts of the General Public License. Of course, the
-commands you use may be called something other than `show w` and `show
-c`; they could even be mouse-clicks or menu items--whatever suits your
-program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the
- program `Gnomovision` (a program to direct compilers to make passes
- at assemblers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-That`s all there is to it!
-
-
-
-
-GPL-2.0
-
-
-GNU GENERAL PUBLIC LICENSE
-
-Version 2, June 1991
-
-Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-Preamble
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public License is intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users. This General Public License applies to most of the Free Software
-Foundation`s software and to any other program whose authors commit to using it. (Some
-other Free Software Foundation software is covered by the GNU Lesser General Public
-License instead.) You can apply it to your programs, too.
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for this service if you wish), that you receive
-source code or can get it if you want it, that you can change the software or use
-pieces of it in new free programs; and that you know you can do these things.
-
-To protect your rights, we need to make restrictions that forbid anyone to deny you
-these rights or to ask you to surrender the rights. These restrictions translate to
-certain responsibilities for you if you distribute copies of the software, or if you
-modify it.
-
-For example, if you distribute copies of such a program, whether gratis or for a fee,
-you must give the recipients all the rights that you have. You must make sure that
-they, too, receive or can get the source code. And you must show them these terms so
-they know their rights.
-
-We protect your rights with two steps: (1) copyright the software, and (2) offer you
-this license which gives you legal permission to copy, distribute and/or modify the
-software.
-
-Also, for each author`s protection and ours, we want to make certain that everyone
-understands that there is no warranty for this free software. If the software is
-modified by someone else and passed on, we want its recipients to know that what they
-have is not the original, so that any problems introduced by others will not reflect
-on the original authors` reputations.
-
-Finally, any free program is threatened constantly by software patents. We wish to
-avoid the danger that redistributors of a free program will individually obtain patent
-licenses, in effect making the program proprietary. To prevent this, we have made it
-clear that any patent must be licensed for everyone`s free use or not licensed at all.
-
-The precise terms and conditions for copying, distribution and modification follow.
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-0. This License applies to any program or other work which contains a notice placed by
-the copyright holder saying it may be distributed under the terms of this General
-Public License. The "Program", below, refers to any such program or work, and a "work
-based on the Program" means either the Program or any derivative work under copyright
-law: that is to say, a work containing the Program or a portion of it, either verbatim
-or with modifications and/or translated into another language. (Hereinafter,
-translation is included without limitation in the term "modification".) Each licensee
-is addressed as "you".
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running the Program is not restricted,
-and the output from the Program is covered only if its contents constitute a work
-based on the Program (independent of having been made by running the Program). Whether
-that is true depends on what the Program does.
-
-1. You may copy and distribute verbatim copies of the Program`s source code as you
-receive it, in any medium, provided that you conspicuously and appropriately publish
-on each copy an appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any warranty; and
-give any other recipients of the Program a copy of this License along with the
-Program.
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-2. You may modify your copy or copies of the Program or any portion of it, thus
-forming a work based on the Program, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-a) You must cause the modified files to carry prominent notices stating that you
-changed the files and the date of any change.
-b) You must cause any work that you distribute or publish, that in whole or in part
-contains or is derived from the Program or any part thereof, to be licensed as a whole
-at no charge to all third parties under the terms of this License.
-c) If the modified program normally reads commands interactively when run, you must
-cause it, when started running for such interactive use in the most ordinary way, to
-print or display an announcement including an appropriate copyright notice and a
-notice that there is no warranty (or else, saying that you provide a warranty) and
-that users may redistribute the program under these conditions, and telling the user
-how to view a copy of this License. (Exception: if the Program itself is interactive
-but does not normally print such an announcement, your work based on the Program is
-not required to print an announcement.)
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Program, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Program,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program with the
-Program (or with a work based on the Program) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-3. You may copy and distribute the Program (or a work based on it, under Section 2) in
-object code or executable form under the terms of Sections 1 and 2 above provided that
-you also do one of the following:
-
-a) Accompany it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a medium customarily
-used for software interchange; or,
-b) Accompany it with a written offer, valid for at least three years, to give any
-third party, for a charge no more than your cost of physically performing source
-distribution, a complete machine-readable copy of the corresponding source code, to be
-distributed under the terms of Sections 1 and 2 above on a medium customarily used for
-software interchange; or,
-c) Accompany it with the information you received as to the offer to distribute
-corresponding source code. (This alternative is allowed only for noncommercial
-distribution and only if you received the program in object code or executable form
-with such an offer, in accord with Subsection b above.)
-The source code for a work means the preferred form of the work for making
-modifications to it. For an executable work, complete source code means all the source
-code for all modules it contains, plus any associated interface definition files, plus
-the scripts used to control compilation and installation of the executable. However,
-as a special exception, the source code distributed need not include anything that is
-normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-If distribution of executable or object code is made by offering access to copy from a
-designated place, then offering equivalent access to copy the source code from the
-same place counts as distribution of the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-4. You may not copy, modify, sublicense, or distribute the Program except as expressly
-provided under this License. Any attempt otherwise to copy, modify, sublicense or
-distribute the Program is void, and will automatically terminate your rights under
-this License. However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such parties remain in
-full compliance.
-
-5. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Program or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Program or works based on it.
-
-6. Each time you redistribute the Program (or any work based on the Program), the
-recipient automatically receives a license from the original licensor to copy,
-distribute or modify the Program subject to these terms and conditions. You may not
-impose any further restrictions on the recipients` exercise of the rights granted
-herein. You are not responsible for enforcing compliance by third parties to this
-License.
-
-7. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Program at all. For example, if a patent license would not permit royalty-free
-redistribution of the Program by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply and the section as a
-whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system,
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-8. If the distribution and/or use of the Program is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Program under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-9. The Free Software Foundation may publish revised and/or new versions of the General
-Public License from time to time. Such new versions will be similar in spirit to the
-present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Program does not
-specify a version number of this License, you may choose any version ever published by
-the Free Software Foundation.
-
-10. If you wish to incorporate parts of the Program into other free programs whose
-distribution conditions are different, write to the author to ask for permission. For
-software which is copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this. Our decision will be
-guided by the two goals of preserving the free status of all derivatives of our free
-software and of promoting the sharing and reuse of software generally.
-
-NO WARRANTY
-
-11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
-WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-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 the "copyright" line and a pointer to where the
-full notice is found.
-
-one line to give the program`s name and an idea of what it does.
-Copyright (C) yyyy name of author
-
-This program is free software; you can redistribute it and/or
-modify it under the terms of the GNU General Public License
-as published by the Free Software Foundation; either version 2
-of the License, or (at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this when it starts
-in an interactive mode:
-
-Gnomovision version 69, Copyright (C) year name of author
-Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
-type `show w`. This is free software, and you are welcome
-to redistribute it under certain conditions; type `show c`
-for details.
-The hypothetical commands `show w` and `show c` should show the appropriate parts of
-the General Public License. Of course, the commands you use may be called something
-other than `show w` and `show c`; they could even be mouse-clicks or menu
-items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample;
-alter the names:
-
-Yoyodyne, Inc., hereby disclaims all copyright
-interest in the program `Gnomovision`
-(which makes passes at compilers) written
-by James Hacker.
-
-signature of Ty Coon, 1 April 1989
-Ty Coon, President of Vice
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may consider it
-more useful to permit linking proprietary applications with the library. If this is
-what you want to do, use the GNU Lesser General Public License instead of this
-License.
-
-
-
-
-GPL-2.0-with-GCC-exception
-
-
-insert GPL v2 text here
-
-GCC Linking Exception
-In addition to the permissions in the GNU General Public License, the Free
-Software Foundation gives you unlimited permission to link the compiled version
-of this file into combinations with other programs, and to distribute those
-combinations without any restriction coming from the use of this file. (The
-General Public License restrictions do apply in other respects; for example,
-they cover modification of the file, and distribution when not linked into a
-combine executable.)
-
-
-
-
-
-
-
-
-
-GPL-2.0-with-classpath-exception
-
-
-insert GPL v2 license text here
-
-Linking this library statically or dynamically with other modules is making a combined
-work based on this library. Thus, the terms and conditions of the GNU General Public
-License cover the whole combination.
-
-As a special exception, the copyright holders of this library give you permission to
-link this library with independent modules to produce an executable, regardless of the
-license terms of these independent modules, and to copy and distribute the resulting
-executable under terms of your choice, provided that you also meet, for each linked
-independent module, the terms and conditions of the license of that module. An
-independent module is a module which is not derived from or based on this library. If
-you modify this library, you may extend this exception to your version of the library,
-but you are not obligated to do so. If you do not wish to do so, delete this exception
-statement from your version.
-
-
-
-
-GPL-3.0
-
-GNU GENERAL PUBLIC LICENSE
-
-Version 3, 29 June 2007
-
-Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-Preamble
-
-The GNU General Public License is a free, copyleft license for software and other
-kinds of works.
-
-The licenses for most software and other practical works are designed to take away
-your freedom to share and change the works. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change all versions of a
-program--to make sure it remains free software for all its users. We, the Free
-Software Foundation, use the GNU General Public License for most of our software; it
-applies also to any other work released this way by its authors. You can apply it to
-your programs, too.
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for them if you wish), that you receive source
-code or can get it if you want it, that you can change the software or use pieces of
-it in new free programs, and that you know you can do these things.
-
-To protect your rights, we need to prevent others from denying you these rights or
-asking you to surrender the rights. Therefore, you have certain responsibilities if
-you distribute copies of the software, or if you modify it: responsibilities to
-respect the freedom of others.
-
-For example, if you distribute copies of such a program, whether gratis or for a fee,
-you must pass on to the recipients the same freedoms that you received. You must make
-sure that they, too, receive or can get the source code. And you must show them these
-terms so they know their rights.
-
-Developers that use the GNU GPL protect your rights with two steps: (1) assert
-copyright on the software, and (2) offer you this License giving you legal permission
-to copy, distribute and/or modify it.
-
-For the developers' and authors' protection, the GPL clearly explains that there is no
-warranty for this free software. For both users' and authors' sake, the GPL requires
-that modified versions be marked as changed, so that their problems will not be
-attributed erroneously to authors of previous versions.
-
-Some devices are designed to deny users access to install or run modified versions of
-the software inside them, although the manufacturer can do so. This is fundamentally
-incompatible with the aim of protecting users' freedom to change the software. The
-systematic pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable. Therefore, we have designed
-this version of the GPL to prohibit the practice for those products. If such problems
-arise substantially in other domains, we stand ready to extend this provision to those
-domains in future versions of the GPL, as needed to protect the freedom of users.
-
-Finally, every program is threatened constantly by software patents. States should not
-allow patents to restrict development and use of software on general-purpose
-computers, but in those that do, we wish to avoid the special danger that patents
-applied to a free program could make it effectively proprietary. To prevent this, the
-GPL assures that patents cannot be used to render the program non-free.
-
-The precise terms and conditions for copying, distribution and modification follow.
-TERMS AND CONDITIONS
-0. Definitions.
-
-”This License” refers to version 3 of the GNU General Public License.
-
-”Copyright” also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-”The Program” refers to any copyrightable work licensed under this
-License. Each licensee is addressed as ”you”. ”Licensees”
-and ”recipients” may be individuals or organizations.
-
-To ”modify” a work means to copy from or adapt all or part of the work in
-a fashion requiring copyright permission, other than the making of an exact copy. The
-resulting work is called a ”modified version” of the earlier work or a
-work ”based on” the earlier work.
-
-A ”covered work” means either the unmodified Program or a work based on
-the Program.
-
-To ”propagate” a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for infringement under
-applicable copyright law, except executing it on a computer or modifying a private
-copy. Propagation includes copying, distribution (with or without modification),
-making available to the public, and in some countries other activities as well.
-
-To ”convey” a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user through a computer
-network, with no transfer of a copy, is not conveying.
-
-An interactive user interface displays ”Appropriate Legal Notices” to the
-extent that it includes a convenient and prominently visible feature that (1) displays
-an appropriate copyright notice, and (2) tells the user that there is no warranty for
-the work (except to the extent that warranties are provided), that licensees may
-convey the work under this License, and how to view a copy of this License. If the
-interface presents a list of user commands or options, such as a menu, a prominent
-item in the list meets this criterion.
-1. Source Code.
-
-The ”source code” for a work means the preferred form of the work for
-making modifications to it. ”Object code” means any non-source form of a
-work.
-
-A ”Standard Interface” means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of interfaces
-specified for a particular programming language, one that is widely used among
-developers working in that language.
-
-The ”System Libraries” of an executable work include anything, other than
-the work as a whole, that (a) is included in the normal form of packaging a Major
-Component, but which is not part of that Major Component, and (b) serves only to
-enable use of the work with that Major Component, or to implement a Standard Interface
-for which an implementation is available to the public in source code form. A
-”Major Component”, in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system (if any) on which
-the executable work runs, or a compiler used to produce the work, or an object code
-interpreter used to run it.
-
-The ”Corresponding Source” for a work in object code form means all the
-source code needed to generate, install, and (for an executable work) run the object
-code and to modify the work, including scripts to control those activities. However,
-it does not include the work's System Libraries, or general-purpose tools or generally
-available free programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source includes interface
-definition files associated with source files for the work, and the source code for
-shared libraries and dynamically linked subprograms that the work is specifically
-designed to require, such as by intimate data communication or control flow between
-those subprograms and other parts of the work.
-
-The Corresponding Source need not include anything that users can regenerate
-automatically from other parts of the Corresponding Source.
-
-The Corresponding Source for a work in source code form is that same work.
-2. Basic Permissions.
-
-All rights granted under this License are granted for the term of copyright on the
-Program, and are irrevocable provided the stated conditions are met. This License
-explicitly affirms your unlimited permission to run the unmodified Program. The output
-from running a covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your rights of fair use
-or other equivalent, as provided by copyright law.
-
-You may make, run and propagate covered works that you do not convey, without
-conditions so long as your license otherwise remains in force. You may convey covered
-works to others for the sole purpose of having them make modifications exclusively for
-you, or provide you with facilities for running those works, provided that you comply
-with the terms of this License in conveying all material for which you do not control
-copyright. Those thus making or running the covered works for you must do so
-exclusively on your behalf, under your direction and control, on terms that prohibit
-them from making any copies of your copyrighted material outside their relationship
-with you.
-
-Conveying under any other circumstances is permitted solely under the conditions
-stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
-3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-No covered work shall be deemed part of an effective technological measure under any
-applicable law fulfilling obligations under article 11 of the WIPO copyright treaty
-adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention
-of such measures.
-
-When you convey a covered work, you waive any legal power to forbid circumvention of
-technological measures to the extent such circumvention is effected by exercising
-rights under this License with respect to the covered work, and you disclaim any
-intention to limit operation or modification of the work as a means of enforcing,
-against the work's users, your or third parties' legal rights to forbid circumvention
-of technological measures.
-4. Conveying Verbatim Copies.
-
-You may convey verbatim copies of the Program's source code as you receive it, in any
-medium, provided that you conspicuously and appropriately publish on each copy an
-appropriate copyright notice; keep intact all notices stating that this License and
-any non-permissive terms added in accord with section 7 apply to the code; keep intact
-all notices of the absence of any warranty; and give all recipients a copy of this
-License along with the Program.
-
-You may charge any price or no price for each copy that you convey, and you may offer
-support or warranty protection for a fee.
-5. Conveying Modified Source Versions.
-
-You may convey a work based on the Program, or the modifications to produce it from
-the Program, in the form of source code under the terms of section 4, provided that
-you also meet all of these conditions:
-
- * a) The work must carry prominent notices stating that you modified it, and
-giving a relevant date.
- * b) The work must carry prominent notices stating that it is released under this
-License and any conditions added under section 7. This requirement modifies the
-requirement in section 4 to ”keep intact all notices”.
- * c) You must license the entire work, as a whole, under this License to anyone
-who comes into possession of a copy. This License will therefore apply, along with any
-applicable section 7 additional terms, to the whole of the work, and all its parts,
-regardless of how they are packaged. This License gives no permission to license the
-work in any other way, but it does not invalidate such permission if you have
-separately received it.
- * d) If the work has interactive user interfaces, each must display Appropriate
-Legal Notices; however, if the Program has interactive interfaces that do not display
-Appropriate Legal Notices, your work need not make them do so.
-
-A compilation of a covered work with other separate and independent works, which are
-not by their nature extensions of the covered work, and which are not combined with it
-such as to form a larger program, in or on a volume of a storage or distribution
-medium, is called an ”aggregate” if the compilation and its resulting
-copyright are not used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work in an aggregate
-does not cause this License to apply to the other parts of the aggregate.
-6. Conveying Non-Source Forms.
-
-You may convey a covered work in object code form under the terms of sections 4 and 5,
-provided that you also convey the machine-readable Corresponding Source under the
-terms of this License, in one of these ways:
-
- * a) Convey the object code in, or embodied in, a physical product (including a
-physical distribution medium), accompanied by the Corresponding Source fixed on a
-durable physical medium customarily used for software interchange.
- * b) Convey the object code in, or embodied in, a physical product (including a
-physical distribution medium), accompanied by a written offer, valid for at least
-three years and valid for as long as you offer spare parts or customer support for
-that product model, to give anyone who possesses the object code either (1) a copy of
-the Corresponding Source for all the software in the product that is covered by this
-License, on a durable physical medium customarily used for software interchange, for a
-price no more than your reasonable cost of physically performing this conveying of
-source, or (2) access to copy the Corresponding Source from a network server at no
-charge.
- * c) Convey individual copies of the object code with a copy of the written offer
-to provide the Corresponding Source. This alternative is allowed only occasionally and
-noncommercially, and only if you received the object code with such an offer, in
-accord with subsection 6b.
- * d) Convey the object code by offering access from a designated place (gratis or
-for a charge), and offer equivalent access to the Corresponding Source in the same way
-through the same place at no further charge. You need not require recipients to copy
-the Corresponding Source along with the object code. If the place to copy the object
-code is a network server, the Corresponding Source may be on a different server
-(operated by you or a third party) that supports equivalent copying facilities,
-provided you maintain clear directions next to the object code saying where to find
-the Corresponding Source. Regardless of what server hosts the Corresponding Source,
-you remain obligated to ensure that it is available for as long as needed to satisfy
-these requirements.
- * e) Convey the object code using peer-to-peer transmission, provided you inform
-other peers where the object code and Corresponding Source of the work are being
-offered to the general public at no charge under subsection 6d.
-
-A separable portion of the object code, whose source code is excluded from the
-Corresponding Source as a System Library, need not be included in conveying the object
-code work.
-
-A ”User Product” is either (1) a ”consumer product”, which
-means any tangible personal property which is normally used for personal, family, or
-household purposes, or (2) anything designed or sold for incorporation into a
-dwelling. In determining whether a product is a consumer product, doubtful cases shall
-be resolved in favor of coverage. For a particular product received by a particular
-user, ”normally used” refers to a typical or common use of that class of
-product, regardless of the status of the particular user or of the way in which the
-particular user actually uses, or expects or is expected to use, the product. A
-product is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent the only
-significant mode of use of the product.
-
-”Installation Information” for a User Product means any methods,
-procedures, authorization keys, or other information required to install and execute
-modified versions of a covered work in that User Product from a modified version of
-its Corresponding Source. The information must suffice to ensure that the continued
-functioning of the modified object code is in no case prevented or interfered with
-solely because modification has been made.
-
-If you convey an object code work under this section in, or with, or specifically for
-use in, a User Product, and the conveying occurs as part of a transaction in which the
-right of possession and use of the User Product is transferred to the recipient in
-perpetuity or for a fixed term (regardless of how the transaction is characterized),
-the Corresponding Source conveyed under this section must be accompanied by the
-Installation Information. But this requirement does not apply if neither you nor any
-third party retains the ability to install modified object code on the User Product
-(for example, the work has been installed in ROM).
-
-The requirement to provide Installation Information does not include a requirement to
-continue to provide support service, warranty, or updates for a work that has been
-modified or installed by the recipient, or for the User Product in which it has been
-modified or installed. Access to a network may be denied when the modification itself
-materially and adversely affects the operation of the network or violates the rules
-and protocols for communication across the network.
-
-Corresponding Source conveyed, and Installation Information provided, in accord with
-this section must be in a format that is publicly documented (and with an
-implementation available to the public in source code form), and must require no
-special password or key for unpacking, reading or copying.
-7. Additional Terms.
-
-”Additional permissions” are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions. Additional
-permissions that are applicable to the entire Program shall be treated as though they
-were included in this License, to the extent that they are valid under applicable law.
-If additional permissions apply only to part of the Program, that part may be used
-separately under those permissions, but the entire Program remains governed by this
-License without regard to the additional permissions.
-
-When you convey a copy of a covered work, you may at your option remove any additional
-permissions from that copy, or from any part of it. (Additional permissions may be
-written to require their own removal in certain cases when you modify the work.) You
-may place additional permissions on material, added by you to a covered work, for
-which you have or can give appropriate copyright permission.
-
-Notwithstanding any other provision of this License, for material you add to a covered
-work, you may (if authorized by the copyright holders of that material) supplement the
-terms of this License with terms:
-
- * a) Disclaiming warranty or limiting liability differently from the terms of
-sections 15 and 16 of this License; or
- * b) Requiring preservation of specified reasonable legal notices or author
-attributions in that material or in the Appropriate Legal Notices displayed by works
-containing it; or
- * c) Prohibiting misrepresentation of the origin of that material, or requiring
-that modified versions of such material be marked in reasonable ways as different from
-the original version; or
- * d) Limiting the use for publicity purposes of names of licensors or authors of
-the material; or
- * e) Declining to grant rights under trademark law for use of some trade names,
-trademarks, or service marks; or
- * f) Requiring indemnification of licensors and authors of that material by anyone
-who conveys the material (or modified versions of it) with contractual assumptions of
-liability to the recipient, for any liability that these contractual assumptions
-directly impose on those licensors and authors.
-
-All other non-permissive additional terms are considered ”further
-restrictions” within the meaning of section 10. If the Program as you received
-it, or any part of it, contains a notice stating that it is governed by this License
-along with a term that is a further restriction, you may remove that term. If a
-license document contains a further restriction but permits relicensing or conveying
-under this License, you may add to a covered work material governed by the terms of
-that license document, provided that the further restriction does not survive such
-relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you must place, in the
-relevant source files, a statement of the additional terms that apply to those files,
-or a notice indicating where to find the applicable terms.
-
-Additional terms, permissive or non-permissive, may be stated in the form of a
-separately written license, or stated as exceptions; the above requirements apply
-either way.
-8. Termination.
-
-You may not propagate or modify a covered work except as expressly provided under this
-License. Any attempt otherwise to propagate or modify it is void, and will
-automatically terminate your rights under this License (including any patent licenses
-granted under the third paragraph of section 11).
-
-However, if you cease all violation of this License, then your license from a
-particular copyright holder is reinstated (a) provisionally, unless and until the
-copyright holder explicitly and finally terminates your license, and (b) permanently,
-if the copyright holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is reinstated permanently if
-the copyright holder notifies you of the violation by some reasonable means, this is
-the first time you have received notice of violation of this License (for any work)
-from that copyright holder, and you cure the violation prior to 30 days after your
-receipt of the notice.
-
-Termination of your rights under this section does not terminate the licenses of
-parties who have received copies or rights from you under this License. If your rights
-have been terminated and not permanently reinstated, you do not qualify to receive new
-licenses for the same material under section 10.
-9. Acceptance Not Required for Having Copies.
-
-You are not required to accept this License in order to receive or run a copy of the
-Program. Ancillary propagation of a covered work occurring solely as a consequence of
-using peer-to-peer transmission to receive a copy likewise does not require
-acceptance. However, nothing other than this License grants you permission to
-propagate or modify any covered work. These actions infringe copyright if you do not
-accept this License. Therefore, by modifying or propagating a covered work, you
-indicate your acceptance of this License to do so.
-10. Automatic Licensing of Downstream Recipients.
-
-Each time you convey a covered work, the recipient automatically receives a license
-from the original licensors, to run, modify and propagate that work, subject to this
-License. You are not responsible for enforcing compliance by third parties with this
-License.
-
-An ”entity transaction” is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an organization, or
-merging organizations. If propagation of a covered work results from an entity
-transaction, each party to that transaction who receives a copy of the work also
-receives whatever licenses to the work the party's predecessor in interest had or
-could give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if the predecessor
-has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the rights granted or
-affirmed under this License. For example, you may not impose a license fee, royalty,
-or other charge for exercise of rights granted under this License, and you may not
-initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging
-that any patent claim is infringed by making, using, selling, offering for sale, or
-importing the Program or any portion of it.
-11. Patents.
-
-A ”contributor” is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The work thus licensed
-is called the contributor's ”contributor version”.
-
-A contributor's ”essential patent claims” are all patent claims owned or
-controlled by the contributor, whether already acquired or hereafter acquired, that
-would be infringed by some manner, permitted by this License, of making, using, or
-selling its contributor version, but do not include claims that would be infringed
-only as a consequence of further modification of the contributor version. For purposes
-of this definition, ”control” includes the right to grant patent
-sublicenses in a manner consistent with the requirements of this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free patent license
-under the contributor's essential patent claims, to make, use, sell, offer for sale,
-import and otherwise run, modify and propagate the contents of its contributor
-version.
-
-In the following three paragraphs, a ”patent license” is any express
-agreement or commitment, however denominated, not to enforce a patent (such as an
-express permission to practice a patent or covenant not to sue for patent
-infringement). To ”grant” such a patent license to a party means to make
-such an agreement or commitment not to enforce a patent against the party.
-
-If you convey a covered work, knowingly relying on a patent license, and the
-Corresponding Source of the work is not available for anyone to copy, free of charge
-and under the terms of this License, through a publicly available network server or
-other readily accessible means, then you must either (1) cause the Corresponding
-Source to be so available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner consistent with
-the requirements of this License, to extend the patent license to downstream
-recipients. ”Knowingly relying” means you have actual knowledge that, but
-for the patent license, your conveying the covered work in a country, or your
-recipient's use of the covered work in a country, would infringe one or more
-identifiable patents in that country that you have reason to believe are valid.
-
-If, pursuant to or in connection with a single transaction or arrangement, you convey,
-or propagate by procuring conveyance of, a covered work, and grant a patent license to
-some of the parties receiving the covered work authorizing them to use, propagate,
-modify or convey a specific copy of the covered work, then the patent license you
-grant is automatically extended to all recipients of the covered work and works based
-on it.
-
-A patent license is ”discriminatory” if it does not include within the
-scope of its coverage, prohibits the exercise of, or is conditioned on the
-non-exercise of one or more of the rights that are specifically granted under this
-License. You may not convey a covered work if you are a party to an arrangement with a
-third party that is in the business of distributing software, under which you make
-payment to the third party based on the extent of your activity of conveying the work,
-and under which the third party grants, to any of the parties who would receive the
-covered work from you, a discriminatory patent license (a) in connection with copies
-of the covered work conveyed by you (or copies made from those copies), or (b)
-primarily for and in connection with specific products or compilations that contain
-the covered work, unless you entered into that arrangement, or that patent license was
-granted, prior to 28 March 2007.
-
-Nothing in this License shall be construed as excluding or limiting any implied
-license or other defenses to infringement that may otherwise be available to you under
-applicable patent law.
-12. No Surrender of Others' Freedom.
-
-If conditions are imposed on you (whether by court order, agreement or otherwise) that
-contradict the conditions of this License, they do not excuse you from the conditions
-of this License. If you cannot convey a covered work so as to satisfy simultaneously
-your obligations under this License and any other pertinent obligations, then as a
-consequence you may not convey it at all. For example, if you agree to terms that
-obligate you to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this License would be
-to refrain entirely from conveying the Program.
-13. Use with the GNU Affero General Public License.
-
-Notwithstanding any other provision of this License, you have permission to link or
-combine any covered work with a work licensed under version 3 of the GNU Affero
-General Public License into a single combined work, and to convey the resulting work.
-The terms of this License will continue to apply to the part which is the covered
-work, but the special requirements of the GNU Affero General Public License, section
-13, concerning interaction through a network will apply to the combination as such.
-14. Revised Versions of this License.
-
-The Free Software Foundation may publish revised and/or new versions of the GNU
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program specifies that a
-certain numbered version of the GNU General Public License ”or any later
-version” applies to it, you have the option of following the terms and
-conditions either of that numbered version or of any later version published by the
-Free Software Foundation. If the Program does not specify a version number of the GNU
-General Public License, you may choose any version ever published by the Free Software
-Foundation.
-
-If the Program specifies that a proxy can decide which future versions of the GNU
-General Public License can be used, that proxy's public statement of acceptance of a
-version permanently authorizes you to choose that version for the Program.
-
-Later license versions may give you additional or different permissions. However, no
-additional obligations are imposed on any author or copyright holder as a result of
-your choosing to follow a later version.
-15. Disclaimer of Warranty.
-
-THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM ”AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
-EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
-QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
-DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-16. Limitation of Liability.
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
-WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-17. Interpretation of Sections 15 and 16.
-
-If the disclaimer of warranty and limitation of liability provided above cannot be
-given local legal effect according to their terms, reviewing courts shall apply local
-law that most closely approximates an absolute waiver of all civil liability in
-connection with the Program, unless a warranty or assumption of liability accompanies
-a copy of the Program in return for a fee.
-
-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 the ”copyright” line and a pointer to
-where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program does terminal interaction, make it output a short notice like this when
-it starts in an interactive mode:
-
- <program> Copyright (C) <year> <name of author>
- This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate parts of
-the General Public License. Of course, your program's commands might be different; for
-a GUI interface, you would use an ”about box”.
-
-You should also get your employer (if you work as a programmer) or school, if any, to
-sign a ”copyright disclaimer” for the program, if necessary. For more
-information on this, and how to apply and follow the GNU GPL, see
-<http://www.gnu.org/licenses/>.
-
-The GNU General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may consider it
-more useful to permit linking proprietary applications with the library. If this is
-what you want to do, use the GNU Lesser General Public License instead of this
-License. But first, please read
-<http://www.gnu.org/philosophy/why-not-lgpl.html>.
-
-
-
-GPL-3.0-with-GCC-exception
-
-
-insert GPL v3 text here
-
-GCC RUNTIME LIBRARY EXCEPTION
-Version 3.1, 31 March 2009
-
-General information:
-http://www.gnu.org/licenses/gcc-exception.html
-Copyright (C) 2009 Free Software Foundation, Inc. <http://fsf.org/>
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-This GCC Runtime Library Exception ("Exception") is an additional permission under
-section 7 of the GNU General Public License, version 3 ("GPLv3"). It applies to a
-given file (the "Runtime Library") that bears a notice placed by the copyright holder
-of the file stating that the file is governed by GPLv3 along with this Exception.
-When you use GCC to compile a program, GCC may combine portions of certain GCC header
-files and runtime libraries with the compiled program. The purpose of this Exception
-is to allow compilation of non-GPL (including proprietary) programs to use, in this
-way, the header files and runtime libraries covered by this Exception.
-
-0. Definitions.
-A file is an "Independent Module" if it either requires the Runtime Library for
-execution after a Compilation Process, or makes use of an interface provided by the
-Runtime Library, but is not otherwise based on the Runtime Library.
-"GCC" means a version of the GNU Compiler Collection, with or without modifications,
-governed by version 3 (or a specified later version) of the GNU General Public License
-(GPL) with the option of using any subsequent versions published by the FSF.
-"GPL-compatible Software" is software whose conditions of propagation, modification
-and use would permit combination with GCC in accord with the license of GCC.
-"Target Code" refers to output from any compiler for a real or virtual target
-processor architecture, in executable form or suitable for input to an assembler,
-loader, linker and/or execution phase. Notwithstanding that, Target Code does not
-include data in any format that is used as a compiler intermediate representation, or
-used for producing a compiler intermediate representation.
-The "Compilation Process" transforms code entirely represented in non-intermediate
-languages designed for human-written code, and/or in Java Virtual Machine byte code,
-into Target Code. Thus, for example, use of source code generators and preprocessors
-need not be considered part of the Compilation Process, since the Compilation Process
-can be understood as starting with the output of the generators or preprocessors.
-A Compilation Process is "Eligible" if it is done using GCC, alone or with other
-GPL-compatible software, or if it is done without using any work based on GCC. For
-example, using non-GPL-compatible Software to optimize any GCC intermediate
-representations would not qualify as an Eligible Compilation Process.
-
-1. Grant of Additional Permission.
-You have permission to propagate a work of Target Code formed by combining the Runtime
-Library with Independent Modules, even if such propagation would otherwise violate the
-terms of GPLv3, provided that all Target Code was generated by Eligible Compilation
-Processes. You may then convey such a combination under terms of your choice,
-consistent with the licensing of the Independent Modules.
-
-2. No Weakening of GCC Copyleft.
-The availability of this Exception does not imply any general presumption that
-third-party software is unaffected by the copyleft requirements of the license of GCC.
-
-
-
-
-GPL-3.0-with-autoconf-exception
-
-
-insert GPL v3 text here
-
-AUTOCONF CONFIGURE SCRIPT EXCEPTION
-
-Version 3.0, 18 August 2009
-
-Copyright © 2009 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-
-This Exception is an additional permission under section 7 of the GNU General Public
-License, version 3 ("GPLv3"). It applies to a given file that bears a notice placed by
-the copyright holder of the file stating that the file is governed by GPLv3 along with
-this Exception.
-
-The purpose of this Exception is to allow distribution of Autoconf`s typical output
-under terms of the recipient`s choice (including proprietary).
-
-0. Definitions.
-"Covered Code" is the source or object code of a version of Autoconf that is a covered
-work under this License.
-
-"Normally Copied Code" for a version of Autoconf means all parts of its Covered Code
-which that version can copy from its code (i.e., not from its input file) into its
-minimally verbose, non-debugging and non-tracing output.
-
-"Ineligible Code" is Covered Code that is not Normally Copied Code.
-
-1. Grant of Additional Permission.
-You have permission to propagate output of Autoconf, even if such propagation would
-otherwise violate the terms of GPLv3. However, if by modifying Autoconf you cause any
-Ineligible Code of the version you received to become Normally Copied Code of your
-modified version, then you void this Exception for the resulting covered work. If you
-convey that resulting covered work, you must remove this Exception in accordance with
-the second paragraph of Section 7 of GPLv3.
-
-2. No Weakening of Autoconf Copyleft.
-The availability of this Exception does not imply any general presumption that
-third-party software is unaffected by the copyleft requirements of the license of
-Autoconf.
-
-
-
-
-ICU
-
-COPYRIGHT AND PERMISSION NOTICE
-
-Copyright (c) 1995-2012 International Business Machines Corporation and others
-
-All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this
-software and associated documentation files (the "Software"), to deal in the Software
-without restriction, including without limitation the rights to use, copy, modify,
-merge, publish, distribute, and/or sell copies of the Software, and to permit persons
-to whom the Software is furnished to do so, provided that the above copyright
-notice(s) and this permission notice appear in all copies of the Software and that
-both the above copyright notice(s) and this permission notice appear in supporting
-documentation.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
-INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
-PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
-COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
-SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
-LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
-TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
-SOFTWARE.
-
-Except as contained in this notice, the name of a copyright holder shall not be used
-in advertising or otherwise to promote the sale, use or other dealings in this
-Software without prior written authorization of the copyright holder.
-
-All trademarks and registered trademarks mentioned herein are the property of their
-respective owners.
-
-
-
-IPL-1.0
-
-
-IBM Public License Version 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM
-PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
-OF THE PROGRAM CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-"Contribution" means:
-
-in the case of International Business Machines Corporation ("IBM"), the Original
-Program, and
-in the case of each Contributor,
-changes to the Program, and
-additions to the Program;
-where such changes and/or additions to the Program originate from and
-are distributed by that particular Contributor. A Contribution
-`originates` from a Contributor if it was added to the Program by
-such Contributor itself or anyone acting on such Contributor`s
-behalf. Contributions do not include additions to the Program which:
-(i) are separate modules of software distributed in conjunction with
-the Program under their own license agreement, and (ii) are not
-derivative works of the Program.
-
-"Contributor" means IBM and any other entity that distributes the Program.
-
-"Licensed Patents " mean patent claims licensable by a
-Contributor which are necessarily infringed by the use or sale of its
-Contribution alone or when combined with the Program.
-
-"Original Program" means the original version of the software
-accompanying this Agreement as released by IBM, including source
-code, object code and documentation, if any.
-
-"Program" means the Original Program and Contributions.
-
-"Recipient" means anyone who receives the Program under this
-Agreement, including all Contributors.
-
-2. GRANT OF RIGHTS
-Subject to the terms of this Agreement, each Contributor hereby
-grants Recipient a non-exclusive, worldwide, royalty-free copyright
-license to reproduce, prepare derivative works of, publicly display,
-publicly perform, distribute and sublicense the Contribution of such
-Contributor, if any, and such derivative works, in source code and
-object code form.
-Subject to the terms of this Agreement, each Contributor hereby
-grants Recipient a non-exclusive, worldwide, royalty-free patent
-license under Licensed Patents to make, use, sell, offer to sell,
-import and otherwise transfer the Contribution of such Contributor,
-if any, in source code and object code form. This patent license
-shall apply to the combination of the Contribution and the Program
-if, at the time the Contribution is added by the Contributor, such
-addition of the Contribution causes such combination to be covered by
-the Licensed Patents. The patent license shall not apply to any
-other combinations which include the Contribution. No hardware per
-se is licensed hereunder.
-
-Recipient understands that although each Contributor grants the
-licenses to its Contributions set forth herein, no assurances are
-provided by any Contributor that the Program does not infringe the
-patent or other intellectual property rights of any other entity.
-Each Contributor disclaims any liability to Recipient for claims
-brought by any other entity based on infringement of intellectual
-property rights or otherwise. As a condition to exercising the
-rights and licenses granted hereunder, each Recipient hereby assumes
-sole responsibility to secure any other intellectual property rights
-needed, if any. For example, if a third party patent license is
-required to allow Recipient to distribute the Program, it is
-Recipient`s responsibility to acquire that license before
-distributing the Program.
-Each Contributor represents that to its knowledge it has
-sufficient copyright rights in its Contribution, if any, to grant the
-copyright license set forth in this Agreement.
-3. REQUIREMENTS
-A Contributor may choose to distribute
-the Program in object code form under its own license agreement,
-provided that:
-
-it complies with the terms and conditions of this Agreement; and
-its license agreement:
-effectively disclaims on behalf of all Contributors all warranties
-and conditions, express and implied, including warranties or
-conditions of title and non-infringement, and implied warranties or
-conditions of merchantability and fitness for a particular purpose;
-effectively excludes on behalf of all Contributors all liability
-for damages, including direct, indirect, special, incidental and
-consequential damages, such as lost profits;
-states that any provisions which differ from this Agreement are
-offered by that Contributor alone and not by any other party; and
-
-states that source code for the Program is available from such
-Contributor, and informs licensees how to obtain it in a reasonable
-manner on or through a medium customarily used for software exchange.
-When the Program is made available in source code form:
-
-it must be made available under this Agreement; and
-a copy of this Agreement must be included with each copy of the
-Program.
-Each Contributor must include the following in a conspicuous location in the Program:
-
-Copyright (C) 1996, 1999 International Business Machines Corporation and others. All
-Rights Reserved.
-
-In addition, each Contributor must identify itself as the originator
-of its Contribution, if any, in a manner that reasonably allows
-subsequent Recipients to identify the originator of the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-Commercial distributors of software may accept certain
-responsibilities with respect to end users, business partners and the
-like. While this license is intended to facilitate the commercial
-use of the Program, the Contributor who includes the Program in a
-commercial product offering should do so in a manner which does not
-create potential liability for other Contributors. Therefore, if a
-Contributor includes the Program in a commercial product offering,
-such Contributor ("Commercial Contributor") hereby agrees to defend
-and indemnify every other Contributor ("Indemnified Contributor")
-against any losses, damages and costs (collectively "Losses") arising
-from claims, lawsuits and other legal actions brought by a third
-party against the Indemnified Contributor to the extent caused by the
-acts or omissions of such Commercial Contributor in connection with
-its distribution of the Program in a commercial product offering.
-The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement.
-In order to qualify, an Indemnified Contributor must: a) promptly
-notify the Commercial Contributor in writing of such claim, and b)
-allow the Commercial Contributor to control, and cooperate with the
-Commercial Contributor in, the defense and any related settlement
-negotiations. The Indemnified Contributor may participate in any
-such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial
-product offering, Product X. That Contributor is then a Commercial
-Contributor. If that Commercial Contributor then makes performance
-claims, or offers warranties related to Product X, those performance
-claims and warranties are such Commercial Contributor`s
-responsibility alone. Under this section, the Commercial Contributor
-would have to defend claims against the other Contributors related to
-those performance claims and warranties, and if a court requires any
-other Contributor to pay any damages as a result, the Commercial
-Contributor must pay those damages.
-
-5. NO WARRANTY
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS
-PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
-WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY
-OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
-responsible for determining the appropriateness of using and
-distributing the Program and assumes all risks associated with its
-exercise of rights under this Agreement, including but not limited to
-the risks and costs of program errors, compliance with applicable
-laws, damage to or loss of data, programs or equipment, and
-unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT
-NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
-TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
-THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
-GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-If any provision of this Agreement is invalid or unenforceable under
-applicable law, it shall not affect the validity or enforceability of
-the remainder of the terms of this Agreement, and without further
-action by the parties hereto, such provision shall be reformed to the
-minimum extent necessary to make such provision valid and enforceable.
-
-If Recipient institutes patent litigation against a Contributor with
-respect to a patent applicable to software (including a cross-claim
-or counterclaim in a lawsuit), then any patent licenses granted by
-that Contributor to such Recipient under this Agreement shall
-terminate as of the date such litigation is filed. In addition, if
-Recipient institutes patent litigation against any entity (including
-a cross-claim or counterclaim in a lawsuit) alleging that the Program
-itself (excluding combinations of the Program with other software or
-hardware) infringes such Recipient`s patent(s), then such Recipient`s
-rights granted under Section 2(b) shall terminate as of the date such
-litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it
-fails to comply with any of the material terms or conditions of this
-Agreement and does not cure such failure in a reasonable period of
-time after becoming aware of such noncompliance. If all Recipient`s
-rights under this Agreement terminate, Recipient agrees to cease use
-and distribution of the Program as soon as reasonably practicable.
-However, Recipient`s obligations under this Agreement and any
-licenses granted by Recipient relating to the Program shall continue
-and survive.
-
-IBM may publish new versions (including revisions) of this Agreement
-from time to time. Each new version of the Agreement will be given a
-distinguishing version number. The Program (including Contributions)
-may always be distributed subject to the version of the Agreement
-under which it was received. In addition, after a new version of the
-Agreement is published, Contributor may elect to distribute the
-Program (including its Contributions) under the new version. No one
-other than IBM has the right to modify this Agreement. Except as
-expressly stated in Sections 2(a) and 2(b) above, Recipient receives
-no rights or licenses to the intellectual property of any Contributor
-under this Agreement, whether expressly, by implication, estoppel or
-otherwise. All rights in the Program not expressly granted under
-this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and
-the intellectual property laws of the United States of America. No
-party to this Agreement will bring a legal action under this
-Agreement more than one year after the cause of action arose. Each
-party waives its rights to a jury trial in any resulting litigation.
-
-
-
-
-ISC
-
-
-ISC License:
-
-Copyright © 2004-2010 by Internet Systems Consortium, Inc. ("ISC")
-Copyright © 1995-2003 by Internet Software Consortium
-
-Permission to use, copy, modify, and/or distribute this software for any purpose with
-or without fee is hereby granted, provided that the above copyright notice and this
-permission notice appear in all copies.
-
-THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
-SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT
-SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
-DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
-OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
-THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
-
-
-
-JLEX
-
- JLEX COPYRIGHT NOTICE, LICENSE, AND DISCLAIMER
- Copyright 1996-2000 by Elliot Joel Berk and C. Scott Ananian
-
- Permission to use, copy, modify, and distribute this software and its
- documentation for any purpose and without fee is hereby granted,
- provided that the above copyright notice appear in all copies and that
- both the copyright notice and this permission notice and warranty
- disclaimer appear in supporting documentation, and that the name of
- the authors or their employers not be used in advertising or publicity
- pertaining to distribution of the software without specific, written
- prior permission.
-
- The authors and their employers disclaim all warranties with regard to
- this software, including all implied warranties of merchantability and
- fitness. In no event shall the authors or their employers be liable
- for any special, indirect or consequential damages or any damages
- whatsoever resulting from loss of use, data or profits, whether in an
- action of contract, negligence or other tortious action, arising out
- of or in connection with the use or performance of this software.
-
-
-
-LGPL-2.0
-
-GNU LIBRARY GENERAL PUBLIC LICENSE
-
-
-
-Version 2, June 1991
-
-
-
-Copyright (C) 1991 Free Software Foundation, Inc.
-
-51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
-
-Everyone is permitted to copy and distribute verbatim copies
-
-of this license document, but changing it is not allowed.
-
-
-
-[This is the first released version of the library GPL. It is
-
- numbered 2 because it goes with version 2 of the ordinary GPL.]
-
-Preamble
-
-
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public Licenses are intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users.
-
-
-
-This license, the Library General Public License, applies to some specially designated
-Free Software Foundation software, and to any other libraries whose authors decide to
-use it. You can use it for your libraries, too.
-
-
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for this service if you wish), that you receive
-source code or can get it if you want it, that you can change the software or use
-pieces of it in new free programs; and that you know you can do these things.
-
-
-
-To protect your rights, we need to make restrictions that forbid anyone to deny you
-these rights or to ask you to surrender the rights. These restrictions translate to
-certain responsibilities for you if you distribute copies of the library, or if you
-modify it.
-
-
-
-For example, if you distribute copies of the library, whether gratis or for a fee, you
-must give the recipients all the rights that we gave you. You must make sure that
-they, too, receive or can get the source code. If you link a program with the library,
-you must provide complete object files to the recipients so that they can relink them
-with the library, after making changes to the library and recompiling it. And you must
-show them these terms so they know their rights.
-
-
-
-Our method of protecting your rights has two steps: (1) copyright the library, and (2)
-offer you this license which gives you legal permission to copy, distribute and/or
-modify the library.
-
-
-
-Also, for each distributor's protection, we want to make certain that everyone
-understands that there is no warranty for this free library. If the library is
-modified by someone else and passed on, we want its recipients to know that what they
-have is not the original version, so that any problems introduced by others will not
-reflect on the original authors' reputations.
-
-
-
-Finally, any free program is threatened constantly by software patents. We wish to
-avoid the danger that companies distributing free software will individually obtain
-patent licenses, thus in effect transforming the program into proprietary software. To
-prevent this, we have made it clear that any patent must be licensed for everyone's
-free use or not licensed at all.
-
-
-
-Most GNU software, including some libraries, is covered by the ordinary GNU General
-Public License, which was designed for utility programs. This license, the GNU Library
-General Public License, applies to certain designated libraries. This license is quite
-different from the ordinary one; be sure to read it in full, and don't assume that
-anything in it is the same as in the ordinary license.
-
-
-
-The reason we have a separate public license for some libraries is that they blur the
-distinction we usually make between modifying or adding to a program and simply using
-it. Linking a program with a library, without changing the library, is in some sense
-simply using the library, and is analogous to running a utility program or application
-program. However, in a textual and legal sense, the linked executable is a combined
-work, a derivative of the original library, and the ordinary General Public License
-treats it as such.
-
-
-
-Because of this blurred distinction, using the ordinary General Public License for
-libraries did not effectively promote software sharing, because most developers did
-not use the libraries. We concluded that weaker conditions might promote sharing
-better.
-
-
-
-However, unrestricted linking of non-free programs would deprive the users of those
-programs of all benefit from the free status of the libraries themselves. This Library
-General Public License is intended to permit developers of non-free programs to use
-free libraries, while preserving your freedom as a user of such programs to change the
-free libraries that are incorporated in them. (We have not seen how to achieve this as
-regards changes in header files, but we have achieved it as regards changes in the
-actual functions of the Library.) The hope is that this will lead to faster
-development of free libraries.
-
-
-
-The precise terms and conditions for copying, distribution and modification follow.
-Pay close attention to the difference between a "work based on the library" and a
-"work that uses the library". The former contains code derived from the library, while
-the latter only works together with the library.
-
-
-
-Note that it is possible for a library to be covered by the ordinary General Public
-License rather than by this special one.
-
-
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-
-
-0. This License Agreement applies to any software library which contains a notice
-placed by the copyright holder or other authorized party saying it may be distributed
-under the terms of this Library General Public License (also called "this License").
-Each licensee is addressed as "you".
-
-
-
-A "library" means a collection of software functions and/or data prepared so as to be
-conveniently linked with application programs (which use some of those functions and
-data) to form executables.
-
-
-
-The "Library", below, refers to any such software library or work which has been
-distributed under these terms. A "work based on the Library" means either the Library
-or any derivative work under copyright law: that is to say, a work containing the
-Library or a portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is included without
-limitation in the term "modification".)
-
-
-
-"Source code" for a work means the preferred form of the work for making modifications
-to it. For a library, complete source code means all the source code for all modules
-it contains, plus any associated interface definition files, plus the scripts used to
-control compilation and installation of the library.
-
-
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running a program using the Library is
-not restricted, and output from such a program is covered only if its contents
-constitute a work based on the Library (independent of the use of the Library in a
-tool for writing it). Whether that is true depends on what the Library does and what
-the program that uses the Library does.
-
-
-
-1. You may copy and distribute verbatim copies of the Library's complete source code
-as you receive it, in any medium, provided that you conspicuously and appropriately
-publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
-intact all the notices that refer to this License and to the absence of any warranty;
-and distribute a copy of this License along with the Library.
-
-
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-
-
-2. You may modify your copy or copies of the Library or any portion of it, thus
-forming a work based on the Library, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-
-
-a) The modified work must itself be a software library.
-
-b) You must cause the files modified to carry prominent notices stating that you
-changed the files and the date of any change.
-
-c) You must cause the whole of the work to be licensed at no charge to all third
-parties under the terms of this License.
-
-d) If a facility in the modified Library refers to a function or a table of data to be
-supplied by an application program that uses the facility, other than as an argument
-passed when the facility is invoked, then you must make a good faith effort to ensure
-that, in the event an application does not supply such function or table, the facility
-still operates, and performs whatever part of its purpose remains meaningful.
-
-(For example, a function in a library to compute square roots has a purpose that is
-entirely well-defined independent of the application. Therefore, Subsection 2d
-requires that any application-supplied function or table used by this function must be
-optional: if the application does not supply it, the square root function must still
-compute square roots.)
-
-
-
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Library, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Library,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Library.
-
-
-
-In addition, mere aggregation of another work not based on the Library with the
-Library (or with a work based on the Library) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-
-
-3. You may opt to apply the terms of the ordinary GNU General Public License instead
-of this License to a given copy of the Library. To do this, you must alter all the
-notices that refer to this License, so that they refer to the ordinary GNU General
-Public License, version 2, instead of to this License. (If a newer version than
-version 2 of the ordinary GNU General Public License has appeared, then you can
-specify that version instead if you wish.) Do not make any other change in these
-notices.
-
-
-
-Once this change is made in a given copy, it is irreversible for that copy, so the
-ordinary GNU General Public License applies to all subsequent copies and derivative
-works made from that copy.
-
-
-
-This option is useful when you wish to copy part of the code of the Library into a
-program that is not a library.
-
-
-
-4. You may copy and distribute the Library (or a portion or derivative of it, under
-Section 2) in object code or executable form under the terms of Sections 1 and 2 above
-provided that you accompany it with the complete corresponding machine-readable source
-code, which must be distributed under the terms of Sections 1 and 2 above on a medium
-customarily used for software interchange.
-
-
-
-If distribution of object code is made by offering access to copy from a designated
-place, then offering equivalent access to copy the source code from the same place
-satisfies the requirement to distribute the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-
-
-5. A program that contains no derivative of any portion of the Library, but is
-designed to work with the Library by being compiled or linked with it, is called a
-"work that uses the Library". Such a work, in isolation, is not a derivative work of
-the Library, and therefore falls outside the scope of this License.
-
-
-
-However, linking a "work that uses the Library" with the Library creates an executable
-that is a derivative of the Library (because it contains portions of the Library),
-rather than a "work that uses the library". The executable is therefore covered by
-this License. Section 6 states terms for distribution of such executables.
-
-
-
-When a "work that uses the Library" uses material from a header file that is part of
-the Library, the object code for the work may be a derivative work of the Library even
-though the source code is not. Whether this is true is especially significant if the
-work can be linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
-
-
-If such an object file uses only numerical parameters, data structure layouts and
-accessors, and small macros and small inline functions (ten lines or less in length),
-then the use of the object file is unrestricted, regardless of whether it is legally a
-derivative work. (Executables containing this object code plus portions of the Library
-will still fall under Section 6.)
-
-
-
-Otherwise, if the work is a derivative of the Library, you may distribute the object
-code for the work under the terms of Section 6. Any executables containing that work
-also fall under Section 6, whether or not they are linked directly with the Library
-itself.
-
-
-
-6. As an exception to the Sections above, you may also compile or link a "work that
-uses the Library" with the Library to produce a work containing portions of the
-Library, and distribute that work under terms of your choice, provided that the terms
-permit modification of the work for the customer's own use and reverse engineering for
-debugging such modifications.
-
-
-
-You must give prominent notice with each copy of the work that the Library is used in
-it and that the Library and its use are covered by this License. You must supply a
-copy of this License. If the work during execution displays copyright notices, you
-must include the copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one of these things:
-
-
-
-a) Accompany the work with the complete corresponding machine-readable source code for
-the Library including whatever changes were used in the work (which must be
-distributed under Sections 1 and 2 above); and, if the work is an executable linked
-with the Library, with the complete machine-readable "work that uses the Library", as
-object code and/or source code, so that the user can modify the Library and then
-relink to produce a modified executable containing the modified Library. (It is
-understood that the user who changes the contents of definitions files in the Library
-will not necessarily be able to recompile the application to use the modified
-definitions.)
-
-b) Accompany the work with a written offer, valid for at least three years, to give
-the same user the materials specified in Subsection 6a, above, for a charge no more
-than the cost of performing this distribution.
-
-c) If distribution of the work is made by offering access to copy from a designated
-place, offer equivalent access to copy the above specified materials from the same
-place.
-
-d) Verify that the user has already received a copy of these materials or that you
-have already sent this user a copy.
-
-For an executable, the required form of the "work that uses the Library" must include
-any data and utility programs needed for reproducing the executable from it. However,
-as a special exception, the source code distributed need not include anything that is
-normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-
-
-It may happen that this requirement contradicts the license restrictions of other
-proprietary libraries that do not normally accompany the operating system. Such a
-contradiction means you cannot use both them and the Library together in an executable
-that you distribute.
-
-
-
-7. You may place library facilities that are a work based on the Library side-by-side
-in a single library together with other library facilities not covered by this
-License, and distribute such a combined library, provided that the separate
-distribution of the work based on the Library and of the other library facilities is
-otherwise permitted, and provided that you do these two things:
-
-
-
-a) Accompany the combined library with a copy of the same work based on the Library,
-uncombined with any other library facilities. This must be distributed under the terms
-of the Sections above.
-
-b) Give prominent notice with the combined library of the fact that part of it is a
-work based on the Library, and explaining where to find the accompanying uncombined
-form of the same work.
-
-8. You may not copy, modify, sublicense, link with, or distribute the Library except
-as expressly provided under this License. Any attempt otherwise to copy, modify,
-sublicense, link with, or distribute the Library is void, and will automatically
-terminate your rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses terminated so long
-as such parties remain in full compliance.
-
-
-
-9. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Library or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Library or works based on it.
-
-
-
-10. Each time you redistribute the Library (or any work based on the Library), the
-recipient automatically receives a license from the original licensor to copy,
-distribute, link with or modify the Library subject to these terms and conditions. You
-may not impose any further restrictions on the recipients' exercise of the rights
-granted herein. You are not responsible for enforcing compliance by third parties to
-this License.
-
-
-
-11. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Library at all. For example, if a patent license would not permit royalty-free
-redistribution of the Library by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply, and the section as a
-whole is intended to apply in other circumstances.
-
-
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-
-
-12. If the distribution and/or use of the Library is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Library under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-
-
-13. The Free Software Foundation may publish revised and/or new versions of the
-Library General Public License from time to time. Such new versions will be similar in
-spirit to the present version, but may differ in detail to address new problems or
-concerns.
-
-
-
-Each version is given a distinguishing version number. If the Library specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Library does not
-specify a license version number, you may choose any version ever published by the
-Free Software Foundation.
-
-
-
-14. If you wish to incorporate parts of the Library into other free programs whose
-distribution conditions are incompatible with these, write to the author to ask for
-permission. For software which is copyrighted by the Free Software Foundation, write
-to the Free Software Foundation; we sometimes make exceptions for this. Our decision
-will be guided by the two goals of preserving the free status of all derivatives of
-our free software and of promoting the sharing and reuse of software generally.
-
-
-
-NO WARRANTY
-
-
-
-15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-
-
-16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
-WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-
-
-END OF TERMS AND CONDITIONS
-
-
-
-How to Apply These Terms to Your New Libraries
-
-
-
-If you develop a new library, and you want it to be of the greatest possible use to
-the public, we recommend making it free software that everyone can redistribute and
-change. You can do so by permitting redistribution under these terms (or,
-alternatively, under the terms of the ordinary General Public License).
-
-
-
-To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
-where the full notice is found.
-
-
-
-one line to give the library's name and an idea of what it does.
-
-Copyright (C) year name of author
-
-
-
-This library is free software; you can redistribute it and/or
-
-modify it under the terms of the GNU Library General Public
-
-License as published by the Free Software Foundation; either
-
-version 2 of the License, or (at your option) any later version.
-
-
-
-This library is distributed in the hope that it will be useful,
-
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-
-Library General Public License for more details.
-
-
-
-You should have received a copy of the GNU Library General Public
-
-License along with this library; if not, write to the
-
-Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
-
-Boston, MA 02110-1301, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
-alter the names:
-
-
-
-Yoyodyne, Inc., hereby disclaims all copyright interest in
-
-the library `Frob' (a library for tweaking knobs) written
-
-by James Random Hacker.
-
-
-
-signature of Ty Coon, 1 April 1990
-
-Ty Coon, President of Vice
-
-That's all there is to it!
-
-
-
-
-LGPL-2.1
-
-
-GNU LESSER GENERAL PUBLIC LICENSE
-
-Version 2.1, February 1999
-
-Copyright (C) 1991, 1999 Free Software Foundation, Inc.
-51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL. It also counts
- as the successor of the GNU Library Public License, version 2, hence
- the version number 2.1.]
-Preamble
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public Licenses are intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users.
-
-This license, the Lesser General Public License, applies to some specially designated
-software packages--typically libraries--of the Free Software Foundation and other
-authors who decide to use it. You can use it too, but we suggest you first think
-carefully about whether this license or the ordinary General Public License is the
-better strategy to use in any particular case, based on the explanations below.
-
-When we speak of free software, we are referring to freedom of use, not price. Our
-General Public Licenses are designed to make sure that you have the freedom to
-distribute copies of free software (and charge for this service if you wish); that you
-receive source code or can get it if you want it; that you can change the software and
-use pieces of it in new free programs; and that you are informed that you can do these
-things.
-
-To protect your rights, we need to make restrictions that forbid distributors to deny
-you these rights or to ask you to surrender these rights. These restrictions translate
-to certain responsibilities for you if you distribute copies of the library or if you
-modify it.
-
-For example, if you distribute copies of the library, whether gratis or for a fee, you
-must give the recipients all the rights that we gave you. You must make sure that
-they, too, receive or can get the source code. If you link other code with the
-library, you must provide complete object files to the recipients, so that they can
-relink them with the library after making changes to the library and recompiling it.
-And you must show them these terms so they know their rights.
-
-We protect your rights with a two-step method: (1) we copyright the library, and (2)
-we offer you this license, which gives you legal permission to copy, distribute and/or
-modify the library.
-
-To protect each distributor, we want to make it very clear that there is no warranty
-for the free library. Also, if the library is modified by someone else and passed on,
-the recipients should know that what they have is not the original version, so that
-the original author`s reputation will not be affected by problems that might be
-introduced by others.
-
-Finally, software patents pose a constant threat to the existence of any free program.
-We wish to make sure that a company cannot effectively restrict the users of a free
-program by obtaining a restrictive license from a patent holder. Therefore, we insist
-that any patent license obtained for a version of the library must be consistent with
-the full freedom of use specified in this license.
-
-Most GNU software, including some libraries, is covered by the ordinary GNU General
-Public License. This license, the GNU Lesser General Public License, applies to
-certain designated libraries, and is quite different from the ordinary General Public
-License. We use this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
-When a program is linked with a library, whether statically or using a shared library,
-the combination of the two is legally speaking a combined work, a derivative of the
-original library. The ordinary General Public License therefore permits such linking
-only if the entire combination fits its criteria of freedom. The Lesser General Public
-License permits more lax criteria for linking other code with the library.
-
-We call this license the "Lesser" General Public License because it does Less to
-protect the user`s freedom than the ordinary General Public License. It also provides
-other free software developers Less of an advantage over competing non-free programs.
-These disadvantages are the reason we use the ordinary General Public License for many
-libraries. However, the Lesser license provides advantages in certain special
-circumstances.
-
-For example, on rare occasions, there may be a special need to encourage the widest
-possible use of a certain library, so that it becomes a de-facto standard. To achieve
-this, non-free programs must be allowed to use the library. A more frequent case is
-that a free library does the same job as widely used non-free libraries. In this case,
-there is little to gain by limiting the free library to free software only, so we use
-the Lesser General Public License.
-
-In other cases, permission to use a particular library in non-free programs enables a
-greater number of people to use a large body of free software. For example, permission
-to use the GNU C Library in non-free programs enables many more people to use the
-whole GNU operating system, as well as its variant, the GNU/Linux operating system.
-
-Although the Lesser General Public License is Less protective of the users` freedom,
-it does ensure that the user of a program that is linked with the Library has the
-freedom and the wherewithal to run that program using a modified version of the
-Library.
-
-The precise terms and conditions for copying, distribution and modification follow.
-Pay close attention to the difference between a "work based on the library" and a
-"work that uses the library". The former contains code derived from the library,
-whereas the latter must be combined with the library in order to run.
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-0. This License Agreement applies to any software library or other program which
-contains a notice placed by the copyright holder or other authorized party saying it
-may be distributed under the terms of this Lesser General Public License (also called
-"this License"). Each licensee is addressed as "you".
-
-A "library" means a collection of software functions and/or data prepared so as to be
-conveniently linked with application programs (which use some of those functions and
-data) to form executables.
-
-The "Library", below, refers to any such software library or work which has been
-distributed under these terms. A "work based on the Library" means either the Library
-or any derivative work under copyright law: that is to say, a work containing the
-Library or a portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is included without
-limitation in the term "modification".)
-
-"Source code" for a work means the preferred form of the work for making modifications
-to it. For a library, complete source code means all the source code for all modules
-it contains, plus any associated interface definition files, plus the scripts used to
-control compilation and installation of the library.
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running a program using the Library is
-not restricted, and output from such a program is covered only if its contents
-constitute a work based on the Library (independent of the use of the Library in a
-tool for writing it). Whether that is true depends on what the Library does and what
-the program that uses the Library does.
-
-1. You may copy and distribute verbatim copies of the Library`s complete source code
-as you receive it, in any medium, provided that you conspicuously and appropriately
-publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
-intact all the notices that refer to this License and to the absence of any warranty;
-and distribute a copy of this License along with the Library.
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-2. You may modify your copy or copies of the Library or any portion of it, thus
-forming a work based on the Library, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-a) The modified work must itself be a software library.
-b) You must cause the files modified to carry prominent notices stating that you
-changed the files and the date of any change.
-c) You must cause the whole of the work to be licensed at no charge to all third
-parties under the terms of this License.
-d) If a facility in the modified Library refers to a function or a table of data to be
-supplied by an application program that uses the facility, other than as an argument
-passed when the facility is invoked, then you must make a good faith effort to ensure
-that, in the event an application does not supply such function or table, the facility
-still operates, and performs whatever part of its purpose remains meaningful.
-(For example, a function in a library to compute square roots has a purpose that is
-entirely well-defined independent of the application. Therefore, Subsection 2d
-requires that any application-supplied function or table used by this function must be
-optional: if the application does not supply it, the square root function must still
-compute square roots.)
-
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Library, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Library,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library with the
-Library (or with a work based on the Library) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-3. You may opt to apply the terms of the ordinary GNU General Public License instead
-of this License to a given copy of the Library. To do this, you must alter all the
-notices that refer to this License, so that they refer to the ordinary GNU General
-Public License, version 2, instead of to this License. (If a newer version than
-version 2 of the ordinary GNU General Public License has appeared, then you can
-specify that version instead if you wish.) Do not make any other change in these
-notices.
-
-Once this change is made in a given copy, it is irreversible for that copy, so the
-ordinary GNU General Public License applies to all subsequent copies and derivative
-works made from that copy.
-
-This option is useful when you wish to copy part of the code of the Library into a
-program that is not a library.
-
-4. You may copy and distribute the Library (or a portion or derivative of it, under
-Section 2) in object code or executable form under the terms of Sections 1 and 2 above
-provided that you accompany it with the complete corresponding machine-readable source
-code, which must be distributed under the terms of Sections 1 and 2 above on a medium
-customarily used for software interchange.
-
-If distribution of object code is made by offering access to copy from a designated
-place, then offering equivalent access to copy the source code from the same place
-satisfies the requirement to distribute the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-5. A program that contains no derivative of any portion of the Library, but is
-designed to work with the Library by being compiled or linked with it, is called a
-"work that uses the Library". Such a work, in isolation, is not a derivative work of
-the Library, and therefore falls outside the scope of this License.
-
-However, linking a "work that uses the Library" with the Library creates an executable
-that is a derivative of the Library (because it contains portions of the Library),
-rather than a "work that uses the library". The executable is therefore covered by
-this License. Section 6 states terms for distribution of such executables.
-
-When a "work that uses the Library" uses material from a header file that is part of
-the Library, the object code for the work may be a derivative work of the Library even
-though the source code is not. Whether this is true is especially significant if the
-work can be linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
-If such an object file uses only numerical parameters, data structure layouts and
-accessors, and small macros and small inline functions (ten lines or less in length),
-then the use of the object file is unrestricted, regardless of whether it is legally a
-derivative work. (Executables containing this object code plus portions of the Library
-will still fall under Section 6.)
-
-Otherwise, if the work is a derivative of the Library, you may distribute the object
-code for the work under the terms of Section 6. Any executables containing that work
-also fall under Section 6, whether or not they are linked directly with the Library
-itself.
-
-6. As an exception to the Sections above, you may also combine or link a "work that
-uses the Library" with the Library to produce a work containing portions of the
-Library, and distribute that work under terms of your choice, provided that the terms
-permit modification of the work for the customer`s own use and reverse engineering for
-debugging such modifications.
-
-You must give prominent notice with each copy of the work that the Library is used in
-it and that the Library and its use are covered by this License. You must supply a
-copy of this License. If the work during execution displays copyright notices, you
-must include the copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one of these things:
-
-a) Accompany the work with the complete corresponding machine-readable source code for
-the Library including whatever changes were used in the work (which must be
-distributed under Sections 1 and 2 above); and, if the work is an executable linked
-with the Library, with the complete machine-readable "work that uses the Library", as
-object code and/or source code, so that the user can modify the Library and then
-relink to produce a modified executable containing the modified Library. (It is
-understood that the user who changes the contents of definitions files in the Library
-will not necessarily be able to recompile the application to use the modified
-definitions.)
-b) Use a suitable shared library mechanism for linking with the Library. A suitable
-mechanism is one that (1) uses at run time a copy of the library already present on
-the user`s computer system, rather than copying library functions into the executable,
-and (2) will operate properly with a modified version of the library, if the user
-installs one, as long as the modified version is interface-compatible with the version
-that the work was made with.
-c) Accompany the work with a written offer, valid for at least three years, to give
-the same user the materials specified in Subsection 6a, above, for a charge no more
-than the cost of performing this distribution.
-d) If distribution of the work is made by offering access to copy from a designated
-place, offer equivalent access to copy the above specified materials from the same
-place.
-e) Verify that the user has already received a copy of these materials or that you
-have already sent this user a copy.
-For an executable, the required form of the "work that uses the Library" must include
-any data and utility programs needed for reproducing the executable from it. However,
-as a special exception, the materials to be distributed need not include anything that
-is normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-It may happen that this requirement contradicts the license restrictions of other
-proprietary libraries that do not normally accompany the operating system. Such a
-contradiction means you cannot use both them and the Library together in an executable
-that you distribute.
-
-7. You may place library facilities that are a work based on the Library side-by-side
-in a single library together with other library facilities not covered by this
-License, and distribute such a combined library, provided that the separate
-distribution of the work based on the Library and of the other library facilities is
-otherwise permitted, and provided that you do these two things:
-
-a) Accompany the combined library with a copy of the same work based on the Library,
-uncombined with any other library facilities. This must be distributed under the terms
-of the Sections above.
-b) Give prominent notice with the combined library of the fact that part of it is a
-work based on the Library, and explaining where to find the accompanying uncombined
-form of the same work.
-8. You may not copy, modify, sublicense, link with, or distribute the Library except
-as expressly provided under this License. Any attempt otherwise to copy, modify,
-sublicense, link with, or distribute the Library is void, and will automatically
-terminate your rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses terminated so long
-as such parties remain in full compliance.
-
-9. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Library or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Library or works based on it.
-
-10. Each time you redistribute the Library (or any work based on the Library), the
-recipient automatically receives a license from the original licensor to copy,
-distribute, link with or modify the Library subject to these terms and conditions. You
-may not impose any further restrictions on the recipients` exercise of the rights
-granted herein. You are not responsible for enforcing compliance by third parties with
-this License.
-
-11. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Library at all. For example, if a patent license would not permit royalty-free
-redistribution of the Library by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply, and the section as a
-whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-12. If the distribution and/or use of the Library is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Library under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-13. The Free Software Foundation may publish revised and/or new versions of the Lesser
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Library does not
-specify a license version number, you may choose any version ever published by the
-Free Software Foundation.
-
-14. If you wish to incorporate parts of the Library into other free programs whose
-distribution conditions are incompatible with these, write to the author to ask for
-permission. For software which is copyrighted by the Free Software Foundation, write
-to the Free Software Foundation; we sometimes make exceptions for this. Our decision
-will be guided by the two goals of preserving the free status of all derivatives of
-our free software and of promoting the sharing and reuse of software generally.
-
-NO WARRANTY
-
-15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
-WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-END OF TERMS AND CONDITIONS
-
-How to Apply These Terms to Your New Libraries
-
-If you develop a new library, and you want it to be of the greatest possible use to
-the public, we recommend making it free software that everyone can redistribute and
-change. You can do so by permitting redistribution under these terms (or,
-alternatively, under the terms of the ordinary General Public License).
-
-To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
-where the full notice is found.
-
-one line to give the library`s name and an idea of what it does.
-Copyright (C) year name of author
-
-This library is free software; you can redistribute it and/or
-modify it under the terms of the GNU Lesser General Public
-License as published by the Free Software Foundation; either
-version 2.1 of the License, or (at your option) any later version.
-
-This library is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-Lesser General Public License for more details.
-
-You should have received a copy of the GNU Lesser General Public
-License along with this library; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
-Also add information on how to contact you by electronic and paper mail.
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
-alter the names:
-
-Yoyodyne, Inc., hereby disclaims all copyright interest in
-the library `Frob` (a library for tweaking knobs) written
-by James Random Hacker.
-
-signature of Ty Coon, 1 April 1990
-Ty Coon, President of Vice
-That`s all there is to it!
-
-
-
-
-LGPL-3.0
-
-GNU LESSER GENERAL PUBLIC LICENSE
-
-Version 3, 29 June 2007
-
-Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-
-This version of the GNU Lesser General Public License incorporates the terms and
-conditions of version 3 of the GNU General Public License, supplemented by the
-additional permissions listed below.
-0. Additional Definitions.
-
-As used herein, ”this License” refers to version 3 of the GNU Lesser
-General Public License, and the ”GNU GPL” refers to version 3 of the GNU
-General Public License.
-
-”The Library” refers to a covered work governed by this License, other
-than an Application or a Combined Work as defined below.
-
-An ”Application” is any work that makes use of an interface provided by
-the Library, but which is not otherwise based on the Library. Defining a subclass of a
-class defined by the Library is deemed a mode of using an interface provided by the
-Library.
-
-A ”Combined Work” is a work produced by combining or linking an
-Application with the Library. The particular version of the Library with which the
-Combined Work was made is also called the ”Linked Version”.
-
-The ”Minimal Corresponding Source” for a Combined Work means the
-Corresponding Source for the Combined Work, excluding any source code for portions of
-the Combined Work that, considered in isolation, are based on the Application, and not
-on the Linked Version.
-
-The ”Corresponding Application Code” for a Combined Work means the object
-code and/or source code for the Application, including any data and utility programs
-needed for reproducing the Combined Work from the Application, but excluding the
-System Libraries of the Combined Work.
-1. Exception to Section 3 of the GNU GPL.
-
-You may convey a covered work under sections 3 and 4 of this License without being
-bound by section 3 of the GNU GPL.
-2. Conveying Modified Versions.
-
-If you modify a copy of the Library, and, in your modifications, a facility refers to
-a function or data to be supplied by an Application that uses the facility (other than
-as an argument passed when the facility is invoked), then you may convey a copy of the
-modified version:
-
- * a) under this License, provided that you make a good faith effort to ensure
-that, in the event an Application does not supply the function or data, the facility
-still operates, and performs whatever part of its purpose remains meaningful, or
- * b) under the GNU GPL, with none of the additional permissions of this License
-applicable to that copy.
-
-3. Object Code Incorporating Material from Library Header Files.
-
-The object code form of an Application may incorporate material from a header file
-that is part of the Library. You may convey such object code under terms of your
-choice, provided that, if the incorporated material is not limited to numerical
-parameters, data structure layouts and accessors, or small macros, inline functions
-and templates (ten or fewer lines in length), you do both of the following:
-
- * a) Give prominent notice with each copy of the object code that the Library is
-used in it and that the Library and its use are covered by this License.
- * b) Accompany the object code with a copy of the GNU GPL and this license
-document.
-
-4. Combined Works.
-
-You may convey a Combined Work under terms of your choice that, taken together,
-effectively do not restrict modification of the portions of the Library contained in
-the Combined Work and reverse engineering for debugging such modifications, if you
-also do each of the following:
-
- * a) Give prominent notice with each copy of the Combined Work that the Library is
-used in it and that the Library and its use are covered by this License.
- * b) Accompany the Combined Work with a copy of the GNU GPL and this license
-document.
- * c) For a Combined Work that displays copyright notices during execution, include
-the copyright notice for the Library among these notices, as well as a reference
-directing the user to the copies of the GNU GPL and this license document.
- * d) Do one of the following:
- o 0) Convey the Minimal Corresponding Source under the terms of this
-License, and the Corresponding Application Code in a form suitable for, and under
-terms that permit, the user to recombine or relink the Application with a modified
-version of the Linked Version to produce a modified Combined Work, in the manner
-specified by section 6 of the GNU GPL for conveying Corresponding Source.
- o 1) Use a suitable shared library mechanism for linking with the Library. A
-suitable mechanism is one that (a) uses at run time a copy of the Library already
-present on the user's computer system, and (b) will operate properly with a modified
-version of the Library that is interface-compatible with the Linked Version.
- * e) Provide Installation Information, but only if you would otherwise be required
-to provide such information under section 6 of the GNU GPL, and only to the extent
-that such information is necessary to install and execute a modified version of the
-Combined Work produced by recombining or relinking the Application with a modified
-version of the Linked Version. (If you use option 4d0, the Installation Information
-must accompany the Minimal Corresponding Source and Corresponding Application Code. If
-you use option 4d1, you must provide the Installation Information in the manner
-specified by section 6 of the GNU GPL for conveying Corresponding Source.)
-
-5. Combined Libraries.
-
-You may place library facilities that are a work based on the Library side by side in
-a single library together with other library facilities that are not Applications and
-are not covered by this License, and convey such a combined library under terms of
-your choice, if you do both of the following:
-
- * a) Accompany the combined library with a copy of the same work based on the
-Library, uncombined with any other library facilities, conveyed under the terms of
-this License.
- * b) Give prominent notice with the combined library that part of it is a work
-based on the Library, and explaining where to find the accompanying uncombined form of
-the same work.
-
-6. Revised Versions of the GNU Lesser General Public License.
-
-The Free Software Foundation may publish revised and/or new versions of the GNU Lesser
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library as you received
-it specifies that a certain numbered version of the GNU Lesser General Public License
-”or any later version” applies to it, you have the option of following
-the terms and conditions either of that published version or of any later version
-published by the Free Software Foundation. If the Library as you received it does not
-specify a version number of the GNU Lesser General Public License, you may choose any
-version of the GNU Lesser General Public License ever published by the Free Software
-Foundation.
-
-If the Library as you received it specifies that a proxy can decide whether future
-versions of the GNU Lesser General Public License shall apply, that proxy's public
-statement of acceptance of any version is permanent authorization for you to choose
-that version for the Library.
-
-
-
-Libpng
-
-
-This copy of the libpng notices is provided for your convenience. In case of
-any discrepancy between this copy and the notices in the file png.h that is
-included in the libpng distribution, the latter shall prevail.
-
-COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
-
-If you modify libpng you may insert additional notices immediately following
-this sentence.
-
-This code is released under the libpng license.
-
-libpng versions 1.2.6, August 15, 2004, through 1.4.5, December 9, 2010, are
-Copyright (c) 2004, 2006-2010 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-1.2.5
-with the following individual added to the list of Contributing Authors
-
- Cosmin Truta
-
-libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are
-Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-1.0.6
-with the following individuals added to the list of Contributing Authors
-
- Simon-Pierre Cadieux
- Eric S. Raymond
- Gilles Vollant
-
-and with the following additions to the disclaimer:
-
- There is no warranty against interference with your enjoyment of the
- library or against infringement. There is no warranty that our
- efforts or the library will fulfill any of your particular purposes
- or needs. This library is provided with all faults, and the entire
- risk of satisfactory quality, performance, accuracy, and effort is with
- the user.
-
-libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
-Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-0.96,
-with the following individuals added to the list of Contributing Authors:
-
- Tom Lane
- Glenn Randers-Pehrson
- Willem van Schaik
-
-libpng versions 0.89, June 1996, through 0.96, May 1997, are
-Copyright (c) 1996, 1997 Andreas Dilger
-Distributed according to the same disclaimer and license as libpng-0.88,
-with the following individuals added to the list of Contributing Authors:
-
- John Bowler
- Kevin Bracey
- Sam Bushell
- Magnus Holmgren
- Greg Roelofs
- Tom Tanner
-
-libpng versions 0.5, May 1995, through 0.88, January 1996, are
-Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.
-
-For the purposes of this copyright and license, "Contributing Authors"
-is defined as the following set of individuals:
-
- Andreas Dilger
- Dave Martindale
- Guy Eric Schalnat
- Paul Schmidt
- Tim Wegner
-
-The PNG Reference Library is supplied "AS IS". The Contributing Authors
-and Group 42, Inc. disclaim all warranties, expressed or implied,
-including, without limitation, the warranties of merchantability and of
-fitness for any purpose. The Contributing Authors and Group 42, Inc.
-assume no liability for direct, indirect, incidental, special, exemplary,
-or consequential damages, which may result from the use of the PNG
-Reference Library, even if advised of the possibility of such damage.
-
-Permission is hereby granted to use, copy, modify, and distribute this
-source code, or portions hereof, for any purpose, without fee, subject
-to the following restrictions:
-
-1. The origin of this source code must not be misrepresented.
-
-2. Altered versions must be plainly marked as such and must not
- be misrepresented as being the original source.
-
-3. This Copyright notice may not be removed or altered from any
- source or altered source distribution.
-
-The Contributing Authors and Group 42, Inc. specifically permit, without
-fee, and encourage the use of this source code as a component to
-supporting the PNG file format in commercial products. If you use this
-source code in a product, acknowledgment is not required but would be
-appreciated.
-
-
-A "png_get_copyright" function is available, for convenient use in "about"
-boxes and the like:
-
- printf("%s",png_get_copyright(NULL));
-
-Also, the PNG logo (in PNG format, of course) is supplied in the
-files "pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).
-
-Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a
-certification mark of the Open Source Initiative.
-
-Glenn Randers-Pehrson
-glennrp at users.sourceforge.net
-December 9, 2010
-
-
-
-
-MIT
-
-
-MIT License
-
-Copyright (c) <year> <copyright holders>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-
-
-MPL-1.0
-
-
-MOZILLA PUBLIC LICENSE
-Version 1.0
-
-1. Definitions.
-
-1.1. ``Contributor`` means each entity that creates or contributes to the creation of
-Modifications.
-1.2. ``Contributor Version`` means the combination of the Original Code, prior
-Modifications used by a Contributor, and the Modifications made by that particular
-Contributor.
-
-1.3. ``Covered Code`` means the Original Code or Modifications or the combination of
-the Original Code and Modifications, in each case including portions thereof.
-
-1.4. ``Electronic Distribution Mechanism`` means a mechanism generally accepted in the
-software development community for the electronic transfer of data.
-
-1.5. ``Executable`` means Covered Code in any form other than Source Code.
-
-1.6. ``Initial Developer`` means the individual or entity identified as the Initial
-Developer in the Source Code notice required by Exhibit A.
-
-1.7. ``Larger Work`` means a work which combines Covered Code or portions thereof with
-code not governed by the terms of this License.
-
-1.8. ``License`` means this document.
-
-1.9. ``Modifications`` means any addition to or deletion from the substance or
-structure of either the Original Code or any previous Modifications. When Covered Code
-is released as a series of files, a Modification is:
-
-A. Any addition to or deletion from the contents of a file containing Original Code or
-previous Modifications.
-
-B. Any new file that contains any part of the Original Code or previous Modifications.
-
-1.10. ``Original Code`` means Source Code of computer software code which is described
-in the Source Code notice required by Exhibit A as Original Code, and which, at the
-time of its release under this License is not already Covered Code governed by this
-License.
-
-1.11. ``Source Code`` means the preferred form of the Covered Code for making
-modifications to it, including all modules it contains, plus any associated interface
-definition files, scripts used to control compilation and installation of an
-Executable, or a list of source code differential comparisons against either the
-Original Code or another well known, available Covered Code of the Contributor`s
-choice. The Source Code can be in a compressed or archival form, provided the
-appropriate decompression or de-archiving software is widely available for no charge.
-
-1.12. ``You`` means an individual or a legal entity exercising rights under, and
-complying with all of the terms of, this License or a future version of this License
-issued under Section 6.1. For legal entities, ``You`` includes any entity which
-controls, is controlled by, or is under common control with You. For purposes of this
-definition, ``control`` means (a) the power, direct or indirect, to cause the
-direction or management of such entity, whether by contract or otherwise, or (b)
-ownership of fifty percent (50%) or more of the outstanding shares or beneficial
-ownership of such entity.
-
-2. Source Code License.
-2.1. The Initial Developer Grant.
-The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive
-license, subject to third party intellectual property claims:
-(a) to use, reproduce, modify, display, perform, sublicense and distribute the
-Original Code (or portions thereof) with or without Modifications, or as part of a
-Larger Work; and
-
-(b) under patents now or hereafter owned or controlled by Initial Developer, to make,
-have made, use and sell (``Utilize``) the Original Code (or portions thereof), but
-solely to the extent that any such patent is reasonably necessary to enable You to
-Utilize the Original Code (or portions thereof) and not to any greater extent that may
-be necessary to Utilize further Modifications or combinations.
-
-2.2. Contributor Grant.
-Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license,
-subject to third party intellectual property claims:
-
-(a) to use, reproduce, modify, display, perform, sublicense and distribute the
-Modifications created by such Contributor (or portions thereof) either on an
-unmodified basis, with other Modifications, as Covered Code or as part of a Larger
-Work; and
-
-(b) under patents now or hereafter owned or controlled by Contributor, to Utilize the
-Contributor Version (or portions thereof), but solely to the extent that any such
-patent is reasonably necessary to enable You to Utilize the Contributor Version (or
-portions thereof), and not to any greater extent that may be necessary to Utilize
-further Modifications or combinations.
-
-3. Distribution Obligations.
-3.1. Application of License.
-The Modifications which You create or to which You contribute are governed by the
-terms of this License, including without limitation Section 2.2. The Source Code
-version of Covered Code may be distributed only under the terms of this License or a
-future version of this License released under Section 6.1, and You must include a copy
-of this License with every copy of the Source Code You distribute. You may not offer
-or impose any terms on any Source Code version that alters or restricts the applicable
-version of this License or the recipients` rights hereunder. However, You may include
-an additional document offering the additional rights described in Section 3.5.
-3.2. Availability of Source Code.
-Any Modification which You create or to which You contribute must be made available in
-Source Code form under the terms of this License either on the same media as an
-Executable version or via an accepted Electronic Distribution Mechanism to anyone to
-whom you made an Executable version available; and if made available via Electronic
-Distribution Mechanism, must remain available for at least twelve (12) months after
-the date it initially became available, or at least six (6) months after a subsequent
-version of that particular Modification has been made available to such recipients.
-You are responsible for ensuring that the Source Code version remains available even
-if the Electronic Distribution Mechanism is maintained by a third party.
-
-3.3. Description of Modifications.
-You must cause all Covered Code to which you contribute to contain a file documenting
-the changes You made to create that Covered Code and the date of any change. You must
-include a prominent statement that the Modification is derived, directly or
-indirectly, from Original Code provided by the Initial Developer and including the
-name of the Initial Developer in (a) the Source Code, and (b) in any notice in an
-Executable version or related documentation in which You describe the origin or
-ownership of the Covered Code.
-
-3.4. Intellectual Property Matters
-
-(a) Third Party Claims.
-If You have knowledge that a party claims an intellectual property right in particular
-functionality or code (or its utilization under this License), you must include a text
-file with the source code distribution titled ``LEGAL`` which describes the claim and
-the party making the claim in sufficient detail that a recipient will know whom to
-contact. If you obtain such knowledge after You make Your Modification available as
-described in Section 3.2, You shall promptly modify the LEGAL file in all copies You
-make available thereafter and shall take other steps (such as notifying appropriate
-mailing lists or newsgroups) reasonably calculated to inform those who received the
-Covered Code that new knowledge has been obtained.
-
-(b) Contributor APIs.
-If Your Modification is an application programming interface and You own or control
-patents which are reasonably necessary to implement that API, you must also include
-this information in the LEGAL file.
-
-3.5. Required Notices.
-You must duplicate the notice in Exhibit A in each file of the Source Code, and this
-License in any documentation for the Source Code, where You describe recipients`
-rights relating to Covered Code. If You created one or more Modification(s), You may
-add your name as a Contributor to the notice described in Exhibit A. If it is not
-possible to put such notice in a particular Source Code file due to its structure,
-then you must include such notice in a location (such as a relevant directory file)
-where a user would be likely to look for such a notice. You may choose to offer, and
-to charge a fee for, warranty, support, indemnity or liability obligations to one or
-more recipients of Covered Code. However, You may do so only on Your own behalf, and
-not on behalf of the Initial Developer or any Contributor. You must make it absolutely
-clear than any such warranty, support, indemnity or liability obligation is offered by
-You alone, and You hereby agree to indemnify the Initial Developer and every
-Contributor for any liability incurred by the Initial Developer or such Contributor as
-a result of warranty, support, indemnity or liability terms You offer.
-
-3.6. Distribution of Executable Versions.
-You may distribute Covered Code in Executable form only if the requirements of Section
-3.1-3.5 have been met for that Covered Code, and if You include a notice stating that
-the Source Code version of the Covered Code is available under the terms of this
-License, including a description of how and where You have fulfilled the obligations
-of Section 3.2. The notice must be conspicuously included in any notice in an
-Executable version, related documentation or collateral in which You describe
-recipients` rights relating to the Covered Code. You may distribute the Executable
-version of Covered Code under a license of Your choice, which may contain terms
-different from this License, provided that You are in compliance with the terms of
-this License and that the license for the Executable version does not attempt to limit
-or alter the recipient`s rights in the Source Code version from the rights set forth
-in this License. If You distribute the Executable version under a different license
-You must make it absolutely clear that any terms which differ from this License are
-offered by You alone, not by the Initial Developer or any Contributor. You hereby
-agree to indemnify the Initial Developer and every Contributor for any liability
-incurred by the Initial Developer or such Contributor as a result of any such terms
-You offer.
-
-3.7. Larger Works.
-You may create a Larger Work by combining Covered Code with other code not governed by
-the terms of this License and distribute the Larger Work as a single product. In such
-a case, You must make sure the requirements of this License are fulfilled for the
-Covered Code.
-
-4. Inability to Comply Due to Statute or Regulation.
-If it is impossible for You to comply with any of the terms of this License with
-respect to some or all of the Covered Code due to statute or regulation then You must:
-(a) comply with the terms of this License to the maximum extent possible; and (b)
-describe the limitations and the code they affect. Such description must be included
-in the LEGAL file described in Section 3.4 and must be included with all distributions
-of the Source Code. Except to the extent prohibited by statute or regulation, such
-description must be sufficiently detailed for a recipient of ordinary skill to be able
-to understand it.
-
-5. Application of this License.
-This License applies to code to which the Initial Developer has attached the notice in
-Exhibit A, and to related Covered Code.
-6. Versions of the License.
-6.1. New Versions.
-Netscape Communications Corporation (``Netscape``) may publish revised and/or new
-versions of the License from time to time. Each version will be given a distinguishing
-version number.
-6.2. Effect of New Versions.
-Once Covered Code has been published under a particular version of the License, You
-may always continue to use it under the terms of that version. You may also choose to
-use such Covered Code under the terms of any subsequent version of the License
-published by Netscape. No one other than Netscape has the right to modify the terms
-applicable to Covered Code created under this License.
-
-6.3. Derivative Works.
-If you create or use a modified version of this License (which you may only do in
-order to apply it to code which is not already Covered Code governed by this License),
-you must (a) rename Your license so that the phrases ``Mozilla``, ``MOZILLAPL``,
-``MOZPL``, ``Netscape``, ``NPL`` or any confusingly similar phrase do not appear
-anywhere in your license and (b) otherwise make it clear that your version of the
-license contains terms which differ from the Mozilla Public License and Netscape
-Public License. (Filling in the name of the Initial Developer, Original Code or
-Contributor in the notice described in Exhibit A shall not of themselves be deemed to
-be modifications of this License.)
-
-7. DISCLAIMER OF WARRANTY.
-COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS`` BASIS, WITHOUT WARRANTY OF
-ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT
-THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
-NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
-IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE
-INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
-SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL
-PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER
-THIS DISCLAIMER.
-8. TERMINATION.
-This License and the rights granted hereunder will terminate automatically if You fail
-to comply with terms herein and fail to cure such breach within 30 days of becoming
-aware of the breach. All sublicenses to the Covered Code which are properly granted
-shall survive any termination of this License. Provisions which, by their nature, must
-remain in effect beyond the termination of this License shall survive.
-9. LIMITATION OF LIABILITY.
-UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
-CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY
-DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU
-OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF
-ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK
-STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
-LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH
-DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
-PERSONAL INJURY RESULTING FROM SUCH PARTY`S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
-PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION
-OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY
-TO YOU.
-10. U.S. GOVERNMENT END USERS.
-The Covered Code is a ``commercial item,`` as that term is defined in 48 C.F.R. 2.101
-(Oct. 1995), consisting of ``commercial computer software`` and ``commercial computer
-software documentation,`` as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
-Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
-1995), all U.S. Government End Users acquire Covered Code with only those rights set
-forth herein.
-11. MISCELLANEOUS.
-This License represents the complete agreement concerning subject matter hereof. If
-any provision of this License is held to be unenforceable, such provision shall be
-reformed only to the extent necessary to make it enforceable. This License shall be
-governed by California law provisions (except to the extent applicable law, if any,
-provides otherwise), excluding its conflict-of-law provisions. With respect to
-disputes in which at least one party is a citizen of, or an entity chartered or
-registered to do business in, the United States of America: (a) unless otherwise
-agreed in writing, all disputes relating to this License (excepting any dispute
-relating to intellectual property rights) shall be subject to final and binding
-arbitration, with the losing party paying all costs of arbitration; (b) any
-arbitration relating to this Agreement shall be held in Santa Clara County,
-California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to
-this Agreement shall be subject to the jurisdiction of the Federal Courts of the
-Northern District of California, with venue lying in Santa Clara County, California,
-with the losing party responsible for costs, including without limitation, court costs
-and reasonable attorneys fees and expenses. The application of the United Nations
-Convention on Contracts for the International Sale of Goods is expressly excluded. Any
-law or regulation which provides that the language of a contract shall be construed
-against the drafter shall not apply to this License.
-12. RESPONSIBILITY FOR CLAIMS.
-Except in cases where another Contributor has failed to comply with Section 3.4, You
-are responsible for damages arising, directly or indirectly, out of Your utilization
-of rights under this License, based on the number of copies of Covered Code you made
-available, the revenues you received from utilizing such rights, and other relevant
-factors. You agree to work with affected parties to distribute responsibility on an
-equitable basis.
-EXHIBIT A.
-``The contents of this file are subject to the Mozilla Public License Version 1.0 (the
-"License"); you may not use this file except in compliance with the License. You may
-obtain a copy of the License at http://www.mozilla.org/MPL/
-Software distributed under the License is distributed on an "AS IS" basis, WITHOUT
-WARRANTY OF ANY KIND, either express or implied. See the License for the specific
-language governing rights and limitations under the License.
-
-The Original Code is ______________________________________.
-
-The Initial Developer of the Original Code is ________________________. Portions
-created by ______________________ are Copyright (C) ______ _______________________.
-All Rights Reserved.
-
-Contributor(s): ______________________________________.``
-
-
-
-
-MPL-2.0
-
-Mozilla Public License Version 2.0
-==================================
-
-1. Definitions
---------------
-
-1.1. "Contributor"
- means each individual or legal entity that creates, contributes to
- the creation of, or owns Covered Software.
-
-1.2. "Contributor Version"
- means the combination of the Contributions of others (if any) used
- by a Contributor and that particular Contributor's Contribution.
-
-1.3. "Contribution"
- means Covered Software of a particular Contributor.
-
-1.4. "Covered Software"
- means Source Code Form to which the initial Contributor has attached
- the notice in Exhibit A, the Executable Form of such Source Code
- Form, and Modifications of such Source Code Form, in each case
- including portions thereof.
-
-1.5. "Incompatible With Secondary Licenses"
- means
-
- (a) that the initial Contributor has attached the notice described
- in Exhibit B to the Covered Software; or
-
- (b) that the Covered Software was made available under the terms of
- version 1.1 or earlier of the License, but not also under the
- terms of a Secondary License.
-
-1.6. "Executable Form"
- means any form of the work other than Source Code Form.
-
-1.7. "Larger Work"
- means a work that combines Covered Software with other material, in
- a separate file or files, that is not Covered Software.
-
-1.8. "License"
- means this document.
-
-1.9. "Licensable"
- means having the right to grant, to the maximum extent possible,
- whether at the time of the initial grant or subsequently, any and
- all of the rights conveyed by this License.
-
-1.10. "Modifications"
- means any of the following:
-
- (a) any file in Source Code Form that results from an addition to,
- deletion from, or modification of the contents of Covered
- Software; or
-
- (b) any new file in Source Code Form that contains any Covered
- Software.
-
-1.11. "Patent Claims" of a Contributor
- means any patent claim(s), including without limitation, method,
- process, and apparatus claims, in any patent Licensable by such
- Contributor that would be infringed, but for the grant of the
- License, by the making, using, selling, offering for sale, having
- made, import, or transfer of either its Contributions or its
- Contributor Version.
-
-1.12. "Secondary License"
- means either the GNU General Public License, Version 2.0, the GNU
- Lesser General Public License, Version 2.1, the GNU Affero General
- Public License, Version 3.0, or any later versions of those
- licenses.
-
-1.13. "Source Code Form"
- means the form of the work preferred for making modifications.
-
-1.14. "You" (or "Your")
- means an individual or a legal entity exercising rights under this
- License. For legal entities, "You" includes any entity that
- controls, is controlled by, or is under common control with You. For
- purposes of this definition, "control" means (a) the power, direct
- or indirect, to cause the direction or management of such entity,
- whether by contract or otherwise, or (b) ownership of more than
- fifty percent (50%) of the outstanding shares or beneficial
- ownership of such entity.
-
-2. License Grants and Conditions
---------------------------------
-
-2.1. Grants
-
-Each Contributor hereby grants You a world-wide, royalty-free,
-non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark)
- Licensable by such Contributor to use, reproduce, make available,
- modify, display, perform, distribute, and otherwise exploit its
- Contributions, either on an unmodified basis, with Modifications, or
- as part of a Larger Work; and
-
-(b) under Patent Claims of such Contributor to make, use, sell, offer
- for sale, have made, import, and otherwise transfer either its
- Contributions or its Contributor Version.
-
-2.2. Effective Date
-
-The licenses granted in Section 2.1 with respect to any Contribution
-become effective for each Contribution on the date the Contributor first
-distributes such Contribution.
-
-2.3. Limitations on Grant Scope
-
-The licenses granted in this Section 2 are the only rights granted under
-this License. No additional rights or licenses will be implied from the
-distribution or licensing of Covered Software under this License.
-Notwithstanding Section 2.1(b) above, no patent license is granted by a
-Contributor:
-
-(a) for any code that a Contributor has removed from Covered Software;
- or
-
-(b) for infringements caused by: (i) Your and any other third party's
- modifications of Covered Software, or (ii) the combination of its
- Contributions with other software (except as part of its Contributor
- Version); or
-
-(c) under Patent Claims infringed by Covered Software in the absence of
- its Contributions.
-
-This License does not grant any rights in the trademarks, service marks,
-or logos of any Contributor (except as may be necessary to comply with
-the notice requirements in Section 3.4).
-
-2.4. Subsequent Licenses
-
-No Contributor makes additional grants as a result of Your choice to
-distribute the Covered Software under a subsequent version of this
-License (see Section 10.2) or under the terms of a Secondary License (if
-permitted under the terms of Section 3.3).
-
-2.5. Representation
-
-Each Contributor represents that the Contributor believes its
-Contributions are its original creation(s) or it has sufficient rights
-to grant the rights to its Contributions conveyed by this License.
-
-2.6. Fair Use
-
-This License is not intended to limit any rights You have under
-applicable copyright doctrines of fair use, fair dealing, or other
-equivalents.
-
-2.7. Conditions
-
-Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
-in Section 2.1.
-
-3. Responsibilities
--------------------
-
-3.1. Distribution of Source Form
-
-All distribution of Covered Software in Source Code Form, including any
-Modifications that You create or to which You contribute, must be under
-the terms of this License. You must inform recipients that the Source
-Code Form of the Covered Software is governed by the terms of this
-License, and how they can obtain a copy of this License. You may not
-attempt to alter or restrict the recipients' rights in the Source Code
-Form.
-
-3.2. Distribution of Executable Form
-
-If You distribute Covered Software in Executable Form then:
-
-(a) such Covered Software must also be made available in Source Code
- Form, as described in Section 3.1, and You must inform recipients of
- the Executable Form how they can obtain a copy of such Source Code
- Form by reasonable means in a timely manner, at a charge no more
- than the cost of distribution to the recipient; and
-
-(b) You may distribute such Executable Form under the terms of this
- License, or sublicense it under different terms, provided that the
- license for the Executable Form does not attempt to limit or alter
- the recipients' rights in the Source Code Form under this License.
-
-3.3. Distribution of a Larger Work
-
-You may create and distribute a Larger Work under terms of Your choice,
-provided that You also comply with the requirements of this License for
-the Covered Software. If the Larger Work is a combination of Covered
-Software with a work governed by one or more Secondary Licenses, and the
-Covered Software is not Incompatible With Secondary Licenses, this
-License permits You to additionally distribute such Covered Software
-under the terms of such Secondary License(s), so that the recipient of
-the Larger Work may, at their option, further distribute the Covered
-Software under the terms of either this License or such Secondary
-License(s).
-
-3.4. Notices
-
-You may not remove or alter the substance of any license notices
-(including copyright notices, patent notices, disclaimers of warranty,
-or limitations of liability) contained within the Source Code Form of
-the Covered Software, except that You may alter any license notices to
-the extent required to remedy known factual inaccuracies.
-
-3.5. Application of Additional Terms
-
-You may choose to offer, and to charge a fee for, warranty, support,
-indemnity or liability obligations to one or more recipients of Covered
-Software. However, You may do so only on Your own behalf, and not on
-behalf of any Contributor. You must make it absolutely clear that any
-such warranty, support, indemnity, or liability obligation is offered by
-You alone, and You hereby agree to indemnify every Contributor for any
-liability incurred by such Contributor as a result of warranty, support,
-indemnity or liability terms You offer. You may include additional
-disclaimers of warranty and limitations of liability specific to any
-jurisdiction.
-
-4. Inability to Comply Due to Statute or Regulation
----------------------------------------------------
-
-If it is impossible for You to comply with any of the terms of this
-License with respect to some or all of the Covered Software due to
-statute, judicial order, or regulation then You must: (a) comply with
-the terms of this License to the maximum extent possible; and (b)
-describe the limitations and the code they affect. Such description must
-be placed in a text file included with all distributions of the Covered
-Software under this License. Except to the extent prohibited by statute
-or regulation, such description must be sufficiently detailed for a
-recipient of ordinary skill to be able to understand it.
-
-5. Termination
---------------
-
-5.1. The rights granted under this License will terminate automatically
-if You fail to comply with any of its terms. However, if You become
-compliant, then the rights granted under this License from a particular
-Contributor are reinstated (a) provisionally, unless and until such
-Contributor explicitly and finally terminates Your grants, and (b) on an
-ongoing basis, if such Contributor fails to notify You of the
-non-compliance by some reasonable means prior to 60 days after You have
-come back into compliance. Moreover, Your grants from a particular
-Contributor are reinstated on an ongoing basis if such Contributor
-notifies You of the non-compliance by some reasonable means, this is the
-first time You have received notice of non-compliance with this License
-from such Contributor, and You become compliant prior to 30 days after
-Your receipt of the notice.
-
-5.2. If You initiate litigation against any entity by asserting a patent
-infringement claim (excluding declaratory judgment actions,
-counter-claims, and cross-claims) alleging that a Contributor Version
-directly or indirectly infringes any patent, then the rights granted to
-You by any and all Contributors for the Covered Software under Section
-2.1 of this License shall terminate.
-
-5.3. In the event of termination under Sections 5.1 or 5.2 above, all
-end user license agreements (excluding distributors and resellers) which
-have been validly granted by You or Your distributors under this License
-prior to termination shall survive termination.
-
-************************************************************************
-* *
-* 6. Disclaimer of Warranty *
-* ------------------------- *
-* *
-* Covered Software is provided under this License on an "as is" *
-* basis, without warranty of any kind, either expressed, implied, or *
-* statutory, including, without limitation, warranties that the *
-* Covered Software is free of defects, merchantable, fit for a *
-* particular purpose or non-infringing. The entire risk as to the *
-* quality and performance of the Covered Software is with You. *
-* Should any Covered Software prove defective in any respect, You *
-* (not any Contributor) assume the cost of any necessary servicing, *
-* repair, or correction. This disclaimer of warranty constitutes an *
-* essential part of this License. No use of any Covered Software is *
-* authorized under this License except under this disclaimer. *
-* *
-************************************************************************
-
-************************************************************************
-* *
-* 7. Limitation of Liability *
-* -------------------------- *
-* *
-* Under no circumstances and under no legal theory, whether tort *
-* (including negligence), contract, or otherwise, shall any *
-* Contributor, or anyone who distributes Covered Software as *
-* permitted above, be liable to You for any direct, indirect, *
-* special, incidental, or consequential damages of any character *
-* including, without limitation, damages for lost profits, loss of *
-* goodwill, work stoppage, computer failure or malfunction, or any *
-* and all other commercial damages or losses, even if such party *
-* shall have been informed of the possibility of such damages. This *
-* limitation of liability shall not apply to liability for death or *
-* personal injury resulting from such party's negligence to the *
-* extent applicable law prohibits such limitation. Some *
-* jurisdictions do not allow the exclusion or limitation of *
-* incidental or consequential damages, so this exclusion and *
-* limitation may not apply to You. *
-* *
-************************************************************************
-
-8. Litigation
--------------
-
-Any litigation relating to this License may be brought only in the
-courts of a jurisdiction where the defendant maintains its principal
-place of business and such litigation shall be governed by laws of that
-jurisdiction, without reference to its conflict-of-law provisions.
-Nothing in this Section shall prevent a party's ability to bring
-cross-claims or counter-claims.
-
-9. Miscellaneous
-----------------
-
-This License represents the complete agreement concerning the subject
-matter hereof. If any provision of this License is held to be
-unenforceable, such provision shall be reformed only to the extent
-necessary to make it enforceable. Any law or regulation which provides
-that the language of a contract shall be construed against the drafter
-shall not be used to construe this License against a Contributor.
-
-10. Versions of the License
----------------------------
-
-10.1. New Versions
-
-Mozilla Foundation is the license steward. Except as provided in Section
-10.3, no one other than the license steward has the right to modify or
-publish new versions of this License. Each version will be given a
-distinguishing version number.
-
-10.2. Effect of New Versions
-
-You may distribute the Covered Software under the terms of the version
-of the License under which You originally received the Covered Software,
-or under the terms of any subsequent version published by the license
-steward.
-
-10.3. Modified Versions
-
-If you create software not governed by this License, and you want to
-create a new license for such software, you may create and use a
-modified version of this License if you rename the license and remove
-any references to the name of the license steward (except to note that
-such modified license differs from this License).
-
-10.4. Distributing Source Code Form that is Incompatible With Secondary
-Licenses
-
-If You choose to distribute Source Code Form that is Incompatible With
-Secondary Licenses under the terms of this version of the License, the
-notice described in Exhibit B of this License must be attached.
-
-Exhibit A - Source Code Form License Notice
--------------------------------------------
-
- This Source Code Form is subject to the terms of the Mozilla Public
- License, v. 2.0. If a copy of the MPL was not distributed with this
- file, You can obtain one at http://mozilla.org/MPL/2.0/.
-
-If it is not possible or desirable to put the notice in a particular
-file, then You may include the notice in a location (such as a LICENSE
-file in a relevant directory) where a recipient would be likely to look
-for such a notice.
-
-You may add additional accurate notices of copyright ownership.
-
-Exhibit B - "Incompatible With Secondary Licenses" Notice
----------------------------------------------------------
-
- This Source Code Form is "Incompatible With Secondary Licenses", as
- defined by the Mozilla Public License, v. 2.0.
-
-
-
-OFL-1.1
-
-
-SIL OPEN FONT LICENSE
-
-Version 1.1 - 26 February 2007
-
-PREAMBLE
-The goals of the Open Font License (OFL) are to stimulate worldwide
-development of collaborative font projects, to support the font creation
-efforts of academic and linguistic communities, and to provide a free and
-open framework in which fonts may be shared and improved in partnership
-with others.
-
-The OFL allows the licensed fonts to be used, studied, modified and
-redistributed freely as long as they are not sold by themselves. The
-fonts, including any derivative works, can be bundled, embedded,
-redistributed and/or sold with any software provided that any reserved
-names are not used by derivative works. The fonts and derivatives,
-however, cannot be released under any other type of license. The
-requirement for fonts to remain under this license does not apply
-to any document created using the fonts or their derivatives.
-
-DEFINITIONS
-"Font Software" refers to the set of files released by the Copyright
-Holder(s) under this license and clearly marked as such. This may
-include source files, build scripts and documentation.
-
-"Reserved Font Name" refers to any names specified as such after the
-copyright statement(s).
-
-"Original Version" refers to the collection of Font Software components as
-distributed by the Copyright Holder(s).
-
-"Modified Version" refers to any derivative made by adding to, deleting,
-or substituting -- in part or in whole -- any of the components of the
-Original Version, by changing formats or by porting the Font Software to a
-new environment.
-
-"Author" refers to any designer, engineer, programmer, technical
-writer or other person who contributed to the Font Software.
-
-PERMISSION & CONDITIONS
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of the Font Software, to use, study, copy, merge, embed, modify,
-redistribute, and sell modified and unmodified copies of the Font
-Software, subject to the following conditions:
-
-1) Neither the Font Software nor any of its individual components,
-in Original or Modified Versions, may be sold by itself.
-
-2) Original or Modified Versions of the Font Software may be bundled,
-redistributed and/or sold with any software, provided that each copy
-contains the above copyright notice and this license. These can be
-included either as stand-alone text files, human-readable headers or
-in the appropriate machine-readable metadata fields within text or
-binary files as long as those fields can be easily viewed by the user.
-
-3) No Modified Version of the Font Software may use the Reserved Font
-Name(s) unless explicit written permission is granted by the corresponding
-Copyright Holder. This restriction only applies to the primary font name as
-presented to the users.
-
-4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
-Software shall not be used to promote, endorse or advertise any
-Modified Version, except to acknowledge the contribution(s) of the
-Copyright Holder(s) and the Author(s) or with their explicit written
-permission.
-
-5) The Font Software, modified or unmodified, in part or in whole,
-must be distributed entirely under this license, and must not be
-distributed under any other license. The requirement for fonts to
-remain under this license does not apply to any document created
-using the Font Software.
-
-TERMINATION
-This license becomes null and void if any of the above conditions are
-not met.
-
-DISCLAIMER
-THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
-OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
-COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
-DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
-OTHER DEALINGS IN THE FONT SOFTWARE.
-
-
-
-
-OpenSSL
-
-
-OpenSSL License
-
- ====================================================================
- Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the
- distribution.
-
- 3. All advertising materials mentioning features or use of this
- software must display the following acknowledgment:
- "This product includes software developed by the OpenSSL Project
- for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
-
- 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
- endorse or promote products derived from this software without
- prior written permission. For written permission, please contact
- openssl-core@openssl.org.
-
- 5. Products derived from this software may not be called "OpenSSL"
- nor may "OpenSSL" appear in their names without prior written
- permission of the OpenSSL Project.
-
- 6. Redistributions of any form whatsoever must retain the following
- acknowledgment:
- "This product includes software developed by the OpenSSL Project
- for use in the OpenSSL Toolkit (http://www.openssl.org/)"
-
- THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS`` AND ANY
- EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
- PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
- ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
- NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
- LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
- STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
- OF THE POSSIBILITY OF SUCH DAMAGE.
- ====================================================================
-
- This product includes cryptographic software written by Eric Young
- (eay@cryptsoft.com). This product includes software written by Tim
- Hudson (tjh@cryptsoft.com).
-
-
- Original SSLeay License
- -----------------------
-
-Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
-All rights reserved.
-
- This package is an SSL implementation written
- by Eric Young (eay@cryptsoft.com).
- The implementation was written so as to conform with Netscapes SSL.
-
- This library is free for commercial and non-commercial use as long as
- the following conditions are aheared to. The following conditions
- apply to all code found in this distribution, be it the RC4, RSA,
- lhash, DES, etc., code; not just the SSL code. The SSL documentation
- included with this distribution is covered by the same copyright terms
- except that the holder is Tim Hudson (tjh@cryptsoft.com).
-
- Copyright remains Eric Young`s, and as such any Copyright notices in
- the code are not to be removed.
- If this package is used in a product, Eric Young should be given attribution
- as the author of the parts of the library used.
- This can be in the form of a textual message at program startup or
- in documentation (online or textual) provided with the package.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
- 1. Redistributions of source code must retain the copyright
- notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
- 3. All advertising materials mentioning features or use of this software
- must display the following acknowledgement:
- "This product includes cryptographic software written by
- Eric Young (eay@cryptsoft.com)"
- The word `cryptographic` can be left out if the rouines from the library
- being used are not cryptographic related :-).
- 4. If you include any Windows specific code (or a derivative thereof) from
- the apps directory (application code) you must include an acknowledgement:
- "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
-
- THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS`` AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
-CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- The licence and distribution terms for any publically available version or
-derivative of this code cannot be changed. i.e. this code cannot simply be copied and
-put under another distribution licence
- [including the GNU Public Licence.]
-
-
-
-
-
-
-
-PD
-
-This is a placeholder for the Public Domain License
-
-
-
-Python-2.0
-
-
-PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
---------------------------------------------
-
-1. This LICENSE AGREEMENT is between the Python Software Foundation
-("PSF"), and the Individual or Organization ("Licensee") accessing and
-otherwise using this software ("Python") in source or binary form and
-its associated documentation.
-
-2. Subject to the terms and conditions of this License Agreement, PSF
-hereby grants Licensee a nonexclusive, royalty-free, world-wide
-license to reproduce, analyze, test, perform and/or display publicly,
-prepare derivative works, distribute, and otherwise use Python
-alone or in any derivative version, provided, however, that PSF`s
-License Agreement and PSF`s notice of copyright, i.e., "Copyright (c)
-2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights
-Reserved" are retained in Python alone or in any derivative version
-prepared by Licensee.
-
-3. In the event Licensee prepares a derivative work that is based on
-or incorporates Python or any part thereof, and wants to make
-the derivative work available to others as provided herein, then
-Licensee hereby agrees to include in any such work a brief summary of
-the changes made to Python.
-
-4. PSF is making Python available to Licensee on an "AS IS"
-basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
-FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
-A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
-OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-6. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-7. Nothing in this License Agreement shall be deemed to create any
-relationship of agency, partnership, or joint venture between PSF and
-Licensee. This License Agreement does not grant permission to use PSF
-trademarks or trade name in a trademark sense to endorse or promote
-products or services of Licensee, or any third party.
-
-8. By copying, installing or otherwise using Python, Licensee
-agrees to be bound by the terms and conditions of this License
-Agreement.
-
-BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
--------------------------------------------
-
-BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
-
-1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
-office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
-Individual or Organization ("Licensee") accessing and otherwise using
-this software in source or binary form and its associated
-documentation ("the Software").
-
-2. Subject to the terms and conditions of this BeOpen Python License
-Agreement, BeOpen hereby grants Licensee a non-exclusive,
-royalty-free, world-wide license to reproduce, analyze, test, perform
-and/or display publicly, prepare derivative works, distribute, and
-otherwise use the Software alone or in any derivative version,
-provided, however, that the BeOpen Python License is retained in the
-Software, alone or in any derivative version prepared by Licensee.
-
-3. BeOpen is making the Software available to Licensee on an "AS IS"
-basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
-SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
-AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
-DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-5. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-6. This License Agreement shall be governed by and interpreted in all
-respects by the law of the State of California, excluding conflict of
-law provisions. Nothing in this License Agreement shall be deemed to
-create any relationship of agency, partnership, or joint venture
-between BeOpen and Licensee. This License Agreement does not grant
-permission to use BeOpen trademarks or trade names in a trademark
-sense to endorse or promote products or services of Licensee, or any
-third party. As an exception, the "BeOpen Python" logos available at
-http://www.pythonlabs.com/logos.html may be used according to the
-permissions granted on that web page.
-
-7. By copying, installing or otherwise using the software, Licensee
-agrees to be bound by the terms and conditions of this License
-Agreement.
-
-CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
----------------------------------------
-
-1. This LICENSE AGREEMENT is between the Corporation for National
-Research Initiatives, having an office at 1895 Preston White Drive,
-Reston, VA 20191 ("CNRI"), and the Individual or Organization
-("Licensee") accessing and otherwise using Python 1.6.1 software in
-source or binary form and its associated documentation.
-
-2. Subject to the terms and conditions of this License Agreement, CNRI
-hereby grants Licensee a nonexclusive, royalty-free, world-wide
-license to reproduce, analyze, test, perform and/or display publicly,
-prepare derivative works, distribute, and otherwise use Python 1.6.1
-alone or in any derivative version, provided, however, that CNRI`s
-License Agreement and CNRI`s notice of copyright, i.e., "Copyright (c)
-1995-2001 Corporation for National Research Initiatives; All Rights
-Reserved" are retained in Python 1.6.1 alone or in any derivative
-version prepared by Licensee. Alternately, in lieu of CNRI`s License
-Agreement, Licensee may substitute the following text (omitting the
-quotes): "Python 1.6.1 is made available subject to the terms and
-conditions in CNRI`s License Agreement. This Agreement together with
-Python 1.6.1 may be located on the Internet using the following
-unique, persistent identifier (known as a handle): 1895.22/1013. This
-Agreement may also be obtained from a proxy server on the Internet
-using the following URL: http://hdl.handle.net/1895.22/1013".
-
-3. In the event Licensee prepares a derivative work that is based on
-or incorporates Python 1.6.1 or any part thereof, and wants to make
-the derivative work available to others as provided herein, then
-Licensee hereby agrees to include in any such work a brief summary of
-the changes made to Python 1.6.1.
-
-4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
-basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
-1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
-A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
-OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-6. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-7. This License Agreement shall be governed by the federal
-intellectual property law of the United States, including without
-limitation the federal copyright law, and, to the extent such
-U.S. federal law does not apply, by the law of the Commonwealth of
-Virginia, excluding Virginia`s conflict of law provisions.
-Notwithstanding the foregoing, with regard to derivative works based
-on Python 1.6.1 that incorporate non-separable material that was
-previously distributed under the GNU General Public License (GPL), the
-law of the Commonwealth of Virginia shall govern this License
-Agreement only as to issues arising under or with respect to
-Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
-License Agreement shall be deemed to create any relationship of
-agency, partnership, or joint venture between CNRI and Licensee. This
-License Agreement does not grant permission to use CNRI trademarks or
-trade name in a trademark sense to endorse or promote products or
-services of Licensee, or any third party.
-
-8. By clicking on the "ACCEPT" button where indicated, or by copying,
-installing or otherwise using Python 1.6.1, Licensee agrees to be
-bound by the terms and conditions of this License Agreement.
-
-ACCEPT
-
-CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
---------------------------------------------------
-
-Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
-The Netherlands. All rights reserved.
-
-Permission to use, copy, modify, and distribute this software and its
-documentation for any purpose and without fee is hereby granted,
-provided that the above copyright notice appear in all copies and that
-both that copyright notice and this permission notice appear in
-supporting documentation, and that the name of Stichting Mathematisch
-Centrum or CWI not be used in advertising or publicity pertaining to
-distribution of the software without specific, written prior
-permission.
-
-STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
-THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
-FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
-FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
-WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
-ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
-OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
-
-
-
-SAX-PD
-
-
-Copyright Status for SAX
-
-SAX is free!
-
-In fact, it`s not possible to own a license to SAX, since it`s been placed in the
-public domain.
-
-No Warranty
-
-Because SAX is released to the public domain, there is no warranty for the design or
-for the software implementation, to the extent permitted by applicable law. Except
-when otherwise stated in writing the copyright holders and/or other parties provide
-SAX "as is" without warranty of any kind, either expressed or implied, including, but
-not limited to, the implied warranties of merchantability and fitness for a particular
-purpose. The entire risk as to the quality and performance of SAX is with you. Should
-SAX prove defective, you assume the cost of all necessary servicing, repair or
-correction.
-
-In no event unless required by applicable law or agreed to in writing will any
-copyright holder, or any other party who may modify and/or redistribute SAX, be liable
-to you for damages, including any general, special, incidental or consequential
-damages arising out of the use or inability to use SAX (including but not limited to
-loss of data or data being rendered inaccurate or losses sustained by you or third
-parties or a failure of the SAX to operate with any other programs), even if such
-holder or other party has been advised of the possibility of such damages.
-
-Copyright Disclaimers
-
-This page includes statements to that effect by David Megginson, who would have been
-able to claim copyright for the original work.
-
-SAX 1.0
-
-Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of
-the XML-DEV mailing list, is hereby released into the public domain.
-
-No one owns SAX: you may use it freely in both commercial and non-commercial
-applications, bundle it with your software distribution, include it on a CD-ROM, list
-the source code in a book, mirror the documentation at your own web site, or use it in
-any other way you see fit.
-
-David Megginson, Megginson Technologies Ltd.
-1998-05-11
-
-SAX 2.0
-
-I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release
-all of the SAX 2.0 source code, compiled code, and documentation contained in this
-distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of
-fitness for any purpose.
-
-David Megginson, Megginson Technologies Ltd.
-2000-05-05
-
-
-
-
-SMAIL_GPL
-
-This is the Debian GNU/Linux package debianutils.
-
-It is an original Debian package. Programs in it were maintained by
-Guy Maor <maor@debian.org>, and are now maintained by Clint Adams
-<schizo@debian.org>.
-
-All its programs except readlink, savelog, and which may be
-redistributed under the terms of the GNU GPL, Version 2 or later,
-found on Debian systems in the file /usr/share/common-licenses/GPL.
-
-which is in the public domain.
-
-readlink is Copyright (c) 1997 Kenneth Stailey, and may also be
-distributed under the terms of the BSD copyright.
-
-savelog may be redistributed under the following terms: (The rest of
-this file consists of savelog's distribution terms.)
-
-#ident "@(#)smail:RELEASE-3_2:COPYING,v 1.2 1996/06/14 18:59:10 woods Exp"
-
- SMAIL GENERAL PUBLIC LICENSE
- (Clarified 11 Feb 1988)
-
- Copyright (C) 1988 Landon Curt Noll & Ronald S. Karr
- Copyright (C) 1992 Ronald S. Karr
- Copyleft (GNU) 1988 Landon Curt Noll & Ronald S. Karr
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license, but changing it is not allowed. You can also
- use this wording to make the terms for other programs.
-
- The license agreements of most software companies keep you at the
-mercy of those companies. By contrast, our general public license is
-intended to give everyone the right to share SMAIL. To make sure that
-you get the rights we want you to have, we need to make restrictions
-that forbid anyone to deny you these rights or to ask you to surrender
-the rights. Hence this license agreement.
-
- Specifically, we want to make sure that you have the right to give
-away copies of SMAIL, that you receive source code or else can get it
-if you want it, that you can change SMAIL or use pieces of it in new
-free programs, and that you know you can do these things.
-
- To make sure that everyone has such rights, we have to forbid you to
-deprive anyone else of these rights. For example, if you distribute
-copies of SMAIL, you must give the recipients all the rights that you
-have. You must make sure that they, too, receive or can get the
-source code. And you must tell them their rights.
-
- Also, for our own protection, we must make certain that everyone
-finds out that there is no warranty for SMAIL. If SMAIL is modified by
-someone else and passed on, we want its recipients to know that what
-they have is not what we distributed, so that any problems introduced
-by others will not reflect on our reputation.
-
- Therefore we (Landon Curt Noll and Ronald S. Karr) make the following
-terms which say what you must do to be allowed to distribute or change
-SMAIL.
-
-
- COPYING POLICIES
-
- 1. You may copy and distribute verbatim copies of SMAIL source code
-as you receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy a valid copyright notice "Copyright
-(C) 1988 Landon Curt Noll & Ronald S. Karr" (or with whatever year is
-appropriate); keep intact the notices on all files that refer to this
-License Agreement and to the absence of any warranty; and give any
-other recipients of the SMAIL program a copy of this License
-Agreement along with the program. You may charge a distribution fee
-for the physical act of transferring a copy.
-
- 2. You may modify your copy or copies of SMAIL or any portion of it,
-and copy and distribute such modifications under the terms of
-Paragraph 1 above, provided that you also do the following:
-
- a) cause the modified files to carry prominent notices stating
- that you changed the files and the date of any change; and
-
- b) cause the whole of any work that you distribute or publish,
- that in whole or in part contains or is a derivative of SMAIL or
- any part thereof, to be licensed at no charge to all third
- parties on terms identical to those contained in this License
- Agreement (except that you may choose to grant more extensive
- warranty protection to some or all third parties, at your option).
-
- c) You may charge a distribution fee for the physical act of
- transferring a copy, and you may at your option offer warranty
- protection in exchange for a fee.
-
-Mere aggregation of another unrelated program with this program (or its
-derivative) on a volume of a storage or distribution medium does not bring
-the other program under the scope of these terms.
-
- 3. You may copy and distribute SMAIL (or a portion or derivative of it,
-under Paragraph 2) in object code or executable form under the terms of
-Paragraphs 1 and 2 above provided that you also do one of the following:
-
- a) accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- b) accompany it with a written offer, valid for at least three
- years, to give any third party free (except for a nominal
- shipping charge) a complete machine-readable copy of the
- corresponding source code, to be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- c) accompany it with the information you received as to where the
- corresponding source code may be obtained. (This alternative is
- allowed only for non-commercial distribution and only if you
- received the program in object code or executable form alone.)
-
-For an executable file, complete source code means all the source code for
-all modules it contains; but, as a special exception, it need not include
-source code for modules which are standard libraries that accompany the
-operating system on which the executable file runs.
-
- 4. You may not copy, sublicense, distribute or transfer SMAIL
-except as expressly provided under this License Agreement. Any attempt
-otherwise to copy, sublicense, distribute or transfer SMAIL is void and
-your rights to use the program under this License agreement shall be
-automatically terminated. However, parties who have received computer
-software programs from you with this License Agreement will not have
-their licenses terminated so long as such parties remain in full compliance.
-
- 5. If you wish to incorporate parts of SMAIL into other free
-programs whose distribution conditions are different, write to Landon
-Curt Noll & Ronald S. Karr via the Free Software Foundation at 51
-Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. We have not yet
-worked out a simple rule that can be stated here, but we will often
-permit this. We will be guided by the two goals of preserving the
-free status of all derivatives of our free software and of promoting
-the sharing and reuse of software.
-
-Your comments and suggestions about our licensing policies and our
-software are welcome! This contract was based on the contract made by
-the Free Software Foundation. Please contact the Free Software
-Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
-USA, or call (617) 542-5942 for details on copylefted material in
-general.
-
- NO WARRANTY
-
- BECAUSE SMAIL IS LICENSED FREE OF CHARGE, WE PROVIDE ABSOLUTELY NO
-WARRANTY, TO THE EXTENT PERMITTED BY APPLICABLE STATE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING, LANDON CURT NOLL & RONALD S. KARR AND/OR
-OTHER PARTIES PROVIDE SMAIL "AS IS" WITHOUT WARRANTY OF ANY KIND,
-EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
-THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF SMAIL IS WITH
-YOU. SHOULD SMAIL PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
-NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL LANDON CURT NOLL &
-RONALD S. KARR AND/OR ANY OTHER PARTY WHO MAY MODIFY AND REDISTRIBUTE
-SMAIL AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-LOST PROFITS, LOST MONIES, OR OTHER SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
-(INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
-INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE
-PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) SMAIL, EVEN IF YOU HAVE
-BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY
-ANY OTHER PARTY.
-
-
-
-SUN
-
-SUN MICROSYSTEMS, INC. THROUGH ITS SUN MICROSYSTEMS LABORATORIES
-DIVISION ("SUN") WILL LICENSE THIS SOFTWARE AND THE ACCOMPANYING
-DOCUMENTATION TO YOU (a "Licensee") ONLY ON YOUR ACCEPTANCE OF ALL
-THE TERMS SET FORTH BELOW.
-
-Sun grants Licensee a non-exclusive, royalty-free right to download,
-install, compile, use, copy and distribute the Software, modify or
-otherwise create derivative works from the Software (each, a
-"Modification") and distribute any Modification in source code and/or
-binary code form to its customers with a license agreement containing
-these terms and noting that the Software has been modified. The
-Software is copyrighted by Sun and other third parties and Licensee
-shall retain and reproduce all copyright and other notices presently
-on the Software. As between Sun and Licensee, Sun is the sole owner of
-all rights in and to the Software other than the limited rights
-granted to Licensee herein; Licensee will own its Modifications,
-expressly subject to Sun's continuing ownership of the
-Software. Licensee will, at its expense, defend and indemnify Sun and
-its licensors from and against any third party claims, including costs
-and reasonable attorneys' fees, and be wholly responsible for any
-liabilities arising out of or related to Licensee's development, use
-or distribution of the Software or Modifications. Any distribution of
-the Software and Modifications must comply with all applicable United
-States export control laws.
-
-THE SOFTWARE IS BEING PROVIDED TO LICENSEE "AS IS" AND ALL EXPRESS OR
-IMPLIED CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
-ARE DISCLAIMED. IN NO EVENT WILL SUN BE LIABLE HEREUNDER FOR ANY
-DIRECT DAMAGES OR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES OF ANY KIND.
-
-
-
-Sleepycat
-
-
-The Sleepycat License
-Copyright (c) 1990-1999
-Sleepycat Software. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Redistributions in any form must be accompanied by information on
-how to obtain complete source code for the DB software and any
-accompanying software that uses the DB software. The source code
-must either be included in the distribution or be available for no
-more than the cost of distribution plus a nominal fee, and must be
-freely redistributable under reasonable conditions. For an
-executable file, complete source code means the source code for all
-modules it contains. It does not include source code for modules or
-files that typically accompany the major components of the operating
-system on which the executable file runs.
-THIS SOFTWARE IS PROVIDED BY SLEEPYCAT SOFTWARE ``AS IS`` AND ANY EXPRESS
-OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
-NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL SLEEPYCAT SOFTWARE
-BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
-THE POSSIBILITY OF SUCH DAMAGE.
-
-Copyright (c) 1990, 1993, 1994, 1995
-The Regents of the University of California. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Neither the name of the University nor the names of its contributors
-may be used to endorse or promote products derived from this software
-without specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS`` AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-Copyright (c) 1995, 1996
-The President and Fellows of Harvard University. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Neither the name of the University nor the names of its contributors
-may be used to endorse or promote products derived from this software
-without specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY HARVARD AND ITS CONTRIBUTORS ``AS IS`` AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL HARVARD OR ITS CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-
-
-
-UCB
-
- Copyright (c) 1987, 1989, 1990, 1991, 1992, 1993, 1994
- The Regents of the University of California. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
- 3. Neither the name of the University nor the names of its contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
- ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
- ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
- FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
- DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
- OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
- OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
- SUCH DAMAGE.
-
-
-
-Unicode
-
-COPYRIGHT AND PERMISSION NOTICE
-
-Copyright 1991-2015 Unicode, Inc. All rights reserved.
-Distributed under the Terms of Use in
-http://www.unicode.org/copyright.html.
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of the Unicode data files and any associated documentation
-(the "Data Files") or Unicode software and any associated documentation
-(the "Software") to deal in the Data Files or Software
-without restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, and/or sell copies of
-the Data Files or Software, and to permit persons to whom the Data Files
-or Software are furnished to do so, provided that
-(a) this copyright and permission notice appear with all copies
-of the Data Files or Software,
-(b) this copyright and permission notice appear in associated
-documentation, and
-(c) there is clear notice in each modified Data File or in the Software
-as well as in the documentation associated with the Data File(s) or
-Software that the data or software has been modified.
-
-THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
-ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT OF THIRD PARTY RIGHTS.
-IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
-NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
-DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
-DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
-TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
-PERFORMANCE OF THE DATA FILES OR SOFTWARE.
-
-Except as contained in this notice, the name of a copyright holder
-shall not be used in advertising or otherwise to promote the sale,
-use or other dealings in these Data Files or Software without prior
-written authorization of the copyright holder.
-
-
-
-W3C
-
-
-W3C SOFTWARE NOTICE AND LICENSE
-This work (and included software, documentation such as READMEs, or other related
-items) is being provided by the copyright holders under the following license.
-License
-By obtaining, using and/or copying this work, you (the licensee) agree that you have
-read, understood, and will comply with the following terms and conditions.
-Permission to copy, modify, and distribute this software and its documentation, with
-or without modification, for any purpose and without fee or royalty is hereby granted,
-provided that you include the following on ALL copies of the software and
-documentation or portions thereof, including modifications:
-The full text of this NOTICE in a location viewable to users of the redistributed or
-derivative work.
-Any pre-existing intellectual property disclaimers, notices, or terms and conditions.
-If none exist, the W3C Software Short Notice should be included (hypertext is
-preferred, text is permitted) within the body of any redistributed or derivative code.
-Notice of any changes or modifications to the files, including the date changes were
-made. (We recommend you provide URIs to the location from which the code is derived.)
-Disclaimers
-THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
-REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
-WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF
-THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
-TRADEMARKS OR OTHER RIGHTS.
-COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
-The name and trademarks of copyright holders may NOT be used in advertising or
-publicity pertaining to the software without specific, written prior permission. Title
-to copyright in this software and any associated documentation will at all times
-remain with copyright holders.
-Notes
-This version: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
-This formulation of W3C`s notice and license became active on December 31 2002. This
-version removes the copyright ownership notice such that this license can be used with
-materials other than those owned by the W3C, reflects that ERCIM is now a host of the
-W3C, includes references to this specific dated version of the license, and removes
-the ambiguous grant of "use". Otherwise, this version is the same as the previous
-version and is written so as to preserve the Free Software Foundation`s assessment of
-GPL compatibility and OSI`s certification under the Open Source Definition.
-
-
-
-
-ZPL-2.1
-
-
-ZPL 2.1
-Zope Public License (ZPL) Version 2.1
-
-A copyright notice accompanies this license document that identifies the copyright
-holders.
-
-This license has been certified as open source. It has also been designated as GPL
-compatible by the Free Software Foundation (FSF).
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions in source code must retain the accompanying copyright notice, this
-list of conditions, and the following disclaimer.
-Redistributions in binary form must reproduce the accompanying copyright notice, this
-list of conditions, and the following disclaimer in the documentation and/or other
-materials provided with the distribution.
-Names of the copyright holders must not be used to endorse or promote products derived
-from this software without prior written permission from the copyright holders.
-The right to distribute this software or to use it for any purpose does not give you
-the right to use Servicemarks (sm) or Trademarks (tm) of the copyright holders. Use of
-them is covered by separate agreement with the copyright holders.
-If any files are modified, you must cause the modified files to carry prominent
-notices stating that you changed the files and the date of any change.
-Disclaimer
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS`` AND ANY EXPRESSED OR
-IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
-THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-Zlib
-
-
-zlib License
-
-
- This software is provided `as-is`, without any express or implied
- warranty. In no event will the authors be held liable for any damages
- arising from the use of this software.
-
- Permission is granted to anyone to use this software for any purpose,
- including commercial applications, and to alter it and redistribute it
- freely, subject to the following restrictions:
-
- 1. The origin of this software must not be misrepresented; you must not
- claim that you wrote the original software. If you use this software
- in a product, an acknowledgment in the product documentation would be
- appreciated but is not required.
- 2. Altered source versions must be plainly marked as such, and must not be
- misrepresented as being the original software.
- 3. This notice may not be removed or altered from any source distribution.
-
-
-
-
-
-copyleft-next-0.3.0
-
- copyleft-next 0.3.0 ("this License")
- Release date: 2013-05-16
-
-1. License Grants; No Trademark License
-
- Subject to the terms of this License, I grant You:
-
- a) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
- copyright license, to reproduce, Distribute, prepare derivative works
- of, publicly perform and publicly display My Work.
-
- b) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
- patent license under Licensed Patents to make, have made, use, sell,
- offer for sale, and import Covered Works.
-
- This License does not grant any rights in My name, trademarks, service
- marks, or logos.
-
-2. Distribution: General Conditions
-
- You may Distribute Covered Works, provided that You (i) inform
- recipients how they can obtain a copy of this License; (ii) satisfy the
- applicable conditions of sections 3 through 6; and (iii) preserve all
- Legal Notices contained in My Work (to the extent they remain
- pertinent). "Legal Notices" means copyright notices, license notices,
- license texts, and author attributions, but does not include logos,
- other graphical images, trademarks or trademark legends.
-
-3. Conditions for Distributing Derived Works; Outbound GPL Compatibility
-
- If You Distribute a Derived Work, You must license the entire Derived
- Work as a whole under this License, with prominent notice of such
- licensing. This condition may not be avoided through such means as
- separate Distribution of portions of the Derived Work. You may
- additionally license the Derived Work under the GPL, so that the
- recipient may further Distribute the Derived Work under either this
- License or the GPL.
-
-4. Condition Against Further Restrictions; Inbound License Compatibility
-
- When Distributing a Covered Work, You may not impose further
- restrictions on the exercise of rights in the Covered Work granted under
- this License. This condition is not excused merely because such
- restrictions result from Your compliance with conditions or obligations
- extrinsic to this License (such as a court order or an agreement with a
- third party).
-
- However, You may Distribute a Covered Work incorporating material
- governed by a license that is both OSI-Approved and FSF-Free as of the
- release date of this License, provided that Your Distribution complies
- with such other license.
-
-5. Conditions for Distributing Object Code
-
- You may Distribute an Object Code form of a Covered Work, provided that
- you accompany the Object Code with a URL through which the Corresponding
- Source is made available, at no charge, by some standard or customary
- means of providing network access to source code.
-
- If you Distribute the Object Code in a physical product or tangible
- storage medium ("Product"), the Corresponding Source must be available
- through such URL for two years from the date of Your most recent
- Distribution of the Object Code in the Product. However, if the Product
- itself contains or is accompanied by the Corresponding Source (made
- available in a customarily accessible manner), You need not also comply
- with the first paragraph of this section.
-
- Each recipient of the Covered Work from You is an intended third-party
- beneficiary of this License solely as to this section 5, with the right
- to enforce its terms.
-
-6. Symmetrical Licensing Condition for Upstream Contributions
-
- If You Distribute a work to Me specifically for inclusion in or
- modification of a Covered Work (a "Patch"), and no explicit licensing
- terms apply to the Patch, You license the Patch under this License, to
- the extent of Your copyright in the Patch. This condition does not
- negate the other conditions of this License, if applicable to the Patch.
-
-7. Nullification of Copyleft/Proprietary Dual Licensing
-
- If I offer to license, for a fee, a Covered Work under terms other than
- a license that is OSI-Approved or FSF-Free as of the release date of this
- License or a numbered version of copyleft-next released by the
- Copyleft-Next Project, then the license I grant You under section 1 is no
- longer subject to the conditions in sections 2 through 5.
-
-8. Copyleft Sunset
-
- The conditions in sections 2 through 5 no longer apply once fifteen
- years have elapsed from the date of My first Distribution of My Work
- under this License.
-
-9. Pass-Through
-
- When You Distribute a Covered Work, the recipient automatically receives
- a license to My Work from Me, subject to the terms of this License.
-
-10. Termination
-
- Your license grants under section 1 are automatically terminated if You
-
- a) fail to comply with the conditions of this License, unless You cure
- such noncompliance within thirty days after becoming aware of it, or
-
- b) initiate a patent infringement litigation claim (excluding
- declaratory judgment actions, counterclaims, and cross-claims)
- alleging that any part of My Work directly or indirectly infringes
- any patent.
-
- Termination of Your license grants extends to all copies of Covered
- Works You subsequently obtain. Termination does not terminate the
- rights of those who have received copies or rights from You subject to
- this License.
-
- To the extent permission to make copies of a Covered Work is necessary
- merely for running it, such permission is not terminable.
-
-11. Later License Versions
-
- The Copyleft-Next Project may release new versions of copyleft-next,
- designated by a distinguishing version number ("Later Versions").
- Unless I explicitly remove the option of Distributing Covered Works
- under Later Versions, You may Distribute Covered Works under any Later
- Version.
-
-** 12. No Warranty **
-** **
-** My Work is provided "as-is", without warranty. You bear the risk **
-** of using it. To the extent permitted by applicable law, each **
-** Distributor of My Work excludes the implied warranties of title, **
-** merchantability, fitness for a particular purpose and **
-** non-infringement. **
-
-** 13. Limitation of Liability **
-** **
-** To the extent permitted by applicable law, in no event will any **
-** Distributor of My Work be liable to You for any damages **
-** whatsoever, whether direct, indirect, special, incidental, or **
-** consequential damages, whether arising under contract, tort **
-** (including negligence), or otherwise, even where the Distributor **
-** knew or should have known about the possibility of such damages. **
-
-14. Severability
-
- The invalidity or unenforceability of any provision of this License
- does not affect the validity or enforceability of the remainder of
- this License. Such provision is to be reformed to the minimum extent
- necessary to make it valid and enforceable.
-
-15. Definitions
-
- "Copyleft-Next Project" means the project that maintains the source
- code repository at <https://gitorious.org/copyleft-next/> as of the
- release date of this License.
-
- "Corresponding Source" of a Covered Work in Object Code form means (i)
- the Source Code form of the Covered Work; (ii) all scripts,
- instructions and similar information that are reasonably necessary for
- a skilled developer to generate such Object Code from the Source Code
- provided under (i); and (iii) a list clearly identifying all Separate
- Works (other than those provided in compliance with (ii)) that were
- specifically used in building and (if applicable) installing the
- Covered Work (for example, a specified proprietary compiler including
- its version number). Corresponding Source must be machine-readable.
-
- "Covered Work" means My Work or a Derived Work.
-
- "Derived Work" means a work of authorship that copies from, modifies,
- adapts, is based on, is a derivative work of, transforms, translates or
- contains all or part of My Work, such that copyright permission is
- required. The following are not Derived Works: (i) Mere Aggregation;
- (ii) a mere reproduction of My Work; and (iii) if My Work fails to
- explicitly state an expectation otherwise, a work that merely makes
- reference to My Work.
-
- "Distribute" means to distribute, transfer or make a copy available to
- someone else, such that copyright permission is required.
-
- "Distributor" means Me and anyone else who Distributes a Covered Work.
-
- "FSF-Free" means classified as 'free' by the Free Software Foundation.
-
- "GPL" means a version of the GNU General Public License or the GNU
- Affero General Public License.
-
- "I"/"Me"/"My" refers to the individual or legal entity that places My
- Work under this License. "You"/"Your" refers to the individual or legal
- entity exercising rights in My Work under this License. A legal entity
- includes each entity that controls, is controlled by, or is under
- common control with such legal entity. "Control" means (a) the power to
- direct the actions of such legal entity, whether by contract or
- otherwise, or (b) ownership of more than fifty percent of the
- outstanding shares or beneficial ownership of such legal entity.
-
- "Licensed Patents" means all patent claims licensable royalty-free by
- Me, now or in the future, that are necessarily infringed by making,
- using, or selling My Work, and excludes claims that would be infringed
- only as a consequence of further modification of My Work.
-
- "Mere Aggregation" means an aggregation of a Covered Work with a
- Separate Work.
-
- "My Work" means the particular work of authorship I license to You
- under this License.
-
- "Object Code" means any form of a work that is not Source Code.
-
- "OSI-Approved" means approved as 'Open Source' by the Open Source
- Initiative.
-
- "Separate Work" means a work that is separate from and independent of a
- particular Covered Work and is not by its nature an extension or
- enhancement of the Covered Work, and/or a runtime library, standard
- library or similar component that is used to generate an Object Code
- form of a Covered Work.
-
- "Source Code" means the preferred form of a work for making
- modifications to it.
-
-
-
-tcl
-
-This software is copyrighted by the Regents of the University of
-California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
-Corporation and other parties. The following terms apply to all files
-associated with the software unless explicitly disclaimed in
-individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7014 (b) (3) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
-
-
-
- Proprietary Licenses
-
-Enea
-
- Copyright (C) 2006 by Enea.
- All rights reserved.
-
- This Software is furnished under a software license agreement and
- may be used only in accordance with the terms of such agreement.
- Any other use or reproduction is prohibited. No title to and
- ownership of the Software is hereby transferred.
-
- PROPRIETARY NOTICE
- This Software consists of confidential information.
- Trade secret law and copyright law protect this Software.
- The above notice of copyright on this Software does not indicate
- any actual or intended publication of such Software.
-
-
-
-
--
cgit v1.2.3-54-g00ecf
From 35b8406aa5eed1d598db530d9826475a63939fa1 Mon Sep 17 00:00:00 2001
From: Jenkins for Enea Linux Test Framework
Date: Wed, 24 Feb 2021 10:56:36 +0100
Subject: Updated licenses.xml
---
.../doc/licenses.xml | 9936 ++++++++++++++++++++
1 file changed, 9936 insertions(+)
(limited to 'doc/book-enea-nfv-access-platform-open-source')
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
index e69de29..352f820 100644
--- a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
@@ -0,0 +1,9936 @@
+
+
+
+ Packages and Licenses
+
+
+ Packages
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Package Name
+ Version
+ Description
+ License
+
+
+
+
+
+
+ 4g-sierra
+ 1.0
+ Scripts to setup 4G modems from Sierra
+ Enea
+
+
+ acl
+ 2.2.52
+ Utilities for managing POSIX Access Control Lists.
+ LGPL-2.1, GPL-2.0
+
+
+ acpid
+ 2.0.28
+ A daemon for delivering ACPI events.
+ GPL-2.0
+
+
+ alsa-lib
+ 1.1.4.1
+ ALSA sound library.
+ LGPL-2.1, GPL-2.0
+
+
+ ant
+ 1.8.1
+ Another Neat Tool - build system for Java
+ Apache-2.0
+
+
+ antlr
+ 2.7.7
+ Framework for constructing recognizers interpreters compilers and translators
+ PD
+
+
+ apache2
+ 2.4.27
+ The Apache HTTP Server is a powerful efficient and extensible web server.
+ Apache-2.0
+
+
+ apr-util
+ 1.6.0
+ Apache Portable Runtime (APR) companion library.
+ Apache-2.0
+
+
+ apr
+ 1.6.2
+ Apache Portable Runtime (APR) library.
+ Apache-2.0
+
+
+ apt
+ 1.2.24
+ Advanced front-end for dpkg.
+ GPL-2.0
+
+
+ attr
+ 2.4.47
+ Utilities for manipulating filesystem extended attributes.
+ LGPL-2.1, GPL-2.0
+
+
+ aufs-util
+ 4.4
+ Tools for managing AUFS mounts.
+ GPL-2.0
+
+
+ augeas
+ 1.5.0
+ Augeas configuration API.
+ LGPL-2.1
+
+
+ autoconf-archive
+ 2016.09.16
+ a collection of freely re-usable Autoconf macros.
+ GPL-3.0-with-autoconf-exception
+
+
+ autoconf
+ 2.69
+ Autoconf is an extensible package of M4 macros that produce shell scripts to automatically configure software source code packages. Autoconf creates a configuration script for a package from a template file that lists the operating system features that the package can use in the form of M4 macro calls.
+ GPL-2.0, GPL-3.0
+
+
+ automake
+ 1.15.1
+ Automake is a tool for automatically generating `Makefile.in' files compliant with the GNU Coding Standards. Automake requires the use of Autoconf.
+ GPL-2.0
+
+
+ avahi
+ 0.6.32
+ "Avahi is a fully LGPL framework for Multicast DNS Service Discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. This tool implements IPv4LL ""Dynamic Configuration of IPv4 Link-Local Addresses"" (IETF RFC3927) a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server."
+ GPL-2.0, LGPL-2.1
+
+
+ avalon-framework-api
+ 4.3
+ Common way for components to be created initialized configured started. (API-only)
+ Apache-2.0
+
+
+ base-files
+ 3.0.14
+ The base-files package creates the basic system directory structure and provides a small set of key configuration files for the system.
+ GPL-2.0
+
+
+ base-passwd
+ 3.5.29
+ The master copies of the user database files (/etc/passwd and /etc/group). The update-passwd tool is also provided to keep the system databases synchronized with these master files.
+ GPL-2.0
+
+
+ bash-completion
+ 2.7
+ Programmable Completion for Bash 4.
+ GPL-2.0
+
+
+ bash
+ 4.4
+ An sh-compatible command language interpreter.
+ GPL-3.0
+
+
+ bc
+ 1.06
+ Arbitrary precision calculator language.
+ GPL-2.0, LGPL-2.1
+
+
+ bcel
+ 5.2
+ Java Bytecode manipulation library
+ Apache-2.0
+
+
+ bind
+ 9.10.5-P3
+ ISC Internet Domain Name Server.
+ ISC, BSD
+
+
+ binutils-cross-x86_64
+ 2.29.1
+ The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
+ GPL-3.0
+
+
+ binutils
+ 2.29.1
+ The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
+ GPL-3.0
+
+
+ bison
+ 3.0.4
+ Bison is a general-purpose parser generator that converts an annotated context-free grammar into an LALR(1) or GLR parser for that grammar. Bison is upward compatible with Yacc: all properly-written Yacc grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with little trouble.
+ GPL-3.0
+
+
+ bjam
+ 1.64.0
+ Portable Boost.Jam build tool for boost.
+ BSL-1.0, MIT, Python-2.0
+
+
+ bmap-tools
+ 3.4
+ "Bmap-tools - tools to generate block map (AKA bmap) and flash images using bmap. Bmaptool is a generic tool for creating the block map (bmap) for a file and copying files using the block map. The idea is that large file containing unused blocks like raw system image files can be copied or flashed a lot faster with bmaptool than with traditional tools like ""dd"" or ""cp""."
+ GPL-2.0
+
+
+ boost
+ 1.64.0
+ Free peer-reviewed portable C++ source libraries.
+ BSL-1.0, MIT, Python-2.0
+
+
+ bridge-utils
+ 1.5
+ Tools for ethernet bridging.
+ GPL-2.0
+
+
+ bsf
+ 2.4.0
+ Bean Scripting Framework package
+ Apache-2.0
+
+
+ btrfs-tools
+ 4.12
+ Btrfs is a new copy on write filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance repair and easy administration. This package contains utilities (mkfs fsck btrfsctl) used to work with btrfs and an utility (btrfs-convert) to make a btrfs filesystem from an ext3.
+ GPL-2.0
+
+
+ busybox
+ 1.24.1
+ BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for most of the utilities you usually find in GNU fileutils shellutils etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete POSIX environment for any small or embedded system.
+ GPL-2.0, BSD-4-Clause
+
+
+ bzip2
+ 1.0.6
+ bzip2 compresses files using the Burrows-Wheeler block-sorting text compression algorithm and Huffman coding. Compression is generally considerably better than that achieved by more conventional LZ77/LZ78-based compressors and approaches the performance of the PPM family of statistical compressors.
+ BSD-4-Clause
+
+
+ ca-certificates
+ 20170717
+ This package includes PEM files of CA certificates to allow SSL-based applications to check for the authenticity of SSL connections. This derived from Debian's CA Certificates.
+ GPL-2.0, MPL-2.0
+
+
+ cacao-initial
+ 0.98
+ CacaoVM for use as OpenEmbedded's Java VM
+ GPL-2.0
+
+
+ cairo
+ 1.14.10
+ Cairo is a multi-platform library providing anti-aliased vector-based rendering for multiple target backends. Paths consist of line segments and cubic splines and can be rendered at any width with various join and cap styles. All colors may be specified with optional translucence (opacity/alpha) and combined using the extended Porter/Duff compositing algebra as found in the X Render Extension.
+ MPL-1.0, LGPL-2.1, GPL-3.0
+
+
+ cantarell-fonts
+ 0.0.24
+ The Cantarell font typeface is designed as a contemporary Humanist sans serif and was developed for on-screen reading; in particular reading web pages on an HTC Dream mobile phone.
+ OFL-1.1
+
+
+ cdrkit
+ 1.1.11
+ CD/DVD command line tools.
+ GPL-2.0
+
+
+ cdrtools
+ 3.01a31
+ A set of tools for CD recording including cdrecord.
+ GPL-2.0, CDDL-1.0, LGPL-2.1
+
+
+ classpath-initial
+ 0.93
+ Java1.4-compatible GNU Classpath variant that is used as bootclasspath for jikes-native.
+ GPL-2.0, SAX-PD
+
+
+ classpath
+ 0.99
+ GNU Classpath standard Java libraries - For native Java-dependent programs
+ GPL-2.0, SAX-PD
+
+
+ cloud-init
+ 0.7.6
+ Init scripts for use on cloud images
+ GPL-3.0
+
+
+ cmake
+ 3.8.2
+ Cross-platform open-source make system.
+ BSD
+
+
+ collectd
+ 5.12.0
+ collectd is a daemon which collects system performance statistics periodically and provides mechanisms to store the values in a variety of ways for example in RRD files.
+ GPL-2.0, MIT
+
+
+ commons-logging
+ 1.1.1
+ Java Internet protocol suite library
+ Apache-2.0
+
+
+ commons-net
+ 1.4.1
+ Java Internet protocol suite library
+ Apache-2.0
+
+
+ compose-file
+ 3.0
+ Parser for the Compose file format (version 3)
+ Apache-2.0
+
+
+ containerd-docker
+ v0.2.x
+ containerd is a daemon to control runC built for performance and density. containerd leverages runC's advanced features such as seccomp and user namespace support as well as checkpoint and restore for cloning and live migration of containers.
+ Apache-2.0
+
+
+ core-image-minimal-initramfs
+ 1.0
+ Small image capable of booting a device. The kernel includes the Minimal RAM-based Initial Root Filesystem (initramfs) which finds the first 'init' program more efficiently.
+ MIT
+
+
+ coreutils
+ 8.27
+ The GNU Core Utilities provide the basic file shell and text manipulation utilities. These are the core utilities which are expected to exist on every system.
+ GPL-3.0
+
+
+ crda
+ 3.18
+ Wireless Central Regulatory Domain Agent.
+ copyleft-next-0.3.0
+
+
+ cross-localedef
+ 2.26
+ Cross locale generation tool for glibc.
+ LGPL-2.1
+
+
+ cryptodev-linux
+ 1.9
+ A /dev/crypto device driver header file.
+ GPL-2.0
+
+
+ cup
+ 0.10k
+ Lexical analyzer generator for Java
+ CUP
+
+
+ curl
+ 7.58.0
+ Command line tool and library for client-side URL transfers.
+ MIT
+
+
+ cwautomacros
+ 20110201
+ Collection of autoconf m4 macros.
+ GPL-2.0
+
+
+ db
+ 5.3.28
+ Berkeley Database v5.
+ Sleepycat
+
+
+ dbus-glib
+ 0.108
+ GLib bindings for the D-Bus message bus that integrate the D-Bus library with the GLib thread abstraction and main loop.
+ AFL-2.0, GPL-2.0
+
+
+ dbus-test
+ 1.10.20
+ D-Bus test package (for D-bus functionality testing only).
+ AFL-2.0, GPL-2.0
+
+
+ dbus
+ 1.10.20
+ "D-Bus is a message bus system a simple way for applications to talk to one another. In addition to interprocess communication D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a \""single instance\"" application or daemon and to launch applications and daemons on demand when their services are needed."
+ AFL-2.0, GPL-2.0
+
+
+ debianutils
+ 4.8.1.1
+ Miscellaneous utilities specific to Debian.
+ GPL-2.0, SMAIL_GPL
+
+
+ depmodwrapper
+ 1.0
+ Wrapper script for the Linux kernel module dependency indexer.
+ MIT
+
+
+ dhcp
+ 4.3.6
+ DHCP (Dynamic Host Configuration Protocol) is a protocol which allows individual devices on an IP network to get their own network configuration information from a server. DHCP helps make it easier to administer devices.
+ ISC
+
+
+ diffutils
+ 3.6
+ Diffutils contains the GNU diff diff3 sdiff and cmp utilities. These programs are usually used for creating patch files.
+ GPL-3.0
+
+
+ dmidecode
+ 3.1
+ DMI (Desktop Management Interface) table related utilities.
+ GPL-2.0
+
+
+ dnsmasq
+ 2.78
+ Lightweight easy to configure DNS forwarder and DHCP server.
+ GPL-2.0, GPL-3.0
+
+
+ docker
+ 17.06.0
+ Linux container runtime Docker complements kernel namespacing with a high-level API which operates at the process level. It runs unix processes with strong guarantees of isolation and repeatability across servers. . Docker is a great building block for automating distributed systems: large-scale web deployments database clusters continuous deployment systems private PaaS service-oriented architectures etc. . This package contains the daemon and client. Using docker.io is officially supported on x86_64 and arm (32-bit) hosts. Other architectures are considered experimental. . Also note that kernel version 3.10 or above is required for proper operation of the daemon process and that any lower versions may have subtle and/or glaring issues.
+ Apache-2.0
+
+
+ dosfstools
+ 4.1
+ DOS FAT Filesystem Utilities.
+ GPL-3.0
+
+
+ dpdk-dev-libibverbs
+ 1.2.1-3.4-2.0.0.0
+ libibverbs library to support Mellanox config
+ GPL-2.0
+
+
+ dpdk
+ 18.02
+ Intel(r) Data Plane Development Kit
+ BSD, LGPL-2.0, GPL-2.0
+
+
+ dpkg
+ 1.18.24
+ Package maintenance system from Debian.
+ GPL-2.0
+
+
+ dtc
+ 1.4.4
+ The Device Tree Compiler is a tool used to manipulate the Open-Firmware-like device tree used by PowerPC kernels.
+ GPL-2.0, BSD
+
+
+ e2fsprogs
+ 1.43.5
+ The Ext2 Filesystem Utilities (e2fsprogs) contain all of the standard utilities for creating fixing configuring and debugging ext2 filesystems.
+ GPL-2.0, LGPL-2.0, BSD, MIT
+
+
+ ebtables
+ 2.0.10-4
+ Utility for basic Ethernet frame filtering on a Linux bridge advanced logging MAC DNAT/SNAT and brouting.
+ GPL-2.0
+
+
+ ecj-bootstrap
+ 1.0
+ JDT Core Batch Compiler - Bootstrap variant
+ MIT
+
+
+ ecj-initial
+ 1.0
+ JDT Core Batch Compiler - Bootstrap variant
+ MIT
+
+
+ efibootmgr
+ 0.15
+ Linux user-space application to modify the EFI Boot Manager.
+ GPL-2.0
+
+
+ efitools
+ 1.7.0
+ From the EFI Tools package in the Linux user-space it's now possible to read and manipulate the UEFI signatures database via the new efi-readvar and efi-updatevar commands. Aside from needing efitools 1.4 the EFIVARFS file-system is also needed which was only introduced in the Linux 3.8 kernel.
+ GPL-2.0
+
+
+ efivar
+ 0.31
+ efivar provides a simple command line interface to the UEFI variable facility
+ LGPL-2.1
+
+
+ element-vcpe
+ 4.1.3
+ vCPE(based on Element-ODM)
+ Enea, BSD, BSD-2-Clause, GPL-3.0, ISC, LGPL-2.1
+
+
+ elfutils
+ 0.170
+ Utilities and libraries for handling compiled object files.
+ GPL-3.0, Elfutils-Exception
+
+
+ enea-nfv-access-vnf
+ 1.0
+ VNF image of the Enea NFV Access Platform includes kernel rootfs and boot parameters
+ MIT
+
+
+ enea-nfv-access
+ 1.0
+ Image for the host side of the Enea NFV Access Platform with ODM and NETCONF Edgelink customizations
+ MIT
+
+
+ ethtool
+ 4.11
+ A small utility for examining and tuning the settings of your ethernet-based network interfaces.
+ GPL-2.0
+
+
+ expat
+ 2.2.3
+ Expat is an XML parser library written in C. It is a stream-oriented parser in which an application registers handlers for things the parser might find in the XML document (like start tags)
+ MIT
+
+
+ fastjar
+ 0.98
+ jar replacement written in C.
+ GPL-2.0
+
+
+ file
+ 5.31
+ File attempts to classify files depending on their contents and prints a description if a match is found.
+ BSD
+
+
+ findutils
+ 4.6.0
+ The GNU Find Utilities are the basic directory searching utilities of the GNU operating system. These programs are typically used in conjunction with other programs to provide modular and powerful directory search and file locating capabilities to other commands.
+ GPL-3.0
+
+
+ flex
+ 2.6.0
+ Flex is a fast lexical analyser generator. Flex is a tool for generating programs that recognize lexical patterns in text.
+ BSD
+
+
+ fontconfig
+ 2.12.4
+ Fontconfig is a font configuration and customization library which does not depend on the X Window System. It is designed to locate fonts within the system and select them according to requirements specified by applications. Fontconfig is not a rasterization library nor does it impose a particular rasterization library on the application. The X-specific library 'Xft' uses fontconfig along with freetype to specify and rasterize fonts.
+ MIT, PD
+
+
+ freetype
+ 2.8
+ FreeType is a software font engine that is designed to be small efficient highly customizable and portable while capable of producing high-quality output (glyph images). It can be used in graphics libraries display servers font conversion tools text image generation tools and many other products as well.
+ FreeType, GPL-2.0
+
+
+ fuse
+ 2.9.7
+ FUSE (Filesystem in Userspace) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. FUSE also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations.
+ GPL-2.0, LGPL-2.0
+
+
+ gawk
+ 4.1.4
+ The GNU version of awk a text processing utility. Awk interprets a special-purpose programming language to do quick and easy text pattern matching and reformatting jobs.
+ GPL-3.0
+
+
+ gcc-cross-initial-x86_64
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc-cross-x86_64
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc-runtime
+ 7.3.0
+ Runtime libraries from GCC.
+ GPL-3.0-with-GCC-exception
+
+
+ gcc-source-7.3.0
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gdbm
+ 1.13
+ Key/value database library with extensible hashing.
+ GPL-3.0
+
+
+ gettext-minimal
+ 0.19.8.1
+ Contains the m4 macros sufficient to support building autoconf/automake. This provides a significant build time speedup by the removal of gettext-native from most dependency chains (now only needed for gettext for the target).
+ FSF-Unlimited
+
+
+ gettext
+ 0.19.8.1
+ GNU gettext is a set of tools that provides a framework to help other programs produce multi-lingual messages. These tools include a set of conventions about how programs should be written to support message catalogs a directory and file naming organization for the message catalogs themselves a runtime library supporting the retrieval of translated messages and a few stand-alone programs to massage in various ways the sets of translatable and already translated strings.
+ GPL-3.0, LGPL-2.1
+
+
+ giflib
+ 5.1.4
+ shared library for GIF images.
+ MIT
+
+
+ git
+ 2.13.3
+ Distributed version control system.
+ GPL-2.0
+
+
+ glib-2.0
+ 2.52.3
+ GLib is a general-purpose utility library which provides many useful data types macros type conversions string utilities file utilities a main loop abstraction and so on.
+ LGPL-2.0, BSD, PD
+
+
+ glibc-locale
+ 2.26
+ Locale data from glibc.
+ GPL-2.0, LGPL-2.1
+
+
+ glibc
+ 2.26
+ The GNU C Library is used as the system C library in most systems with the Linux kernel.
+ GPL-2.0, LGPL-2.1
+
+
+ gmp
+ 6.1.2
+ GMP is a free library for arbitrary precision arithmetic operating on signed integers rational numbers and floating point numbers
+ GPL-2.0, LGPL-3.0
+
+
+ gnome-desktop-testing
+ 2014.1
+ Test runner for GNOME-style installed tests.
+ LGPL-2.0
+
+
+ gnu-config
+ 20150728
+ Tool that installs the GNU config.guess / config.sub into a directory tree
+ GPL-3.0-with-autoconf-exception
+
+
+ gnu-efi
+ 3.0.6
+ Libraries for producing EFI binaries.
+ GPL-2.0, BSD-2-Clause
+
+
+ gnujaf
+ 1.1.1
+ Provides a mean to type data and locate components suitable for performing various kinds of action on it.
+ GPL-2.0-with-GCC-exception
+
+
+ gnulib
+ 2017-08-20.18
+ A collection of software subroutines which are designed to be usable on many operating systems. The goal of the project is to make it easy for free software authors to make their software run on many operating systems. Since source is designed to be copied from gnulib it is not a library per-se as much as a collection of portable idioms to be used in other projects.
+ LGPL-2.0
+
+
+ gnumail
+ 1.1.2
+ GNU's free implementation of the JavaMail API specification
+ GPL-2.0-with-GCC-exception
+
+
+ gnutls
+ 3.5.13
+ GNU Transport Layer Security Library.
+ GPL-3.0, LGPL-2.1
+
+
+ go-capability
+ 0.0
+ Utilities for manipulating POSIX capabilities in Go.
+ BSD-2-Clause
+
+
+ go-cli
+ 1.1.0
+ A small package for building command line apps in Go
+ MIT
+
+
+ go-connections
+ 0.2.1
+ Utility package to work with network connections
+ Apache-2.0
+
+
+ go-context
+ git
+ A golang registry for global request variables.
+ BSD-3-Clause
+
+
+ go-cross-x86_64
+ 1.9.4
+ The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
+ BSD-3-Clause
+
+
+ go-dbus
+ 4.0.0
+ Native Go bindings for D-Bus
+ BSD-2-Clause
+
+
+ go-distribution
+ 2.6.0
+ The Docker toolset to pack ship store and deliver content
+ Apache-2.0
+
+
+ go-fsnotify
+ 1.2.11
+ A golang registry for global request variables.
+ BSD-3-Clause
+
+
+ go-libtrust
+ 0.0
+ Primitives for identity and authorization
+ Apache-2.0
+
+
+ go-logrus
+ 0.11.0
+ A golang registry for global request variables.
+ MIT
+
+
+ go-mux
+ git
+ A powerful URL router and dispatcher for golang.
+ BSD-3-Clause
+
+
+ go-patricia
+ 2.2.6
+ A generic patricia trie (also called radix tree) implemented in Go (Golang)
+ MIT
+
+
+ go-pty
+ git
+ PTY interface for Go
+ MIT
+
+
+ go-systemd
+ 4
+ Go bindings to systemd socket activation journal D-Bus and unit files
+ Apache-2.0
+
+
+ go
+ 1.9.4
+ The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
+ BSD-3-Clause
+
+
+ gobject-introspection
+ 1.52.1
+ Middleware layer between GObject-using C libraries and language bindings.
+ LGPL-2.0, GPL-2.0
+
+
+ gotty
+ 1.0
+ Run a terminal application as a web service
+ MIT
+
+
+ gperf
+ 3.1
+ GNU gperf is a perfect hash function generator
+ GPL-3.0
+
+
+ gpgme
+ 1.9.0
+ GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a High-Level Crypto API for encryption decryption signing signature verification and key management
+ GPL-2.0, LGPL-2.1
+
+
+ gptfdisk
+ 1.0.3
+ GPT fdisk is a disk partitioning tool loosely modeled on Linux fdisk but used for modifying GUID Partition Table (GPT) disks. The related FixParts utility fixes some common problems on Master Boot Record (MBR) disks.
+ GPL-2.0
+
+
+ grep
+ 3.1
+ GNU grep utility.
+ GPL-3.0
+
+
+ groff
+ 1.22.3
+ The groff (GNU troff) software is a typesetting package which reads plain text mixed with formatting commands and produces formatted output.
+ GPL-3.0
+
+
+ grpc-go
+ 1.4.0
+ The Go language implementation of gRPC. HTTP/2 based RPC
+ BSD
+
+
+ grub-disable-fallback
+ 1.0
+ Enea service to disable grub fallback when boot is successful
+ Enea
+
+
+ grub-efi
+ 2.02
+ GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
+ GPL-3.0
+
+
+ grub
+ 2.02
+ GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
+ GPL-3.0
+
+
+ gtk-doc
+ 1.25
+ Gtk-doc is a set of scripts that extract specially formatted comments from glib-based software and produce a set of html documentation files from them
+ GPL-2.0
+
+
+ gzip
+ 1.8
+ GNU Gzip is a popular data compression program originally written by Jean-loup Gailly for the GNU project. Mark Adler wrote the decompression part
+ GPL-3.0
+
+
+ harfbuzz
+ 1.4.8
+ HarfBuzz is an OpenType text shaping engine.
+ MIT
+
+
+ haveged
+ 1.9.1
+ The haveged project is an attempt to provide an easy-to-use unpredictable random number generator based upon an adaptation of the HAVEGE algorithm. Haveged was created to remedy low-entropy conditions in the Linux random device that can occur under some workloads especially on headless servers.
+ GPL-3.0
+
+
+ help2man
+ 1.47.4
+ Program for creating simple man pages.
+ GPL-3.0
+
+
+ hostapd
+ 2.9
+ User space daemon for extended IEEE 802.11 management.
+ BSD-3-Clause
+
+
+ htop
+ 1.0.3
+ htop process monitor.
+ GPL-2.0
+
+
+ hugepage-reservation
+ 1.0
+ Reserve hugepages on system startup.
+ Enea
+
+
+ icedtea7
+ 2.1.3
+ Harness to build the source code from OpenJDK using Free Software build tools
+ GPL-2.0-with-classpath-exception
+
+
+ icu
+ 59.1
+ The International Component for Unicode (ICU) is a mature portable set of C/C++ and Java libraries for Unicode support software internationalization (I18N) and globalization (G11N) giving applications the same results on all platforms.
+ ICU
+
+
+ inetlib
+ 1.1.1
+ GNU Classpath inetlib is an extension library to provide extra network protocol support for GNU Classpath and ClasspathX project but it can also used standalone to add http imap pop3 and smtp client support applications.
+ GPL-2.0-with-GCC-exception
+
+
+ initramfs-framework
+ 1.0
+ Modular initramfs system.
+ MIT
+
+
+ initramfs-module-install-efi
+ 1.0
+ initramfs-framework module for EFI installation option.
+ MIT
+
+
+ initramfs-module-install
+ 1.0
+ initramfs-framework module for installation option.
+ MIT
+
+
+ initramfs-module-setup-live
+ 1.0
+ initramfs-framework module for live booting.
+ MIT
+
+
+ initramfs-ostree-image
+ 1.0
+ OSTree initramfs image
+ MIT
+
+
+ inputproto
+ 2.3.2
+ This package provides the wire protocol for the X Input extension. The extension supports input devices other then the core X keyboard and pointer.
+ MIT
+
+
+ intltool
+ 0.51.0
+ Utility scripts for internationalizing XML.
+ GPL-2.0
+
+
+ iperf3
+ 3.2
+ iperf is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing protocols and buffers. For each test it reports the bandwidth loss and other parameters.
+ BSD
+
+
+ iproute2
+ 4.11.0
+ Iproute2 is a collection of utilities for controlling TCP / IP networking and traffic control in Linux. Of the utilities ip and tc are the most important. ip controls IPv4 and IPv6 configuration and tc stands for traffic control.
+ GPL-2.0
+
+
+ iptables
+ 1.6.1
+ iptables is the userspace command line program used to configure and control network packet filtering code in Linux.
+ GPL-2.0
+
+
+ iw
+ 4.9
+ iw is a new nl80211 based CLI configuration utility for wireless devices. It supports almost all new drivers that have been added to the kernel recently.
+ BSD
+
+
+ ixgbe
+ 5.10.2
+ The ixgbe driver supports 82598- and 82599-based PCI Express* 10 Gigabit Network Connections.
+ GPL-2.0
+
+
+ ixgbevf
+ 4.10.2
+ This virtual function driver supports kernel versions 2.6.x and newer This driver supports 82599 X540 X550 and X552-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support. The guest OS loading this driver must support MSI-X interrupts.
+ GPL-2.0
+
+
+ jacl
+ 1.4.1
+ Tcl interpreter for Java
+ UCB, SUN, AMD, CDS
+
+
+ jamvm
+ 2.0.0-devel
+ A compact Java Virtual Machine which conforms to the JVM specification version 2.
+ GPL-2.0
+
+
+ jansson
+ 2.9
+ Jansson is a C library for encoding decoding and manipulating JSON data.
+ MIT
+
+
+ jaxp1.3
+ 1.4.01
+ Java XML parser and transformer APIs (DOM SAX JAXP TrAX)
+ Apache-2.0, W3C, PD
+
+
+ jdepend
+ 2.9.1
+ Design quality metrics generator for each Java
+ BSD
+
+
+ jikes-initial
+ 1.0
+ Initial Java 1.4-compatible (and not higher) compiler.
+ MIT
+
+
+ jikes
+ 1.22
+ Java compiler adhering to language and VM specifications
+ IPL-1.0
+
+
+ jlex
+ 1.2.6
+ Lexical analyzer generator for Java
+ JLEX
+
+
+ jq
+ 1.5
+ jq is like sed for JSON data you can use it to slice and filter and map and transform structured data with the same ease that sed awk grep and friends let you play with text.
+ MIT
+
+
+ jsch
+ 0.1.40
+ SSH implementation in Java
+ BSD
+
+
+ junit
+ 3.8.2
+ JUnit is a testing framework for Java
+ CPL-1.0
+
+
+ jzlib
+ 1.0.7
+ zlib implementation in Java
+ BSD
+
+
+ kbd
+ 2.0.4
+ Keytable files and keyboard utilities.
+ GPL-2.0
+
+
+ kbproto
+ 1.0.7
+ This package provides the wire protocol for the X Keyboard extension. This extension is used to control options related to keyboard handling and layout.
+ MIT
+
+
+ kern-tools
+ 0.2
+ Tools for managing Yocto Project style branched kernels.
+ GPL-2.0
+
+
+ keymaps
+ 1.0
+ Keymaps and initscript to set the keymap on bootup.
+ GPL-2.0
+
+
+ keyutils
+ 1.5.10
+ Utilities to control the kernel key management facility and to provide a mechanism by which the kernel call back to userspace to get a key instantiated.
+ LGPL-2.1, GPL-2.0
+
+
+ kmod
+ 24
+ kmod is a set of tools to handle common tasks with Linux kernel modules like insert remove list check properties resolve dependencies and aliases.
+ GPL-2.0, LGPL-2.1
+
+
+ krb5
+ 1.15.1
+ "Kerberos is a system for authenticating users and services on a network. Kerberos is a trusted third-party service. That means that there is a third party (the Kerberos server) that is trusted by all the entities on the network (users and services usually called ""principals""). . This is the MIT reference implementation of Kerberos V5. . This package contains the Kerberos key server (KDC). The KDC manages all authentication credentials for a Kerberos realm holds the master keys for the realm and responds to authentication requests. This package should be installed on both master and slave KDCs."
+ MIT
+
+
+ ldconfig
+ 2.12.1
+ A standalone native ldconfig build.
+ GPL-2.0
+
+
+ less
+ 487
+ Less is a program similar to more i.e. a terminal based program for viewing text files and the output from other programs. Less offers many features beyond those that more does.
+ GPL-3.0, BSD-2-Clause
+
+
+ libaio
+ 0.3.110
+ Asynchronous input/output library that uses the kernels native interface
+ LGPL-2.1
+
+
+ libarchive
+ 3.3.2
+ C library and command-line tools for reading and writing tar cpio zip ISO and other archive formats
+ BSD
+
+
+ libassuan
+ 2.4.3
+ IPC library used by GnuPG and GPGME.
+ GPL-3.0, LGPL-2.1
+
+
+ libbsd
+ 0.8.6
+ This library provides useful functions commonly found on BSD systems and lacking on others like GNU systems thus making it easier to port projects with strong BSD origins without needing to embed the same code over and over again on each project.
+ BSD-4-Clause, ISC, PD
+
+
+ libcap
+ 2.25
+ Library for getting/setting POSIX.1e capabilities.
+ BSD, GPL-2.0
+
+
+ libcgroup
+ 0.41
+ libcgroup is a library that abstracts the control group file system in Linux. Control groups allow you to limit account and isolate resource usage (CPU memory disk I/O etc.) of groups of processes.
+ LGPL-2.1
+
+
+ libcheck
+ 0.10.0
+ Check - unit testing framework for C code.
+ LGPL-2.1
+
+
+ libdaemon
+ 0.14
+ Lightweight C library which eases the writing of UNIX daemons.
+ LGPL-2.1
+
+
+ libdevmapper
+ 2.02.171
+ LVM2 is a set of utilities to manage logical volumes in Linux.
+ GPL-2.0, LGPL-2.0
+
+
+ libecj-bootstrap
+ 3.6.2
+ JDT Core Batch Compiler - Jar only
+ EPL-1.0
+
+
+ liberation-fonts
+ 2.00.1
+ The Liberation(tm) Fonts is a font family originally created by Ascender(c) which aims at metric compatibility with Arial Times New Roman Courier New.
+ OFL-1.1
+
+
+ libffi
+ 3.2.1
+ The `libffi' library provides a portable high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. FFI stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The `libffi' library really only provides the lowest machine dependent layer of a fully featured foreign function interface. A layer must exist above `libffi' that handles type conversions for values passed between the two languages.
+ MIT
+
+
+ libfile-slurp-perl
+ 9999.19
+ This module provides subroutines to read or write entire files with a simple call. It also has a subroutine for reading the list of filenames in a directory.
+ Artistic-1.0, GPL-1.0
+
+
+ libgcc-initial
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception
+
+
+ libgcc
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ libgcrypt
+ 1.8.0
+ General purpose cryptographic library based on the code from GnuPG.
+ GPL-2.0, LGPL-2.1, GPL-3.0
+
+
+ libgpg-error
+ 1.27
+ Small library that defines common error values for all GnuPG components.
+ GPL-2.0, LGPL-2.1
+
+
+ libgudev
+ 231
+ GObject wrapper for libudev.
+ LGPL-2.1
+
+
+ libice
+ 1.0.9
+ The Inter-Client Exchange (ICE) protocol provides a generic framework for building protocols on top of reliable byte-stream transport connections. It provides basic mechanisms for setting up and shutting down connections for performing authentication for negotiating versions and for reporting errors.
+ MIT
+
+
+ libidn
+ 1.33
+ Implementation of the Stringprep Punycode and IDNA specifications defined by the IETF Internationalized Domain Names (IDN) working group.
+ LGPL-2.1, LGPL-3.0, GPL-3.0
+
+
+ libjpeg-turbo
+ 1.5.2
+ libjpeg-turbo is a derivative of libjpeg that uses SIMD instructions (MMX SSE2 NEON) to accelerate baseline JPEG compression and decompression
+ BSD-3-Clause
+
+
+ libmbim
+ 1.16.0
+ libmbim is a glib-based library for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol
+ GPL-2.0, LGPL-2.1
+
+
+ libmnl
+ 1.0.4
+ Minimalistic user-space library oriented to Netlink developers providing functions for common tasks in parsing validating and constructing both the Netlink header and TLVs.
+ LGPL-2.1
+
+
+ libmpc
+ 1.0.3
+ Mpc is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result. It is built upon and follows the same principles as Mpfr
+ LGPL-3.0
+
+
+ libndp
+ 1.6
+ Library for IPv6 Neighbor Discovery Protocol.
+ LGPL-2.1
+
+
+ libnewt
+ 0.52.20
+ Newt is a programming library for color text mode widget based user interfaces. Newt can be used to add stacked windows entry widgets checkboxes radio buttons labels plain text fields scrollbars etc. to text mode user interfaces. This package also contains the shared library needed by programs built with newt as well as a /usr/bin/dialog replacement called whiptail. Newt is based on the slang library.
+ LGPL-2.0
+
+
+ libnl
+ 3.4.0
+ A library for applications dealing with netlink sockets.
+ LGPL-2.1
+
+
+ libnss-mdns
+ 0.10
+ Name Service Switch module for Multicast DNS (zeroconf) name resolution.
+ LGPL-2.1
+
+
+ libpcap
+ 1.8.1
+ Libpcap provides a portable framework for low-level network monitoring. Libpcap can provide network statistics collection security monitoring and network debugging.
+ BSD
+
+
+ libpciaccess
+ 0.13.5
+ libpciaccess provides functionality for X to access the PCI bus and devices in a platform-independent way.
+ MIT
+
+
+ libpcre
+ 8.41
+ The PCRE library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. PCRE has its own native API as well as a set of wrapper functions that correspond to the POSIX regular expression API.
+ BSD
+
+
+ libpng
+ 1.6.31
+ PNG image format decoding library.
+ Libpng
+
+
+ libpthread-stubs
+ 0.4
+ This library provides weak aliases for pthread functions not provided in libc or otherwise available by default.
+ MIT
+
+
+ libqmi
+ 1.20.2
+ libqmi is a glib-based library for talking to WWAN modems and devices which speak the Qualcomm MSM Interface (QMI) protocol
+ GPL-2.0, LGPL-2.1
+
+
+ libsdl
+ 1.2.15
+ Simple DirectMedia Layer is a cross-platform multimedia library designed to provide low level access to audio keyboard mouse joystick 3D hardware via OpenGL and 2D video framebuffer.
+ LGPL-2.1
+
+
+ libsign
+ 0.3.2
+ This project targets to provide a generic signing framework. This framework separates the signing request and signing process and correspondingly forms the so-called signlet and signaturelet. Each signaturelet only concerns about the details about how to construct the layout of a signature format and signlet only cares how to construct the signing request.
+ BSD-3-Clause
+
+
+ libsm
+ 1.2.2
+ "The Session Management Library (SMlib) is a low-level \""C\"" language interface to XSMP. The purpose of the X Session Management Protocol (XSMP) is to provide a uniform mechanism for users to save and restore their sessions. A session is a group of clients each of which has a particular state."
+ MIT
+
+
+ libtasn1
+ 4.12
+ Library for ASN.1 and DER manipulation.
+ GPL-3.0, LGPL-2.1
+
+
+ libtool
+ 2.4.6
+ This is GNU libtool a generic library support script. Libtool hides the complexity of generating special library types (such as shared libraries) behind a consistent interface.
+ GPL-2.0, LGPL-2.1
+
+
+ libunistring
+ 0.9.7
+ Text files are nowadays usually encoded in Unicode and may consist of very different scripts from Latin letters to Chinese Hanzi with many kinds of special characters accents right-to-left writing marks hyphens Roman numbers and much more. But the POSIX platform APIs for text do not contain adequate functions for dealing with particular properties of many Unicode characters. In fact the POSIX APIs for text have several assumptions at their base which don't hold for Unicode text. This library provides functions for manipulating Unicode strings and for manipulating C strings according to the Unicode standard. This package contains documentation.
+ LGPL-3.0, GPL-2.0
+
+
+ libusb1
+ 1.0.21
+ Userspace library to access USB (version 1.0).
+ LGPL-2.1
+
+
+ libvirt
+ 4.2.0
+ A toolkit to interact with the virtualization capabilities of recent versions of Linux.
+ LGPL-2.1, GPL-2.0
+
+
+ libx11
+ 1.6.5
+ This package provides a client interface to the X Window System otherwise known as 'Xlib'. It provides a complete API for the basic functions of the window system.
+ MIT, BSD
+
+
+ libxau
+ 1.0.8
+ libxau provides the main interfaces to the X11 authorisation handling which controls authorisation for X connections both client-side and server-side.
+ MIT
+
+
+ libxcb
+ 1.12
+ The X protocol C-language Binding (XCB) is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
+ MIT
+
+
+ libxdmcp
+ 1.1.2
+ The purpose of the X Display Manager Control Protocol (XDMCP) is to provide a uniform mechanism for an autonomous display to request login service from a remote host. An X terminal (screen keyboard mouse processor network interface) is a prime example of an autonomous display.
+ MIT
+
+
+ libxext
+ 1.3.3
+ libXext provides an X Window System client interface to several extensions to the X protocol. The supported protocol extensions are DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. libXext also provides a small set of utility functions to aid authors of client APIs for X protocol extensions.
+ MIT
+
+
+ libxft
+ 2.3.2
+ Xft was designed to provide good support for scalable fonts and to do so efficiently. Unlike the core fonts system it supports features such as anti-aliasing and sub-pixel rasterisation. Perhaps more importantly it gives applications full control over the way glyphs are rendered making fine typesetting and WYSIWIG display possible. Finally it allows applications to use fonts that are not installed system-wide for displaying documents with embedded fonts. Xft is not compatible with the core fonts system: usage of Xft requires fairly extensive changes to toolkits (user-interface libraries).
+ MIT
+
+
+ libxkbcommon
+ 0.7.1
+ libxkbcommon is a keymap compiler and support library which processes a reduced subset of keymaps as defined by the XKB specification.
+ MIT
+
+
+ libxml-parser-perl
+ 2.44
+ XML::Parser - A perl module for parsing XML documents.
+ Artistic-1.0, GPL-1.0
+
+
+ libxml2
+ 2.9.5
+ The XML Parser Library allows for manipulation of XML files. Libxml2 exports Push and Pull type parser interfaces for both XML and HTML. It can do DTD validation at parse time on a parsed document instance or with an arbitrary DTD. Libxml2 includes complete XPath XPointer and Xinclude implementations. It also has a SAX like interface which is designed to be compatible with Expat.
+ MIT
+
+
+ libxrandr
+ 1.5.1
+ The X Resize Rotate and Reflect Extension called RandR for short brings the ability to resize rotate and reflect the root window of a screen. It is based on the X Resize and Rotate Extension as specified in the Proceedings of the 2001 Usenix Technical Conference [RANDR].
+ MIT
+
+
+ libxrender
+ 0.9.10
+ The X Rendering Extension (Render) introduces digital image composition as the foundation of a new rendering model within the X Window System. Rendering geometric figures is accomplished by client-side tessellation into either triangles or trapezoids. Text is drawn by loading glyphs into the server and rendering sets of them.
+ MIT
+
+
+ libxslt
+ 1.1.29
+ GNOME XSLT library.
+ MIT
+
+
+ libyaml
+ 0.1.7
+ LibYAML is a C library for parsing and emitting data in YAML 1.1 a human-readable data serialization format.
+ MIT
+
+
+ lighttpd
+ 1.4.45
+ Lightweight high-performance web server.
+ BSD
+
+
+ linux-firmware
+ 0.0
+ Firmware files for use with Linux kernel.
+ Redistributable binaries
+
+
+ linux-intel-guest
+ 4.14.123
+ Linux kernel.
+ GPL-2.0
+
+
+ linux-intel-host
+ 4.14.123
+ Linux kernel.
+ GPL-2.0
+
+
+ linux-libc-headers
+ 4.12
+ Sanitized set of kernel headers for the C library's use.
+ GPL-2.0
+
+
+ lmsensors-config
+ 1.0
+ Hardware health monitoring configuration files
+ MIT
+
+
+ lmsensors
+ 3.6.0
+ Hardware health monitoring applications.
+ GPL-2.0, LGPL-2.1
+
+
+ log-collector
+ 1.0
+ Service that collects platform logs
+ Enea
+
+
+ log4j1.2
+ 1.2.17
+ Java library to help the programmer output log statements to a variety of output targets
+ Apache-2.0
+
+
+ logkit
+ 1.2.2
+ Logging toolkit designed for secure performance orientated logging in Java applications
+ Apache-2.0
+
+
+ logrotate
+ 3.12.3
+ Rotates compresses removes and mails system log files.
+ GPL-2.0
+
+
+ lsb
+ 4.1
+ LSB support for OpenEmbedded.
+ GPL-2.0
+
+
+ lsbinitscripts
+ 9.72
+ SysV init scripts which are only used in an LSB image.
+ GPL-2.0
+
+
+ lshw
+ 02.17
+ A small tool to provide detailed information on the hardware configuration of the machine. It can report exact memory configuration firmware version mainboard configuration CPU version and speed cache configuration bus speed etc. on DMI-capable or EFI systems.
+ GPL-2.0
+
+
+ lsof
+ 4.89
+ Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open Files and it does just that.
+ BSD
+
+
+ lvm2
+ 2.02.171
+ LVM2 is a set of utilities to manage logical volumes in Linux.
+ GPL-2.0, LGPL-2.0
+
+
+ lxc
+ 2.0.8
+ lxc aims to use these new functionnalities to provide an userspace container object
+ GPL-2.0
+
+
+ lxd
+ git
+ "LXD is a container ""hypervisor"" and a new user experience for LXC Specifically it's made of three components: - A system-wide daemon (lxd) - A command line client (lxc) - An OpenStack Nova plugin (nova-compute-lxd)"
+ Apache-2.0
+
+
+ lz4
+ 1.7.4
+ LZ4 is a very fast lossless compression algorithm providing compression speed at 400 MB/s per core scalable with multi-cores CPU. It also features an extremely fast decoder with speed in multiple GB/s per core typically reaching RAM speed limits on multi-core systems.
+ BSD, BSD-2-Clause, GPL-2.0
+
+
+ lzo
+ 2.10
+ Lossless data compression library.
+ GPL-2.0
+
+
+ lzop
+ 1.03
+ lzop is a compression utility which is designed to be a companion to gzip. \nIt is based on the LZO data compression library and its main advantages over \ngzip are much higher compression and decompression speed at the cost of some \ncompression ratio. The lzop compression utility was designed with the goals \nof reliability speed portability and with reasonable drop-in compatibility \nto gzip.
+ GPL-2.0
+
+
+ m4
+ 1.4.18
+ GNU m4 is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible although it has some extensions (for example handling more than 9 positional parameters to macros). GNU M4 also has built-in functions for including files running shell commands doing arithmetic etc.
+ GPL-3.0
+
+
+ make
+ 4.2.1
+ Make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. Make gets its knowledge of how to build your program from a file called the makefile which lists each of the non-source files and how to compute it from other files.
+ GPL-3.0, LGPL-2.0
+
+
+ makedepend
+ 1.0.5
+ The makedepend program reads each sourcefile in sequence and parses it like a C-preprocessor processing all #include #define #undef #ifdef #ifndef #endif #if #elif and #else directives so that it can correctly tell which #include directives would be used in a compilation. Any #include directives can reference files having other #include directives and parsing will occur in these files as well.
+ MIT
+
+
+ makedevs
+ 1.0.1
+ Tool for creating device nodes.
+ GPL-2.0
+
+
+ mklibs
+ 0.1.43
+ mklibs produces cut-down shared libraries that contain only the routines required by a particular set of executables.
+ GPL-2.0
+
+
+ modemmanager
+ 1.7.991
+ ModemManager is a DBus-activated daemon which controls mobile broadband (2G/3G/4G) devices and connections
+ GPL-2.0, LGPL-2.1
+
+
+ mokutil
+ 0.3.0
+ The utility to manipulate machines owner keys which managed in shim.
+ GPL-3.0
+
+
+ mozjs
+ 17.0.0
+ SpiderMonkey is Mozilla's JavaScript engine written in C/C++.
+ MPL-2.0
+
+
+ mpfr
+ 3.1.5
+ C library for multiple-precision floating-point computations with exact rounding.
+ GPL-3.0, LGPL-3.0
+
+
+ mtools
+ 4.0.18
+ Mtools is a collection of utilities to access MS-DOS disks from GNU and Unix without mounting them.
+ GPL-3.0
+
+
+ nasm
+ 2.13.01
+ General-purpose x86 assembler.
+ BSD-2-Clause
+
+
+ ncurses
+ 6.0
+ SVr4 and XSI-Curses compatible curses library and terminfo tools including tic infocmp captoinfo. Supports color multiple highlights forms-drawing characters and automatic recognition of keypad and function-key sequences. Extensions include resizable windows and mouse support on both xterm and Linux console using the gpm library.
+ MIT
+
+
+ net-snmp
+ 5.7.3
+ Various tools relating to the Simple Network Management Protocol.
+ BSD
+
+
+ net-tools
+ 1.60-26
+ A collection of programs that form the base set of the NET-3 networking distribution for the Linux operating system
+ GPL-2.0
+
+
+ netbase
+ 5.4
+ This package provides the necessary infrastructure for basic TCP/IP based networking
+ GPL-2.0
+
+
+ netcat-openbsd
+ 1.105
+ A simple Unix utility which reads and writes data across network connections using TCP or UDP protocol. It is designed to be a reliable 'back-end' tool that can be used directly or easily driven by other programs and scripts. At the same time it is a feature-rich network debugging and exploration tool since it can create almost any kind of connection you would need and has several interesting built-in capabilities.
+ BSD-3-Clause
+
+
+ netcf
+ 0.2.8
+ netcf is a cross-platform network configuration library.
+ LGPL-2.1
+
+
+ nettle
+ 3.3
+ A low level cryptographic library.
+ LGPL-3.0, GPL-2.0
+
+
+ networkmanager
+ 1.10.10
+ NetworkManager.
+ GPL-2.0
+
+
+ nfv-init
+ 1.0
+ Enea service expected to be run after cloud-init
+ Enea
+
+
+ nfv-installer
+ 1.0
+ Enea NFV Access installer
+ Enea
+
+
+ nfva-cfgtool
+ 1.0
+ Command line tool to for accessing the Enea NFV Access install configuration json file
+ Enea
+
+
+ nfva-hotfixes
+ 1.0
+ Different hotfixes
+ Enea
+
+
+ nfva-startup
+ 1.0
+ Service that configures the network according to installer settings
+ Enea
+
+
+ nodejs
+ 8.4.0
+ nodeJS Evented I/O for V8 JavaScript
+ MIT, BSD, Artistic-2.0
+
+
+ notary
+ 0.4.2
+ Notary is a Docker project that allows anyone to have trust over arbitrary collections of data
+ Apache-2.0
+
+
+ nspr
+ 4.16
+ Netscape Portable Runtime Library.
+ GPL-2.0, MPL-2.0, LGPL-2.1
+
+
+ nss
+ 3.31.1
+ Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3 TLS PKCS 5 PKCS 7 PKCS 11 PKCS 12 S/MIME X.509 v3 certificates and other security standards.
+ MPL-2.0, GPL-2.0, MPL-2.0, LGPL-2.1
+
+
+ ntp-user-stub
+ 1.0
+ The NTP user/group were added in previous NFVA releases and are needed for OSTree upgrades to ensure backwards compatibility.
+ Enea
+
+
+ numactl
+ 2.0.11
+ Simple NUMA policy support. It consists of a numactl program to run other programs with a specific NUMA policy and a libnuma to do allocations with NUMA policy in applications.
+ GPL-2.0, LGPL-2.1
+
+
+ onig
+ 5.9.6
+ Regular expressions library. The characteristics of this library is that different character encoding for every regular expression object can be specified.
+ BSD
+
+
+ openipmi
+ 2.0.24
+ OpenIPMI is an effort to create a full-function IPMI system to allow full access to all IPMI information on a server and to abstract it to a level that will make it easy to use
+ GPL-2.0, LGPL-2.1, BSD
+
+
+ openjdk-8
+ 102b14
+ Java runtime based upon the OpenJDK Project
+ GPL-2.0-with-classpath-exception
+
+
+ openssh
+ 7.5p1
+ Secure rlogin/rsh/rcp/telnet replacement (OpenSSH) Ssh (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine.
+ BSD
+
+
+ openssl
+ 1.0.2o
+ Secure Socket Layer (SSL) binary and related cryptographic tools.
+ OpenSSL
+
+
+ openvswitch
+ 2.9
+ Open vSwitch is a production quality multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension while still supporting standard management interfaces and protocols (e.g. NetFlow sFlow SPAN RSPAN CLI LACP 802.1ag)
+ Apache-2.0
+
+
+ opkg-utils
+ 0.3.5
+ Additional utilities for the opkg package manager.
+ GPL-2.0
+
+
+ oro
+ 2.0.8
+ Perl5-compatible regular expressions library for Java
+ Apache-2.0
+
+
+ os-release
+ 1.0
+ The /etc/os-release file contains operating system identification data.
+ MIT
+
+
+ ostree-initrd
+ 3
+ Extremely basic live image init script.
+ MIT
+
+
+ ostree-rw
+ 1.0
+ Enea bash script to make current ostree hash writable
+ Enea
+
+
+ ostree
+ v2018.7
+ Tool for managing bootable immutable versioned filesystem trees.
+ LGPL-2.0
+
+
+ packagegroup-core-boot
+ 1.0
+ The minimal set of packages required to boot the system
+ MIT
+
+
+ packagegroup-core-ssh-openssh
+ 1.0
+ OpenSSH SSH client/server.
+ MIT
+
+
+ packagegroup-efi-secure-boot
+ 1.0
+ EFI Secure Boot packages for secure-environment.
+ MIT
+
+
+ packagegroup-enea-telemetry
+ 1.0
+ Packages for Telemetry.
+ MIT
+
+
+ packagegroup-enea-virtualization-4gusb-modems
+ 1.0
+ Packagegroup for 4G usb modems.
+ MIT
+
+
+ packagegroup-enea-virtualization-docker
+ 1.0
+ Packagegroup for Docker.
+ MIT
+
+
+ packagegroup-enea-virtualization-dpdk
+ 1.0
+ Packagegroup for DPDK.
+ MIT
+
+
+ packagegroup-enea-virtualization-guest
+ 1.0
+ This package group includes packages and packagegroups specific to the guest side of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-virtualization-host
+ 1.0
+ This package group includes packages and packagegroups specific to the host side of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-virtualization-libvirt
+ 1.0
+ Package group for libvirt.
+ MIT
+
+
+ packagegroup-enea-virtualization-lxc
+ 1.0
+ Packagegroup for LXC.
+ MIT
+
+
+ packagegroup-enea-virtualization-lxd
+ 1.0
+ Packagegroup for LXD.
+ MIT
+
+
+ packagegroup-enea-virtualization-ovs
+ 1.0
+ Packagegroup for Open vSwitch.
+ MIT
+
+
+ packagegroup-enea-virtualization-qemu
+ 1.0
+ Packagegroup for QEMU.
+ MIT
+
+
+ packagegroup-enea-virtualization
+ 1.0
+ This packagegroup includes packages and packagegroups required for both host and guest images of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-wifi
+ 1.0
+ This package group includes packages and packagegroups that enable WiFi connectivity in the Enea NFV Access platform
+ MIT
+
+
+ pango
+ 1.40.6
+ Pango is a library for laying out and rendering of text with an emphasis on internationalization. Pango can be used anywhere that text layout is needed though most of the work on Pango so far has been done in the context of the GTK+ widget toolkit. Pango forms the core of text and font handling for GTK+-2.x.
+ LGPL-2.0
+
+
+ parted
+ 3.2
+ Disk partition editing/resizing utility.
+ GPL-3.0
+
+
+ partrt
+ 1.1
+ partrt is a tool for dividing a SMP Linux system into a real time domain and a non-real time domain.
+ BSD
+
+
+ pciutils
+ 3.5.5
+ The PCI Utilities package contains a library for portable access to PCI bus configuration space and several utilities based on this library.
+ GPL-2.0
+
+
+ perl
+ 5.24.1
+ Perl scripting language.
+ Artistic-1.0, GPL-1.0
+
+
+ pigz
+ 2.3.4
+ pigz which stands for parallel implementation of gzip is a fully functional replacement for gzip that exploits multiple processors and multiple cores to the hilt when compressing data. pigz was written by Mark Adler and uses the zlib and pthread libraries.
+ Zlib, Apache-2.0
+
+
+ pixman
+ 0.34.0
+ Pixman provides a library for manipulating pixel regions -- a set of Y-X banded rectangles image compositing using the Porter/Duff model and implicit mask generation for geometric primitives including trapezoids triangles and rectangles.
+ MIT, PD
+
+
+ pkgconfig
+ 0.29.2
+ pkg-config is a helper tool used when compiling applications and libraries. It helps determined the correct compiler/link options. It is also language-agnostic.
+ GPL-2.0
+
+
+ pm-utils
+ 1.4.1
+ Simple shell command line tools to suspend and hibernate.
+ GPL-2.0
+
+
+ polkit
+ 0.113
+ The polkit package is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes.
+ LGPL-2.0
+
+
+ popt
+ 1.16
+ Library for parsing command line options.
+ MIT
+
+
+ prelink
+ 1.0
+ The prelink package contains a utility which modifies ELF shared libraries and executables so that far fewer relocations need to be resolved at runtime and thus programs come up faster.
+ GPL-2.0
+
+
+ procps
+ 3.3.12
+ Procps contains a set of system utilities that provide system information about processes using the /proc filesystem. The package includes the programs ps top vmstat w kill and skill.
+ GPL-2.0, LGPL-2.0
+
+
+ pseudo
+ 1.8.2
+ Pseudo gives fake root capabilities to a normal user.
+ LGPL-2.1
+
+
+ ptest-runner
+ 2.1
+ The ptest-runner2 package installs a ptest-runner program which loops through all installed ptest test suites and runs them in sequence.
+ GPL-2.0
+
+
+ python-asn1crypto
+ 0.23.0
+ Python binding to the Networking and Cryptography (NaCl) library
+ Apache-2.0
+
+
+ python-certifi
+ 2017.7.27.1
+ This installable Python package contains a CA Bundle that you can reference in your Python code. This is useful for verifying HTTP requests for example. This is the same CA Bundle which ships with the Requests codebase and is derived from Mozilla Firefox's canonical set.
+ ISC
+
+
+ python-cffi
+ 1.11.2
+ Foreign Function Interface for Python calling C code.
+ MIT
+
+
+ python-chardet
+ 3.0.4
+ Universal encoding detector for Python 2 and 3.
+ LGPL-2.1
+
+
+ python-cryptography-vectors
+ 2.0.3
+ Test vectors for the cryptography package..
+ Apache-2.0, BSD
+
+
+ python-cryptography
+ 2.0.3
+ Provides cryptographic recipes and primitives to python developers.
+ Apache-2.0, BSD
+
+
+ python-cython
+ 0.27.1
+ Cython is a language specially designed for writing Python extension modules. It's designed to bridge the gap between the nice high-level easy-to-use world of Python and the messy low-level world of C.
+ Apache-2.0
+
+
+ python-enum34
+ 1.1.6
+ backport of Python 3.4's enum package.
+ BSD-3-Clause
+
+
+ python-functools32
+ 3.2.3-2
+ Backport of the functools module from Python 3.2.3 for use on 2.7 and PyPy..
+ Python-2.0
+
+
+ python-futures
+ 3.0.5
+ The concurrent.futures module provides a high-level interface for asynchronously executing callables.
+ BSD
+
+
+ python-idna
+ 2.6
+ Internationalised Domain Names in Applications.
+ BSD-3-Clause, Python-2.0, Unicode
+
+
+ python-ipaddress
+ 1.0.18
+ Python 3.3+'s ipaddress for Python 2.6 2.7 3.2..
+ Python-2.0
+
+
+ python-iso8601
+ 0.1.12
+ Simple module to parse ISO 8601 dates.
+ MIT
+
+
+ python-jsonpatch
+ 1.16
+ Appling JSON patches in Python 2.6+ and 3.x.
+ BSD
+
+
+ python-jsonpointer
+ 1.12
+ Resolve JSON Pointers in Python.
+ BSD
+
+
+ python-jsonschema
+ 2.6.0
+ An implementation of JSON Schema validation for Python.
+ MIT
+
+
+ python-m2crypto
+ 0.26.4
+ A Python crypto and SSL toolkit.
+ BSD
+
+
+ python-ndg-httpsclient
+ 0.4.3
+ Provides enhanced HTTPS support for httplib and urllib2 using PyOpenSSL
+ BSD
+
+
+ python-netaddr
+ 0.7.19
+ A network address manipulation library for Python..
+ BSD
+
+
+ python-netifaces
+ 0.10.6
+ Portable network interface information.
+ MIT
+
+
+ python-pip
+ 9.0.1
+ PIP is a tool for installing and managing Python packages.
+ MIT, LGPL-2.1
+
+
+ python-pretend
+ 1.0.8
+ A library for stubbing in Python.
+ BSD
+
+
+ python-prettytable
+ 0.7.2
+ Python library for displaying tabular data in a ASCII table format.
+ BSD
+
+
+ python-psutil
+ 5.3.1
+ A cross-platform process and system utilities module for Python.
+ BSD
+
+
+ python-py
+ 1.4.34
+ Library with cross-python path ini-parsing io code log facilities.
+ MIT
+
+
+ python-pyasn1
+ 0.3.6
+ Python library implementing ASN.1 types..
+ BSD-2-Clause
+
+
+ python-pycparser
+ 2.18
+ Parser of the C language written in pure Python.
+ BSD-3-Clause
+
+
+ python-pyopenssl
+ 17.3.0
+ Simple Python wrapper around the OpenSSL library.
+ Apache-2.0
+
+
+ python-pysocks
+ 1.6.7
+ A Python SOCKS client module
+ BSD
+
+
+ python-pytest-runner
+ 2.12.1
+ Invoke py.test as distutils command with dependency resolution.
+ MIT
+
+
+ python-pytest
+ 3.2.2
+ Simple powerful teting with python.
+ MIT
+
+
+ python-pyyaml
+ 3.11
+ YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. . PyYAML features a complete YAML 1.1 parser Unicode support pickle support capable extension API and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. . PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistance.
+ MIT
+
+
+ python-requests
+ 2.18.4
+ Python HTTP for Humans.
+ Apache-2.0
+
+
+ python-rfc3987
+ 1.3.7
+ Parsing and validation of URIs (RFC 3986) and IRIs (RFC 3987).
+ GPL-3.0
+
+
+ python-setuptools-scm
+ 1.15.6
+ the blessed package to manage your versions by scm tags.
+ MIT
+
+
+ python-setuptools
+ 36.2.7
+ Download build install upgrade and uninstall Python packages.
+ MIT
+
+
+ python-six
+ 1.11.0
+ Python 2 and 3 compatibility library.
+ MIT
+
+
+ python-strict-rfc3339
+ 0.7
+ Strict simple lightweight RFC3339 function.s.
+ GPL-3.0
+
+
+ python-typing
+ 3.6.2
+ Simple Python module defined by PEP 484..
+ Python-2.0
+
+
+ python-urllib3
+ 1.22
+ Python HTTP library with thread-safe connection pooling file post support sanity friendly and more.
+ MIT
+
+
+ python-vcversioner
+ 2.16.0.0
+ Python vcversioner automagically update the project's version.
+ ISC
+
+
+ python
+ 2.7.13
+ The Python Programming Language.
+ Python-2.0
+
+
+ python3-netifaces
+ 0.10.6
+ Portable network interface information.
+ MIT
+
+
+ python3-pip
+ 9.0.1
+ The PyPA recommended tool for installing Python packages.
+ MIT
+
+
+ python3-setuptools
+ 36.2.7
+ Download build install upgrade and uninstall Python packages.
+ MIT
+
+
+ python3-six
+ 1.10.0
+ Python 2 and 3 compatibility library.
+ MIT
+
+
+ python3-twisted
+ 13.2.0
+ Twisted is an event-driven networking framework written in Python and licensed under the LGPL. Twisted supports TCP UDP SSL/TLS multicast Unix sockets a large number of protocols (including HTTP NNTP IMAP SSH IRC FTP and others) and much more.
+ MIT
+
+
+ python3-zopeinterface
+ 4.4.3
+ Interface definitions for Zope products.
+ ZPL-2.1
+
+
+ python3
+ 3.5.3
+ The Python Programming Language.
+ Python-2.0
+
+
+ qemu-helper
+ 1.0
+ Helper utilities needed by the runqemu script.
+ GPL-2.0
+
+
+ qemu
+ 2.11.1
+ Fast open source processor emulator.
+ GPL-2.0, LGPL-2.1
+
+
+ qemuwrapper
+ 1.0
+ QEMU wrapper script.
+ MIT
+
+
+ quilt
+ 0.65
+ Tool for working with series of patches.
+ GPL-2.0
+
+
+ randrproto
+ 1.5.0
+ This package provides the wire protocol for the X Resize Rotate and Reflect extension. This extension provides the ability to resize rotate and reflect the root window of a screen.
+ MIT
+
+
+ readline
+ 7.0
+ The GNU Readline library provides a set of functions for use by applications that allow users to edit command lines as they are typed in. Both Emacs and vi editing modes are available. The Readline library includes additional functions to maintain a list of previously-entered command lines to recall and perhaps reedit those lines and perform csh-like history expansion on previous commands.
+ GPL-3.0
+
+
+ regexp
+ 1.5
+ Java Regular Expression package
+ Apache-2.0
+
+
+ renderproto
+ 0.11.1
+ This package provides the wire protocol for the X Rendering extension. This is the basis the image composition within the X window system.
+ MIT
+
+
+ rhino
+ 1.7r4
+ Lexical analyzer generator for Java
+ MPL-2.0
+
+
+ rpm
+ 4.13.90
+ The RPM Package Manager (RPM) is a powerful command line driven package management system capable of installing uninstalling verifying querying and updating software packages. Each software package consists of an archive of files along with information about the package like its version a description etc.
+ GPL-2.0
+
+
+ rrdtool
+ 1.6.0
+ High performance data logging and graphing system for time series data.
+ GPL-2.0
+
+
+ rsync
+ 3.1.3
+ File synchronization tool.
+ GPL-3.0
+
+
+ run-postinsts
+ 1.0
+ Runs postinstall scripts on first boot of the target device.
+ MIT
+
+
+ runc-docker
+ 1.0.0-rc3
+ runc is a CLI tool for spawning and running containers according to the OCI specification.
+ Apache-2.0
+
+
+ sbsigntool
+ 0.6
+ Utilities for signing UEFI binaries for use with secure boot.
+ GPL-3.0
+
+
+ sed
+ 4.2.2
+ Stream EDitor (text filtering utility).
+ GPL-3.0
+
+
+ seloader
+ 0.4.6
+ The SELoader is designed to authenticate the non-PE files such as grub configuration initrd grub modules which cannot be verified by the MOK Verify Protocol registered by shim loader. In order to conveniently authenticate the PE file with gBS->LoadImage() and gBS->StartImage() the SELoader hooks EFI Security2 Architectural Protocol and employs MOK Verify Protocol to verify the PE file. If only UEFI Secure Boot is enabled the SELoader just simplily calls gBS->LoadImage() and gBS->StartImage() to allow BIOS to verify PE file. The SELoader publishes MOK2 Verify Protocol which provides a flexible interface to allow the bootloader to verify the file file buffer or memory buffer without knowing the file format.
+ BSD-3-Clause
+
+
+ servlet2.3
+ 4.1.37
+ Servlet API 2.3 (from Tomcat 4.1)
+ Apache-2.0
+
+
+ shadow-securetty
+ 4.2.1
+ Provider of the machine specific securetty file.
+ MIT
+
+
+ shadow-sysroot
+ 4.2.1
+ Shadow utils requirements for useradd.bbclass.
+ BSD, Artistic-1.0
+
+
+ shadow
+ 4.2.1
+ Tools to change and administer password and group data.
+ BSD, Artistic-1.0
+
+
+ shared-mime-info
+ 1.8
+ Shared MIME type database and specification.
+ LGPL-2.0
+
+
+ shim
+ 12
+ shim is a trivial EFI application that when run attempts to open and execute another application. It will initially attempt to do this via the standard EFI LoadImage() and StartImage() calls. If these fail (because secure boot is enabled and the binary is not signed with an appropriate key for instance) it will then validate the binary against a built-in certificate. If this succeeds and if the binary or signing key are not blacklisted then shim will relocate and execute the binary.
+ BSD-2-Clause
+
+
+ simpleproxy
+ 1.0
+ Simpleproxy.
+ GPL-2.0
+
+
+ slang
+ 2.3.1a
+ S-Lang is an interpreted language and a programming library. The S-Lang language was designed so that it can be easily embedded into a program to provide the program with a powerful extension language. The S-Lang library provided in this package provides the S-Lang extension language. S-Lang's syntax resembles C which makes it easy to recode S-Lang procedures in C if you need to.
+ GPL-2.0
+
+
+ sqlite3
+ 3.20.0
+ Embeddable SQL database engine.
+ PD
+
+
+ squashfs-tools
+ 4.3
+ Tools for manipulating SquashFS filesystems.
+ GPL-2.0, PD
+
+
+ sshpass
+ 1.06
+ Tool for non-interactivly performing ssh password authentication
+ GPL-2.0
+
+
+ swig
+ 3.0.12
+ SWIG - Simplified Wrapper and Interface Generator.
+ BSD, GPL-3.0
+
+
+ sysfsutils
+ 2.1.0
+ Tools for working with the sysfs virtual filesystem. The tool 'systool' can query devices by bus class and topology.
+ GPL-2.0, LGPL-2.1
+
+
+ sysklogd
+ 1.5.1
+ The sysklogd package implements two system log daemons: syslogd klogd
+ GPL-2.0, BSD
+
+
+ syslinux
+ 6.03
+ Multi-purpose linux bootloader.
+ GPL-2.0
+
+
+ systemd-boot
+ 234
+ systemd is a system and service 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.
+ GPL-2.0, LGPL-2.1
+
+
+ systemd-compat-units
+ 1.0
+ Enhances systemd compatilibity with existing SysVinit scripts.
+ MIT
+
+
+ systemd-serialgetty
+ 1.0
+ Serial terminal support for systemd.
+ GPL-2.0
+
+
+ systemd-systemctl
+ 1.0
+ Wrapper for enabling systemd services.
+ MIT
+
+
+ systemd
+ 234
+ systemd is a system and service 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.
+ GPL-2.0, LGPL-2.1
+
+
+ tar
+ 1.29
+ GNU tar saves many files together into a single tape or disk archive and can restore individual files from the archive.
+ GPL-3.0
+
+
+ tcl
+ 8.6.7
+ Tool Command Language.
+ tcl, BSD-3-Clause
+
+
+ tcpdump
+ 4.9.2
+ A sophisticated network protocol analyzer.
+ BSD
+
+
+ texinfo-dummy
+ 1.0
+ Fake version of the texinfo utility suite.
+ MIT
+
+
+ thin-provisioning-tools
+ 0.6.3
+ A suite of tools for manipulating the metadata of the dm-thin device-mapper target.
+ GPL-3.0
+
+
+ tunctl
+ 1.5
+ Tool for controlling the Linux TUN/TAP driver.
+ GPL-2.0
+
+
+ tzcode
+ 2018c
+ tzcode timezone zoneinfo utils -- zic zdump tzselect.
+ PD, BSD, BSD-3-Clause
+
+
+ tzdata
+ 2018c
+ Timezone data.
+ PD, BSD, BSD-3-Clause
+
+
+ udev-extraconf
+ 1.1
+ Extra machine specific configuration files for udev specifically blacklist information.
+ MIT
+
+
+ unifdef
+ 2.11
+ Selectively remove #ifdef statements from sources.
+ BSD-2-Clause
+
+
+ unzip
+ 6.0
+ Utilities for extracting and viewing files in .zip archives.
+ BSD-3-Clause
+
+
+ update-rc.d
+ 0.7
+ update-rc.d is a utility that allows the management of symlinks to the initscripts in the /etc/rcN.d directory structure.
+ GPL-2.0
+
+
+ usb-modeswitch-data
+ 20170205
+ Data files for usbmodeswitch.
+ GPL-2.0
+
+
+ usb-modeswitch
+ 2.5.0
+ A mode switching tool for controlling 'flip flop' (multiple device) USB gear.
+ GPL-2.0
+
+
+ usbutils
+ 013
+ Contains the lsusb utility for inspecting the devices connected to the USB bus.
+ GPL-2.0, GPL-3.0
+
+
+ util-linux
+ 2.30
+ Util-linux includes a suite of basic system administration utilities commonly found on most Linux systems. Some of the more important utilities include disk partitioning kernel message management filesystem creation and system login.
+ GPL-2.0, LGPL-2.1, BSD
+
+
+ util-macros
+ 1.19.1
+ M4 autotools macros used by various X.org programs.
+ MIT
+
+
+ v86d
+ 0.1.10
+ User support binary for the uvesafb kernel module.
+ GPL-2.0
+
+
+ vala
+ 0.36.4
+ Vala is a C#-like language dedicated to ease GObject programming. Vala compiles to plain C and has no runtime environment nor penalities whatsoever.
+ LGPL-2.1
+
+
+ volatile-binds
+ 1.0
+ Volatile bind mount setup and configuration for read-only-rootfs
+ MIT
+
+
+ web-installer-backend
+ 0.1
+ Web installer go server
+ Enea, BSD-3-Clause
+
+
+ web-installer-frontend
+ 0.1
+ Web installer post-install application
+ Enea, Apache-2.0, BSD, BSD-2-Clause, BSD-3-Clause, CC-BY-4.0, ISC, MIT, Zlib
+
+
+ which
+ 2.21
+ Which is a utility that prints out the full path of the executables that bash(1) would execute when the passed program names would have been entered on the shell prompt. It does this by using the exact same algorithm as bash.
+ GPL-3.0
+
+
+ wireless-regdb
+ 2020.11.20
+ Wireless Central Regulatory Domain Database.
+ ISC
+
+
+ wpa-supplicant
+ 2.6
+ Client for Wi-Fi Protected Access (WPA).
+ BSD
+
+
+ xalan-j
+ 2.7.1
+ Java XSLT processor
+ Apache-2.0
+
+
+ xcb-proto
+ 1.12
+ Function prototypes for the X protocol C-language Binding (XCB). XCB is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
+ MIT
+
+
+ xerces-j
+ 2.11.0
+ Reference implementation of XNI the Xerces Native Interface and also a fully conforming XML Schema processor.
+ Apache-2.0
+
+
+ xextproto
+ 7.3.0
+ This package provides the wire protocol for several X extensions. These protocol extensions include DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. In addition a small set of utility functions are also available.
+ MIT
+
+
+ xkeyboard-config
+ 2.21
+ The non-arch keyboard configuration database for X Window. The goal is to provide the consistent well-structured frequently released open source of X keyboard configuration data for X Window System implementations. The project is targeted to XKB-based systems.
+ MIT
+
+
+ xml-commons-resolver1.1
+ 1.2
+ Library to resolve various public or system identifiers into accessible URLs (Java)
+ Apache-2.0
+
+
+ xproto
+ 7.0.31
+ This package provides the basic headers for the X Window System.
+ MIT
+
+
+ xtrans
+ 1.3.5
+ The X Transport Interface is intended to combine all system and transport specific code into a single place. This API should be used by all libraries clients and servers of the X Window System. Use of this API should allow the addition of new types of transports and support for new platforms without making any changes to the source except in the X Transport Interface code.
+ MIT
+
+
+ xz
+ 5.2.3
+ Utilities for managing LZMA compressed files.
+ GPL-2.0, GPL-3.0-with-autoconf-exception, LGPL-2.1, PD
+
+
+ yajl
+ 2.1.0
+ YAJL is a small event-driven (SAX-style) JSON parser written in ANSI C and a small validating JSON generator.
+ ISC
+
+
+ zip
+ 3.0
+ Compressor/archiver for creating and modifying .zip files.
+ BSD-3-Clause
+
+
+ zisofs-tools
+ 1.0.8
+ Utilities for creating compressed CD-ROM filesystems.
+ GPL-2.0
+
+
+ zlib
+ 1.2.11
+ Zlib is a general-purpose patent-free lossless data compression library which is used by many different programs.
+ Zlib
+
+
+
+
+
+
+ Open Source Licenses
+
+AFL-2.0
+
+
+The Academic Free License
+ v. 2.0
+
+This Academic Free License (the "License") applies to any original work of authorship
+(the "Original Work") whose owner (the "Licensor") has placed the following notice
+immediately following the copyright notice for the Original Work:
+Licensed under the Academic Free License version 2.0
+
+1) Grant of Copyright License. Licensor hereby grants You a world-wide, royalty-free,
+non-exclusive, perpetual, sublicenseable license to do the following:
+a) to reproduce the Original Work in copies;
+
+b) to prepare derivative works ("Derivative Works") based upon the Original Work;
+
+c) to distribute copies of the Original Work and Derivative Works to the public;
+
+d) to perform the Original Work publicly; and
+
+e) to display the Original Work publicly.
+
+2) Grant of Patent License. Licensor hereby grants You a world-wide, royalty-free,
+non-exclusive, perpetual, sublicenseable license, under patent claims owned or
+controlled by the Licensor that are embodied in the Original Work as furnished by the
+Licensor, to make, use, sell and offer for sale the Original Work and Derivative
+Works.
+
+3) Grant of Source Code License. The term "Source Code" means the preferred form of
+the Original Work for making modifications to it and all available documentation
+describing how to modify the Original Work. Licensor hereby agrees to provide a
+machine-readable copy of the Source Code of the Original Work along with each copy of
+the Original Work that Licensor distributes. Licensor reserves the right to satisfy
+this obligation by placing a machine-readable copy of the Source Code in an
+information repository reasonably calculated to permit inexpensive and convenient
+access by You for as long as Licensor continues to distribute the Original Work, and
+by publishing the address of that information repository in a notice immediately
+following the copyright notice that applies to the Original Work.
+
+4) Exclusions From License Grant. Neither the names of Licensor, nor the names of any
+contributors to the Original Work, nor any of their trademarks or service marks, may
+be used to endorse or promote products derived from this Original Work without express
+prior written permission of the Licensor. Nothing in this License shall be deemed to
+grant any rights to trademarks, copyrights, patents, trade secrets or any other
+intellectual property of Licensor except as expressly stated herein. No patent
+license is granted to make, use, sell or offer to sell embodiments of any patent
+claims other than the licensed claims defined in Section 2. No right is granted to
+the trademarks of Licensor even if such marks are included in the Original Work.
+Nothing in this License shall be interpreted to prohibit Licensor from licensing under
+different terms from this License any Original Work that Licensor otherwise would have
+a right to license.
+
+5) This section intentionally omitted.
+
+6) Attribution Rights. You must retain, in the Source Code of any Derivative Works
+that You create, all copyright, patent or trademark notices from the Source Code of
+the Original Work, as well as any notices of licensing and any descriptive text
+identified therein as an "Attribution Notice." You must cause the Source Code for any
+Derivative Works that You create to carry a prominent Attribution Notice reasonably
+calculated to inform recipients that You have modified the Original Work.
+
+7) Warranty of Provenance and Disclaimer of Warranty. Licensor warrants that the
+copyright in and to the Original Work and the patent rights granted herein by Licensor
+are owned by the Licensor or are sublicensed to You under the terms of this License
+with the permission of the contributor(s) of those copyrights and patent rights.
+Except as expressly stated in the immediately proceeding sentence, the Original Work
+is provided under this License on an "AS IS" BASIS and WITHOUT WARRANTY, either
+express or implied, including, without limitation, the warranties of NON-INFRINGEMENT,
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+QUALITY OF THE ORIGINAL WORK IS WITH YOU. This DISCLAIMER OF WARRANTY constitutes an
+essential part of this License. No license to Original Work is granted hereunder
+except under this disclaimer.
+
+8) Limitation of Liability. Under no circumstances and under no legal theory, whether
+in tort (including negligence), contract, or otherwise, shall the Licensor be liable
+to any person for any direct, indirect, special, incidental, or consequential damages
+of any character arising as a result of this License or the use of the Original Work
+including, without limitation, damages for loss of goodwill, work stoppage, computer
+failure or malfunction, or any and all other commercial damages or losses. This
+limitation of liability shall not apply to liability for death or personal injury
+resulting from Licensor`s negligence to the extent applicable law prohibits such
+limitation. Some jurisdictions do not allow the exclusion or limitation of incidental
+or consequential damages, so this exclusion and limitation may not apply to You.
+
+9) Acceptance and Termination. If You distribute copies of the Original Work or a
+Derivative Work, You must make a reasonable effort under the circumstances to obtain
+the express assent of recipients to the terms of this License. Nothing else but this
+License (or another written agreement between Licensor and You) grants You permission
+to create Derivative Works based upon the Original Work or to exercise any of the
+rights granted in Section 1 herein, and any attempt to do so except under the terms of
+this License (or another written agreement between Licensor and You) is expressly
+prohibited by U.S. copyright law, the equivalent laws of other countries, and by
+international treaty. Therefore, by exercising any of the rights granted to You in
+Section 1 herein, You indicate Your acceptance of this License and all of its terms
+and conditions.
+
+10) Termination for Patent Action. This License shall terminate automatically and You
+may no longer exercise any of the rights granted to You by this License as of the date
+You commence an action, including a cross-claim or counterclaim, for patent
+infringement (i) against Licensor with respect to a patent applicable to software or
+(ii) against any entity with respect to a patent applicable to the Original Work (but
+excluding combinations of the Original Work with other software or hardware).
+
+11) Jurisdiction, Venue and Governing Law. Any action or suit relating to this License
+may be brought only in the courts of a jurisdiction wherein the Licensor resides or in
+which Licensor conducts its primary business, and under the laws of that jurisdiction
+excluding its conflict-of-law provisions. The application of the United Nations
+Convention on Contracts for the International Sale of Goods is expressly excluded.
+Any use of the Original Work outside the scope of this License or after its
+termination shall be subject to the requirements and penalties of the U.S. Copyright
+Act, 17 U.S.C. ¤ 101 et seq., the equivalent laws of other countries, and
+international treaty. This section shall survive the termination of this License.
+
+12) Attorneys Fees. In any action to enforce the terms of this License or seeking
+damages relating thereto, the prevailing party shall be entitled to recover its costs
+and expenses, including, without limitation, reasonable attorneys` fees and costs
+incurred in connection with such action, including any appeal of such action. This
+section shall survive the termination of this License.
+
+13) Miscellaneous. This License represents the complete agreement concerning the
+subject matter hereof. If any provision of this License is held to be unenforceable,
+such provision shall be reformed only to the extent necessary to make it enforceable.
+
+14) Definition of "You" in This License. "You" throughout this License, whether in
+upper or lower case, means an individual or a legal entity exercising rights under,
+and complying with all of the terms of, this License. For legal entities, "You"
+includes any entity that controls, is controlled by, or is under common control with
+you. For purposes of this definition, "control" means (i) the power, direct or
+indirect, to cause the direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares,
+or (iii) beneficial ownership of such entity.
+
+15) Right to Use. You may use the Original Work in all ways not otherwise restricted
+or conditioned by this License or by law, and Licensor promises not to interfere with
+or be responsible for such uses by You.
+
+This license is Copyright (C) 2003 Lawrence E. Rosen. All rights reserved.
+Permission is hereby granted to copy and distribute this license without modification.
+This license may not be modified without the express written permission of its
+copyright owner.
+
+
+
+
+AMD
+
+� 2005 Advanced Micro Devices, Inc. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that existing copyright notices
+are retained in all copies, this notice is included verbatim in any
+distributions, and the terms and conditions hererin are met.
+
+Use of the this software manifests acceptance of the terms of this
+license by performance.
+
+The name of Advanced Micro Devices, Inc. may not be used to endorse or
+promote products derived from this software without specific prior
+written permission.
+
+THIS SOFTWARE IS PROVIDED BY ADVANCED MICRO DEVICES, INC. "AS IS" AND ANY
+EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+PURPOSE AND NON-INFRINGEMENT, OR THOSE ARISING FROM CUSTOM OF TRADE OR
+COURSE OF USAGE ARE DISCLAIMED.
+
+IN NO EVENT SHALL ADVANCED MICRO DEVICES, INC. BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED, AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE ITS DOCUMENTATION OR ANY DERIVATIVES
+THEREOF, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BY USING THIS
+SOFTWARE WITHOUT CHARGE, YOU ACCEPT THIS ALLOCATION OF RISK. THIS
+DISCLAIMER OF LIABILITY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE.
+ADVANCED MICRO DEVICES, INC. HAS NO OBLIGATION TO PROVIDE MAINTENANCE,
+SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS OF THIS SOFTWARE.
+
+In the redistribution and use of this software, each party shall at all
+times comply with all applicable governmental laws, statutes, ordinances,
+rules, regulations, orders, and other requirements, including without
+limitation such governmental requirements applicable to environmental
+protection, health, safety, wages, hours, equal employment opportunity,
+nondiscrimination, working conditions, import or export control, and
+transportation. Without limiting the foregoing, each party shall adhere
+to the U.S. Export Administration Regulations (EAR), currently found at
+15 C.F.R. Sections 730 through 744, and, unless properly authorized by
+the U.S. Government, shall not (1) export, re-export or release restricted
+technology, software, or source code to a national of a country in Country
+Groups D:1 or E:1, or (2) export to Country Groups D:1 or E:1 the direct
+product of such technology or software, if such foreign produced direct
+product is subject to national security controls as identified on the
+Commerce Control List (currently found in Supplement 1 to Section 774 of EAR).
+These export requirements shall survive any expiration or termination
+of this agreement.
+
+
+
+Apache-2.0
+
+
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don`t include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+
+
+
+Artistic-1.0
+
+
+The Artistic License
+Preamble
+
+The intent of this document is to state the conditions under which a Package may be
+copied, such that the Copyright Holder maintains some semblance of artistic control
+over the development of the package, while giving the users of the package the right
+to use and distribute the Package in a more-or-less customary fashion, plus the right
+to make reasonable modifications.
+
+Definitions:
+
+"Package" refers to the collection of files distributed by the Copyright Holder, and
+derivatives of that collection of files created through textual modification.
+"Standard Version" refers to such a Package if it has not been modified, or has been
+modified in accordance with the wishes of the Copyright Holder.
+"Copyright Holder" is whoever is named in the copyright or copyrights for the package.
+"You" is you, if you`re thinking about copying or distributing this Package.
+"Reasonable copying fee" is whatever you can justify on the basis of media cost,
+duplication charges, time of people involved, and so on. (You will not be required to
+justify it to the Copyright Holder, but only to the computing community at large as a
+market that must bear the fee.)
+"Freely Available" means that no fee is charged for the item itself, though there may
+be fees involved in handling the item. It also means that recipients of the item may
+redistribute it under the same conditions they received it.
+1. You may make and give away verbatim copies of the source form of the Standard
+Version of this Package without restriction, provided that you duplicate all of the
+original copyright notices and associated disclaimers.
+
+2. You may apply bug fixes, portability fixes and other modifications derived from the
+Public Domain or from the Copyright Holder. A Package modified in such a way shall
+still be considered the Standard Version.
+
+3. You may otherwise modify your copy of this Package in any way, provided that you
+insert a prominent notice in each changed file stating how and when you changed that
+file, and provided that you do at least ONE of the following:
+
+a) place your modifications in the Public Domain or otherwise make them Freely
+Available, such as by posting said modifications to Usenet or an equivalent medium, or
+placing the modifications on a major archive site 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.
+
+4. You may distribute the programs of this Package in object code or executable form,
+provided that you do at least ONE of the following:
+
+a) distribute a Standard Version of the executables and library files, together with
+instructions (in the manual page or equivalent) on where to get the Standard Version.
+
+b) accompany the distribution with the machine-readable source of the Package with
+your modifications.
+
+c) accompany any non-standard executables with their corresponding Standard Version
+executables, giving the non-standard executables non-standard names, and clearly
+documenting the differences in manual pages (or equivalent), together with
+instructions on where to get the Standard Version.
+
+d) make other distribution arrangements with the Copyright Holder.
+
+5. You may charge a reasonable copying fee for any distribution of this Package. You
+may charge any fee you choose for support of this Package. You may not charge a fee
+for this Package itself. However, you may distribute this Package in aggregate with
+other (possibly commercial) programs as part of a larger (possibly commercial)
+software distribution provided that you do not advertise this Package as a product of
+your own.
+
+6. The scripts and library files supplied as input to or produced as output from the
+programs of this Package do not automatically fall under the copyright of this
+Package, but belong to whomever generated them, and may be sold commercially, and may
+be aggregated with this Package.
+
+7. C or perl subroutines supplied by you and linked into this Package shall not be
+considered part of this Package.
+
+8. The name of the Copyright Holder may not be used to endorse or promote products
+derived from this software without specific prior written permission.
+
+9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
+INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS
+FOR A PARTICULAR PURPOSE.
+
+The End
+
+
+
+
+Artistic-2.0
+
+
+ The Artistic License 2.0
+
+ Copyright (c) 2000-2006, The Perl Foundation.
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+Preamble
+
+This license establishes the terms under which a given free software
+Package may be copied, modified, distributed, and/or redistributed.
+The intent is that the Copyright Holder maintains some artistic
+control over the development of that Package while still keeping the
+Package available as open source and free software.
+
+You are always permitted to make arrangements wholly outside of this
+license directly with the Copyright Holder of a given Package. If the
+terms of this license do not permit the full use that you propose to
+make of the Package, you should contact the Copyright Holder and seek
+a different licensing arrangement.
+
+Definitions
+
+ "Copyright Holder" means the individual(s) or organization(s)
+ named in the copyright notice for the entire Package.
+
+ "Contributor" means any party that has contributed code or other
+ material to the Package, in accordance with the Copyright Holder`s
+ procedures.
+
+ "You" and "your" means any person who would like to copy,
+ distribute, or modify the Package.
+
+ "Package" means the collection of files distributed by the
+ Copyright Holder, and derivatives of that collection and/or of
+ those files. A given Package may consist of either the Standard
+ Version, or a Modified Version.
+
+ "Distribute" means providing a copy of the Package or making it
+ accessible to anyone else, or in the case of a company or
+ organization, to others outside of your company or organization.
+
+ "Distributor Fee" means any fee that you charge for Distributing
+ this Package or providing support for this Package to another
+ party. It does not mean licensing fees.
+
+ "Standard Version" refers to the Package if it has not been
+ modified, or has been modified only in ways explicitly requested
+ by the Copyright Holder.
+
+ "Modified Version" means the Package, if it has been changed, and
+ such changes were not explicitly requested by the Copyright
+ Holder.
+
+ "Original License" means this Artistic License as Distributed with
+ the Standard Version of the Package, in its current version or as
+ it may be modified by The Perl Foundation in the future.
+
+ "Source" form means the source code, documentation source, and
+ configuration files for the Package.
+
+ "Compiled" form means the compiled bytecode, object code, binary,
+ or any other form resulting from mechanical transformation or
+ translation of the Source form.
+
+
+Permission for Use and Modification Without Distribution
+
+(1) You are permitted to use the Standard Version and create and use
+Modified Versions for any purpose without restriction, provided that
+you do not Distribute the Modified Version.
+
+
+Permissions for Redistribution of the Standard Version
+
+(2) You may Distribute verbatim copies of the Source form of the
+Standard Version of this Package in any medium without restriction,
+either gratis or for a Distributor Fee, provided that you duplicate
+all of the original copyright notices and associated disclaimers. At
+your discretion, such verbatim copies may or may not include a
+Compiled form of the Package.
+
+(3) You may apply any bug fixes, portability changes, and other
+modifications made available from the Copyright Holder. The resulting
+Package will still be considered the Standard Version, and as such
+will be subject to the Original License.
+
+
+Distribution of Modified Versions of the Package as Source
+
+(4) You may Distribute your Modified Version as Source (either gratis
+or for a Distributor Fee, and with or without a Compiled form of the
+Modified Version) provided that you clearly document how it differs
+from the Standard Version, including, but not limited to, documenting
+any non-standard features, executables, or modules, and provided that
+you do at least ONE of the following:
+
+ (a) make the Modified Version available to the Copyright Holder
+ of the Standard Version, under the Original License, so that the
+ Copyright Holder may include your modifications in the Standard
+ Version.
+
+ (b) ensure that installation of your Modified Version does not
+ prevent the user installing or running the Standard Version. In
+ addition, the Modified Version must bear a name that is different
+ from the name of the Standard Version.
+
+ (c) allow anyone who receives a copy of the Modified Version to
+ make the Source form of the Modified Version available to others
+ under
+
+ (i) the Original License or
+
+ (ii) a license that permits the licensee to freely copy,
+ modify and redistribute the Modified Version using the same
+ licensing terms that apply to the copy that the licensee
+ received, and requires that the Source form of the Modified
+ Version, and of any works derived from it, be made freely
+ available in that license fees are prohibited but Distributor
+ Fees are allowed.
+
+
+Distribution of Compiled Forms of the Standard Version
+or Modified Versions without the Source
+
+(5) You may Distribute Compiled forms of the Standard Version without
+the Source, provided that you include complete instructions on how to
+get the Source of the Standard Version. Such instructions must be
+valid at the time of your distribution. If these instructions, at any
+time while you are carrying out such distribution, become invalid, you
+must provide new instructions on demand or cease further distribution.
+If you provide valid instructions or cease distribution within thirty
+days after you become aware that the instructions are invalid, then
+you do not forfeit any of your rights under this license.
+
+(6) You may Distribute a Modified Version in Compiled form without
+the Source, provided that you comply with Section 4 with respect to
+the Source of the Modified Version.
+
+
+Aggregating or Linking the Package
+
+(7) You may aggregate the Package (either the Standard Version or
+Modified Version) with other packages and Distribute the resulting
+aggregation provided that you do not charge a licensing fee for the
+Package. Distributor Fees are permitted, and licensing fees for other
+components in the aggregation are permitted. The terms of this license
+apply to the use and Distribution of the Standard or Modified Versions
+as included in the aggregation.
+
+(8) You are permitted to link Modified and Standard Versions with
+other works, to embed the Package in a larger work of your own, or to
+build stand-alone binary or bytecode versions of applications that
+include the Package, and Distribute the result without restriction,
+provided the result does not expose a direct interface to the Package.
+
+
+Items That are Not Considered Part of a Modified Version
+
+(9) Works (including, but not limited to, modules and scripts) that
+merely extend or make use of the Package, do not, by themselves, cause
+the Package to be a Modified Version. In addition, such works are not
+considered parts of the Package itself, and are not subject to the
+terms of this license.
+
+
+General Provisions
+
+(10) Any use, modification, and distribution of the Standard or
+Modified Versions is governed by this Artistic License. By using,
+modifying or distributing the Package, you accept this license. Do not
+use, modify, or distribute the Package, if you do not accept this
+license.
+
+(11) If your Modified Version has been derived from a Modified
+Version made by someone other than you, you are nevertheless required
+to ensure that your Modified Version complies with the requirements of
+this license.
+
+(12) This license does not grant you the right to use any trademark,
+service mark, tradename, or logo of the Copyright Holder.
+
+(13) This license includes the non-exclusive, worldwide,
+free-of-charge patent license to make, have made, use, offer to sell,
+sell, import and otherwise transfer the Package with respect to any
+patent claims licensable by the Copyright Holder that are necessarily
+infringed by the Package. If you institute patent litigation
+(including a cross-claim or counterclaim) against any party alleging
+that the Package constitutes direct or contributory patent
+infringement, then this Artistic License to you shall terminate on the
+date that such litigation is filed.
+
+(14) Disclaimer of Warranty:
+THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS
+IS` AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
+NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL
+LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL
+BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+BSD
+
+Copyright (c) The Regents of the University of California.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. Neither the name of the University nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+
+
+BSD-2-Clause
+
+
+The FreeBSD Copyright
+
+Copyright 1992-2010 The FreeBSD Project. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this list of
+conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright notice, this list of
+conditions and the following disclaimer in the documentation and/or other materials
+provided with the distribution.
+THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS`` AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD
+PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+The views and conclusions contained in the software and documentation are those of the
+authors and should not be interpreted as representing official policies, either
+expressed or implied, of the FreeBSD Project.
+
+
+
+
+BSD-3-Clause
+
+
+Copyright (c) <YEAR>, <OWNER>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this list of
+conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright notice, this list of
+conditions and the following disclaimer in the documentation and/or other materials
+provided with the distribution.
+Neither the name of the <ORGANIZATION> nor the names of its contributors may be
+used to endorse or promote products derived from this software without specific prior
+written permission.
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
+SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
+TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
+WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGE.
+
+
+
+
+BSD-4-Clause
+
+
+Copyright (c) <year>, <copyright holder>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. All advertising materials mentioning features or use of this software
+ must display the following acknowledgement:
+ This product includes software developed by the <organization>.
+4. Neither the name of the <organization> nor the
+ names of its contributors may be used to endorse or promote products
+ derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY <COPYRIGHT HOLDER> ``AS IS`` AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+BSL-1.0
+
+
+Boost Software License - Version 1.0 - August 17th, 2003
+
+Permission is hereby granted, free of charge, to any person or organization
+obtaining a copy of the software and accompanying documentation covered by
+this license (the "Software") to use, reproduce, display, distribute,
+execute, and transmit the Software, and to prepare derivative works of the
+Software, and to permit third-parties to whom the Software is furnished to
+do so, all subject to the following:
+
+The copyright notices in the Software and this entire statement, including
+the above license grant, this restriction and the following disclaimer,
+must be included in all copies of the Software, in whole or in part, and
+all derivative works of the Software, unless such copies or derivative
+works are solely in the form of machine-executable object code generated by
+a source language processor.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
+SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
+FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
+ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.
+
+
+
+
+CC-BY-4.0
+
+Attribution 4.0 International
+
+=======================================================================
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and
+does not provide legal services or legal advice. Distribution of
+Creative Commons public licenses does not create a lawyer-client or
+other relationship. Creative Commons makes its licenses and related
+information available on an "as-is" basis. Creative Commons gives no
+warranties regarding its licenses, any material licensed under their
+terms and conditions, or any related information. Creative Commons
+disclaims all liability for damages resulting from their use to the
+fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and
+conditions that creators and other rights holders may use to share
+original works of authorship and other material subject to copyright
+and certain other rights specified in the public license below. The
+following considerations are for informational purposes only, are not
+exhaustive, and do not form part of our licenses.
+
+ Considerations for licensors: Our public licenses are
+ intended for use by those authorized to give the public
+ permission to use material in ways otherwise restricted by
+ copyright and certain other rights. Our licenses are
+ irrevocable. Licensors should read and understand the terms
+ and conditions of the license they choose before applying it.
+ Licensors should also secure all rights necessary before
+ applying our licenses so that the public can reuse the
+ material as expected. Licensors should clearly mark any
+ material not subject to the license. This includes other CC-
+ licensed material, or material used under an exception or
+ limitation to copyright. More considerations for licensors:
+ wiki.creativecommons.org/Considerations_for_licensors
+
+ Considerations for the public: By using one of our public
+ licenses, a licensor grants the public permission to use the
+ licensed material under specified terms and conditions. If
+ the licensor's permission is not necessary for any reason--for
+ example, because of any applicable exception or limitation to
+ copyright--then that use is not regulated by the license. Our
+ licenses grant only permissions under copyright and certain
+ other rights that a licensor has authority to grant. Use of
+ the licensed material may still be restricted for other
+ reasons, including because others have copyright or other
+ rights in the material. A licensor may make special requests,
+ such as asking that all changes be marked or described.
+ Although not required by our licenses, you are encouraged to
+ respect those requests where reasonable. More_considerations
+ for the public:
+ wiki.creativecommons.org/Considerations_for_licensees
+
+=======================================================================
+
+Creative Commons Attribution 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree
+to be bound by the terms and conditions of this Creative Commons
+Attribution 4.0 International Public License ("Public License"). To the
+extent this Public License may be interpreted as a contract, You are
+granted the Licensed Rights in consideration of Your acceptance of
+these terms and conditions, and the Licensor grants You such rights in
+consideration of benefits the Licensor receives from making the
+Licensed Material available under these terms and conditions.
+
+
+Section 1 -- Definitions.
+
+ a. Adapted Material means material subject to Copyright and Similar
+ Rights that is derived from or based upon the Licensed Material
+ and in which the Licensed Material is translated, altered,
+ arranged, transformed, or otherwise modified in a manner requiring
+ permission under the Copyright and Similar Rights held by the
+ Licensor. For purposes of this Public License, where the Licensed
+ Material is a musical work, performance, or sound recording,
+ Adapted Material is always produced where the Licensed Material is
+ synched in timed relation with a moving image.
+
+ b. Adapter's License means the license You apply to Your Copyright
+ and Similar Rights in Your contributions to Adapted Material in
+ accordance with the terms and conditions of this Public License.
+
+ c. Copyright and Similar Rights means copyright and/or similar rights
+ closely related to copyright including, without limitation,
+ performance, broadcast, sound recording, and Sui Generis Database
+ Rights, without regard to how the rights are labeled or
+ categorized. For purposes of this Public License, the rights
+ specified in Section 2(b)(1)-(2) are not Copyright and Similar
+ Rights.
+
+ d. Effective Technological Measures means those measures that, in the
+ absence of proper authority, may not be circumvented under laws
+ fulfilling obligations under Article 11 of the WIPO Copyright
+ Treaty adopted on December 20, 1996, and/or similar international
+ agreements.
+
+ e. Exceptions and Limitations means fair use, fair dealing, and/or
+ any other exception or limitation to Copyright and Similar Rights
+ that applies to Your use of the Licensed Material.
+
+ f. Licensed Material means the artistic or literary work, database,
+ or other material to which the Licensor applied this Public
+ License.
+
+ g. Licensed Rights means the rights granted to You subject to the
+ terms and conditions of this Public License, which are limited to
+ all Copyright and Similar Rights that apply to Your use of the
+ Licensed Material and that the Licensor has authority to license.
+
+ h. Licensor means the individual(s) or entity(ies) granting rights
+ under this Public License.
+
+ i. Share means to provide material to the public by any means or
+ process that requires permission under the Licensed Rights, such
+ as reproduction, public display, public performance, distribution,
+ dissemination, communication, or importation, and to make material
+ available to the public including in ways that members of the
+ public may access the material from a place and at a time
+ individually chosen by them.
+
+ j. Sui Generis Database Rights means rights other than copyright
+ resulting from Directive 96/9/EC of the European Parliament and of
+ the Council of 11 March 1996 on the legal protection of databases,
+ as amended and/or succeeded, as well as other essentially
+ equivalent rights anywhere in the world.
+
+ k. You means the individual or entity exercising the Licensed Rights
+ under this Public License. Your has a corresponding meaning.
+
+
+Section 2 -- Scope.
+
+ a. License grant.
+
+ 1. Subject to the terms and conditions of this Public License,
+ the Licensor hereby grants You a worldwide, royalty-free,
+ non-sublicensable, non-exclusive, irrevocable license to
+ exercise the Licensed Rights in the Licensed Material to:
+
+ a. reproduce and Share the Licensed Material, in whole or
+ in part; and
+
+ b. produce, reproduce, and Share Adapted Material.
+
+ 2. Exceptions and Limitations. For the avoidance of doubt, where
+ Exceptions and Limitations apply to Your use, this Public
+ License does not apply, and You do not need to comply with
+ its terms and conditions.
+
+ 3. Term. The term of this Public License is specified in Section
+ 6(a).
+
+ 4. Media and formats; technical modifications allowed. The
+ Licensor authorizes You to exercise the Licensed Rights in
+ all media and formats whether now known or hereafter created,
+ and to make technical modifications necessary to do so. The
+ Licensor waives and/or agrees not to assert any right or
+ authority to forbid You from making technical modifications
+ necessary to exercise the Licensed Rights, including
+ technical modifications necessary to circumvent Effective
+ Technological Measures. For purposes of this Public License,
+ simply making modifications authorized by this Section 2(a)
+ (4) never produces Adapted Material.
+
+ 5. Downstream recipients.
+
+ a. Offer from the Licensor -- Licensed Material. Every
+ recipient of the Licensed Material automatically
+ receives an offer from the Licensor to exercise the
+ Licensed Rights under the terms and conditions of this
+ Public License.
+
+ b. No downstream restrictions. You may not offer or impose
+ any additional or different terms or conditions on, or
+ apply any Effective Technological Measures to, the
+ Licensed Material if doing so restricts exercise of the
+ Licensed Rights by any recipient of the Licensed
+ Material.
+
+ 6. No endorsement. Nothing in this Public License constitutes or
+ may be construed as permission to assert or imply that You
+ are, or that Your use of the Licensed Material is, connected
+ with, or sponsored, endorsed, or granted official status by,
+ the Licensor or others designated to receive attribution as
+ provided in Section 3(a)(1)(A)(i).
+
+ b. Other rights.
+
+ 1. Moral rights, such as the right of integrity, are not
+ licensed under this Public License, nor are publicity,
+ privacy, and/or other similar personality rights; however, to
+ the extent possible, the Licensor waives and/or agrees not to
+ assert any such rights held by the Licensor to the limited
+ extent necessary to allow You to exercise the Licensed
+ Rights, but not otherwise.
+
+ 2. Patent and trademark rights are not licensed under this
+ Public License.
+
+ 3. To the extent possible, the Licensor waives any right to
+ collect royalties from You for the exercise of the Licensed
+ Rights, whether directly or through a collecting society
+ under any voluntary or waivable statutory or compulsory
+ licensing scheme. In all other cases the Licensor expressly
+ reserves any right to collect such royalties.
+
+
+Section 3 -- License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the
+following conditions.
+
+ a. Attribution.
+
+ 1. If You Share the Licensed Material (including in modified
+ form), You must:
+
+ a. retain the following if it is supplied by the Licensor
+ with the Licensed Material:
+
+ i. identification of the creator(s) of the Licensed
+ Material and any others designated to receive
+ attribution, in any reasonable manner requested by
+ the Licensor (including by pseudonym if
+ designated);
+
+ ii. a copyright notice;
+
+ iii. a notice that refers to this Public License;
+
+ iv. a notice that refers to the disclaimer of
+ warranties;
+
+ v. a URI or hyperlink to the Licensed Material to the
+ extent reasonably practicable;
+
+ b. indicate if You modified the Licensed Material and
+ retain an indication of any previous modifications; and
+
+ c. indicate the Licensed Material is licensed under this
+ Public License, and include the text of, or the URI or
+ hyperlink to, this Public License.
+
+ 2. You may satisfy the conditions in Section 3(a)(1) in any
+ reasonable manner based on the medium, means, and context in
+ which You Share the Licensed Material. For example, it may be
+ reasonable to satisfy the conditions by providing a URI or
+ hyperlink to a resource that includes the required
+ information.
+
+ 3. If requested by the Licensor, You must remove any of the
+ information required by Section 3(a)(1)(A) to the extent
+ reasonably practicable.
+
+ 4. If You Share Adapted Material You produce, the Adapter's
+ License You apply must not prevent recipients of the Adapted
+ Material from complying with this Public License.
+
+
+Section 4 -- Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that
+apply to Your use of the Licensed Material:
+
+ a. for the avoidance of doubt, Section 2(a)(1) grants You the right
+ to extract, reuse, reproduce, and Share all or a substantial
+ portion of the contents of the database;
+
+ b. if You include all or a substantial portion of the database
+ contents in a database in which You have Sui Generis Database
+ Rights, then the database in which You have Sui Generis Database
+ Rights (but not its individual contents) is Adapted Material; and
+
+ c. You must comply with the conditions in Section 3(a) if You Share
+ all or a substantial portion of the contents of the database.
+
+For the avoidance of doubt, this Section 4 supplements and does not
+replace Your obligations under this Public License where the Licensed
+Rights include other Copyright and Similar Rights.
+
+
+Section 5 -- Disclaimer of Warranties and Limitation of Liability.
+
+ a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
+ EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
+ AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
+ ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
+ IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
+ WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
+ PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
+ ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
+ KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
+ ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
+
+ b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
+ TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
+ NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
+ INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
+ COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
+ USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
+ ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
+ DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
+ IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
+
+ c. The disclaimer of warranties and limitation of liability provided
+ above shall be interpreted in a manner that, to the extent
+ possible, most closely approximates an absolute disclaimer and
+ waiver of all liability.
+
+
+Section 6 -- Term and Termination.
+
+ a. This Public License applies for the term of the Copyright and
+ Similar Rights licensed here. However, if You fail to comply with
+ this Public License, then Your rights under this Public License
+ terminate automatically.
+
+ b. Where Your right to use the Licensed Material has terminated under
+ Section 6(a), it reinstates:
+
+ 1. automatically as of the date the violation is cured, provided
+ it is cured within 30 days of Your discovery of the
+ violation; or
+
+ 2. upon express reinstatement by the Licensor.
+
+ For the avoidance of doubt, this Section 6(b) does not affect any
+ right the Licensor may have to seek remedies for Your violations
+ of this Public License.
+
+ c. For the avoidance of doubt, the Licensor may also offer the
+ Licensed Material under separate terms or conditions or stop
+ distributing the Licensed Material at any time; however, doing so
+ will not terminate this Public License.
+
+ d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
+ License.
+
+
+Section 7 -- Other Terms and Conditions.
+
+ a. The Licensor shall not be bound by any additional or different
+ terms or conditions communicated by You unless expressly agreed.
+
+ b. Any arrangements, understandings, or agreements regarding the
+ Licensed Material not stated herein are separate from and
+ independent of the terms and conditions of this Public License.
+
+
+Section 8 -- Interpretation.
+
+ a. For the avoidance of doubt, this Public License does not, and
+ shall not be interpreted to, reduce, limit, restrict, or impose
+ conditions on any use of the Licensed Material that could lawfully
+ be made without permission under this Public License.
+
+ b. To the extent possible, if any provision of this Public License is
+ deemed unenforceable, it shall be automatically reformed to the
+ minimum extent necessary to make it enforceable. If the provision
+ cannot be reformed, it shall be severed from this Public License
+ without affecting the enforceability of the remaining terms and
+ conditions.
+
+ c. No term or condition of this Public License will be waived and no
+ failure to comply consented to unless expressly agreed to by the
+ Licensor.
+
+ d. Nothing in this Public License constitutes or may be interpreted
+ as a limitation upon, or waiver of, any privileges and immunities
+ that apply to the Licensor or You, including from the legal
+ processes of any jurisdiction or authority.
+
+
+=======================================================================
+
+Creative Commons is not a party to its public
+licenses. Notwithstanding, Creative Commons may elect to apply one of
+its public licenses to material it publishes and in those instances
+will be considered the ”Licensor.” The text of the Creative Commons
+public licenses is dedicated to the public domain under the CC0 Public
+Domain Dedication. Except for the limited purpose of indicating that
+material is shared under a Creative Commons public license or as
+otherwise permitted by the Creative Commons policies published at
+creativecommons.org/policies, Creative Commons does not authorize the
+use of the trademark "Creative Commons" or any other trademark or logo
+of Creative Commons without its prior written consent including,
+without limitation, in connection with any unauthorized modifications
+to any of its public licenses or any other arrangements,
+understandings, or agreements concerning use of licensed material. For
+the avoidance of doubt, this paragraph does not form part of the
+public licenses.
+
+Creative Commons may be contacted at creativecommons.org.
+
+
+
+CDDL-1.0
+
+
+COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
+Version 1.0
+1. Definitions.
+
+1.1. “Contributor” means each individual or entity that creates or
+contributes to the creation of Modifications.
+
+1.2. “Contributor Version” means the combination of the Original
+Software, prior Modifications used by a Contributor (if any), and the Modifications
+made by that particular Contributor.
+
+1.3. “Covered Software” means (a) the Original Software, or (b)
+Modifications, or (c) the combination of files containing Original Software with files
+containing Modifications, in each case including portions thereof.
+
+1.4. “Executable” means the Covered Software in any form other
+than Source Code.
+
+1.5. “Initial Developer” means the individual or entity that first
+makes Original Software available under this License.
+
+1.6. “Larger Work” means a work which combines Covered Software or
+portions thereof with code not governed by the terms of this License.
+
+1.7. “License” means this document.
+
+1.8. “Licensable” means having the right to grant, to the maximum
+extent possible, whether at the time of the initial grant or subsequently acquired,
+any and all of the rights conveyed herein.
+
+1.9. “Modifications” means the Source Code and Executable form of
+any of the following:
+
+A. Any file that results from an addition to, deletion from or modification of the
+contents of a file containing Original Software or previous Modifications;
+
+B. Any new file that contains any part of the Original Software or previous
+Modification; or
+
+C. Any new file that is contributed or otherwise made available under the terms of
+this License.
+
+1.10. “Original Software” means the Source Code and Executable
+form of computer software code that is originally released under this License.
+
+1.11. “Patent Claims” means any patent claim(s), now owned or
+hereafter acquired, including without limitation, method, process, and apparatus
+claims, in any patent Licensable by grantor.
+
+1.12. “Source Code” means (a) the common form of computer software
+code in which modifications are made and (b) associated documentation included in or
+with such code.
+
+1.13. “You” (or “Your”) means an individual or
+a legal entity exercising rights under, and complying with all of the terms of, this
+License. For legal entities, “You” includes any entity which
+controls, is controlled by, or is under common control with You. For purposes of this
+definition, “control” means (a) the power, direct or indirect, to
+cause the direction or management of such entity, whether by contract or otherwise, or
+(b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial
+ownership of such entity.
+
+2. License Grants.
+
+2.1. The Initial Developer Grant.
+
+Conditioned upon Your compliance with Section 3.1 below and subject to third party
+intellectual property claims, the Initial Developer hereby grants You a world-wide,
+royalty-free, non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark) Licensable by
+Initial Developer, to use, reproduce, modify, display, perform, sublicense and
+distribute the Original Software (or portions thereof), with or without Modifications,
+and/or as part of a Larger Work; and
+
+(b) under Patent Claims infringed by the making, using or selling of Original
+Software, to make, have made, use, practice, sell, and offer for sale, and/or
+otherwise dispose of the Original Software (or portions thereof).
+
+(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial
+Developer first distributes or otherwise makes the Original Software available to a
+third party under the terms of this License.
+
+(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code
+that You delete from the Original Software, or (2) for infringements caused by: (i)
+the modification of the Original Software, or (ii) the combination of the Original
+Software with other software or devices.
+
+2.2. Contributor Grant.
+
+Conditioned upon Your compliance with Section 3.1 below and subject to third party
+intellectual property claims, each Contributor hereby grants You a world-wide,
+royalty-free, non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark) Licensable by
+Contributor to use, reproduce, modify, display, perform, sublicense and distribute the
+Modifications created by such Contributor (or portions thereof), either on an
+unmodified basis, with other Modifications, as Covered Software and/or as part of a
+Larger Work; and
+
+(b) under Patent Claims infringed by the making, using, or selling of Modifications
+made by that Contributor either alone and/or in combination with its Contributor
+Version (or portions of such combination), to make, use, sell, offer for sale, have
+made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or
+portions thereof); and (2) the combination of Modifications made by that Contributor
+with its Contributor Version (or portions of such combination).
+
+(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
+Contributor first distributes or otherwise makes the Modifications available to a
+third party.
+
+(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any
+code that Contributor has deleted from the Contributor Version; (2) for infringements
+caused by: (i) third party modifications of Contributor Version, or (ii) the
+combination of Modifications made by that Contributor with other software (except as
+part of the Contributor Version) or other devices; or (3) under Patent Claims
+infringed by Covered Software in the absence of Modifications made by that
+Contributor.
+
+3. Distribution Obligations.
+
+3.1. Availability of Source Code.
+
+Any Covered Software that You distribute or otherwise make available in Executable
+form must also be made available in Source Code form and that Source Code form must be
+distributed only under the terms of this License. You must include a copy of this
+License with every copy of the Source Code form of the Covered Software You distribute
+or otherwise make available. You must inform recipients of any such Covered Software
+in Executable form as to how they can obtain such Covered Software in Source Code form
+in a reasonable manner on or through a medium customarily used for software exchange.
+
+3.2. Modifications.
+
+The Modifications that You create or to which You contribute are governed by the terms
+of this License. You represent that You believe Your Modifications are Your original
+creation(s) and/or You have sufficient rights to grant the rights conveyed by this
+License.
+
+3.3. Required Notices.
+
+You must include a notice in each of Your Modifications that identifies You as the
+Contributor of the Modification. You may not remove or alter any copyright, patent or
+trademark notices contained within the Covered Software, or any notices of licensing
+or any descriptive text giving attribution to any Contributor or the Initial
+Developer.
+
+3.4. Application of Additional Terms.
+
+You may not offer or impose any terms on any Covered Software in Source Code form that
+alters or restricts the applicable version of this License or the
+recipients’ rights hereunder. You may choose to offer, and to charge a fee
+for, warranty, support, indemnity or liability obligations to one or more recipients
+of Covered Software. However, you may do so only on Your own behalf, and not on behalf
+of the Initial Developer or any Contributor. You must make it absolutely clear that
+any such warranty, support, indemnity or liability obligation is offered by You alone,
+and You hereby agree to indemnify the Initial Developer and every Contributor for any
+liability incurred by the Initial Developer or such Contributor as a result of
+warranty, support, indemnity or liability terms You offer.
+
+3.5. Distribution of Executable Versions.
+
+You may distribute the Executable form of the Covered Software under the terms of this
+License or under the terms of a license of Your choice, which may contain terms
+different from this License, provided that You are in compliance with the terms of
+this License and that the license for the Executable form does not attempt to limit or
+alter the recipient’s rights in the Source Code form from the rights set
+forth in this License. If You distribute the Covered Software in Executable form under
+a different license, You must make it absolutely clear that any terms which differ
+from this License are offered by You alone, not by the Initial Developer or
+Contributor. You hereby agree to indemnify the Initial Developer and every Contributor
+for any liability incurred by the Initial Developer or such Contributor as a result of
+any such terms You offer.
+
+3.6. Larger Works.
+
+You may create a Larger Work by combining Covered Software with other code not
+governed by the terms of this License and distribute the Larger Work as a single
+product. In such a case, You must make sure the requirements of this License are
+fulfilled for the Covered Software.
+
+4. Versions of the License.
+
+4.1. New Versions.
+
+Sun Microsystems, Inc. is the initial license steward and may publish revised and/or
+new versions of this License from time to time. Each version will be given a
+distinguishing version number. Except as provided in Section 4.3, no one other than
+the license steward has the right to modify this License.
+
+4.2. Effect of New Versions.
+
+You may always continue to use, distribute or otherwise make the Covered Software
+available under the terms of the version of the License under which You originally
+received the Covered Software. If the Initial Developer includes a notice in the
+Original Software prohibiting it from being distributed or otherwise made available
+under any subsequent version of the License, You must distribute and make the Covered
+Software available under the terms of the version of the License under which You
+originally received the Covered Software. Otherwise, You may also choose to use,
+distribute or otherwise make the Covered Software available under the terms of any
+subsequent version of the License published by the license steward.
+
+4.3. Modified Versions.
+
+When You are an Initial Developer and You want to create a new license for Your
+Original Software, You may create and use a modified version of this License if You:
+(a) rename the license and remove any references to the name of the license steward
+(except to note that the license differs from this License); and (b) otherwise make it
+clear that the license contains terms which differ from this License.
+
+5. DISCLAIMER OF WARRANTY.
+
+COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS”
+BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
+LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT
+FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
+PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
+DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR)
+ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
+WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE
+IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
+
+6. TERMINATION.
+
+6.1. This License and the rights granted hereunder will terminate automatically if You
+fail to comply with terms herein and fail to cure such breach within 30 days of
+becoming aware of the breach. Provisions which, by their nature, must remain in effect
+beyond the termination of this License shall survive.
+
+6.2. If You assert a patent infringement claim (excluding declaratory judgment
+actions) against Initial Developer or a Contributor (the Initial Developer or
+Contributor against whom You assert such claim is referred to as
+“Participant”) alleging that the Participant Software (meaning the
+Contributor Version where the Participant is a Contributor or the Original Software
+where the Participant is the Initial Developer) directly or indirectly infringes any
+patent, then any and all rights granted directly or indirectly to You by such
+Participant, the Initial Developer (if the Initial Developer is not the Participant)
+and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days
+notice from Participant terminate prospectively and automatically at the expiration of
+such 60 day notice period, unless if within such 60 day period You withdraw Your claim
+with respect to the Participant Software against such Participant either unilaterally
+or pursuant to a written agreement with Participant.
+
+6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user
+licenses that have been validly granted by You or any distributor hereunder prior to
+termination (excluding licenses granted to You by any distributor) shall survive
+termination.
+
+7. LIMITATION OF LIABILITY.
+
+UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
+CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR
+ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE
+TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
+CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,
+WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL
+DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF
+SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
+PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT
+APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
+EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
+LIMITATION MAY NOT APPLY TO YOU.
+
+8. U.S. GOVERNMENT END USERS.
+
+The Covered Software is a “commercial item,” as that term is
+defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of “commercial computer
+software” (as that term is defined at 48 C.F.R. §
+252.227-7014(a)(1)) and “commercial computer software
+documentation” as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
+Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
+1995), all U.S. Government End Users acquire Covered Software with only those rights
+set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes,
+any other FAR, DFAR, or other clause or provision that addresses Government rights in
+computer software under this License.
+
+9. MISCELLANEOUS.
+
+This License represents the complete agreement concerning subject matter hereof. If
+any provision of this License is held to be unenforceable, such provision shall be
+reformed only to the extent necessary to make it enforceable. This License shall be
+governed by the law of the jurisdiction specified in a notice contained within the
+Original Software (except to the extent applicable law, if any, provides otherwise),
+excluding such jurisdiction’s conflict-of-law provisions. Any litigation
+relating to this License shall be subject to the jurisdiction of the courts located in
+the jurisdiction and venue specified in a notice contained within the Original
+Software, with the losing party responsible for costs, including, without limitation,
+court costs and reasonable attorneys’ fees and expenses. The application of
+the United Nations Convention on Contracts for the International Sale of Goods is
+expressly excluded. Any law or regulation which provides that the language of a
+contract shall be construed against the drafter shall not apply to this License. You
+agree that You alone are responsible for compliance with the United States export
+administration regulations (and the export control laws and regulation of any other
+countries) when You use, distribute or otherwise make available any Covered Software.
+
+10. RESPONSIBILITY FOR CLAIMS.
+
+As between Initial Developer and the Contributors, each party is responsible for
+claims and damages arising, directly or indirectly, out of its utilization of rights
+under this License and You agree to work with Initial Developer and Contributors to
+distribute such responsibility on an equitable basis. Nothing herein is intended or
+shall be deemed to constitute any admission of liability.
+
+
+
+
+CDS
+
+This software is copyrighted by Cadence Design Systems, Inc., and other
+parties. The following terms apply to all files associated with the
+software unless explicitly disclaimed in individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+-----------------------------------------------------------------------
+ Following is the original agreement for the Tcl/Tk software from
+ Sun Microsystems.
+-----------------------------------------------------------------------
+
+This software is copyrighted by the Regents of the University of
+California, Sun Microsystems, Inc., and other parties. The following
+terms apply to all files associated with the software unless explicitly
+disclaimed in individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+
+
+CPL-1.0
+
+
+Common Public License Version 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
+LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
+CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+a) in the case of the initial Contributor, the initial code and
+documentation distributed under this Agreement, and
+
+b) in the case of each subsequent Contributor:
+
+i) changes to the Program, and
+
+ii) additions to the Program;
+
+where such changes and/or additions to the Program originate from and are
+distributed by that particular Contributor. A Contribution `originates` from a
+Contributor if it was added to the Program by such Contributor itself or anyone
+acting on such Contributor`s behalf. Contributions do not include additions to
+the Program which: (i) are separate modules of software distributed in
+conjunction with the Program under their own license agreement, and (ii) are not
+derivative works of the Program.
+
+"Contributor" means any person or entity that distributes the Program.
+
+"Licensed Patents " mean patent claims licensable by a Contributor which are
+necessarily infringed by the use or sale of its Contribution alone or when
+combined with the Program.
+
+"Program" means the Contributions distributed in accordance with this Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement,
+including all Contributors.
+
+2. GRANT OF RIGHTS
+
+a) Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide, royalty-free copyright license to
+reproduce, prepare derivative works of, publicly display, publicly perform,
+distribute and sublicense the Contribution of such Contributor, if any, and such
+derivative works, in source code and object code form.
+
+b) Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
+Patents to make, use, sell, offer to sell, import and otherwise transfer the
+Contribution of such Contributor, if any, in source code and object code form.
+This patent license shall apply to the combination of the Contribution and the
+Program if, at the time the Contribution is added by the Contributor, such
+addition of the Contribution causes such combination to be covered by the
+Licensed Patents. The patent license shall not apply to any other combinations
+which include the Contribution. No hardware per se is licensed hereunder.
+
+c) Recipient understands that although each Contributor grants the licenses
+to its Contributions set forth herein, no assurances are provided by any
+Contributor that the Program does not infringe the patent or other intellectual
+property rights of any other entity. Each Contributor disclaims any liability to
+Recipient for claims brought by any other entity based on infringement of
+intellectual property rights or otherwise. As a condition to exercising the
+rights and licenses granted hereunder, each Recipient hereby assumes sole
+responsibility to secure any other intellectual property rights needed, if any.
+For example, if a third party patent license is required to allow Recipient to
+distribute the Program, it is Recipient`s responsibility to acquire that license
+before distributing the Program.
+
+d) Each Contributor represents that to its knowledge it has sufficient
+copyright rights in its Contribution, if any, to grant the copyright license set
+forth in this Agreement.
+
+3. REQUIREMENTS
+
+A Contributor may choose to distribute the Program in object code form under its
+own license agreement, provided that:
+
+a) it complies with the terms and conditions of this Agreement; and
+
+b) its license agreement:
+
+i) effectively disclaims on behalf of all Contributors all warranties and
+conditions, express and implied, including warranties or conditions of title and
+non-infringement, and implied warranties or conditions of merchantability and
+fitness for a particular purpose;
+
+ii) effectively excludes on behalf of all Contributors all liability for
+damages, including direct, indirect, special, incidental and consequential
+damages, such as lost profits;
+
+iii) states that any provisions which differ from this Agreement are offered
+by that Contributor alone and not by any other party; and
+
+iv) states that source code for the Program is available from such
+Contributor, and informs licensees how to obtain it in a reasonable manner on or
+through a medium customarily used for software exchange.
+
+When the Program is made available in source code form:
+
+a) it must be made available under this Agreement; and
+
+b) a copy of this Agreement must be included with each copy of the Program.
+
+Contributors may not remove or alter any copyright notices contained within the
+Program.
+
+Each Contributor must identify itself as the originator of its Contribution, if
+any, in a manner that reasonably allows subsequent Recipients to identify the
+originator of the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities with
+respect to end users, business partners and the like. While this license is
+intended to facilitate the commercial use of the Program, the Contributor who
+includes the Program in a commercial product offering should do so in a manner
+which does not create potential liability for other Contributors. Therefore, if
+a Contributor includes the Program in a commercial product offering, such
+Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
+every other Contributor ("Indemnified Contributor") against any losses, damages
+and costs (collectively "Losses") arising from claims, lawsuits and other legal
+actions brought by a third party against the Indemnified Contributor to the
+extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product
+offering. The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement. In order
+to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
+Contributor in writing of such claim, and b) allow the Commercial Contributor to
+control, and cooperate with the Commercial Contributor in, the defense and any
+related settlement negotiations. The Indemnified Contributor may participate in
+any such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial product
+offering, Product X. That Contributor is then a Commercial Contributor. If that
+Commercial Contributor then makes performance claims, or offers warranties
+related to Product X, those performance claims and warranties are such
+Commercial Contributor`s responsibility alone. Under this section, the
+Commercial Contributor would have to defend claims against the other
+Contributors related to those performance claims and warranties, and if a court
+requires any other Contributor to pay any damages as a result, the Commercial
+Contributor must pay those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
+IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
+NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
+Recipient is solely responsible for determining the appropriateness of using and
+distributing the Program and assumes all risks associated with its exercise of
+rights under this Agreement, including but not limited to the risks and costs of
+program errors, compliance with applicable laws, damage to or loss of data,
+programs or equipment, and unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
+CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
+PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
+GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under applicable
+law, it shall not affect the validity or enforceability of the remainder of the
+terms of this Agreement, and without further action by the parties hereto, such
+provision shall be reformed to the minimum extent necessary to make such
+provision valid and enforceable.
+
+If Recipient institutes patent litigation against a Contributor with respect to
+a patent applicable to software (including a cross-claim or counterclaim in a
+lawsuit), then any patent licenses granted by that Contributor to such Recipient
+under this Agreement shall terminate as of the date such litigation is filed. In
+addition, if Recipient institutes patent litigation against any entity
+(including a cross-claim or counterclaim in a lawsuit) alleging that the Program
+itself (excluding combinations of the Program with other software or hardware)
+infringes such Recipient`s patent(s), then such Recipient`s rights granted under
+Section 2(b) shall terminate as of the date such litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it fails to
+comply with any of the material terms or conditions of this Agreement and does
+not cure such failure in a reasonable period of time after becoming aware of
+such noncompliance. If all Recipient`s rights under this Agreement terminate,
+Recipient agrees to cease use and distribution of the Program as soon as
+reasonably practicable. However, Recipient`s obligations under this Agreement
+and any licenses granted by Recipient relating to the Program shall continue and
+survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement, but in
+order to avoid inconsistency the Agreement is copyrighted and may only be
+modified in the following manner. The Agreement Steward reserves the right to
+publish new versions (including revisions) of this Agreement from time to time.
+No one other than the Agreement Steward has the right to modify this Agreement.
+IBM is the initial Agreement Steward. IBM may assign the responsibility to serve
+as the Agreement Steward to a suitable separate entity. Each new version of the
+Agreement will be given a distinguishing version number. The Program (including
+Contributions) may always be distributed subject to the version of the Agreement
+under which it was received. In addition, after a new version of the Agreement
+is published, Contributor may elect to distribute the Program (including its
+Contributions) under the new version. Except as expressly stated in Sections
+2(a) and 2(b) above, Recipient receives no rights or licenses to the
+intellectual property of any Contributor under this Agreement, whether
+expressly, by implication, estoppel or otherwise. All rights in the Program not
+expressly granted under this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and the
+intellectual property laws of the United States of America. No party to this
+Agreement will bring a legal action under this Agreement more than one year
+after the cause of action arose. Each party waives its rights to a jury trial in
+any resulting litigation.
+
+
+
+
+CUP
+
+CUP PARSER GENERATOR COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
+
+Copyright 1996 by Scott Hudson, Frank Flannery, C. Scott Ananian
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted,
+provided that the above copyright notice appear in all copies and that
+both the copyright notice and this permission notice and warranty
+disclaimer appear in supporting documentation, and that the names of
+the authors or their employers not be used in advertising or publicity
+pertaining to distribution of the software without specific, written
+prior permission.
+
+The authors and their employers disclaim all warranties with regard to
+this software, including all implied warranties of merchantability and
+fitness. In no event shall the authors or their employers be liable
+for any special, indirect or consequential damages or any damages
+whatsoever resulting from loss of use, data or profits, whether in an
+action of contract, negligence or other tortious action, arising out of
+or in connection with the use or performance of this software.
+
+
+
+EPL-1.0
+
+
+Eclipse Public License - v 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE
+("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES
+RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+a) in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and
+b) in the case of each subsequent Contributor:
+i) changes to the Program, and
+ii) additions to the Program;
+where such changes and/or additions to the Program originate from and are distributed
+by that particular Contributor. A Contribution `originates` from a Contributor if it
+was added to the Program by such Contributor itself or anyone acting on such
+Contributor`s behalf. Contributions do not include additions to the Program which: (i)
+are separate modules of software distributed in conjunction with the Program under
+their own license agreement, and (ii) are not derivative works of the Program.
+"Contributor" means any person or entity that distributes the Program.
+
+"Licensed Patents" mean patent claims licensable by a Contributor which are
+necessarily infringed by the use or sale of its Contribution alone or when combined
+with the Program.
+
+"Program" means the Contributions distributed in accordance with this Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement, including all
+Contributors.
+
+2. GRANT OF RIGHTS
+
+a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
+non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare
+derivative works of, publicly display, publicly perform, distribute and sublicense the
+Contribution of such Contributor, if any, and such derivative works, in source code
+and object code form.
+b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
+non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make,
+use, sell, offer to sell, import and otherwise transfer the Contribution of such
+Contributor, if any, in source code and object code form. This patent license shall
+apply to the combination of the Contribution and the Program if, at the time the
+Contribution is added by the Contributor, such addition of the Contribution causes
+such combination to be covered by the Licensed Patents. The patent license shall not
+apply to any other combinations which include the Contribution. No hardware per se is
+licensed hereunder.
+c) Recipient understands that although each Contributor grants the licenses to its
+Contributions set forth herein, no assurances are provided by any Contributor that the
+Program does not infringe the patent or other intellectual property rights of any
+other entity. Each Contributor disclaims any liability to Recipient for claims brought
+by any other entity based on infringement of intellectual property rights or
+otherwise. As a condition to exercising the rights and licenses granted hereunder,
+each Recipient hereby assumes sole responsibility to secure any other intellectual
+property rights needed, if any. For example, if a third party patent license is
+required to allow Recipient to distribute the Program, it is Recipient`s
+responsibility to acquire that license before distributing the Program.
+d) Each Contributor represents that to its knowledge it has sufficient copyright
+rights in its Contribution, if any, to grant the copyright license set forth in this
+Agreement.
+3. REQUIREMENTS
+
+A Contributor may choose to distribute the Program in object code form under its own
+license agreement, provided that:
+
+a) it complies with the terms and conditions of this Agreement; and
+b) its license agreement:
+i) effectively disclaims on behalf of all Contributors all warranties and conditions,
+express and implied, including warranties or conditions of title and non-infringement,
+and implied warranties or conditions of merchantability and fitness for a particular
+purpose;
+ii) effectively excludes on behalf of all Contributors all liability for damages,
+including direct, indirect, special, incidental and consequential damages, such as
+lost profits;
+iii) states that any provisions which differ from this Agreement are offered by that
+Contributor alone and not by any other party; and
+iv) states that source code for the Program is available from such Contributor, and
+informs licensees how to obtain it in a reasonable manner on or through a medium
+customarily used for software exchange.
+When the Program is made available in source code form:
+
+a) it must be made available under this Agreement; and
+b) a copy of this Agreement must be included with each copy of the Program.
+Contributors may not remove or alter any copyright notices contained within the
+Program.
+
+Each Contributor must identify itself as the originator of its Contribution, if any,
+in a manner that reasonably allows subsequent Recipients to identify the originator of
+the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities with respect
+to end users, business partners and the like. While this license is intended to
+facilitate the commercial use of the Program, the Contributor who includes the Program
+in a commercial product offering should do so in a manner which does not create
+potential liability for other Contributors. Therefore, if a Contributor includes the
+Program in a commercial product offering, such Contributor ("Commercial Contributor")
+hereby agrees to defend and indemnify every other Contributor ("Indemnified
+Contributor") against any losses, damages and costs (collectively "Losses") arising
+from claims, lawsuits and other legal actions brought by a third party against the
+Indemnified Contributor to the extent caused by the acts or omissions of such
+Commercial Contributor in connection with its distribution of the Program in a
+commercial product offering. The obligations in this section do not apply to any
+claims or Losses relating to any actual or alleged intellectual property infringement.
+In order to qualify, an Indemnified Contributor must: a) promptly notify the
+Commercial Contributor in writing of such claim, and b) allow the Commercial
+Contributor to control, and cooperate with the Commercial Contributor in, the defense
+and any related settlement negotiations. The Indemnified Contributor may participate
+in any such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial product offering,
+Product X. That Contributor is then a Commercial Contributor. If that Commercial
+Contributor then makes performance claims, or offers warranties related to Product X,
+those performance claims and warranties are such Commercial Contributor`s
+responsibility alone. Under this section, the Commercial Contributor would have to
+defend claims against the other Contributors related to those performance claims and
+warranties, and if a court requires any other Contributor to pay any damages as a
+result, the Commercial Contributor must pay those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS"
+BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED
+INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
+NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient
+is solely responsible for determining the appropriateness of using and distributing
+the Program and assumes all risks associated with its exercise of rights under this
+Agreement , including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs or equipment, and
+unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
+CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS),
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR
+DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under applicable law,
+it shall not affect the validity or enforceability of the remainder of the terms of
+this Agreement, and without further action by the parties hereto, such provision shall
+be reformed to the minimum extent necessary to make such provision valid and
+enforceable.
+
+If Recipient institutes patent litigation against any entity (including a cross-claim
+or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations
+of the Program with other software or hardware) infringes such Recipient`s patent(s),
+then such Recipient`s rights granted under Section 2(b) shall terminate as of the date
+such litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it fails to comply with
+any of the material terms or conditions of this Agreement and does not cure such
+failure in a reasonable period of time after becoming aware of such noncompliance. If
+all Recipient`s rights under this Agreement terminate, Recipient agrees to cease use
+and distribution of the Program as soon as reasonably practicable. However,
+Recipient`s obligations under this Agreement and any licenses granted by Recipient
+relating to the Program shall continue and survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement, but in order to
+avoid inconsistency the Agreement is copyrighted and may only be modified in the
+following manner. The Agreement Steward reserves the right to publish new versions
+(including revisions) of this Agreement from time to time. No one other than the
+Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is
+the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to
+serve as the Agreement Steward to a suitable separate entity. Each new version of the
+Agreement will be given a distinguishing version number. The Program (including
+Contributions) may always be distributed subject to the version of the Agreement under
+which it was received. In addition, after a new version of the Agreement is published,
+Contributor may elect to distribute the Program (including its Contributions) under
+the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
+receives no rights or licenses to the intellectual property of any Contributor under
+this Agreement, whether expressly, by implication, estoppel or otherwise. All rights
+in the Program not expressly granted under this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and the intellectual
+property laws of the United States of America. No party to this Agreement will bring a
+legal action under this Agreement more than one year after the cause of action arose.
+Each party waives its rights to a jury trial in any resulting litigation.
+
+
+
+
+Elfutils-Exception
+
+ This file describes the limits of the Exception under which you are allowed
+ to distribute Non-GPL Code in linked combination with Red Hat elfutils.
+ For the full text of the license, please see one of the header files
+ included with the source distribution or the file COPYING found in the
+ top level directory of the source.
+
+ The Approved Interfaces are the functions declared in the files:
+
+ libelf.h
+ libdw.h
+ libdwfl.h
+
+
+
+
+FSF-Unlimited
+
+Copyright (C) 1997-2010 Free Software Foundation, Inc.
+This file is free software; the Free Software Foundation
+gives unlimited permission to copy and/or distribute it,
+with or without modifications, as long as this notice is preserved.
+
+
+
+FreeType
+
+ The FreeType Project LICENSE
+ ----------------------------
+
+ 2006-Jan-27
+
+ Copyright 1996-2002, 2006 by
+ David Turner, Robert Wilhelm, and Werner Lemberg
+
+
+
+Introduction
+============
+
+ The FreeType Project is distributed in several archive packages;
+ some of them may contain, in addition to the FreeType font engine,
+ various tools and contributions which rely on, or relate to, the
+ FreeType Project.
+
+ This license applies to all files found in such packages, and
+ which do not fall under their own explicit license. The license
+ affects thus the FreeType font engine, the test programs,
+ documentation and makefiles, at the very least.
+
+ This license was inspired by the BSD, Artistic, and IJG
+ (Independent JPEG Group) licenses, which all encourage inclusion
+ and use of free software in commercial and freeware products
+ alike. As a consequence, its main points are that:
+
+ o We don't promise that this software works. However, we will be
+ interested in any kind of bug reports. (`as is' distribution)
+
+ o You can use this software for whatever you want, in parts or
+ full form, without having to pay us. (`royalty-free' usage)
+
+ o You may not pretend that you wrote this software. If you use
+ it, or only parts of it, in a program, you must acknowledge
+ somewhere in your documentation that you have used the
+ FreeType code. (`credits')
+
+ We specifically permit and encourage the inclusion of this
+ software, with or without modifications, in commercial products.
+ We disclaim all warranties covering The FreeType Project and
+ assume no liability related to The FreeType Project.
+
+
+ Finally, many people asked us for a preferred form for a
+ credit/disclaimer to use in compliance with this license. We thus
+ encourage you to use the following text:
+
+ """
+ Portions of this software are copyright � <year> The FreeType
+ Project (www.freetype.org). All rights reserved.
+ """
+
+ Please replace <year> with the value from the FreeType version you
+ actually use.
+
+
+Legal Terms
+===========
+
+0. Definitions
+--------------
+
+ Throughout this license, the terms `package', `FreeType Project',
+ and `FreeType archive' refer to the set of files originally
+ distributed by the authors (David Turner, Robert Wilhelm, and
+ Werner Lemberg) as the `FreeType Project', be they named as alpha,
+ beta or final release.
+
+ `You' refers to the licensee, or person using the project, where
+ `using' is a generic term including compiling the project's source
+ code as well as linking it to form a `program' or `executable'.
+ This program is referred to as `a program using the FreeType
+ engine'.
+
+ This license applies to all files distributed in the original
+ FreeType Project, including all source code, binaries and
+ documentation, unless otherwise stated in the file in its
+ original, unmodified form as distributed in the original archive.
+ If you are unsure whether or not a particular file is covered by
+ this license, you must contact us to verify this.
+
+ The FreeType Project is copyright (C) 1996-2000 by David Turner,
+ Robert Wilhelm, and Werner Lemberg. All rights reserved except as
+ specified below.
+
+1. No Warranty
+--------------
+
+ THE FREETYPE PROJECT IS PROVIDED `AS IS' WITHOUT WARRANTY OF ANY
+ KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+ WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE. IN NO EVENT WILL ANY OF THE AUTHORS OR COPYRIGHT HOLDERS
+ BE LIABLE FOR ANY DAMAGES CAUSED BY THE USE OR THE INABILITY TO
+ USE, OF THE FREETYPE PROJECT.
+
+2. Redistribution
+-----------------
+
+ This license grants a worldwide, royalty-free, perpetual and
+ irrevocable right and license to use, execute, perform, compile,
+ display, copy, create derivative works of, distribute and
+ sublicense the FreeType Project (in both source and object code
+ forms) and derivative works thereof for any purpose; and to
+ authorize others to exercise some or all of the rights granted
+ herein, subject to the following conditions:
+
+ o Redistribution of source code must retain this license file
+ (`FTL.TXT') unaltered; any additions, deletions or changes to
+ the original files must be clearly indicated in accompanying
+ documentation. The copyright notices of the unaltered,
+ original files must be preserved in all copies of source
+ files.
+
+ o Redistribution in binary form must provide a disclaimer that
+ states that the software is based in part of the work of the
+ FreeType Team, in the distribution documentation. We also
+ encourage you to put an URL to the FreeType web page in your
+ documentation, though this isn't mandatory.
+
+ These conditions apply to any software derived from or based on
+ the FreeType Project, not just the unmodified files. If you use
+ our work, you must acknowledge us. However, no fee need be paid
+ to us.
+
+3. Advertising
+--------------
+
+ Neither the FreeType authors and contributors nor you shall use
+ the name of the other for commercial, advertising, or promotional
+ purposes without specific prior written permission.
+
+ We suggest, but do not require, that you use one or more of the
+ following phrases to refer to this software in your documentation
+ or advertising materials: `FreeType Project', `FreeType Engine',
+ `FreeType library', or `FreeType Distribution'.
+
+ As you have not signed this license, you are not required to
+ accept it. However, as the FreeType Project is copyrighted
+ material, only this license, or another one contracted with the
+ authors, grants you the right to use, distribute, and modify it.
+ Therefore, by using, distributing, or modifying the FreeType
+ Project, you indicate that you understand and accept all the terms
+ of this license.
+
+4. Contacts
+-----------
+
+ There are two mailing lists related to FreeType:
+
+ o freetype@nongnu.org
+
+ Discusses general use and applications of FreeType, as well as
+ future and wanted additions to the library and distribution.
+ If you are looking for support, start in this list if you
+ haven't found anything to help you in the documentation.
+
+ o freetype-devel@nongnu.org
+
+ Discusses bugs, as well as engine internals, design issues,
+ specific licenses, porting, etc.
+
+ Our home page can be found at
+
+ http://www.freetype.org
+
+
+--- end of FTL.TXT ---
+
+
+
+
+GPL-1.0
+
+
+GNU General Public License, version 1
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 1, February 1989
+
+ Copyright (C) 1989 Free Software Foundation, Inc.
+ 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The license agreements of most software companies try to keep users
+at the mercy of those companies. By contrast, our General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. The
+General Public License applies to the Free Software Foundation`s
+software and to any other program whose authors commit to using it.
+You can use it for your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Specifically, the General Public License is designed to make
+sure that you have the freedom to give away or sell copies of free
+software, that you receive source code or can get it if you want it,
+that you can change the software or use pieces of it in new free
+programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of a such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author`s protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors` reputations.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any program or other work which
+contains a notice placed by the copyright holder saying it may be
+distributed under the terms of this General Public License. The
+"Program", below, refers to any such program or work, and a "work based
+on the Program" means either the Program or any work containing the
+Program or a portion of it, either verbatim or with modifications. Each
+licensee is addressed as "you".
+
+ 1. You may copy and distribute verbatim copies of the Program`s source
+code as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice and
+disclaimer of warranty; keep intact all the notices that refer to this
+General Public License and to the absence of any warranty; and give any
+other recipients of the Program a copy of this General Public License
+along with the Program. You may charge a fee for the physical act of
+transferring a copy.
+
+ 2. You may modify your copy or copies of the Program or any portion of
+it, and copy and distribute such modifications under the terms of Paragraph
+1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating that
+ you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish, that
+ in whole or in part contains the Program or any part thereof, either
+ with or without modifications, to be licensed at no charge to all
+ third parties under the terms of this General Public License (except
+ that you may choose to grant warranty protection to some or all
+ third parties, at your option).
+
+ c) If the modified program normally reads commands interactively when
+ run, you must cause it, when started running for such interactive use
+ in the simplest and most usual way, to print or display an
+ announcement including an appropriate copyright notice and a notice
+ that there is no warranty (or else, saying that you provide a
+ warranty) and that users may redistribute the program under these
+ conditions, and telling the user how to view a copy of this General
+ Public License.
+
+ d) You may charge a fee for the physical act of transferring a
+ copy, and you may at your option offer warranty protection in
+ exchange for a fee.
+
+Mere aggregation of another independent work with the Program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other work under the scope of these terms.
+
+ 3. You may copy and distribute the Program (or a portion or derivative of
+it, under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+ a) accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal charge
+ for the cost of distribution) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+Source code for a work means the preferred form of the work for making
+modifications to it. For an executable file, complete source code means
+all the source code for all modules it contains; but, as a special
+exception, it need not include source code for modules which are standard
+libraries that accompany the operating system on which the executable
+file runs, or for standard header files or definitions files that
+accompany that operating system.
+
+ 4. You may not copy, modify, sublicense, distribute or transfer the
+Program except as expressly provided under this General Public License.
+Any attempt otherwise to copy, modify, sublicense, distribute or transfer
+the Program is void, and will automatically terminate your rights to use
+the Program under this License. However, parties who have received
+copies, or rights to use copies, from you under this General Public
+License will not have their licenses terminated so long as such parties
+remain in full compliance.
+
+ 5. By copying, distributing or modifying the Program (or any work based
+on the Program) you indicate your acceptance of this license to do so,
+and all its terms and conditions.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the original
+licensor to copy, distribute or modify the Program subject to these
+terms and conditions. You may not impose any further restrictions on the
+recipients` exercise of the rights granted herein.
+
+ 7. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of the license which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+the license, you may choose any version ever published by the Free Software
+Foundation.
+
+ 8. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ 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
+the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program`s name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 1, or (at your option)
+ any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19xx name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w`.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c` for details.
+
+The hypothetical commands `show w` and `show c` should show the
+appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than `show w` and `show
+c`; they could even be mouse-clicks or menu items--whatever suits your
+program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ program `Gnomovision` (a program to direct compilers to make passes
+ at assemblers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+That`s all there is to it!
+
+
+
+
+GPL-2.0
+
+
+GNU GENERAL PUBLIC LICENSE
+
+Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public License is intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users. This General Public License applies to most of the Free Software
+Foundation`s software and to any other program whose authors commit to using it. (Some
+other Free Software Foundation software is covered by the GNU Lesser General Public
+License instead.) You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for this service if you wish), that you receive
+source code or can get it if you want it, that you can change the software or use
+pieces of it in new free programs; and that you know you can do these things.
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you
+these rights or to ask you to surrender the rights. These restrictions translate to
+certain responsibilities for you if you distribute copies of the software, or if you
+modify it.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee,
+you must give the recipients all the rights that you have. You must make sure that
+they, too, receive or can get the source code. And you must show them these terms so
+they know their rights.
+
+We protect your rights with two steps: (1) copyright the software, and (2) offer you
+this license which gives you legal permission to copy, distribute and/or modify the
+software.
+
+Also, for each author`s protection and ours, we want to make certain that everyone
+understands that there is no warranty for this free software. If the software is
+modified by someone else and passed on, we want its recipients to know that what they
+have is not the original, so that any problems introduced by others will not reflect
+on the original authors` reputations.
+
+Finally, any free program is threatened constantly by software patents. We wish to
+avoid the danger that redistributors of a free program will individually obtain patent
+licenses, in effect making the program proprietary. To prevent this, we have made it
+clear that any patent must be licensed for everyone`s free use or not licensed at all.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License applies to any program or other work which contains a notice placed by
+the copyright holder saying it may be distributed under the terms of this General
+Public License. The "Program", below, refers to any such program or work, and a "work
+based on the Program" means either the Program or any derivative work under copyright
+law: that is to say, a work containing the Program or a portion of it, either verbatim
+or with modifications and/or translated into another language. (Hereinafter,
+translation is included without limitation in the term "modification".) Each licensee
+is addressed as "you".
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running the Program is not restricted,
+and the output from the Program is covered only if its contents constitute a work
+based on the Program (independent of having been made by running the Program). Whether
+that is true depends on what the Program does.
+
+1. You may copy and distribute verbatim copies of the Program`s source code as you
+receive it, in any medium, provided that you conspicuously and appropriately publish
+on each copy an appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any warranty; and
+give any other recipients of the Program a copy of this License along with the
+Program.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Program or any portion of it, thus
+forming a work based on the Program, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+a) You must cause the modified files to carry prominent notices stating that you
+changed the files and the date of any change.
+b) You must cause any work that you distribute or publish, that in whole or in part
+contains or is derived from the Program or any part thereof, to be licensed as a whole
+at no charge to all third parties under the terms of this License.
+c) If the modified program normally reads commands interactively when run, you must
+cause it, when started running for such interactive use in the most ordinary way, to
+print or display an announcement including an appropriate copyright notice and a
+notice that there is no warranty (or else, saying that you provide a warranty) and
+that users may redistribute the program under these conditions, and telling the user
+how to view a copy of this License. (Exception: if the Program itself is interactive
+but does not normally print such an announcement, your work based on the Program is
+not required to print an announcement.)
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Program, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Program,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program with the
+Program (or with a work based on the Program) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+3. You may copy and distribute the Program (or a work based on it, under Section 2) in
+object code or executable form under the terms of Sections 1 and 2 above provided that
+you also do one of the following:
+
+a) Accompany it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a medium customarily
+used for software interchange; or,
+b) Accompany it with a written offer, valid for at least three years, to give any
+third party, for a charge no more than your cost of physically performing source
+distribution, a complete machine-readable copy of the corresponding source code, to be
+distributed under the terms of Sections 1 and 2 above on a medium customarily used for
+software interchange; or,
+c) Accompany it with the information you received as to the offer to distribute
+corresponding source code. (This alternative is allowed only for noncommercial
+distribution and only if you received the program in object code or executable form
+with such an offer, in accord with Subsection b above.)
+The source code for a work means the preferred form of the work for making
+modifications to it. For an executable work, complete source code means all the source
+code for all modules it contains, plus any associated interface definition files, plus
+the scripts used to control compilation and installation of the executable. However,
+as a special exception, the source code distributed need not include anything that is
+normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+If distribution of executable or object code is made by offering access to copy from a
+designated place, then offering equivalent access to copy the source code from the
+same place counts as distribution of the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+4. You may not copy, modify, sublicense, or distribute the Program except as expressly
+provided under this License. Any attempt otherwise to copy, modify, sublicense or
+distribute the Program is void, and will automatically terminate your rights under
+this License. However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such parties remain in
+full compliance.
+
+5. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Program or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Program or works based on it.
+
+6. Each time you redistribute the Program (or any work based on the Program), the
+recipient automatically receives a license from the original licensor to copy,
+distribute or modify the Program subject to these terms and conditions. You may not
+impose any further restrictions on the recipients` exercise of the rights granted
+herein. You are not responsible for enforcing compliance by third parties to this
+License.
+
+7. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Program at all. For example, if a patent license would not permit royalty-free
+redistribution of the Program by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply and the section as a
+whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system,
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+8. If the distribution and/or use of the Program is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Program under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+9. The Free Software Foundation may publish revised and/or new versions of the General
+Public License from time to time. Such new versions will be similar in spirit to the
+present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Program does not
+specify a version number of this License, you may choose any version ever published by
+the Free Software Foundation.
+
+10. If you wish to incorporate parts of the Program into other free programs whose
+distribution conditions are different, write to the author to ask for permission. For
+software which is copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our decision will be
+guided by the two goals of preserving the free status of all derivatives of our free
+software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
+WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+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 the "copyright" line and a pointer to where the
+full notice is found.
+
+one line to give the program`s name and an idea of what it does.
+Copyright (C) yyyy name of author
+
+This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License
+as published by the Free Software Foundation; either version 2
+of the License, or (at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this when it starts
+in an interactive mode:
+
+Gnomovision version 69, Copyright (C) year name of author
+Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
+type `show w`. This is free software, and you are welcome
+to redistribute it under certain conditions; type `show c`
+for details.
+The hypothetical commands `show w` and `show c` should show the appropriate parts of
+the General Public License. Of course, the commands you use may be called something
+other than `show w` and `show c`; they could even be mouse-clicks or menu
+items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample;
+alter the names:
+
+Yoyodyne, Inc., hereby disclaims all copyright
+interest in the program `Gnomovision`
+(which makes passes at compilers) written
+by James Hacker.
+
+signature of Ty Coon, 1 April 1989
+Ty Coon, President of Vice
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may consider it
+more useful to permit linking proprietary applications with the library. If this is
+what you want to do, use the GNU Lesser General Public License instead of this
+License.
+
+
+
+
+GPL-2.0-with-GCC-exception
+
+
+insert GPL v2 text here
+
+GCC Linking Exception
+In addition to the permissions in the GNU General Public License, the Free
+Software Foundation gives you unlimited permission to link the compiled version
+of this file into combinations with other programs, and to distribute those
+combinations without any restriction coming from the use of this file. (The
+General Public License restrictions do apply in other respects; for example,
+they cover modification of the file, and distribution when not linked into a
+combine executable.)
+
+
+
+
+
+
+
+
+
+GPL-2.0-with-classpath-exception
+
+
+insert GPL v2 license text here
+
+Linking this library statically or dynamically with other modules is making a combined
+work based on this library. Thus, the terms and conditions of the GNU General Public
+License cover the whole combination.
+
+As a special exception, the copyright holders of this library give you permission to
+link this library with independent modules to produce an executable, regardless of the
+license terms of these independent modules, and to copy and distribute the resulting
+executable under terms of your choice, provided that you also meet, for each linked
+independent module, the terms and conditions of the license of that module. An
+independent module is a module which is not derived from or based on this library. If
+you modify this library, you may extend this exception to your version of the library,
+but you are not obligated to do so. If you do not wish to do so, delete this exception
+statement from your version.
+
+
+
+
+GPL-3.0
+
+GNU GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+Preamble
+
+The GNU General Public License is a free, copyleft license for software and other
+kinds of works.
+
+The licenses for most software and other practical works are designed to take away
+your freedom to share and change the works. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change all versions of a
+program--to make sure it remains free software for all its users. We, the Free
+Software Foundation, use the GNU General Public License for most of our software; it
+applies also to any other work released this way by its authors. You can apply it to
+your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for them if you wish), that you receive source
+code or can get it if you want it, that you can change the software or use pieces of
+it in new free programs, and that you know you can do these things.
+
+To protect your rights, we need to prevent others from denying you these rights or
+asking you to surrender the rights. Therefore, you have certain responsibilities if
+you distribute copies of the software, or if you modify it: responsibilities to
+respect the freedom of others.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee,
+you must pass on to the recipients the same freedoms that you received. You must make
+sure that they, too, receive or can get the source code. And you must show them these
+terms so they know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps: (1) assert
+copyright on the software, and (2) offer you this License giving you legal permission
+to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains that there is no
+warranty for this free software. For both users' and authors' sake, the GPL requires
+that modified versions be marked as changed, so that their problems will not be
+attributed erroneously to authors of previous versions.
+
+Some devices are designed to deny users access to install or run modified versions of
+the software inside them, although the manufacturer can do so. This is fundamentally
+incompatible with the aim of protecting users' freedom to change the software. The
+systematic pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we have designed
+this version of the GPL to prohibit the practice for those products. If such problems
+arise substantially in other domains, we stand ready to extend this provision to those
+domains in future versions of the GPL, as needed to protect the freedom of users.
+
+Finally, every program is threatened constantly by software patents. States should not
+allow patents to restrict development and use of software on general-purpose
+computers, but in those that do, we wish to avoid the special danger that patents
+applied to a free program could make it effectively proprietary. To prevent this, the
+GPL assures that patents cannot be used to render the program non-free.
+
+The precise terms and conditions for copying, distribution and modification follow.
+TERMS AND CONDITIONS
+0. Definitions.
+
+”This License” refers to version 3 of the GNU General Public License.
+
+”Copyright” also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+”The Program” refers to any copyrightable work licensed under this
+License. Each licensee is addressed as ”you”. ”Licensees”
+and ”recipients” may be individuals or organizations.
+
+To ”modify” a work means to copy from or adapt all or part of the work in
+a fashion requiring copyright permission, other than the making of an exact copy. The
+resulting work is called a ”modified version” of the earlier work or a
+work ”based on” the earlier work.
+
+A ”covered work” means either the unmodified Program or a work based on
+the Program.
+
+To ”propagate” a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for infringement under
+applicable copyright law, except executing it on a computer or modifying a private
+copy. Propagation includes copying, distribution (with or without modification),
+making available to the public, and in some countries other activities as well.
+
+To ”convey” a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through a computer
+network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays ”Appropriate Legal Notices” to the
+extent that it includes a convenient and prominently visible feature that (1) displays
+an appropriate copyright notice, and (2) tells the user that there is no warranty for
+the work (except to the extent that warranties are provided), that licensees may
+convey the work under this License, and how to view a copy of this License. If the
+interface presents a list of user commands or options, such as a menu, a prominent
+item in the list meets this criterion.
+1. Source Code.
+
+The ”source code” for a work means the preferred form of the work for
+making modifications to it. ”Object code” means any non-source form of a
+work.
+
+A ”Standard Interface” means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of interfaces
+specified for a particular programming language, one that is widely used among
+developers working in that language.
+
+The ”System Libraries” of an executable work include anything, other than
+the work as a whole, that (a) is included in the normal form of packaging a Major
+Component, but which is not part of that Major Component, and (b) serves only to
+enable use of the work with that Major Component, or to implement a Standard Interface
+for which an implementation is available to the public in source code form. A
+”Major Component”, in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system (if any) on which
+the executable work runs, or a compiler used to produce the work, or an object code
+interpreter used to run it.
+
+The ”Corresponding Source” for a work in object code form means all the
+source code needed to generate, install, and (for an executable work) run the object
+code and to modify the work, including scripts to control those activities. However,
+it does not include the work's System Libraries, or general-purpose tools or generally
+available free programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source includes interface
+definition files associated with source files for the work, and the source code for
+shared libraries and dynamically linked subprograms that the work is specifically
+designed to require, such as by intimate data communication or control flow between
+those subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate
+automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+2. Basic Permissions.
+
+All rights granted under this License are granted for the term of copyright on the
+Program, and are irrevocable provided the stated conditions are met. This License
+explicitly affirms your unlimited permission to run the unmodified Program. The output
+from running a covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your rights of fair use
+or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without
+conditions so long as your license otherwise remains in force. You may convey covered
+works to others for the sole purpose of having them make modifications exclusively for
+you, or provide you with facilities for running those works, provided that you comply
+with the terms of this License in conveying all material for which you do not control
+copyright. Those thus making or running the covered works for you must do so
+exclusively on your behalf, under your direction and control, on terms that prohibit
+them from making any copies of your copyrighted material outside their relationship
+with you.
+
+Conveying under any other circumstances is permitted solely under the conditions
+stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological measure under any
+applicable law fulfilling obligations under article 11 of the WIPO copyright treaty
+adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention
+of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of
+technological measures to the extent such circumvention is effected by exercising
+rights under this License with respect to the covered work, and you disclaim any
+intention to limit operation or modification of the work as a means of enforcing,
+against the work's users, your or third parties' legal rights to forbid circumvention
+of technological measures.
+4. Conveying Verbatim Copies.
+
+You may convey verbatim copies of the Program's source code as you receive it, in any
+medium, provided that you conspicuously and appropriately publish on each copy an
+appropriate copyright notice; keep intact all notices stating that this License and
+any non-permissive terms added in accord with section 7 apply to the code; keep intact
+all notices of the absence of any warranty; and give all recipients a copy of this
+License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer
+support or warranty protection for a fee.
+5. Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to produce it from
+the Program, in the form of source code under the terms of section 4, provided that
+you also meet all of these conditions:
+
+ * a) The work must carry prominent notices stating that you modified it, and
+giving a relevant date.
+ * b) The work must carry prominent notices stating that it is released under this
+License and any conditions added under section 7. This requirement modifies the
+requirement in section 4 to ”keep intact all notices”.
+ * c) You must license the entire work, as a whole, under this License to anyone
+who comes into possession of a copy. This License will therefore apply, along with any
+applicable section 7 additional terms, to the whole of the work, and all its parts,
+regardless of how they are packaged. This License gives no permission to license the
+work in any other way, but it does not invalidate such permission if you have
+separately received it.
+ * d) If the work has interactive user interfaces, each must display Appropriate
+Legal Notices; however, if the Program has interactive interfaces that do not display
+Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are
+not by their nature extensions of the covered work, and which are not combined with it
+such as to form a larger program, in or on a volume of a storage or distribution
+medium, is called an ”aggregate” if the compilation and its resulting
+copyright are not used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work in an aggregate
+does not cause this License to apply to the other parts of the aggregate.
+6. Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms of sections 4 and 5,
+provided that you also convey the machine-readable Corresponding Source under the
+terms of this License, in one of these ways:
+
+ * a) Convey the object code in, or embodied in, a physical product (including a
+physical distribution medium), accompanied by the Corresponding Source fixed on a
+durable physical medium customarily used for software interchange.
+ * b) Convey the object code in, or embodied in, a physical product (including a
+physical distribution medium), accompanied by a written offer, valid for at least
+three years and valid for as long as you offer spare parts or customer support for
+that product model, to give anyone who possesses the object code either (1) a copy of
+the Corresponding Source for all the software in the product that is covered by this
+License, on a durable physical medium customarily used for software interchange, for a
+price no more than your reasonable cost of physically performing this conveying of
+source, or (2) access to copy the Corresponding Source from a network server at no
+charge.
+ * c) Convey individual copies of the object code with a copy of the written offer
+to provide the Corresponding Source. This alternative is allowed only occasionally and
+noncommercially, and only if you received the object code with such an offer, in
+accord with subsection 6b.
+ * d) Convey the object code by offering access from a designated place (gratis or
+for a charge), and offer equivalent access to the Corresponding Source in the same way
+through the same place at no further charge. You need not require recipients to copy
+the Corresponding Source along with the object code. If the place to copy the object
+code is a network server, the Corresponding Source may be on a different server
+(operated by you or a third party) that supports equivalent copying facilities,
+provided you maintain clear directions next to the object code saying where to find
+the Corresponding Source. Regardless of what server hosts the Corresponding Source,
+you remain obligated to ensure that it is available for as long as needed to satisfy
+these requirements.
+ * e) Convey the object code using peer-to-peer transmission, provided you inform
+other peers where the object code and Corresponding Source of the work are being
+offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the
+Corresponding Source as a System Library, need not be included in conveying the object
+code work.
+
+A ”User Product” is either (1) a ”consumer product”, which
+means any tangible personal property which is normally used for personal, family, or
+household purposes, or (2) anything designed or sold for incorporation into a
+dwelling. In determining whether a product is a consumer product, doubtful cases shall
+be resolved in favor of coverage. For a particular product received by a particular
+user, ”normally used” refers to a typical or common use of that class of
+product, regardless of the status of the particular user or of the way in which the
+particular user actually uses, or expects or is expected to use, the product. A
+product is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent the only
+significant mode of use of the product.
+
+”Installation Information” for a User Product means any methods,
+procedures, authorization keys, or other information required to install and execute
+modified versions of a covered work in that User Product from a modified version of
+its Corresponding Source. The information must suffice to ensure that the continued
+functioning of the modified object code is in no case prevented or interfered with
+solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for
+use in, a User Product, and the conveying occurs as part of a transaction in which the
+right of possession and use of the User Product is transferred to the recipient in
+perpetuity or for a fixed term (regardless of how the transaction is characterized),
+the Corresponding Source conveyed under this section must be accompanied by the
+Installation Information. But this requirement does not apply if neither you nor any
+third party retains the ability to install modified object code on the User Product
+(for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to
+continue to provide support service, warranty, or updates for a work that has been
+modified or installed by the recipient, or for the User Product in which it has been
+modified or installed. Access to a network may be denied when the modification itself
+materially and adversely affects the operation of the network or violates the rules
+and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with
+this section must be in a format that is publicly documented (and with an
+implementation available to the public in source code form), and must require no
+special password or key for unpacking, reading or copying.
+7. Additional Terms.
+
+”Additional permissions” are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions. Additional
+permissions that are applicable to the entire Program shall be treated as though they
+were included in this License, to the extent that they are valid under applicable law.
+If additional permissions apply only to part of the Program, that part may be used
+separately under those permissions, but the entire Program remains governed by this
+License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional
+permissions from that copy, or from any part of it. (Additional permissions may be
+written to require their own removal in certain cases when you modify the work.) You
+may place additional permissions on material, added by you to a covered work, for
+which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered
+work, you may (if authorized by the copyright holders of that material) supplement the
+terms of this License with terms:
+
+ * a) Disclaiming warranty or limiting liability differently from the terms of
+sections 15 and 16 of this License; or
+ * b) Requiring preservation of specified reasonable legal notices or author
+attributions in that material or in the Appropriate Legal Notices displayed by works
+containing it; or
+ * c) Prohibiting misrepresentation of the origin of that material, or requiring
+that modified versions of such material be marked in reasonable ways as different from
+the original version; or
+ * d) Limiting the use for publicity purposes of names of licensors or authors of
+the material; or
+ * e) Declining to grant rights under trademark law for use of some trade names,
+trademarks, or service marks; or
+ * f) Requiring indemnification of licensors and authors of that material by anyone
+who conveys the material (or modified versions of it) with contractual assumptions of
+liability to the recipient, for any liability that these contractual assumptions
+directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered ”further
+restrictions” within the meaning of section 10. If the Program as you received
+it, or any part of it, contains a notice stating that it is governed by this License
+along with a term that is a further restriction, you may remove that term. If a
+license document contains a further restriction but permits relicensing or conveying
+under this License, you may add to a covered work material governed by the terms of
+that license document, provided that the further restriction does not survive such
+relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the
+relevant source files, a statement of the additional terms that apply to those files,
+or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a
+separately written license, or stated as exceptions; the above requirements apply
+either way.
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this
+License. Any attempt otherwise to propagate or modify it is void, and will
+automatically terminate your rights under this License (including any patent licenses
+granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a
+particular copyright holder is reinstated (a) provisionally, unless and until the
+copyright holder explicitly and finally terminates your license, and (b) permanently,
+if the copyright holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if
+the copyright holder notifies you of the violation by some reasonable means, this is
+the first time you have received notice of violation of this License (for any work)
+from that copyright holder, and you cure the violation prior to 30 days after your
+receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of
+parties who have received copies or rights from you under this License. If your rights
+have been terminated and not permanently reinstated, you do not qualify to receive new
+licenses for the same material under section 10.
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the
+Program. Ancillary propagation of a covered work occurring solely as a consequence of
+using peer-to-peer transmission to receive a copy likewise does not require
+acceptance. However, nothing other than this License grants you permission to
+propagate or modify any covered work. These actions infringe copyright if you do not
+accept this License. Therefore, by modifying or propagating a covered work, you
+indicate your acceptance of this License to do so.
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license
+from the original licensors, to run, modify and propagate that work, subject to this
+License. You are not responsible for enforcing compliance by third parties with this
+License.
+
+An ”entity transaction” is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an organization, or
+merging organizations. If propagation of a covered work results from an entity
+transaction, each party to that transaction who receives a copy of the work also
+receives whatever licenses to the work the party's predecessor in interest had or
+could give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if the predecessor
+has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or
+affirmed under this License. For example, you may not impose a license fee, royalty,
+or other charge for exercise of rights granted under this License, and you may not
+initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging
+that any patent claim is infringed by making, using, selling, offering for sale, or
+importing the Program or any portion of it.
+11. Patents.
+
+A ”contributor” is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The work thus licensed
+is called the contributor's ”contributor version”.
+
+A contributor's ”essential patent claims” are all patent claims owned or
+controlled by the contributor, whether already acquired or hereafter acquired, that
+would be infringed by some manner, permitted by this License, of making, using, or
+selling its contributor version, but do not include claims that would be infringed
+only as a consequence of further modification of the contributor version. For purposes
+of this definition, ”control” includes the right to grant patent
+sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license
+under the contributor's essential patent claims, to make, use, sell, offer for sale,
+import and otherwise run, modify and propagate the contents of its contributor
+version.
+
+In the following three paragraphs, a ”patent license” is any express
+agreement or commitment, however denominated, not to enforce a patent (such as an
+express permission to practice a patent or covenant not to sue for patent
+infringement). To ”grant” such a patent license to a party means to make
+such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the
+Corresponding Source of the work is not available for anyone to copy, free of charge
+and under the terms of this License, through a publicly available network server or
+other readily accessible means, then you must either (1) cause the Corresponding
+Source to be so available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner consistent with
+the requirements of this License, to extend the patent license to downstream
+recipients. ”Knowingly relying” means you have actual knowledge that, but
+for the patent license, your conveying the covered work in a country, or your
+recipient's use of the covered work in a country, would infringe one or more
+identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey,
+or propagate by procuring conveyance of, a covered work, and grant a patent license to
+some of the parties receiving the covered work authorizing them to use, propagate,
+modify or convey a specific copy of the covered work, then the patent license you
+grant is automatically extended to all recipients of the covered work and works based
+on it.
+
+A patent license is ”discriminatory” if it does not include within the
+scope of its coverage, prohibits the exercise of, or is conditioned on the
+non-exercise of one or more of the rights that are specifically granted under this
+License. You may not convey a covered work if you are a party to an arrangement with a
+third party that is in the business of distributing software, under which you make
+payment to the third party based on the extent of your activity of conveying the work,
+and under which the third party grants, to any of the parties who would receive the
+covered work from you, a discriminatory patent license (a) in connection with copies
+of the covered work conveyed by you (or copies made from those copies), or (b)
+primarily for and in connection with specific products or compilations that contain
+the covered work, unless you entered into that arrangement, or that patent license was
+granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied
+license or other defenses to infringement that may otherwise be available to you under
+applicable patent law.
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that
+contradict the conditions of this License, they do not excuse you from the conditions
+of this License. If you cannot convey a covered work so as to satisfy simultaneously
+your obligations under this License and any other pertinent obligations, then as a
+consequence you may not convey it at all. For example, if you agree to terms that
+obligate you to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this License would be
+to refrain entirely from conveying the Program.
+13. Use with the GNU Affero General Public License.
+
+Notwithstanding any other provision of this License, you have permission to link or
+combine any covered work with a work licensed under version 3 of the GNU Affero
+General Public License into a single combined work, and to convey the resulting work.
+The terms of this License will continue to apply to the part which is the covered
+work, but the special requirements of the GNU Affero General Public License, section
+13, concerning interaction through a network will apply to the combination as such.
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies that a
+certain numbered version of the GNU General Public License ”or any later
+version” applies to it, you have the option of following the terms and
+conditions either of that numbered version or of any later version published by the
+Free Software Foundation. If the Program does not specify a version number of the GNU
+General Public License, you may choose any version ever published by the Free Software
+Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU
+General Public License can be used, that proxy's public statement of acceptance of a
+version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions. However, no
+additional obligations are imposed on any author or copyright holder as a result of
+your choosing to follow a later version.
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM ”AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
+EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
+DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
+WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be
+given local legal effect according to their terms, reviewing courts shall apply local
+law that most closely approximates an absolute waiver of all civil liability in
+connection with the Program, unless a warranty or assumption of liability accompanies
+a copy of the Program in return for a fee.
+
+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 the ”copyright” line and a pointer to
+where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program does terminal interaction, make it output a short notice like this when
+it starts in an interactive mode:
+
+ <program> Copyright (C) <year> <name of author>
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate parts of
+the General Public License. Of course, your program's commands might be different; for
+a GUI interface, you would use an ”about box”.
+
+You should also get your employer (if you work as a programmer) or school, if any, to
+sign a ”copyright disclaimer” for the program, if necessary. For more
+information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+The GNU General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may consider it
+more useful to permit linking proprietary applications with the library. If this is
+what you want to do, use the GNU Lesser General Public License instead of this
+License. But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
+
+
+
+GPL-3.0-with-GCC-exception
+
+
+insert GPL v3 text here
+
+GCC RUNTIME LIBRARY EXCEPTION
+Version 3.1, 31 March 2009
+
+General information:
+http://www.gnu.org/licenses/gcc-exception.html
+Copyright (C) 2009 Free Software Foundation, Inc. <http://fsf.org/>
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+This GCC Runtime Library Exception ("Exception") is an additional permission under
+section 7 of the GNU General Public License, version 3 ("GPLv3"). It applies to a
+given file (the "Runtime Library") that bears a notice placed by the copyright holder
+of the file stating that the file is governed by GPLv3 along with this Exception.
+When you use GCC to compile a program, GCC may combine portions of certain GCC header
+files and runtime libraries with the compiled program. The purpose of this Exception
+is to allow compilation of non-GPL (including proprietary) programs to use, in this
+way, the header files and runtime libraries covered by this Exception.
+
+0. Definitions.
+A file is an "Independent Module" if it either requires the Runtime Library for
+execution after a Compilation Process, or makes use of an interface provided by the
+Runtime Library, but is not otherwise based on the Runtime Library.
+"GCC" means a version of the GNU Compiler Collection, with or without modifications,
+governed by version 3 (or a specified later version) of the GNU General Public License
+(GPL) with the option of using any subsequent versions published by the FSF.
+"GPL-compatible Software" is software whose conditions of propagation, modification
+and use would permit combination with GCC in accord with the license of GCC.
+"Target Code" refers to output from any compiler for a real or virtual target
+processor architecture, in executable form or suitable for input to an assembler,
+loader, linker and/or execution phase. Notwithstanding that, Target Code does not
+include data in any format that is used as a compiler intermediate representation, or
+used for producing a compiler intermediate representation.
+The "Compilation Process" transforms code entirely represented in non-intermediate
+languages designed for human-written code, and/or in Java Virtual Machine byte code,
+into Target Code. Thus, for example, use of source code generators and preprocessors
+need not be considered part of the Compilation Process, since the Compilation Process
+can be understood as starting with the output of the generators or preprocessors.
+A Compilation Process is "Eligible" if it is done using GCC, alone or with other
+GPL-compatible software, or if it is done without using any work based on GCC. For
+example, using non-GPL-compatible Software to optimize any GCC intermediate
+representations would not qualify as an Eligible Compilation Process.
+
+1. Grant of Additional Permission.
+You have permission to propagate a work of Target Code formed by combining the Runtime
+Library with Independent Modules, even if such propagation would otherwise violate the
+terms of GPLv3, provided that all Target Code was generated by Eligible Compilation
+Processes. You may then convey such a combination under terms of your choice,
+consistent with the licensing of the Independent Modules.
+
+2. No Weakening of GCC Copyleft.
+The availability of this Exception does not imply any general presumption that
+third-party software is unaffected by the copyleft requirements of the license of GCC.
+
+
+
+
+GPL-3.0-with-autoconf-exception
+
+
+insert GPL v3 text here
+
+AUTOCONF CONFIGURE SCRIPT EXCEPTION
+
+Version 3.0, 18 August 2009
+
+Copyright © 2009 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+
+This Exception is an additional permission under section 7 of the GNU General Public
+License, version 3 ("GPLv3"). It applies to a given file that bears a notice placed by
+the copyright holder of the file stating that the file is governed by GPLv3 along with
+this Exception.
+
+The purpose of this Exception is to allow distribution of Autoconf`s typical output
+under terms of the recipient`s choice (including proprietary).
+
+0. Definitions.
+"Covered Code" is the source or object code of a version of Autoconf that is a covered
+work under this License.
+
+"Normally Copied Code" for a version of Autoconf means all parts of its Covered Code
+which that version can copy from its code (i.e., not from its input file) into its
+minimally verbose, non-debugging and non-tracing output.
+
+"Ineligible Code" is Covered Code that is not Normally Copied Code.
+
+1. Grant of Additional Permission.
+You have permission to propagate output of Autoconf, even if such propagation would
+otherwise violate the terms of GPLv3. However, if by modifying Autoconf you cause any
+Ineligible Code of the version you received to become Normally Copied Code of your
+modified version, then you void this Exception for the resulting covered work. If you
+convey that resulting covered work, you must remove this Exception in accordance with
+the second paragraph of Section 7 of GPLv3.
+
+2. No Weakening of Autoconf Copyleft.
+The availability of this Exception does not imply any general presumption that
+third-party software is unaffected by the copyleft requirements of the license of
+Autoconf.
+
+
+
+
+ICU
+
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright (c) 1995-2012 International Business Machines Corporation and others
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this
+software and associated documentation files (the "Software"), to deal in the Software
+without restriction, including without limitation the rights to use, copy, modify,
+merge, publish, distribute, and/or sell copies of the Software, and to permit persons
+to whom the Software is furnished to do so, provided that the above copyright
+notice(s) and this permission notice appear in all copies of the Software and that
+both the above copyright notice(s) and this permission notice appear in supporting
+documentation.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
+PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
+SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
+LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
+SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder shall not be used
+in advertising or otherwise to promote the sale, use or other dealings in this
+Software without prior written authorization of the copyright holder.
+
+All trademarks and registered trademarks mentioned herein are the property of their
+respective owners.
+
+
+
+IPL-1.0
+
+
+IBM Public License Version 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM
+PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
+OF THE PROGRAM CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+"Contribution" means:
+
+in the case of International Business Machines Corporation ("IBM"), the Original
+Program, and
+in the case of each Contributor,
+changes to the Program, and
+additions to the Program;
+where such changes and/or additions to the Program originate from and
+are distributed by that particular Contributor. A Contribution
+`originates` from a Contributor if it was added to the Program by
+such Contributor itself or anyone acting on such Contributor`s
+behalf. Contributions do not include additions to the Program which:
+(i) are separate modules of software distributed in conjunction with
+the Program under their own license agreement, and (ii) are not
+derivative works of the Program.
+
+"Contributor" means IBM and any other entity that distributes the Program.
+
+"Licensed Patents " mean patent claims licensable by a
+Contributor which are necessarily infringed by the use or sale of its
+Contribution alone or when combined with the Program.
+
+"Original Program" means the original version of the software
+accompanying this Agreement as released by IBM, including source
+code, object code and documentation, if any.
+
+"Program" means the Original Program and Contributions.
+
+"Recipient" means anyone who receives the Program under this
+Agreement, including all Contributors.
+
+2. GRANT OF RIGHTS
+Subject to the terms of this Agreement, each Contributor hereby
+grants Recipient a non-exclusive, worldwide, royalty-free copyright
+license to reproduce, prepare derivative works of, publicly display,
+publicly perform, distribute and sublicense the Contribution of such
+Contributor, if any, and such derivative works, in source code and
+object code form.
+Subject to the terms of this Agreement, each Contributor hereby
+grants Recipient a non-exclusive, worldwide, royalty-free patent
+license under Licensed Patents to make, use, sell, offer to sell,
+import and otherwise transfer the Contribution of such Contributor,
+if any, in source code and object code form. This patent license
+shall apply to the combination of the Contribution and the Program
+if, at the time the Contribution is added by the Contributor, such
+addition of the Contribution causes such combination to be covered by
+the Licensed Patents. The patent license shall not apply to any
+other combinations which include the Contribution. No hardware per
+se is licensed hereunder.
+
+Recipient understands that although each Contributor grants the
+licenses to its Contributions set forth herein, no assurances are
+provided by any Contributor that the Program does not infringe the
+patent or other intellectual property rights of any other entity.
+Each Contributor disclaims any liability to Recipient for claims
+brought by any other entity based on infringement of intellectual
+property rights or otherwise. As a condition to exercising the
+rights and licenses granted hereunder, each Recipient hereby assumes
+sole responsibility to secure any other intellectual property rights
+needed, if any. For example, if a third party patent license is
+required to allow Recipient to distribute the Program, it is
+Recipient`s responsibility to acquire that license before
+distributing the Program.
+Each Contributor represents that to its knowledge it has
+sufficient copyright rights in its Contribution, if any, to grant the
+copyright license set forth in this Agreement.
+3. REQUIREMENTS
+A Contributor may choose to distribute
+the Program in object code form under its own license agreement,
+provided that:
+
+it complies with the terms and conditions of this Agreement; and
+its license agreement:
+effectively disclaims on behalf of all Contributors all warranties
+and conditions, express and implied, including warranties or
+conditions of title and non-infringement, and implied warranties or
+conditions of merchantability and fitness for a particular purpose;
+effectively excludes on behalf of all Contributors all liability
+for damages, including direct, indirect, special, incidental and
+consequential damages, such as lost profits;
+states that any provisions which differ from this Agreement are
+offered by that Contributor alone and not by any other party; and
+
+states that source code for the Program is available from such
+Contributor, and informs licensees how to obtain it in a reasonable
+manner on or through a medium customarily used for software exchange.
+When the Program is made available in source code form:
+
+it must be made available under this Agreement; and
+a copy of this Agreement must be included with each copy of the
+Program.
+Each Contributor must include the following in a conspicuous location in the Program:
+
+Copyright (C) 1996, 1999 International Business Machines Corporation and others. All
+Rights Reserved.
+
+In addition, each Contributor must identify itself as the originator
+of its Contribution, if any, in a manner that reasonably allows
+subsequent Recipients to identify the originator of the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+Commercial distributors of software may accept certain
+responsibilities with respect to end users, business partners and the
+like. While this license is intended to facilitate the commercial
+use of the Program, the Contributor who includes the Program in a
+commercial product offering should do so in a manner which does not
+create potential liability for other Contributors. Therefore, if a
+Contributor includes the Program in a commercial product offering,
+such Contributor ("Commercial Contributor") hereby agrees to defend
+and indemnify every other Contributor ("Indemnified Contributor")
+against any losses, damages and costs (collectively "Losses") arising
+from claims, lawsuits and other legal actions brought by a third
+party against the Indemnified Contributor to the extent caused by the
+acts or omissions of such Commercial Contributor in connection with
+its distribution of the Program in a commercial product offering.
+The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement.
+In order to qualify, an Indemnified Contributor must: a) promptly
+notify the Commercial Contributor in writing of such claim, and b)
+allow the Commercial Contributor to control, and cooperate with the
+Commercial Contributor in, the defense and any related settlement
+negotiations. The Indemnified Contributor may participate in any
+such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial
+product offering, Product X. That Contributor is then a Commercial
+Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance
+claims and warranties are such Commercial Contributor`s
+responsibility alone. Under this section, the Commercial Contributor
+would have to defend claims against the other Contributors related to
+those performance claims and warranties, and if a court requires any
+other Contributor to pay any damages as a result, the Commercial
+Contributor must pay those damages.
+
+5. NO WARRANTY
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS
+PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
+WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY
+OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
+responsible for determining the appropriateness of using and
+distributing the Program and assumes all risks associated with its
+exercise of rights under this Agreement, including but not limited to
+the risks and costs of program errors, compliance with applicable
+laws, damage to or loss of data, programs or equipment, and
+unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT
+NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
+TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
+THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
+GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+If any provision of this Agreement is invalid or unenforceable under
+applicable law, it shall not affect the validity or enforceability of
+the remainder of the terms of this Agreement, and without further
+action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.
+
+If Recipient institutes patent litigation against a Contributor with
+respect to a patent applicable to software (including a cross-claim
+or counterclaim in a lawsuit), then any patent licenses granted by
+that Contributor to such Recipient under this Agreement shall
+terminate as of the date such litigation is filed. In addition, if
+Recipient institutes patent litigation against any entity (including
+a cross-claim or counterclaim in a lawsuit) alleging that the Program
+itself (excluding combinations of the Program with other software or
+hardware) infringes such Recipient`s patent(s), then such Recipient`s
+rights granted under Section 2(b) shall terminate as of the date such
+litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it
+fails to comply with any of the material terms or conditions of this
+Agreement and does not cure such failure in a reasonable period of
+time after becoming aware of such noncompliance. If all Recipient`s
+rights under this Agreement terminate, Recipient agrees to cease use
+and distribution of the Program as soon as reasonably practicable.
+However, Recipient`s obligations under this Agreement and any
+licenses granted by Recipient relating to the Program shall continue
+and survive.
+
+IBM may publish new versions (including revisions) of this Agreement
+from time to time. Each new version of the Agreement will be given a
+distinguishing version number. The Program (including Contributions)
+may always be distributed subject to the version of the Agreement
+under which it was received. In addition, after a new version of the
+Agreement is published, Contributor may elect to distribute the
+Program (including its Contributions) under the new version. No one
+other than IBM has the right to modify this Agreement. Except as
+expressly stated in Sections 2(a) and 2(b) above, Recipient receives
+no rights or licenses to the intellectual property of any Contributor
+under this Agreement, whether expressly, by implication, estoppel or
+otherwise. All rights in the Program not expressly granted under
+this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and
+the intellectual property laws of the United States of America. No
+party to this Agreement will bring a legal action under this
+Agreement more than one year after the cause of action arose. Each
+party waives its rights to a jury trial in any resulting litigation.
+
+
+
+
+ISC
+
+
+ISC License:
+
+Copyright © 2004-2010 by Internet Systems Consortium, Inc. ("ISC")
+Copyright © 1995-2003 by Internet Software Consortium
+
+Permission to use, copy, modify, and/or distribute this software for any purpose with
+or without fee is hereby granted, provided that the above copyright notice and this
+permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
+SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT
+SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
+DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
+OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
+THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+
+
+
+JLEX
+
+ JLEX COPYRIGHT NOTICE, LICENSE, AND DISCLAIMER
+ Copyright 1996-2000 by Elliot Joel Berk and C. Scott Ananian
+
+ Permission to use, copy, modify, and distribute this software and its
+ documentation for any purpose and without fee is hereby granted,
+ provided that the above copyright notice appear in all copies and that
+ both the copyright notice and this permission notice and warranty
+ disclaimer appear in supporting documentation, and that the name of
+ the authors or their employers not be used in advertising or publicity
+ pertaining to distribution of the software without specific, written
+ prior permission.
+
+ The authors and their employers disclaim all warranties with regard to
+ this software, including all implied warranties of merchantability and
+ fitness. In no event shall the authors or their employers be liable
+ for any special, indirect or consequential damages or any damages
+ whatsoever resulting from loss of use, data or profits, whether in an
+ action of contract, negligence or other tortious action, arising out
+ of or in connection with the use or performance of this software.
+
+
+
+LGPL-2.0
+
+GNU LIBRARY GENERAL PUBLIC LICENSE
+
+
+
+Version 2, June 1991
+
+
+
+Copyright (C) 1991 Free Software Foundation, Inc.
+
+51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+
+of this license document, but changing it is not allowed.
+
+
+
+[This is the first released version of the library GPL. It is
+
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+Preamble
+
+
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public Licenses are intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users.
+
+
+
+This license, the Library General Public License, applies to some specially designated
+Free Software Foundation software, and to any other libraries whose authors decide to
+use it. You can use it for your libraries, too.
+
+
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for this service if you wish), that you receive
+source code or can get it if you want it, that you can change the software or use
+pieces of it in new free programs; and that you know you can do these things.
+
+
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you
+these rights or to ask you to surrender the rights. These restrictions translate to
+certain responsibilities for you if you distribute copies of the library, or if you
+modify it.
+
+
+
+For example, if you distribute copies of the library, whether gratis or for a fee, you
+must give the recipients all the rights that we gave you. You must make sure that
+they, too, receive or can get the source code. If you link a program with the library,
+you must provide complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling it. And you must
+show them these terms so they know their rights.
+
+
+
+Our method of protecting your rights has two steps: (1) copyright the library, and (2)
+offer you this license which gives you legal permission to copy, distribute and/or
+modify the library.
+
+
+
+Also, for each distributor's protection, we want to make certain that everyone
+understands that there is no warranty for this free library. If the library is
+modified by someone else and passed on, we want its recipients to know that what they
+have is not the original version, so that any problems introduced by others will not
+reflect on the original authors' reputations.
+
+
+
+Finally, any free program is threatened constantly by software patents. We wish to
+avoid the danger that companies distributing free software will individually obtain
+patent licenses, thus in effect transforming the program into proprietary software. To
+prevent this, we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+
+
+Most GNU software, including some libraries, is covered by the ordinary GNU General
+Public License, which was designed for utility programs. This license, the GNU Library
+General Public License, applies to certain designated libraries. This license is quite
+different from the ordinary one; be sure to read it in full, and don't assume that
+anything in it is the same as in the ordinary license.
+
+
+
+The reason we have a separate public license for some libraries is that they blur the
+distinction we usually make between modifying or adding to a program and simply using
+it. Linking a program with a library, without changing the library, is in some sense
+simply using the library, and is analogous to running a utility program or application
+program. However, in a textual and legal sense, the linked executable is a combined
+work, a derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+
+
+Because of this blurred distinction, using the ordinary General Public License for
+libraries did not effectively promote software sharing, because most developers did
+not use the libraries. We concluded that weaker conditions might promote sharing
+better.
+
+
+
+However, unrestricted linking of non-free programs would deprive the users of those
+programs of all benefit from the free status of the libraries themselves. This Library
+General Public License is intended to permit developers of non-free programs to use
+free libraries, while preserving your freedom as a user of such programs to change the
+free libraries that are incorporated in them. (We have not seen how to achieve this as
+regards changes in header files, but we have achieved it as regards changes in the
+actual functions of the Library.) The hope is that this will lead to faster
+development of free libraries.
+
+
+
+The precise terms and conditions for copying, distribution and modification follow.
+Pay close attention to the difference between a "work based on the library" and a
+"work that uses the library". The former contains code derived from the library, while
+the latter only works together with the library.
+
+
+
+Note that it is possible for a library to be covered by the ordinary General Public
+License rather than by this special one.
+
+
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+
+
+0. This License Agreement applies to any software library which contains a notice
+placed by the copyright holder or other authorized party saying it may be distributed
+under the terms of this Library General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+
+
+A "library" means a collection of software functions and/or data prepared so as to be
+conveniently linked with application programs (which use some of those functions and
+data) to form executables.
+
+
+
+The "Library", below, refers to any such software library or work which has been
+distributed under these terms. A "work based on the Library" means either the Library
+or any derivative work under copyright law: that is to say, a work containing the
+Library or a portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is included without
+limitation in the term "modification".)
+
+
+
+"Source code" for a work means the preferred form of the work for making modifications
+to it. For a library, complete source code means all the source code for all modules
+it contains, plus any associated interface definition files, plus the scripts used to
+control compilation and installation of the library.
+
+
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running a program using the Library is
+not restricted, and output from such a program is covered only if its contents
+constitute a work based on the Library (independent of the use of the Library in a
+tool for writing it). Whether that is true depends on what the Library does and what
+the program that uses the Library does.
+
+
+
+1. You may copy and distribute verbatim copies of the Library's complete source code
+as you receive it, in any medium, provided that you conspicuously and appropriately
+publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
+intact all the notices that refer to this License and to the absence of any warranty;
+and distribute a copy of this License along with the Library.
+
+
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+
+
+2. You may modify your copy or copies of the Library or any portion of it, thus
+forming a work based on the Library, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+
+
+a) The modified work must itself be a software library.
+
+b) You must cause the files modified to carry prominent notices stating that you
+changed the files and the date of any change.
+
+c) You must cause the whole of the work to be licensed at no charge to all third
+parties under the terms of this License.
+
+d) If a facility in the modified Library refers to a function or a table of data to be
+supplied by an application program that uses the facility, other than as an argument
+passed when the facility is invoked, then you must make a good faith effort to ensure
+that, in the event an application does not supply such function or table, the facility
+still operates, and performs whatever part of its purpose remains meaningful.
+
+(For example, a function in a library to compute square roots has a purpose that is
+entirely well-defined independent of the application. Therefore, Subsection 2d
+requires that any application-supplied function or table used by this function must be
+optional: if the application does not supply it, the square root function must still
+compute square roots.)
+
+
+
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Library, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Library,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Library.
+
+
+
+In addition, mere aggregation of another work not based on the Library with the
+Library (or with a work based on the Library) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+
+
+3. You may opt to apply the terms of the ordinary GNU General Public License instead
+of this License to a given copy of the Library. To do this, you must alter all the
+notices that refer to this License, so that they refer to the ordinary GNU General
+Public License, version 2, instead of to this License. (If a newer version than
+version 2 of the ordinary GNU General Public License has appeared, then you can
+specify that version instead if you wish.) Do not make any other change in these
+notices.
+
+
+
+Once this change is made in a given copy, it is irreversible for that copy, so the
+ordinary GNU General Public License applies to all subsequent copies and derivative
+works made from that copy.
+
+
+
+This option is useful when you wish to copy part of the code of the Library into a
+program that is not a library.
+
+
+
+4. You may copy and distribute the Library (or a portion or derivative of it, under
+Section 2) in object code or executable form under the terms of Sections 1 and 2 above
+provided that you accompany it with the complete corresponding machine-readable source
+code, which must be distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange.
+
+
+
+If distribution of object code is made by offering access to copy from a designated
+place, then offering equivalent access to copy the source code from the same place
+satisfies the requirement to distribute the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+
+
+5. A program that contains no derivative of any portion of the Library, but is
+designed to work with the Library by being compiled or linked with it, is called a
+"work that uses the Library". Such a work, in isolation, is not a derivative work of
+the Library, and therefore falls outside the scope of this License.
+
+
+
+However, linking a "work that uses the Library" with the Library creates an executable
+that is a derivative of the Library (because it contains portions of the Library),
+rather than a "work that uses the library". The executable is therefore covered by
+this License. Section 6 states terms for distribution of such executables.
+
+
+
+When a "work that uses the Library" uses material from a header file that is part of
+the Library, the object code for the work may be a derivative work of the Library even
+though the source code is not. Whether this is true is especially significant if the
+work can be linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+
+
+If such an object file uses only numerical parameters, data structure layouts and
+accessors, and small macros and small inline functions (ten lines or less in length),
+then the use of the object file is unrestricted, regardless of whether it is legally a
+derivative work. (Executables containing this object code plus portions of the Library
+will still fall under Section 6.)
+
+
+
+Otherwise, if the work is a derivative of the Library, you may distribute the object
+code for the work under the terms of Section 6. Any executables containing that work
+also fall under Section 6, whether or not they are linked directly with the Library
+itself.
+
+
+
+6. As an exception to the Sections above, you may also compile or link a "work that
+uses the Library" with the Library to produce a work containing portions of the
+Library, and distribute that work under terms of your choice, provided that the terms
+permit modification of the work for the customer's own use and reverse engineering for
+debugging such modifications.
+
+
+
+You must give prominent notice with each copy of the work that the Library is used in
+it and that the Library and its use are covered by this License. You must supply a
+copy of this License. If the work during execution displays copyright notices, you
+must include the copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one of these things:
+
+
+
+a) Accompany the work with the complete corresponding machine-readable source code for
+the Library including whatever changes were used in the work (which must be
+distributed under Sections 1 and 2 above); and, if the work is an executable linked
+with the Library, with the complete machine-readable "work that uses the Library", as
+object code and/or source code, so that the user can modify the Library and then
+relink to produce a modified executable containing the modified Library. (It is
+understood that the user who changes the contents of definitions files in the Library
+will not necessarily be able to recompile the application to use the modified
+definitions.)
+
+b) Accompany the work with a written offer, valid for at least three years, to give
+the same user the materials specified in Subsection 6a, above, for a charge no more
+than the cost of performing this distribution.
+
+c) If distribution of the work is made by offering access to copy from a designated
+place, offer equivalent access to copy the above specified materials from the same
+place.
+
+d) Verify that the user has already received a copy of these materials or that you
+have already sent this user a copy.
+
+For an executable, the required form of the "work that uses the Library" must include
+any data and utility programs needed for reproducing the executable from it. However,
+as a special exception, the source code distributed need not include anything that is
+normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+
+
+It may happen that this requirement contradicts the license restrictions of other
+proprietary libraries that do not normally accompany the operating system. Such a
+contradiction means you cannot use both them and the Library together in an executable
+that you distribute.
+
+
+
+7. You may place library facilities that are a work based on the Library side-by-side
+in a single library together with other library facilities not covered by this
+License, and distribute such a combined library, provided that the separate
+distribution of the work based on the Library and of the other library facilities is
+otherwise permitted, and provided that you do these two things:
+
+
+
+a) Accompany the combined library with a copy of the same work based on the Library,
+uncombined with any other library facilities. This must be distributed under the terms
+of the Sections above.
+
+b) Give prominent notice with the combined library of the fact that part of it is a
+work based on the Library, and explaining where to find the accompanying uncombined
+form of the same work.
+
+8. You may not copy, modify, sublicense, link with, or distribute the Library except
+as expressly provided under this License. Any attempt otherwise to copy, modify,
+sublicense, link with, or distribute the Library is void, and will automatically
+terminate your rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses terminated so long
+as such parties remain in full compliance.
+
+
+
+9. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Library or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Library or works based on it.
+
+
+
+10. Each time you redistribute the Library (or any work based on the Library), the
+recipient automatically receives a license from the original licensor to copy,
+distribute, link with or modify the Library subject to these terms and conditions. You
+may not impose any further restrictions on the recipients' exercise of the rights
+granted herein. You are not responsible for enforcing compliance by third parties to
+this License.
+
+
+
+11. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Library at all. For example, if a patent license would not permit royalty-free
+redistribution of the Library by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply, and the section as a
+whole is intended to apply in other circumstances.
+
+
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+
+
+12. If the distribution and/or use of the Library is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Library under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+
+
+13. The Free Software Foundation may publish revised and/or new versions of the
+Library General Public License from time to time. Such new versions will be similar in
+spirit to the present version, but may differ in detail to address new problems or
+concerns.
+
+
+
+Each version is given a distinguishing version number. If the Library specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Library does not
+specify a license version number, you may choose any version ever published by the
+Free Software Foundation.
+
+
+
+14. If you wish to incorporate parts of the Library into other free programs whose
+distribution conditions are incompatible with these, write to the author to ask for
+permission. For software which is copyrighted by the Free Software Foundation, write
+to the Free Software Foundation; we sometimes make exceptions for this. Our decision
+will be guided by the two goals of preserving the free status of all derivatives of
+our free software and of promoting the sharing and reuse of software generally.
+
+
+
+NO WARRANTY
+
+
+
+15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+
+
+16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
+WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+
+
+END OF TERMS AND CONDITIONS
+
+
+
+How to Apply These Terms to Your New Libraries
+
+
+
+If you develop a new library, and you want it to be of the greatest possible use to
+the public, we recommend making it free software that everyone can redistribute and
+change. You can do so by permitting redistribution under these terms (or,
+alternatively, under the terms of the ordinary General Public License).
+
+
+
+To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
+where the full notice is found.
+
+
+
+one line to give the library's name and an idea of what it does.
+
+Copyright (C) year name of author
+
+
+
+This library is free software; you can redistribute it and/or
+
+modify it under the terms of the GNU Library General Public
+
+License as published by the Free Software Foundation; either
+
+version 2 of the License, or (at your option) any later version.
+
+
+
+This library is distributed in the hope that it will be useful,
+
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+
+Library General Public License for more details.
+
+
+
+You should have received a copy of the GNU Library General Public
+
+License along with this library; if not, write to the
+
+Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+
+Boston, MA 02110-1301, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
+alter the names:
+
+
+
+Yoyodyne, Inc., hereby disclaims all copyright interest in
+
+the library `Frob' (a library for tweaking knobs) written
+
+by James Random Hacker.
+
+
+
+signature of Ty Coon, 1 April 1990
+
+Ty Coon, President of Vice
+
+That's all there is to it!
+
+
+
+
+LGPL-2.1
+
+
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 2.1, February 1999
+
+Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public Licenses are intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users.
+
+This license, the Lesser General Public License, applies to some specially designated
+software packages--typically libraries--of the Free Software Foundation and other
+authors who decide to use it. You can use it too, but we suggest you first think
+carefully about whether this license or the ordinary General Public License is the
+better strategy to use in any particular case, based on the explanations below.
+
+When we speak of free software, we are referring to freedom of use, not price. Our
+General Public Licenses are designed to make sure that you have the freedom to
+distribute copies of free software (and charge for this service if you wish); that you
+receive source code or can get it if you want it; that you can change the software and
+use pieces of it in new free programs; and that you are informed that you can do these
+things.
+
+To protect your rights, we need to make restrictions that forbid distributors to deny
+you these rights or to ask you to surrender these rights. These restrictions translate
+to certain responsibilities for you if you distribute copies of the library or if you
+modify it.
+
+For example, if you distribute copies of the library, whether gratis or for a fee, you
+must give the recipients all the rights that we gave you. You must make sure that
+they, too, receive or can get the source code. If you link other code with the
+library, you must provide complete object files to the recipients, so that they can
+relink them with the library after making changes to the library and recompiling it.
+And you must show them these terms so they know their rights.
+
+We protect your rights with a two-step method: (1) we copyright the library, and (2)
+we offer you this license, which gives you legal permission to copy, distribute and/or
+modify the library.
+
+To protect each distributor, we want to make it very clear that there is no warranty
+for the free library. Also, if the library is modified by someone else and passed on,
+the recipients should know that what they have is not the original version, so that
+the original author`s reputation will not be affected by problems that might be
+introduced by others.
+
+Finally, software patents pose a constant threat to the existence of any free program.
+We wish to make sure that a company cannot effectively restrict the users of a free
+program by obtaining a restrictive license from a patent holder. Therefore, we insist
+that any patent license obtained for a version of the library must be consistent with
+the full freedom of use specified in this license.
+
+Most GNU software, including some libraries, is covered by the ordinary GNU General
+Public License. This license, the GNU Lesser General Public License, applies to
+certain designated libraries, and is quite different from the ordinary General Public
+License. We use this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+When a program is linked with a library, whether statically or using a shared library,
+the combination of the two is legally speaking a combined work, a derivative of the
+original library. The ordinary General Public License therefore permits such linking
+only if the entire combination fits its criteria of freedom. The Lesser General Public
+License permits more lax criteria for linking other code with the library.
+
+We call this license the "Lesser" General Public License because it does Less to
+protect the user`s freedom than the ordinary General Public License. It also provides
+other free software developers Less of an advantage over competing non-free programs.
+These disadvantages are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain special
+circumstances.
+
+For example, on rare occasions, there may be a special need to encourage the widest
+possible use of a certain library, so that it becomes a de-facto standard. To achieve
+this, non-free programs must be allowed to use the library. A more frequent case is
+that a free library does the same job as widely used non-free libraries. In this case,
+there is little to gain by limiting the free library to free software only, so we use
+the Lesser General Public License.
+
+In other cases, permission to use a particular library in non-free programs enables a
+greater number of people to use a large body of free software. For example, permission
+to use the GNU C Library in non-free programs enables many more people to use the
+whole GNU operating system, as well as its variant, the GNU/Linux operating system.
+
+Although the Lesser General Public License is Less protective of the users` freedom,
+it does ensure that the user of a program that is linked with the Library has the
+freedom and the wherewithal to run that program using a modified version of the
+Library.
+
+The precise terms and conditions for copying, distribution and modification follow.
+Pay close attention to the difference between a "work based on the library" and a
+"work that uses the library". The former contains code derived from the library,
+whereas the latter must be combined with the library in order to run.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License Agreement applies to any software library or other program which
+contains a notice placed by the copyright holder or other authorized party saying it
+may be distributed under the terms of this Lesser General Public License (also called
+"this License"). Each licensee is addressed as "you".
+
+A "library" means a collection of software functions and/or data prepared so as to be
+conveniently linked with application programs (which use some of those functions and
+data) to form executables.
+
+The "Library", below, refers to any such software library or work which has been
+distributed under these terms. A "work based on the Library" means either the Library
+or any derivative work under copyright law: that is to say, a work containing the
+Library or a portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is included without
+limitation in the term "modification".)
+
+"Source code" for a work means the preferred form of the work for making modifications
+to it. For a library, complete source code means all the source code for all modules
+it contains, plus any associated interface definition files, plus the scripts used to
+control compilation and installation of the library.
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running a program using the Library is
+not restricted, and output from such a program is covered only if its contents
+constitute a work based on the Library (independent of the use of the Library in a
+tool for writing it). Whether that is true depends on what the Library does and what
+the program that uses the Library does.
+
+1. You may copy and distribute verbatim copies of the Library`s complete source code
+as you receive it, in any medium, provided that you conspicuously and appropriately
+publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
+intact all the notices that refer to this License and to the absence of any warranty;
+and distribute a copy of this License along with the Library.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Library or any portion of it, thus
+forming a work based on the Library, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+a) The modified work must itself be a software library.
+b) You must cause the files modified to carry prominent notices stating that you
+changed the files and the date of any change.
+c) You must cause the whole of the work to be licensed at no charge to all third
+parties under the terms of this License.
+d) If a facility in the modified Library refers to a function or a table of data to be
+supplied by an application program that uses the facility, other than as an argument
+passed when the facility is invoked, then you must make a good faith effort to ensure
+that, in the event an application does not supply such function or table, the facility
+still operates, and performs whatever part of its purpose remains meaningful.
+(For example, a function in a library to compute square roots has a purpose that is
+entirely well-defined independent of the application. Therefore, Subsection 2d
+requires that any application-supplied function or table used by this function must be
+optional: if the application does not supply it, the square root function must still
+compute square roots.)
+
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Library, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Library,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library with the
+Library (or with a work based on the Library) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+3. You may opt to apply the terms of the ordinary GNU General Public License instead
+of this License to a given copy of the Library. To do this, you must alter all the
+notices that refer to this License, so that they refer to the ordinary GNU General
+Public License, version 2, instead of to this License. (If a newer version than
+version 2 of the ordinary GNU General Public License has appeared, then you can
+specify that version instead if you wish.) Do not make any other change in these
+notices.
+
+Once this change is made in a given copy, it is irreversible for that copy, so the
+ordinary GNU General Public License applies to all subsequent copies and derivative
+works made from that copy.
+
+This option is useful when you wish to copy part of the code of the Library into a
+program that is not a library.
+
+4. You may copy and distribute the Library (or a portion or derivative of it, under
+Section 2) in object code or executable form under the terms of Sections 1 and 2 above
+provided that you accompany it with the complete corresponding machine-readable source
+code, which must be distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange.
+
+If distribution of object code is made by offering access to copy from a designated
+place, then offering equivalent access to copy the source code from the same place
+satisfies the requirement to distribute the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+5. A program that contains no derivative of any portion of the Library, but is
+designed to work with the Library by being compiled or linked with it, is called a
+"work that uses the Library". Such a work, in isolation, is not a derivative work of
+the Library, and therefore falls outside the scope of this License.
+
+However, linking a "work that uses the Library" with the Library creates an executable
+that is a derivative of the Library (because it contains portions of the Library),
+rather than a "work that uses the library". The executable is therefore covered by
+this License. Section 6 states terms for distribution of such executables.
+
+When a "work that uses the Library" uses material from a header file that is part of
+the Library, the object code for the work may be a derivative work of the Library even
+though the source code is not. Whether this is true is especially significant if the
+work can be linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+If such an object file uses only numerical parameters, data structure layouts and
+accessors, and small macros and small inline functions (ten lines or less in length),
+then the use of the object file is unrestricted, regardless of whether it is legally a
+derivative work. (Executables containing this object code plus portions of the Library
+will still fall under Section 6.)
+
+Otherwise, if the work is a derivative of the Library, you may distribute the object
+code for the work under the terms of Section 6. Any executables containing that work
+also fall under Section 6, whether or not they are linked directly with the Library
+itself.
+
+6. As an exception to the Sections above, you may also combine or link a "work that
+uses the Library" with the Library to produce a work containing portions of the
+Library, and distribute that work under terms of your choice, provided that the terms
+permit modification of the work for the customer`s own use and reverse engineering for
+debugging such modifications.
+
+You must give prominent notice with each copy of the work that the Library is used in
+it and that the Library and its use are covered by this License. You must supply a
+copy of this License. If the work during execution displays copyright notices, you
+must include the copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one of these things:
+
+a) Accompany the work with the complete corresponding machine-readable source code for
+the Library including whatever changes were used in the work (which must be
+distributed under Sections 1 and 2 above); and, if the work is an executable linked
+with the Library, with the complete machine-readable "work that uses the Library", as
+object code and/or source code, so that the user can modify the Library and then
+relink to produce a modified executable containing the modified Library. (It is
+understood that the user who changes the contents of definitions files in the Library
+will not necessarily be able to recompile the application to use the modified
+definitions.)
+b) Use a suitable shared library mechanism for linking with the Library. A suitable
+mechanism is one that (1) uses at run time a copy of the library already present on
+the user`s computer system, rather than copying library functions into the executable,
+and (2) will operate properly with a modified version of the library, if the user
+installs one, as long as the modified version is interface-compatible with the version
+that the work was made with.
+c) Accompany the work with a written offer, valid for at least three years, to give
+the same user the materials specified in Subsection 6a, above, for a charge no more
+than the cost of performing this distribution.
+d) If distribution of the work is made by offering access to copy from a designated
+place, offer equivalent access to copy the above specified materials from the same
+place.
+e) Verify that the user has already received a copy of these materials or that you
+have already sent this user a copy.
+For an executable, the required form of the "work that uses the Library" must include
+any data and utility programs needed for reproducing the executable from it. However,
+as a special exception, the materials to be distributed need not include anything that
+is normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+It may happen that this requirement contradicts the license restrictions of other
+proprietary libraries that do not normally accompany the operating system. Such a
+contradiction means you cannot use both them and the Library together in an executable
+that you distribute.
+
+7. You may place library facilities that are a work based on the Library side-by-side
+in a single library together with other library facilities not covered by this
+License, and distribute such a combined library, provided that the separate
+distribution of the work based on the Library and of the other library facilities is
+otherwise permitted, and provided that you do these two things:
+
+a) Accompany the combined library with a copy of the same work based on the Library,
+uncombined with any other library facilities. This must be distributed under the terms
+of the Sections above.
+b) Give prominent notice with the combined library of the fact that part of it is a
+work based on the Library, and explaining where to find the accompanying uncombined
+form of the same work.
+8. You may not copy, modify, sublicense, link with, or distribute the Library except
+as expressly provided under this License. Any attempt otherwise to copy, modify,
+sublicense, link with, or distribute the Library is void, and will automatically
+terminate your rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses terminated so long
+as such parties remain in full compliance.
+
+9. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Library or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Library or works based on it.
+
+10. Each time you redistribute the Library (or any work based on the Library), the
+recipient automatically receives a license from the original licensor to copy,
+distribute, link with or modify the Library subject to these terms and conditions. You
+may not impose any further restrictions on the recipients` exercise of the rights
+granted herein. You are not responsible for enforcing compliance by third parties with
+this License.
+
+11. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Library at all. For example, if a patent license would not permit royalty-free
+redistribution of the Library by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply, and the section as a
+whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+12. If the distribution and/or use of the Library is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Library under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+13. The Free Software Foundation may publish revised and/or new versions of the Lesser
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Library does not
+specify a license version number, you may choose any version ever published by the
+Free Software Foundation.
+
+14. If you wish to incorporate parts of the Library into other free programs whose
+distribution conditions are incompatible with these, write to the author to ask for
+permission. For software which is copyrighted by the Free Software Foundation, write
+to the Free Software Foundation; we sometimes make exceptions for this. Our decision
+will be guided by the two goals of preserving the free status of all derivatives of
+our free software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
+WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Libraries
+
+If you develop a new library, and you want it to be of the greatest possible use to
+the public, we recommend making it free software that everyone can redistribute and
+change. You can do so by permitting redistribution under these terms (or,
+alternatively, under the terms of the ordinary General Public License).
+
+To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
+where the full notice is found.
+
+one line to give the library`s name and an idea of what it does.
+Copyright (C) year name of author
+
+This library is free software; you can redistribute it and/or
+modify it under the terms of the GNU Lesser General Public
+License as published by the Free Software Foundation; either
+version 2.1 of the License, or (at your option) any later version.
+
+This library is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public
+License along with this library; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
+alter the names:
+
+Yoyodyne, Inc., hereby disclaims all copyright interest in
+the library `Frob` (a library for tweaking knobs) written
+by James Random Hacker.
+
+signature of Ty Coon, 1 April 1990
+Ty Coon, President of Vice
+That`s all there is to it!
+
+
+
+
+LGPL-3.0
+
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the terms and
+conditions of version 3 of the GNU General Public License, supplemented by the
+additional permissions listed below.
+0. Additional Definitions.
+
+As used herein, ”this License” refers to version 3 of the GNU Lesser
+General Public License, and the ”GNU GPL” refers to version 3 of the GNU
+General Public License.
+
+”The Library” refers to a covered work governed by this License, other
+than an Application or a Combined Work as defined below.
+
+An ”Application” is any work that makes use of an interface provided by
+the Library, but which is not otherwise based on the Library. Defining a subclass of a
+class defined by the Library is deemed a mode of using an interface provided by the
+Library.
+
+A ”Combined Work” is a work produced by combining or linking an
+Application with the Library. The particular version of the Library with which the
+Combined Work was made is also called the ”Linked Version”.
+
+The ”Minimal Corresponding Source” for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code for portions of
+the Combined Work that, considered in isolation, are based on the Application, and not
+on the Linked Version.
+
+The ”Corresponding Application Code” for a Combined Work means the object
+code and/or source code for the Application, including any data and utility programs
+needed for reproducing the Combined Work from the Application, but excluding the
+System Libraries of the Combined Work.
+1. Exception to Section 3 of the GNU GPL.
+
+You may convey a covered work under sections 3 and 4 of this License without being
+bound by section 3 of the GNU GPL.
+2. Conveying Modified Versions.
+
+If you modify a copy of the Library, and, in your modifications, a facility refers to
+a function or data to be supplied by an Application that uses the facility (other than
+as an argument passed when the facility is invoked), then you may convey a copy of the
+modified version:
+
+ * a) under this License, provided that you make a good faith effort to ensure
+that, in the event an Application does not supply the function or data, the facility
+still operates, and performs whatever part of its purpose remains meaningful, or
+ * b) under the GNU GPL, with none of the additional permissions of this License
+applicable to that copy.
+
+3. Object Code Incorporating Material from Library Header Files.
+
+The object code form of an Application may incorporate material from a header file
+that is part of the Library. You may convey such object code under terms of your
+choice, provided that, if the incorporated material is not limited to numerical
+parameters, data structure layouts and accessors, or small macros, inline functions
+and templates (ten or fewer lines in length), you do both of the following:
+
+ * a) Give prominent notice with each copy of the object code that the Library is
+used in it and that the Library and its use are covered by this License.
+ * b) Accompany the object code with a copy of the GNU GPL and this license
+document.
+
+4. Combined Works.
+
+You may convey a Combined Work under terms of your choice that, taken together,
+effectively do not restrict modification of the portions of the Library contained in
+the Combined Work and reverse engineering for debugging such modifications, if you
+also do each of the following:
+
+ * a) Give prominent notice with each copy of the Combined Work that the Library is
+used in it and that the Library and its use are covered by this License.
+ * b) Accompany the Combined Work with a copy of the GNU GPL and this license
+document.
+ * c) For a Combined Work that displays copyright notices during execution, include
+the copyright notice for the Library among these notices, as well as a reference
+directing the user to the copies of the GNU GPL and this license document.
+ * d) Do one of the following:
+ o 0) Convey the Minimal Corresponding Source under the terms of this
+License, and the Corresponding Application Code in a form suitable for, and under
+terms that permit, the user to recombine or relink the Application with a modified
+version of the Linked Version to produce a modified Combined Work, in the manner
+specified by section 6 of the GNU GPL for conveying Corresponding Source.
+ o 1) Use a suitable shared library mechanism for linking with the Library. A
+suitable mechanism is one that (a) uses at run time a copy of the Library already
+present on the user's computer system, and (b) will operate properly with a modified
+version of the Library that is interface-compatible with the Linked Version.
+ * e) Provide Installation Information, but only if you would otherwise be required
+to provide such information under section 6 of the GNU GPL, and only to the extent
+that such information is necessary to install and execute a modified version of the
+Combined Work produced by recombining or relinking the Application with a modified
+version of the Linked Version. (If you use option 4d0, the Installation Information
+must accompany the Minimal Corresponding Source and Corresponding Application Code. If
+you use option 4d1, you must provide the Installation Information in the manner
+specified by section 6 of the GNU GPL for conveying Corresponding Source.)
+
+5. Combined Libraries.
+
+You may place library facilities that are a work based on the Library side by side in
+a single library together with other library facilities that are not Applications and
+are not covered by this License, and convey such a combined library under terms of
+your choice, if you do both of the following:
+
+ * a) Accompany the combined library with a copy of the same work based on the
+Library, uncombined with any other library facilities, conveyed under the terms of
+this License.
+ * b) Give prominent notice with the combined library that part of it is a work
+based on the Library, and explaining where to find the accompanying uncombined form of
+the same work.
+
+6. Revised Versions of the GNU Lesser General Public License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Lesser
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library as you received
+it specifies that a certain numbered version of the GNU Lesser General Public License
+”or any later version” applies to it, you have the option of following
+the terms and conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you received it does not
+specify a version number of the GNU Lesser General Public License, you may choose any
+version of the GNU Lesser General Public License ever published by the Free Software
+Foundation.
+
+If the Library as you received it specifies that a proxy can decide whether future
+versions of the GNU Lesser General Public License shall apply, that proxy's public
+statement of acceptance of any version is permanent authorization for you to choose
+that version for the Library.
+
+
+
+Libpng
+
+
+This copy of the libpng notices is provided for your convenience. In case of
+any discrepancy between this copy and the notices in the file png.h that is
+included in the libpng distribution, the latter shall prevail.
+
+COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
+
+If you modify libpng you may insert additional notices immediately following
+this sentence.
+
+This code is released under the libpng license.
+
+libpng versions 1.2.6, August 15, 2004, through 1.4.5, December 9, 2010, are
+Copyright (c) 2004, 2006-2010 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-1.2.5
+with the following individual added to the list of Contributing Authors
+
+ Cosmin Truta
+
+libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are
+Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-1.0.6
+with the following individuals added to the list of Contributing Authors
+
+ Simon-Pierre Cadieux
+ Eric S. Raymond
+ Gilles Vollant
+
+and with the following additions to the disclaimer:
+
+ There is no warranty against interference with your enjoyment of the
+ library or against infringement. There is no warranty that our
+ efforts or the library will fulfill any of your particular purposes
+ or needs. This library is provided with all faults, and the entire
+ risk of satisfactory quality, performance, accuracy, and effort is with
+ the user.
+
+libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
+Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-0.96,
+with the following individuals added to the list of Contributing Authors:
+
+ Tom Lane
+ Glenn Randers-Pehrson
+ Willem van Schaik
+
+libpng versions 0.89, June 1996, through 0.96, May 1997, are
+Copyright (c) 1996, 1997 Andreas Dilger
+Distributed according to the same disclaimer and license as libpng-0.88,
+with the following individuals added to the list of Contributing Authors:
+
+ John Bowler
+ Kevin Bracey
+ Sam Bushell
+ Magnus Holmgren
+ Greg Roelofs
+ Tom Tanner
+
+libpng versions 0.5, May 1995, through 0.88, January 1996, are
+Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.
+
+For the purposes of this copyright and license, "Contributing Authors"
+is defined as the following set of individuals:
+
+ Andreas Dilger
+ Dave Martindale
+ Guy Eric Schalnat
+ Paul Schmidt
+ Tim Wegner
+
+The PNG Reference Library is supplied "AS IS". The Contributing Authors
+and Group 42, Inc. disclaim all warranties, expressed or implied,
+including, without limitation, the warranties of merchantability and of
+fitness for any purpose. The Contributing Authors and Group 42, Inc.
+assume no liability for direct, indirect, incidental, special, exemplary,
+or consequential damages, which may result from the use of the PNG
+Reference Library, even if advised of the possibility of such damage.
+
+Permission is hereby granted to use, copy, modify, and distribute this
+source code, or portions hereof, for any purpose, without fee, subject
+to the following restrictions:
+
+1. The origin of this source code must not be misrepresented.
+
+2. Altered versions must be plainly marked as such and must not
+ be misrepresented as being the original source.
+
+3. This Copyright notice may not be removed or altered from any
+ source or altered source distribution.
+
+The Contributing Authors and Group 42, Inc. specifically permit, without
+fee, and encourage the use of this source code as a component to
+supporting the PNG file format in commercial products. If you use this
+source code in a product, acknowledgment is not required but would be
+appreciated.
+
+
+A "png_get_copyright" function is available, for convenient use in "about"
+boxes and the like:
+
+ printf("%s",png_get_copyright(NULL));
+
+Also, the PNG logo (in PNG format, of course) is supplied in the
+files "pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).
+
+Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a
+certification mark of the Open Source Initiative.
+
+Glenn Randers-Pehrson
+glennrp at users.sourceforge.net
+December 9, 2010
+
+
+
+
+MIT
+
+
+MIT License
+
+Copyright (c) <year> <copyright holders>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+
+
+MPL-1.0
+
+
+MOZILLA PUBLIC LICENSE
+Version 1.0
+
+1. Definitions.
+
+1.1. ``Contributor`` means each entity that creates or contributes to the creation of
+Modifications.
+1.2. ``Contributor Version`` means the combination of the Original Code, prior
+Modifications used by a Contributor, and the Modifications made by that particular
+Contributor.
+
+1.3. ``Covered Code`` means the Original Code or Modifications or the combination of
+the Original Code and Modifications, in each case including portions thereof.
+
+1.4. ``Electronic Distribution Mechanism`` means a mechanism generally accepted in the
+software development community for the electronic transfer of data.
+
+1.5. ``Executable`` means Covered Code in any form other than Source Code.
+
+1.6. ``Initial Developer`` means the individual or entity identified as the Initial
+Developer in the Source Code notice required by Exhibit A.
+
+1.7. ``Larger Work`` means a work which combines Covered Code or portions thereof with
+code not governed by the terms of this License.
+
+1.8. ``License`` means this document.
+
+1.9. ``Modifications`` means any addition to or deletion from the substance or
+structure of either the Original Code or any previous Modifications. When Covered Code
+is released as a series of files, a Modification is:
+
+A. Any addition to or deletion from the contents of a file containing Original Code or
+previous Modifications.
+
+B. Any new file that contains any part of the Original Code or previous Modifications.
+
+1.10. ``Original Code`` means Source Code of computer software code which is described
+in the Source Code notice required by Exhibit A as Original Code, and which, at the
+time of its release under this License is not already Covered Code governed by this
+License.
+
+1.11. ``Source Code`` means the preferred form of the Covered Code for making
+modifications to it, including all modules it contains, plus any associated interface
+definition files, scripts used to control compilation and installation of an
+Executable, or a list of source code differential comparisons against either the
+Original Code or another well known, available Covered Code of the Contributor`s
+choice. The Source Code can be in a compressed or archival form, provided the
+appropriate decompression or de-archiving software is widely available for no charge.
+
+1.12. ``You`` means an individual or a legal entity exercising rights under, and
+complying with all of the terms of, this License or a future version of this License
+issued under Section 6.1. For legal entities, ``You`` includes any entity which
+controls, is controlled by, or is under common control with You. For purposes of this
+definition, ``control`` means (a) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or otherwise, or (b)
+ownership of fifty percent (50%) or more of the outstanding shares or beneficial
+ownership of such entity.
+
+2. Source Code License.
+2.1. The Initial Developer Grant.
+The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive
+license, subject to third party intellectual property claims:
+(a) to use, reproduce, modify, display, perform, sublicense and distribute the
+Original Code (or portions thereof) with or without Modifications, or as part of a
+Larger Work; and
+
+(b) under patents now or hereafter owned or controlled by Initial Developer, to make,
+have made, use and sell (``Utilize``) the Original Code (or portions thereof), but
+solely to the extent that any such patent is reasonably necessary to enable You to
+Utilize the Original Code (or portions thereof) and not to any greater extent that may
+be necessary to Utilize further Modifications or combinations.
+
+2.2. Contributor Grant.
+Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license,
+subject to third party intellectual property claims:
+
+(a) to use, reproduce, modify, display, perform, sublicense and distribute the
+Modifications created by such Contributor (or portions thereof) either on an
+unmodified basis, with other Modifications, as Covered Code or as part of a Larger
+Work; and
+
+(b) under patents now or hereafter owned or controlled by Contributor, to Utilize the
+Contributor Version (or portions thereof), but solely to the extent that any such
+patent is reasonably necessary to enable You to Utilize the Contributor Version (or
+portions thereof), and not to any greater extent that may be necessary to Utilize
+further Modifications or combinations.
+
+3. Distribution Obligations.
+3.1. Application of License.
+The Modifications which You create or to which You contribute are governed by the
+terms of this License, including without limitation Section 2.2. The Source Code
+version of Covered Code may be distributed only under the terms of this License or a
+future version of this License released under Section 6.1, and You must include a copy
+of this License with every copy of the Source Code You distribute. You may not offer
+or impose any terms on any Source Code version that alters or restricts the applicable
+version of this License or the recipients` rights hereunder. However, You may include
+an additional document offering the additional rights described in Section 3.5.
+3.2. Availability of Source Code.
+Any Modification which You create or to which You contribute must be made available in
+Source Code form under the terms of this License either on the same media as an
+Executable version or via an accepted Electronic Distribution Mechanism to anyone to
+whom you made an Executable version available; and if made available via Electronic
+Distribution Mechanism, must remain available for at least twelve (12) months after
+the date it initially became available, or at least six (6) months after a subsequent
+version of that particular Modification has been made available to such recipients.
+You are responsible for ensuring that the Source Code version remains available even
+if the Electronic Distribution Mechanism is maintained by a third party.
+
+3.3. Description of Modifications.
+You must cause all Covered Code to which you contribute to contain a file documenting
+the changes You made to create that Covered Code and the date of any change. You must
+include a prominent statement that the Modification is derived, directly or
+indirectly, from Original Code provided by the Initial Developer and including the
+name of the Initial Developer in (a) the Source Code, and (b) in any notice in an
+Executable version or related documentation in which You describe the origin or
+ownership of the Covered Code.
+
+3.4. Intellectual Property Matters
+
+(a) Third Party Claims.
+If You have knowledge that a party claims an intellectual property right in particular
+functionality or code (or its utilization under this License), you must include a text
+file with the source code distribution titled ``LEGAL`` which describes the claim and
+the party making the claim in sufficient detail that a recipient will know whom to
+contact. If you obtain such knowledge after You make Your Modification available as
+described in Section 3.2, You shall promptly modify the LEGAL file in all copies You
+make available thereafter and shall take other steps (such as notifying appropriate
+mailing lists or newsgroups) reasonably calculated to inform those who received the
+Covered Code that new knowledge has been obtained.
+
+(b) Contributor APIs.
+If Your Modification is an application programming interface and You own or control
+patents which are reasonably necessary to implement that API, you must also include
+this information in the LEGAL file.
+
+3.5. Required Notices.
+You must duplicate the notice in Exhibit A in each file of the Source Code, and this
+License in any documentation for the Source Code, where You describe recipients`
+rights relating to Covered Code. If You created one or more Modification(s), You may
+add your name as a Contributor to the notice described in Exhibit A. If it is not
+possible to put such notice in a particular Source Code file due to its structure,
+then you must include such notice in a location (such as a relevant directory file)
+where a user would be likely to look for such a notice. You may choose to offer, and
+to charge a fee for, warranty, support, indemnity or liability obligations to one or
+more recipients of Covered Code. However, You may do so only on Your own behalf, and
+not on behalf of the Initial Developer or any Contributor. You must make it absolutely
+clear than any such warranty, support, indemnity or liability obligation is offered by
+You alone, and You hereby agree to indemnify the Initial Developer and every
+Contributor for any liability incurred by the Initial Developer or such Contributor as
+a result of warranty, support, indemnity or liability terms You offer.
+
+3.6. Distribution of Executable Versions.
+You may distribute Covered Code in Executable form only if the requirements of Section
+3.1-3.5 have been met for that Covered Code, and if You include a notice stating that
+the Source Code version of the Covered Code is available under the terms of this
+License, including a description of how and where You have fulfilled the obligations
+of Section 3.2. The notice must be conspicuously included in any notice in an
+Executable version, related documentation or collateral in which You describe
+recipients` rights relating to the Covered Code. You may distribute the Executable
+version of Covered Code under a license of Your choice, which may contain terms
+different from this License, provided that You are in compliance with the terms of
+this License and that the license for the Executable version does not attempt to limit
+or alter the recipient`s rights in the Source Code version from the rights set forth
+in this License. If You distribute the Executable version under a different license
+You must make it absolutely clear that any terms which differ from this License are
+offered by You alone, not by the Initial Developer or any Contributor. You hereby
+agree to indemnify the Initial Developer and every Contributor for any liability
+incurred by the Initial Developer or such Contributor as a result of any such terms
+You offer.
+
+3.7. Larger Works.
+You may create a Larger Work by combining Covered Code with other code not governed by
+the terms of this License and distribute the Larger Work as a single product. In such
+a case, You must make sure the requirements of this License are fulfilled for the
+Covered Code.
+
+4. Inability to Comply Due to Statute or Regulation.
+If it is impossible for You to comply with any of the terms of this License with
+respect to some or all of the Covered Code due to statute or regulation then You must:
+(a) comply with the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must be included
+in the LEGAL file described in Section 3.4 and must be included with all distributions
+of the Source Code. Except to the extent prohibited by statute or regulation, such
+description must be sufficiently detailed for a recipient of ordinary skill to be able
+to understand it.
+
+5. Application of this License.
+This License applies to code to which the Initial Developer has attached the notice in
+Exhibit A, and to related Covered Code.
+6. Versions of the License.
+6.1. New Versions.
+Netscape Communications Corporation (``Netscape``) may publish revised and/or new
+versions of the License from time to time. Each version will be given a distinguishing
+version number.
+6.2. Effect of New Versions.
+Once Covered Code has been published under a particular version of the License, You
+may always continue to use it under the terms of that version. You may also choose to
+use such Covered Code under the terms of any subsequent version of the License
+published by Netscape. No one other than Netscape has the right to modify the terms
+applicable to Covered Code created under this License.
+
+6.3. Derivative Works.
+If you create or use a modified version of this License (which you may only do in
+order to apply it to code which is not already Covered Code governed by this License),
+you must (a) rename Your license so that the phrases ``Mozilla``, ``MOZILLAPL``,
+``MOZPL``, ``Netscape``, ``NPL`` or any confusingly similar phrase do not appear
+anywhere in your license and (b) otherwise make it clear that your version of the
+license contains terms which differ from the Mozilla Public License and Netscape
+Public License. (Filling in the name of the Initial Developer, Original Code or
+Contributor in the notice described in Exhibit A shall not of themselves be deemed to
+be modifications of this License.)
+
+7. DISCLAIMER OF WARRANTY.
+COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS`` BASIS, WITHOUT WARRANTY OF
+ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT
+THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
+NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
+IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE
+INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
+SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL
+PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER
+THIS DISCLAIMER.
+8. TERMINATION.
+This License and the rights granted hereunder will terminate automatically if You fail
+to comply with terms herein and fail to cure such breach within 30 days of becoming
+aware of the breach. All sublicenses to the Covered Code which are properly granted
+shall survive any termination of this License. Provisions which, by their nature, must
+remain in effect beyond the termination of this License shall survive.
+9. LIMITATION OF LIABILITY.
+UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
+CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY
+DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU
+OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF
+ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK
+STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
+LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH
+DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
+PERSONAL INJURY RESULTING FROM SUCH PARTY`S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
+PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION
+OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY
+TO YOU.
+10. U.S. GOVERNMENT END USERS.
+The Covered Code is a ``commercial item,`` as that term is defined in 48 C.F.R. 2.101
+(Oct. 1995), consisting of ``commercial computer software`` and ``commercial computer
+software documentation,`` as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
+Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
+1995), all U.S. Government End Users acquire Covered Code with only those rights set
+forth herein.
+11. MISCELLANEOUS.
+This License represents the complete agreement concerning subject matter hereof. If
+any provision of this License is held to be unenforceable, such provision shall be
+reformed only to the extent necessary to make it enforceable. This License shall be
+governed by California law provisions (except to the extent applicable law, if any,
+provides otherwise), excluding its conflict-of-law provisions. With respect to
+disputes in which at least one party is a citizen of, or an entity chartered or
+registered to do business in, the United States of America: (a) unless otherwise
+agreed in writing, all disputes relating to this License (excepting any dispute
+relating to intellectual property rights) shall be subject to final and binding
+arbitration, with the losing party paying all costs of arbitration; (b) any
+arbitration relating to this Agreement shall be held in Santa Clara County,
+California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to
+this Agreement shall be subject to the jurisdiction of the Federal Courts of the
+Northern District of California, with venue lying in Santa Clara County, California,
+with the losing party responsible for costs, including without limitation, court costs
+and reasonable attorneys fees and expenses. The application of the United Nations
+Convention on Contracts for the International Sale of Goods is expressly excluded. Any
+law or regulation which provides that the language of a contract shall be construed
+against the drafter shall not apply to this License.
+12. RESPONSIBILITY FOR CLAIMS.
+Except in cases where another Contributor has failed to comply with Section 3.4, You
+are responsible for damages arising, directly or indirectly, out of Your utilization
+of rights under this License, based on the number of copies of Covered Code you made
+available, the revenues you received from utilizing such rights, and other relevant
+factors. You agree to work with affected parties to distribute responsibility on an
+equitable basis.
+EXHIBIT A.
+``The contents of this file are subject to the Mozilla Public License Version 1.0 (the
+"License"); you may not use this file except in compliance with the License. You may
+obtain a copy of the License at http://www.mozilla.org/MPL/
+Software distributed under the License is distributed on an "AS IS" basis, WITHOUT
+WARRANTY OF ANY KIND, either express or implied. See the License for the specific
+language governing rights and limitations under the License.
+
+The Original Code is ______________________________________.
+
+The Initial Developer of the Original Code is ________________________. Portions
+created by ______________________ are Copyright (C) ______ _______________________.
+All Rights Reserved.
+
+Contributor(s): ______________________________________.``
+
+
+
+
+MPL-2.0
+
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+ means each individual or legal entity that creates, contributes to
+ the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+ means the combination of the Contributions of others (if any) used
+ by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+ means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+ means Source Code Form to which the initial Contributor has attached
+ the notice in Exhibit A, the Executable Form of such Source Code
+ Form, and Modifications of such Source Code Form, in each case
+ including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+ means
+
+ (a) that the initial Contributor has attached the notice described
+ in Exhibit B to the Covered Software; or
+
+ (b) that the Covered Software was made available under the terms of
+ version 1.1 or earlier of the License, but not also under the
+ terms of a Secondary License.
+
+1.6. "Executable Form"
+ means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+ means a work that combines Covered Software with other material, in
+ a separate file or files, that is not Covered Software.
+
+1.8. "License"
+ means this document.
+
+1.9. "Licensable"
+ means having the right to grant, to the maximum extent possible,
+ whether at the time of the initial grant or subsequently, any and
+ all of the rights conveyed by this License.
+
+1.10. "Modifications"
+ means any of the following:
+
+ (a) any file in Source Code Form that results from an addition to,
+ deletion from, or modification of the contents of Covered
+ Software; or
+
+ (b) any new file in Source Code Form that contains any Covered
+ Software.
+
+1.11. "Patent Claims" of a Contributor
+ means any patent claim(s), including without limitation, method,
+ process, and apparatus claims, in any patent Licensable by such
+ Contributor that would be infringed, but for the grant of the
+ License, by the making, using, selling, offering for sale, having
+ made, import, or transfer of either its Contributions or its
+ Contributor Version.
+
+1.12. "Secondary License"
+ means either the GNU General Public License, Version 2.0, the GNU
+ Lesser General Public License, Version 2.1, the GNU Affero General
+ Public License, Version 3.0, or any later versions of those
+ licenses.
+
+1.13. "Source Code Form"
+ means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+ means an individual or a legal entity exercising rights under this
+ License. For legal entities, "You" includes any entity that
+ controls, is controlled by, or is under common control with You. For
+ purposes of this definition, "control" means (a) the power, direct
+ or indirect, to cause the direction or management of such entity,
+ whether by contract or otherwise, or (b) ownership of more than
+ fifty percent (50%) of the outstanding shares or beneficial
+ ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+ Licensable by such Contributor to use, reproduce, make available,
+ modify, display, perform, distribute, and otherwise exploit its
+ Contributions, either on an unmodified basis, with Modifications, or
+ as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+ for sale, have made, import, and otherwise transfer either its
+ Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+ or
+
+(b) for infringements caused by: (i) Your and any other third party's
+ modifications of Covered Software, or (ii) the combination of its
+ Contributions with other software (except as part of its Contributor
+ Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+ its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+ Form, as described in Section 3.1, and You must inform recipients of
+ the Executable Form how they can obtain a copy of such Source Code
+ Form by reasonable means in a timely manner, at a charge no more
+ than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+ License, or sublicense it under different terms, provided that the
+ license for the Executable Form does not attempt to limit or alter
+ the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+* *
+* 6. Disclaimer of Warranty *
+* ------------------------- *
+* *
+* Covered Software is provided under this License on an "as is" *
+* basis, without warranty of any kind, either expressed, implied, or *
+* statutory, including, without limitation, warranties that the *
+* Covered Software is free of defects, merchantable, fit for a *
+* particular purpose or non-infringing. The entire risk as to the *
+* quality and performance of the Covered Software is with You. *
+* Should any Covered Software prove defective in any respect, You *
+* (not any Contributor) assume the cost of any necessary servicing, *
+* repair, or correction. This disclaimer of warranty constitutes an *
+* essential part of this License. No use of any Covered Software is *
+* authorized under this License except under this disclaimer. *
+* *
+************************************************************************
+
+************************************************************************
+* *
+* 7. Limitation of Liability *
+* -------------------------- *
+* *
+* Under no circumstances and under no legal theory, whether tort *
+* (including negligence), contract, or otherwise, shall any *
+* Contributor, or anyone who distributes Covered Software as *
+* permitted above, be liable to You for any direct, indirect, *
+* special, incidental, or consequential damages of any character *
+* including, without limitation, damages for lost profits, loss of *
+* goodwill, work stoppage, computer failure or malfunction, or any *
+* and all other commercial damages or losses, even if such party *
+* shall have been informed of the possibility of such damages. This *
+* limitation of liability shall not apply to liability for death or *
+* personal injury resulting from such party's negligence to the *
+* extent applicable law prohibits such limitation. Some *
+* jurisdictions do not allow the exclusion or limitation of *
+* incidental or consequential damages, so this exclusion and *
+* limitation may not apply to You. *
+* *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+ This Source Code Form is subject to the terms of the Mozilla Public
+ License, v. 2.0. If a copy of the MPL was not distributed with this
+ file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+ This Source Code Form is "Incompatible With Secondary Licenses", as
+ defined by the Mozilla Public License, v. 2.0.
+
+
+
+OFL-1.1
+
+
+SIL OPEN FONT LICENSE
+
+Version 1.1 - 26 February 2007
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
+
+
+
+
+OpenSSL
+
+
+OpenSSL License
+
+ ====================================================================
+ Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ 1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the
+ distribution.
+
+ 3. All advertising materials mentioning features or use of this
+ software must display the following acknowledgment:
+ "This product includes software developed by the OpenSSL Project
+ for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
+
+ 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
+ endorse or promote products derived from this software without
+ prior written permission. For written permission, please contact
+ openssl-core@openssl.org.
+
+ 5. Products derived from this software may not be called "OpenSSL"
+ nor may "OpenSSL" appear in their names without prior written
+ permission of the OpenSSL Project.
+
+ 6. Redistributions of any form whatsoever must retain the following
+ acknowledgment:
+ "This product includes software developed by the OpenSSL Project
+ for use in the OpenSSL Toolkit (http://www.openssl.org/)"
+
+ THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS`` AND ANY
+ EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
+ ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+ NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+ OF THE POSSIBILITY OF SUCH DAMAGE.
+ ====================================================================
+
+ This product includes cryptographic software written by Eric Young
+ (eay@cryptsoft.com). This product includes software written by Tim
+ Hudson (tjh@cryptsoft.com).
+
+
+ Original SSLeay License
+ -----------------------
+
+Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
+All rights reserved.
+
+ This package is an SSL implementation written
+ by Eric Young (eay@cryptsoft.com).
+ The implementation was written so as to conform with Netscapes SSL.
+
+ This library is free for commercial and non-commercial use as long as
+ the following conditions are aheared to. The following conditions
+ apply to all code found in this distribution, be it the RC4, RSA,
+ lhash, DES, etc., code; not just the SSL code. The SSL documentation
+ included with this distribution is covered by the same copyright terms
+ except that the holder is Tim Hudson (tjh@cryptsoft.com).
+
+ Copyright remains Eric Young`s, and as such any Copyright notices in
+ the code are not to be removed.
+ If this package is used in a product, Eric Young should be given attribution
+ as the author of the parts of the library used.
+ This can be in the form of a textual message at program startup or
+ in documentation (online or textual) provided with the package.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the copyright
+ notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ 3. All advertising materials mentioning features or use of this software
+ must display the following acknowledgement:
+ "This product includes cryptographic software written by
+ Eric Young (eay@cryptsoft.com)"
+ The word `cryptographic` can be left out if the rouines from the library
+ being used are not cryptographic related :-).
+ 4. If you include any Windows specific code (or a derivative thereof) from
+ the apps directory (application code) you must include an acknowledgement:
+ "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
+
+ THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS`` AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
+CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+ The licence and distribution terms for any publically available version or
+derivative of this code cannot be changed. i.e. this code cannot simply be copied and
+put under another distribution licence
+ [including the GNU Public Licence.]
+
+
+
+
+
+
+
+PD
+
+This is a placeholder for the Public Domain License
+
+
+
+Python-2.0
+
+
+PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
+--------------------------------------------
+
+1. This LICENSE AGREEMENT is between the Python Software Foundation
+("PSF"), and the Individual or Organization ("Licensee") accessing and
+otherwise using this software ("Python") in source or binary form and
+its associated documentation.
+
+2. Subject to the terms and conditions of this License Agreement, PSF
+hereby grants Licensee a nonexclusive, royalty-free, world-wide
+license to reproduce, analyze, test, perform and/or display publicly,
+prepare derivative works, distribute, and otherwise use Python
+alone or in any derivative version, provided, however, that PSF`s
+License Agreement and PSF`s notice of copyright, i.e., "Copyright (c)
+2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights
+Reserved" are retained in Python alone or in any derivative version
+prepared by Licensee.
+
+3. In the event Licensee prepares a derivative work that is based on
+or incorporates Python or any part thereof, and wants to make
+the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to Python.
+
+4. PSF is making Python available to Licensee on an "AS IS"
+basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
+FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
+A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
+OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+7. Nothing in this License Agreement shall be deemed to create any
+relationship of agency, partnership, or joint venture between PSF and
+Licensee. This License Agreement does not grant permission to use PSF
+trademarks or trade name in a trademark sense to endorse or promote
+products or services of Licensee, or any third party.
+
+8. By copying, installing or otherwise using Python, Licensee
+agrees to be bound by the terms and conditions of this License
+Agreement.
+
+BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
+-------------------------------------------
+
+BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
+
+1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
+office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
+Individual or Organization ("Licensee") accessing and otherwise using
+this software in source or binary form and its associated
+documentation ("the Software").
+
+2. Subject to the terms and conditions of this BeOpen Python License
+Agreement, BeOpen hereby grants Licensee a non-exclusive,
+royalty-free, world-wide license to reproduce, analyze, test, perform
+and/or display publicly, prepare derivative works, distribute, and
+otherwise use the Software alone or in any derivative version,
+provided, however, that the BeOpen Python License is retained in the
+Software, alone or in any derivative version prepared by Licensee.
+
+3. BeOpen is making the Software available to Licensee on an "AS IS"
+basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
+SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
+AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
+DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+5. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+6. This License Agreement shall be governed by and interpreted in all
+respects by the law of the State of California, excluding conflict of
+law provisions. Nothing in this License Agreement shall be deemed to
+create any relationship of agency, partnership, or joint venture
+between BeOpen and Licensee. This License Agreement does not grant
+permission to use BeOpen trademarks or trade names in a trademark
+sense to endorse or promote products or services of Licensee, or any
+third party. As an exception, the "BeOpen Python" logos available at
+http://www.pythonlabs.com/logos.html may be used according to the
+permissions granted on that web page.
+
+7. By copying, installing or otherwise using the software, Licensee
+agrees to be bound by the terms and conditions of this License
+Agreement.
+
+CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
+---------------------------------------
+
+1. This LICENSE AGREEMENT is between the Corporation for National
+Research Initiatives, having an office at 1895 Preston White Drive,
+Reston, VA 20191 ("CNRI"), and the Individual or Organization
+("Licensee") accessing and otherwise using Python 1.6.1 software in
+source or binary form and its associated documentation.
+
+2. Subject to the terms and conditions of this License Agreement, CNRI
+hereby grants Licensee a nonexclusive, royalty-free, world-wide
+license to reproduce, analyze, test, perform and/or display publicly,
+prepare derivative works, distribute, and otherwise use Python 1.6.1
+alone or in any derivative version, provided, however, that CNRI`s
+License Agreement and CNRI`s notice of copyright, i.e., "Copyright (c)
+1995-2001 Corporation for National Research Initiatives; All Rights
+Reserved" are retained in Python 1.6.1 alone or in any derivative
+version prepared by Licensee. Alternately, in lieu of CNRI`s License
+Agreement, Licensee may substitute the following text (omitting the
+quotes): "Python 1.6.1 is made available subject to the terms and
+conditions in CNRI`s License Agreement. This Agreement together with
+Python 1.6.1 may be located on the Internet using the following
+unique, persistent identifier (known as a handle): 1895.22/1013. This
+Agreement may also be obtained from a proxy server on the Internet
+using the following URL: http://hdl.handle.net/1895.22/1013".
+
+3. In the event Licensee prepares a derivative work that is based on
+or incorporates Python 1.6.1 or any part thereof, and wants to make
+the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to Python 1.6.1.
+
+4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
+basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
+1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
+A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
+OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+7. This License Agreement shall be governed by the federal
+intellectual property law of the United States, including without
+limitation the federal copyright law, and, to the extent such
+U.S. federal law does not apply, by the law of the Commonwealth of
+Virginia, excluding Virginia`s conflict of law provisions.
+Notwithstanding the foregoing, with regard to derivative works based
+on Python 1.6.1 that incorporate non-separable material that was
+previously distributed under the GNU General Public License (GPL), the
+law of the Commonwealth of Virginia shall govern this License
+Agreement only as to issues arising under or with respect to
+Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
+License Agreement shall be deemed to create any relationship of
+agency, partnership, or joint venture between CNRI and Licensee. This
+License Agreement does not grant permission to use CNRI trademarks or
+trade name in a trademark sense to endorse or promote products or
+services of Licensee, or any third party.
+
+8. By clicking on the "ACCEPT" button where indicated, or by copying,
+installing or otherwise using Python 1.6.1, Licensee agrees to be
+bound by the terms and conditions of this License Agreement.
+
+ACCEPT
+
+CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
+--------------------------------------------------
+
+Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
+The Netherlands. All rights reserved.
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted,
+provided that the above copyright notice appear in all copies and that
+both that copyright notice and this permission notice appear in
+supporting documentation, and that the name of Stichting Mathematisch
+Centrum or CWI not be used in advertising or publicity pertaining to
+distribution of the software without specific, written prior
+permission.
+
+STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
+THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
+FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
+OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+
+
+
+SAX-PD
+
+
+Copyright Status for SAX
+
+SAX is free!
+
+In fact, it`s not possible to own a license to SAX, since it`s been placed in the
+public domain.
+
+No Warranty
+
+Because SAX is released to the public domain, there is no warranty for the design or
+for the software implementation, to the extent permitted by applicable law. Except
+when otherwise stated in writing the copyright holders and/or other parties provide
+SAX "as is" without warranty of any kind, either expressed or implied, including, but
+not limited to, the implied warranties of merchantability and fitness for a particular
+purpose. The entire risk as to the quality and performance of SAX is with you. Should
+SAX prove defective, you assume the cost of all necessary servicing, repair or
+correction.
+
+In no event unless required by applicable law or agreed to in writing will any
+copyright holder, or any other party who may modify and/or redistribute SAX, be liable
+to you for damages, including any general, special, incidental or consequential
+damages arising out of the use or inability to use SAX (including but not limited to
+loss of data or data being rendered inaccurate or losses sustained by you or third
+parties or a failure of the SAX to operate with any other programs), even if such
+holder or other party has been advised of the possibility of such damages.
+
+Copyright Disclaimers
+
+This page includes statements to that effect by David Megginson, who would have been
+able to claim copyright for the original work.
+
+SAX 1.0
+
+Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of
+the XML-DEV mailing list, is hereby released into the public domain.
+
+No one owns SAX: you may use it freely in both commercial and non-commercial
+applications, bundle it with your software distribution, include it on a CD-ROM, list
+the source code in a book, mirror the documentation at your own web site, or use it in
+any other way you see fit.
+
+David Megginson, Megginson Technologies Ltd.
+1998-05-11
+
+SAX 2.0
+
+I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release
+all of the SAX 2.0 source code, compiled code, and documentation contained in this
+distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of
+fitness for any purpose.
+
+David Megginson, Megginson Technologies Ltd.
+2000-05-05
+
+
+
+
+SMAIL_GPL
+
+This is the Debian GNU/Linux package debianutils.
+
+It is an original Debian package. Programs in it were maintained by
+Guy Maor <maor@debian.org>, and are now maintained by Clint Adams
+<schizo@debian.org>.
+
+All its programs except readlink, savelog, and which may be
+redistributed under the terms of the GNU GPL, Version 2 or later,
+found on Debian systems in the file /usr/share/common-licenses/GPL.
+
+which is in the public domain.
+
+readlink is Copyright (c) 1997 Kenneth Stailey, and may also be
+distributed under the terms of the BSD copyright.
+
+savelog may be redistributed under the following terms: (The rest of
+this file consists of savelog's distribution terms.)
+
+#ident "@(#)smail:RELEASE-3_2:COPYING,v 1.2 1996/06/14 18:59:10 woods Exp"
+
+ SMAIL GENERAL PUBLIC LICENSE
+ (Clarified 11 Feb 1988)
+
+ Copyright (C) 1988 Landon Curt Noll & Ronald S. Karr
+ Copyright (C) 1992 Ronald S. Karr
+ Copyleft (GNU) 1988 Landon Curt Noll & Ronald S. Karr
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license, but changing it is not allowed. You can also
+ use this wording to make the terms for other programs.
+
+ The license agreements of most software companies keep you at the
+mercy of those companies. By contrast, our general public license is
+intended to give everyone the right to share SMAIL. To make sure that
+you get the rights we want you to have, we need to make restrictions
+that forbid anyone to deny you these rights or to ask you to surrender
+the rights. Hence this license agreement.
+
+ Specifically, we want to make sure that you have the right to give
+away copies of SMAIL, that you receive source code or else can get it
+if you want it, that you can change SMAIL or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To make sure that everyone has such rights, we have to forbid you to
+deprive anyone else of these rights. For example, if you distribute
+copies of SMAIL, you must give the recipients all the rights that you
+have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+ Also, for our own protection, we must make certain that everyone
+finds out that there is no warranty for SMAIL. If SMAIL is modified by
+someone else and passed on, we want its recipients to know that what
+they have is not what we distributed, so that any problems introduced
+by others will not reflect on our reputation.
+
+ Therefore we (Landon Curt Noll and Ronald S. Karr) make the following
+terms which say what you must do to be allowed to distribute or change
+SMAIL.
+
+
+ COPYING POLICIES
+
+ 1. You may copy and distribute verbatim copies of SMAIL source code
+as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy a valid copyright notice "Copyright
+(C) 1988 Landon Curt Noll & Ronald S. Karr" (or with whatever year is
+appropriate); keep intact the notices on all files that refer to this
+License Agreement and to the absence of any warranty; and give any
+other recipients of the SMAIL program a copy of this License
+Agreement along with the program. You may charge a distribution fee
+for the physical act of transferring a copy.
+
+ 2. You may modify your copy or copies of SMAIL or any portion of it,
+and copy and distribute such modifications under the terms of
+Paragraph 1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating
+ that you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish,
+ that in whole or in part contains or is a derivative of SMAIL or
+ any part thereof, to be licensed at no charge to all third
+ parties on terms identical to those contained in this License
+ Agreement (except that you may choose to grant more extensive
+ warranty protection to some or all third parties, at your option).
+
+ c) You may charge a distribution fee for the physical act of
+ transferring a copy, and you may at your option offer warranty
+ protection in exchange for a fee.
+
+Mere aggregation of another unrelated program with this program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other program under the scope of these terms.
+
+ 3. You may copy and distribute SMAIL (or a portion or derivative of it,
+under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+ a) accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal
+ shipping charge) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for non-commercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+For an executable file, complete source code means all the source code for
+all modules it contains; but, as a special exception, it need not include
+source code for modules which are standard libraries that accompany the
+operating system on which the executable file runs.
+
+ 4. You may not copy, sublicense, distribute or transfer SMAIL
+except as expressly provided under this License Agreement. Any attempt
+otherwise to copy, sublicense, distribute or transfer SMAIL is void and
+your rights to use the program under this License agreement shall be
+automatically terminated. However, parties who have received computer
+software programs from you with this License Agreement will not have
+their licenses terminated so long as such parties remain in full compliance.
+
+ 5. If you wish to incorporate parts of SMAIL into other free
+programs whose distribution conditions are different, write to Landon
+Curt Noll & Ronald S. Karr via the Free Software Foundation at 51
+Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. We have not yet
+worked out a simple rule that can be stated here, but we will often
+permit this. We will be guided by the two goals of preserving the
+free status of all derivatives of our free software and of promoting
+the sharing and reuse of software.
+
+Your comments and suggestions about our licensing policies and our
+software are welcome! This contract was based on the contract made by
+the Free Software Foundation. Please contact the Free Software
+Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
+USA, or call (617) 542-5942 for details on copylefted material in
+general.
+
+ NO WARRANTY
+
+ BECAUSE SMAIL IS LICENSED FREE OF CHARGE, WE PROVIDE ABSOLUTELY NO
+WARRANTY, TO THE EXTENT PERMITTED BY APPLICABLE STATE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING, LANDON CURT NOLL & RONALD S. KARR AND/OR
+OTHER PARTIES PROVIDE SMAIL "AS IS" WITHOUT WARRANTY OF ANY KIND,
+EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF SMAIL IS WITH
+YOU. SHOULD SMAIL PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
+NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL LANDON CURT NOLL &
+RONALD S. KARR AND/OR ANY OTHER PARTY WHO MAY MODIFY AND REDISTRIBUTE
+SMAIL AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+LOST PROFITS, LOST MONIES, OR OTHER SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
+(INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
+INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE
+PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) SMAIL, EVEN IF YOU HAVE
+BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY
+ANY OTHER PARTY.
+
+
+
+SUN
+
+SUN MICROSYSTEMS, INC. THROUGH ITS SUN MICROSYSTEMS LABORATORIES
+DIVISION ("SUN") WILL LICENSE THIS SOFTWARE AND THE ACCOMPANYING
+DOCUMENTATION TO YOU (a "Licensee") ONLY ON YOUR ACCEPTANCE OF ALL
+THE TERMS SET FORTH BELOW.
+
+Sun grants Licensee a non-exclusive, royalty-free right to download,
+install, compile, use, copy and distribute the Software, modify or
+otherwise create derivative works from the Software (each, a
+"Modification") and distribute any Modification in source code and/or
+binary code form to its customers with a license agreement containing
+these terms and noting that the Software has been modified. The
+Software is copyrighted by Sun and other third parties and Licensee
+shall retain and reproduce all copyright and other notices presently
+on the Software. As between Sun and Licensee, Sun is the sole owner of
+all rights in and to the Software other than the limited rights
+granted to Licensee herein; Licensee will own its Modifications,
+expressly subject to Sun's continuing ownership of the
+Software. Licensee will, at its expense, defend and indemnify Sun and
+its licensors from and against any third party claims, including costs
+and reasonable attorneys' fees, and be wholly responsible for any
+liabilities arising out of or related to Licensee's development, use
+or distribution of the Software or Modifications. Any distribution of
+the Software and Modifications must comply with all applicable United
+States export control laws.
+
+THE SOFTWARE IS BEING PROVIDED TO LICENSEE "AS IS" AND ALL EXPRESS OR
+IMPLIED CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
+ARE DISCLAIMED. IN NO EVENT WILL SUN BE LIABLE HEREUNDER FOR ANY
+DIRECT DAMAGES OR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES OF ANY KIND.
+
+
+
+Sleepycat
+
+
+The Sleepycat License
+Copyright (c) 1990-1999
+Sleepycat Software. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Redistributions in any form must be accompanied by information on
+how to obtain complete source code for the DB software and any
+accompanying software that uses the DB software. The source code
+must either be included in the distribution or be available for no
+more than the cost of distribution plus a nominal fee, and must be
+freely redistributable under reasonable conditions. For an
+executable file, complete source code means the source code for all
+modules it contains. It does not include source code for modules or
+files that typically accompany the major components of the operating
+system on which the executable file runs.
+THIS SOFTWARE IS PROVIDED BY SLEEPYCAT SOFTWARE ``AS IS`` AND ANY EXPRESS
+OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
+NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL SLEEPYCAT SOFTWARE
+BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGE.
+
+Copyright (c) 1990, 1993, 1994, 1995
+The Regents of the University of California. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Neither the name of the University nor the names of its contributors
+may be used to endorse or promote products derived from this software
+without specific prior written permission.
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS`` AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+Copyright (c) 1995, 1996
+The President and Fellows of Harvard University. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Neither the name of the University nor the names of its contributors
+may be used to endorse or promote products derived from this software
+without specific prior written permission.
+THIS SOFTWARE IS PROVIDED BY HARVARD AND ITS CONTRIBUTORS ``AS IS`` AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL HARVARD OR ITS CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+
+
+
+UCB
+
+ Copyright (c) 1987, 1989, 1990, 1991, 1992, 1993, 1994
+ The Regents of the University of California. All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ 3. Neither the name of the University nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ SUCH DAMAGE.
+
+
+
+Unicode
+
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright 1991-2015 Unicode, Inc. All rights reserved.
+Distributed under the Terms of Use in
+http://www.unicode.org/copyright.html.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Unicode data files and any associated documentation
+(the "Data Files") or Unicode software and any associated documentation
+(the "Software") to deal in the Data Files or Software
+without restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, and/or sell copies of
+the Data Files or Software, and to permit persons to whom the Data Files
+or Software are furnished to do so, provided that
+(a) this copyright and permission notice appear with all copies
+of the Data Files or Software,
+(b) this copyright and permission notice appear in associated
+documentation, and
+(c) there is clear notice in each modified Data File or in the Software
+as well as in the documentation associated with the Data File(s) or
+Software that the data or software has been modified.
+
+THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
+ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT OF THIRD PARTY RIGHTS.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
+NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
+DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
+DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+PERFORMANCE OF THE DATA FILES OR SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder
+shall not be used in advertising or otherwise to promote the sale,
+use or other dealings in these Data Files or Software without prior
+written authorization of the copyright holder.
+
+
+
+W3C
+
+
+W3C SOFTWARE NOTICE AND LICENSE
+This work (and included software, documentation such as READMEs, or other related
+items) is being provided by the copyright holders under the following license.
+License
+By obtaining, using and/or copying this work, you (the licensee) agree that you have
+read, understood, and will comply with the following terms and conditions.
+Permission to copy, modify, and distribute this software and its documentation, with
+or without modification, for any purpose and without fee or royalty is hereby granted,
+provided that you include the following on ALL copies of the software and
+documentation or portions thereof, including modifications:
+The full text of this NOTICE in a location viewable to users of the redistributed or
+derivative work.
+Any pre-existing intellectual property disclaimers, notices, or terms and conditions.
+If none exist, the W3C Software Short Notice should be included (hypertext is
+preferred, text is permitted) within the body of any redistributed or derivative code.
+Notice of any changes or modifications to the files, including the date changes were
+made. (We recommend you provide URIs to the location from which the code is derived.)
+Disclaimers
+THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
+REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
+WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF
+THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
+TRADEMARKS OR OTHER RIGHTS.
+COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
+The name and trademarks of copyright holders may NOT be used in advertising or
+publicity pertaining to the software without specific, written prior permission. Title
+to copyright in this software and any associated documentation will at all times
+remain with copyright holders.
+Notes
+This version: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
+This formulation of W3C`s notice and license became active on December 31 2002. This
+version removes the copyright ownership notice such that this license can be used with
+materials other than those owned by the W3C, reflects that ERCIM is now a host of the
+W3C, includes references to this specific dated version of the license, and removes
+the ambiguous grant of "use". Otherwise, this version is the same as the previous
+version and is written so as to preserve the Free Software Foundation`s assessment of
+GPL compatibility and OSI`s certification under the Open Source Definition.
+
+
+
+
+ZPL-2.1
+
+
+ZPL 2.1
+Zope Public License (ZPL) Version 2.1
+
+A copyright notice accompanies this license document that identifies the copyright
+holders.
+
+This license has been certified as open source. It has also been designated as GPL
+compatible by the Free Software Foundation (FSF).
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions in source code must retain the accompanying copyright notice, this
+list of conditions, and the following disclaimer.
+Redistributions in binary form must reproduce the accompanying copyright notice, this
+list of conditions, and the following disclaimer in the documentation and/or other
+materials provided with the distribution.
+Names of the copyright holders must not be used to endorse or promote products derived
+from this software without prior written permission from the copyright holders.
+The right to distribute this software or to use it for any purpose does not give you
+the right to use Servicemarks (sm) or Trademarks (tm) of the copyright holders. Use of
+them is covered by separate agreement with the copyright holders.
+If any files are modified, you must cause the modified files to carry prominent
+notices stating that you changed the files and the date of any change.
+Disclaimer
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS`` AND ANY EXPRESSED OR
+IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
+THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+Zlib
+
+
+zlib License
+
+
+ This software is provided `as-is`, without any express or implied
+ warranty. In no event will the authors be held liable for any damages
+ arising from the use of this software.
+
+ Permission is granted to anyone to use this software for any purpose,
+ including commercial applications, and to alter it and redistribute it
+ freely, subject to the following restrictions:
+
+ 1. The origin of this software must not be misrepresented; you must not
+ claim that you wrote the original software. If you use this software
+ in a product, an acknowledgment in the product documentation would be
+ appreciated but is not required.
+ 2. Altered source versions must be plainly marked as such, and must not be
+ misrepresented as being the original software.
+ 3. This notice may not be removed or altered from any source distribution.
+
+
+
+
+
+copyleft-next-0.3.0
+
+ copyleft-next 0.3.0 ("this License")
+ Release date: 2013-05-16
+
+1. License Grants; No Trademark License
+
+ Subject to the terms of this License, I grant You:
+
+ a) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
+ copyright license, to reproduce, Distribute, prepare derivative works
+ of, publicly perform and publicly display My Work.
+
+ b) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
+ patent license under Licensed Patents to make, have made, use, sell,
+ offer for sale, and import Covered Works.
+
+ This License does not grant any rights in My name, trademarks, service
+ marks, or logos.
+
+2. Distribution: General Conditions
+
+ You may Distribute Covered Works, provided that You (i) inform
+ recipients how they can obtain a copy of this License; (ii) satisfy the
+ applicable conditions of sections 3 through 6; and (iii) preserve all
+ Legal Notices contained in My Work (to the extent they remain
+ pertinent). "Legal Notices" means copyright notices, license notices,
+ license texts, and author attributions, but does not include logos,
+ other graphical images, trademarks or trademark legends.
+
+3. Conditions for Distributing Derived Works; Outbound GPL Compatibility
+
+ If You Distribute a Derived Work, You must license the entire Derived
+ Work as a whole under this License, with prominent notice of such
+ licensing. This condition may not be avoided through such means as
+ separate Distribution of portions of the Derived Work. You may
+ additionally license the Derived Work under the GPL, so that the
+ recipient may further Distribute the Derived Work under either this
+ License or the GPL.
+
+4. Condition Against Further Restrictions; Inbound License Compatibility
+
+ When Distributing a Covered Work, You may not impose further
+ restrictions on the exercise of rights in the Covered Work granted under
+ this License. This condition is not excused merely because such
+ restrictions result from Your compliance with conditions or obligations
+ extrinsic to this License (such as a court order or an agreement with a
+ third party).
+
+ However, You may Distribute a Covered Work incorporating material
+ governed by a license that is both OSI-Approved and FSF-Free as of the
+ release date of this License, provided that Your Distribution complies
+ with such other license.
+
+5. Conditions for Distributing Object Code
+
+ You may Distribute an Object Code form of a Covered Work, provided that
+ you accompany the Object Code with a URL through which the Corresponding
+ Source is made available, at no charge, by some standard or customary
+ means of providing network access to source code.
+
+ If you Distribute the Object Code in a physical product or tangible
+ storage medium ("Product"), the Corresponding Source must be available
+ through such URL for two years from the date of Your most recent
+ Distribution of the Object Code in the Product. However, if the Product
+ itself contains or is accompanied by the Corresponding Source (made
+ available in a customarily accessible manner), You need not also comply
+ with the first paragraph of this section.
+
+ Each recipient of the Covered Work from You is an intended third-party
+ beneficiary of this License solely as to this section 5, with the right
+ to enforce its terms.
+
+6. Symmetrical Licensing Condition for Upstream Contributions
+
+ If You Distribute a work to Me specifically for inclusion in or
+ modification of a Covered Work (a "Patch"), and no explicit licensing
+ terms apply to the Patch, You license the Patch under this License, to
+ the extent of Your copyright in the Patch. This condition does not
+ negate the other conditions of this License, if applicable to the Patch.
+
+7. Nullification of Copyleft/Proprietary Dual Licensing
+
+ If I offer to license, for a fee, a Covered Work under terms other than
+ a license that is OSI-Approved or FSF-Free as of the release date of this
+ License or a numbered version of copyleft-next released by the
+ Copyleft-Next Project, then the license I grant You under section 1 is no
+ longer subject to the conditions in sections 2 through 5.
+
+8. Copyleft Sunset
+
+ The conditions in sections 2 through 5 no longer apply once fifteen
+ years have elapsed from the date of My first Distribution of My Work
+ under this License.
+
+9. Pass-Through
+
+ When You Distribute a Covered Work, the recipient automatically receives
+ a license to My Work from Me, subject to the terms of this License.
+
+10. Termination
+
+ Your license grants under section 1 are automatically terminated if You
+
+ a) fail to comply with the conditions of this License, unless You cure
+ such noncompliance within thirty days after becoming aware of it, or
+
+ b) initiate a patent infringement litigation claim (excluding
+ declaratory judgment actions, counterclaims, and cross-claims)
+ alleging that any part of My Work directly or indirectly infringes
+ any patent.
+
+ Termination of Your license grants extends to all copies of Covered
+ Works You subsequently obtain. Termination does not terminate the
+ rights of those who have received copies or rights from You subject to
+ this License.
+
+ To the extent permission to make copies of a Covered Work is necessary
+ merely for running it, such permission is not terminable.
+
+11. Later License Versions
+
+ The Copyleft-Next Project may release new versions of copyleft-next,
+ designated by a distinguishing version number ("Later Versions").
+ Unless I explicitly remove the option of Distributing Covered Works
+ under Later Versions, You may Distribute Covered Works under any Later
+ Version.
+
+** 12. No Warranty **
+** **
+** My Work is provided "as-is", without warranty. You bear the risk **
+** of using it. To the extent permitted by applicable law, each **
+** Distributor of My Work excludes the implied warranties of title, **
+** merchantability, fitness for a particular purpose and **
+** non-infringement. **
+
+** 13. Limitation of Liability **
+** **
+** To the extent permitted by applicable law, in no event will any **
+** Distributor of My Work be liable to You for any damages **
+** whatsoever, whether direct, indirect, special, incidental, or **
+** consequential damages, whether arising under contract, tort **
+** (including negligence), or otherwise, even where the Distributor **
+** knew or should have known about the possibility of such damages. **
+
+14. Severability
+
+ The invalidity or unenforceability of any provision of this License
+ does not affect the validity or enforceability of the remainder of
+ this License. Such provision is to be reformed to the minimum extent
+ necessary to make it valid and enforceable.
+
+15. Definitions
+
+ "Copyleft-Next Project" means the project that maintains the source
+ code repository at <https://gitorious.org/copyleft-next/> as of the
+ release date of this License.
+
+ "Corresponding Source" of a Covered Work in Object Code form means (i)
+ the Source Code form of the Covered Work; (ii) all scripts,
+ instructions and similar information that are reasonably necessary for
+ a skilled developer to generate such Object Code from the Source Code
+ provided under (i); and (iii) a list clearly identifying all Separate
+ Works (other than those provided in compliance with (ii)) that were
+ specifically used in building and (if applicable) installing the
+ Covered Work (for example, a specified proprietary compiler including
+ its version number). Corresponding Source must be machine-readable.
+
+ "Covered Work" means My Work or a Derived Work.
+
+ "Derived Work" means a work of authorship that copies from, modifies,
+ adapts, is based on, is a derivative work of, transforms, translates or
+ contains all or part of My Work, such that copyright permission is
+ required. The following are not Derived Works: (i) Mere Aggregation;
+ (ii) a mere reproduction of My Work; and (iii) if My Work fails to
+ explicitly state an expectation otherwise, a work that merely makes
+ reference to My Work.
+
+ "Distribute" means to distribute, transfer or make a copy available to
+ someone else, such that copyright permission is required.
+
+ "Distributor" means Me and anyone else who Distributes a Covered Work.
+
+ "FSF-Free" means classified as 'free' by the Free Software Foundation.
+
+ "GPL" means a version of the GNU General Public License or the GNU
+ Affero General Public License.
+
+ "I"/"Me"/"My" refers to the individual or legal entity that places My
+ Work under this License. "You"/"Your" refers to the individual or legal
+ entity exercising rights in My Work under this License. A legal entity
+ includes each entity that controls, is controlled by, or is under
+ common control with such legal entity. "Control" means (a) the power to
+ direct the actions of such legal entity, whether by contract or
+ otherwise, or (b) ownership of more than fifty percent of the
+ outstanding shares or beneficial ownership of such legal entity.
+
+ "Licensed Patents" means all patent claims licensable royalty-free by
+ Me, now or in the future, that are necessarily infringed by making,
+ using, or selling My Work, and excludes claims that would be infringed
+ only as a consequence of further modification of My Work.
+
+ "Mere Aggregation" means an aggregation of a Covered Work with a
+ Separate Work.
+
+ "My Work" means the particular work of authorship I license to You
+ under this License.
+
+ "Object Code" means any form of a work that is not Source Code.
+
+ "OSI-Approved" means approved as 'Open Source' by the Open Source
+ Initiative.
+
+ "Separate Work" means a work that is separate from and independent of a
+ particular Covered Work and is not by its nature an extension or
+ enhancement of the Covered Work, and/or a runtime library, standard
+ library or similar component that is used to generate an Object Code
+ form of a Covered Work.
+
+ "Source Code" means the preferred form of a work for making
+ modifications to it.
+
+
+
+tcl
+
+This software is copyrighted by the Regents of the University of
+California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
+Corporation and other parties. The following terms apply to all files
+associated with the software unless explicitly disclaimed in
+individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7014 (b) (3) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+
+
+
+ Proprietary Licenses
+
+Enea
+
+ Copyright (C) 2006 by Enea.
+ All rights reserved.
+
+ This Software is furnished under a software license agreement and
+ may be used only in accordance with the terms of such agreement.
+ Any other use or reproduction is prohibited. No title to and
+ ownership of the Software is hereby transferred.
+
+ PROPRIETARY NOTICE
+ This Software consists of confidential information.
+ Trade secret law and copyright law protect this Software.
+ The above notice of copyright on this Software does not indicate
+ any actual or intended publication of such Software.
+
+
+
+
--
cgit v1.2.3-54-g00ecf
From e55c3d2a23de3eac0ae2f312b27a478e041b48e8 Mon Sep 17 00:00:00 2001
From: iosc
Date: Fri, 19 Mar 2021 13:07:53 +0100
Subject: USERDOCAP-636 - all books changes
Change-Id: I944098c2d726657c91edff3d62dc4a40fc8df8bb
Signed-off-by: iosc
---
doc/Makefile | 8 +-
.../doc/about.xml | 2 +-
.../doc/book.xml | 2 +-
.../doc/licenses.xml | 4 +-
.../swcomp.mk | 2 +-
.../book-enea-nfv-access-auto-fw-th-user-guide.pdf | Bin 0 -> 401538 bytes
.../doc/automation_framework_test_harness.xml | 364 ++++++++++-----------
.../doc/book.xml | 2 +-
.../doc/components.xml | 51 ++-
.../doc/getting_started.xml | 32 +-
.../doc/overview.xml | 23 +-
.../doc/troubleshooting_guide.xml | 4 +-
.../swcomp.mk | 2 +-
.../doc/128t_vnf_router.xml | 6 +-
.../doc/appendix_4.xml | 4 +-
.../doc/appendix_5.xml | 6 +-
.../doc/book.xml | 2 +-
.../doc/clav_vnf_examples.xml | 4 +-
.../doc/enea_test_vnf_examples.xml | 12 +-
.../doc/forti_vnf_examples.xml | 8 +-
.../doc/introduction.xml | 4 +-
.../doc/service_chaining_128t_fortigate.xml | 4 +-
.../doc/vnf_chaining.xml | 10 +-
.../swcomp.mk | 2 +-
.../doc/advanced_configurations.xml | 178 +++++-----
.../doc/book.xml | 2 +-
.../doc/grafana.xml | 209 ++++++------
.../doc/installation_guide.xml | 256 +++++++--------
.../doc/introduction.xml | 46 +--
.../doc/log_collector.xml | 46 +--
.../doc/net_config_options.xml | 123 +++----
.../doc/troubleshooting.xml | 74 ++---
.../doc/upgrade_ena.xml | 79 ++---
.../doc/vnf_mg.xml | 102 +++---
doc/book-enea-nfv-access-getting-started/swcomp.mk | 2 +-
.../doc/about.xml | 2 +-
.../doc/book.xml | 2 +-
.../doc/licenses.xml | 10 +-
.../swcomp.mk | 2 +-
.../doc/about_release.xml | 36 +-
doc/book-enea-nfv-access-release-info/doc/book.xml | 2 +-
.../doc/known_bugs_and_limitations.xml | 37 +--
.../doc/main_changes.xml | 45 ++-
doc/book-enea-nfv-access-release-info/swcomp.mk | 2 +-
.../doc/book.xml | 2 +-
.../doc/configuration.xml | 6 +-
.../doc/overview.xml | 14 +-
.../doc/sample_test_cases.xml | 153 +++++----
.../swcomp.mk | 2 +-
.../doc/about.xml | 2 +-
.../doc/book.xml | 2 +-
.../swcomp.mk | 2 +-
.../doc/about.xml | 2 +-
.../doc/book.xml | 2 +-
.../swcomp.mk | 2 +-
55 files changed, 1002 insertions(+), 1000 deletions(-)
create mode 100644 doc/book-enea-nfv-access-auto-fw-th-user-guide/book-enea-nfv-access-auto-fw-th-user-guide.pdf
(limited to 'doc/book-enea-nfv-access-platform-open-source')
diff --git a/doc/Makefile b/doc/Makefile
index a0956d4..1a415b3 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -26,8 +26,8 @@ include init.mk
#BUILDBOOT_XML := book-enea-nfv-access-release-info/doc/build_boot_generated.xml
#BUILDBOOT_TEMPLATE := book-enea-nfv-access-release-info/doc/build_boot_template.xml
-PKGDIFF_GEN_XML := book-enea-nfv-access-release-info/doc/pkgdiff_generated.xml
-JIRA_ISSUES_GEN_XML := book-enea-nfv-access-release-info/doc/jiraissues_generated.xml
+#PKGDIFF_GEN_XML := book-enea-nfv-access-release-info/doc/pkgdiff_generated.xml
+#JIRA_ISSUES_GEN_XML := book-enea-nfv-access-release-info/doc/jiraissues_generated.xml
MACHINE_LIST_XML := book-enea-nfv-access-release-info/doc/machine_list_generated.xml
@@ -50,7 +50,7 @@ DOCBOOK_TO_BOOKDIR ?= yes
DOCBOOK_CLEANTMP ?= yes
#Components (books) in this subsystem. Now use all books found here
-COMPONENTS := book-enea-nfv-access-auto-fw-th-open-source book-enea-nfv-access-auto-fw-th-user-guide book-enea-nfv-access-cmc-example-usecases book-enea-nfv-access-example-usecases book-enea-nfv-access-getting-started book-enea-nfv-access-platform-open-source book-enea-nfv-access-getting-started book-enea-nfv-access-ucpem-open-source book-enea-nfv-access-telemetry-open-source book-enea-nfv-access-release-info book-enea-nfv-access-system-test-specification book-enea-nfv-access-evalkit
+COMPONENTS := book-enea-nfv-access-auto-fw-th-open-source book-enea-nfv-access-auto-fw-th-user-guide book-enea-nfv-access-cmc-example-usecases book-enea-nfv-access-example-usecases book-enea-nfv-access-getting-started book-enea-nfv-access-platform-open-source book-enea-nfv-access-ucpem-open-source book-enea-nfv-access-telemetry-open-source book-enea-nfv-access-release-info book-enea-nfv-access-system-test-specification book-enea-nfv-access-evalkit book-enea-nfv-access-auto-fw-open-source book-enea-nfv-access-auto-fw-user-guide
# --------------------------------------------------------------
@@ -184,7 +184,7 @@ endif
books: init
# BOOKPACKAGES is defined in all book-*/swcomp.mk
$(VERB)DISTRO_VERSION=`egrep '"EneaLinux_REL_VER">' $(ELTF_PARAMS_UPDATED) | sed 's/.*//;s/<\/phrase>.*//'` ; \
- BOOKVER="Enea NFV Access-$$DISTRO_VERSION"-$(shell date +"%Y.%m.%d"); \
+ BOOKVER="Enea Edge-$$DISTRO_VERSION"-$(shell date +"%Y.%m.%d"); \
for book in $(BOOKPACKAGES); do \
for format in $(FORMAT); do \
$(MAKE) -f $(DOCBOOKMAKE)/make_docbook_standalone.mk BOOK=$$book FORMAT=$$format BOOK_VER="$$BOOKVER" books || exit 10; \
diff --git a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/about.xml b/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/about.xml
index dbf06e3..4dc19aa 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/about.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/about.xml
@@ -6,7 +6,7 @@
This document contains the open source and license information
pertaining to the Automation Framework and Test Harness provided with
- Enea NFV Access .
diff --git a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/book.xml b/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/book.xml
index 3305873..f849ad4 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/book.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access Automation Framework and Test Harness Open Source Report
+ Enea Edge Automation Framework and Test Harness Open Source Report
Release Version
- Configuration and Automation Framework for the uCPE Manager
+ Configuration and Automation Framework for the Edge Manager
GUI.
ENEA-SRC-R2
@@ -54,7 +54,7 @@
xmlns:xi="http://www.w3.org/2001/XInclude"
xpointer="element(EneaLinux_REL_VER/1)" />
- Configuration and Automation Framework for the uCPE Manager
+ Configuration and Automation Framework for the Edge Manager
GUI.
ENEA-EXAMPLE-R2
diff --git a/doc/book-enea-nfv-access-auto-fw-th-open-source/swcomp.mk b/doc/book-enea-nfv-access-auto-fw-th-open-source/swcomp.mk
index 2f2e677..702e86f 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-open-source/swcomp.mk
+++ b/doc/book-enea-nfv-access-auto-fw-th-open-source/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-auto-fw-th-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) AF&TH Open Source Report"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) AF&TH Open Source Report"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/book-enea-nfv-access-auto-fw-th-user-guide.pdf b/doc/book-enea-nfv-access-auto-fw-th-user-guide/book-enea-nfv-access-auto-fw-th-user-guide.pdf
new file mode 100644
index 0000000..5d601c1
Binary files /dev/null and b/doc/book-enea-nfv-access-auto-fw-th-user-guide/book-enea-nfv-access-auto-fw-th-user-guide.pdf differ
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
index 5e6ba24..a569d59 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
@@ -11,15 +11,15 @@
The /device folder contains Python scripts for
adding uCPE device(s), receiving uCPE events' reports, removing a uCPE
- device, waiting for a uCPE device to connect to the uCPE Manager, as well
+ device, waiting for a uCPE device to connect to the Enea Edge Management, as well
as scripts for adding and removing an offline configuration store. This
folder also contains scripts for uploading and removing an NFVA image into
- the uCPE Manager, and for installing and activating a NFVA image on a uCPE
+ the Enea Edge Management, and for installing and activating a NFVA image on a uCPE
Device.
The /customScripts folder contains Python scripts
- for uploading custom scripts onto the uCPE Manager and uCPE device(s), for
- removing custom scripts from the uCPE Manager and uCPE device(s).
+ for uploading custom scripts onto the Enea Edge Management and uCPE device(s), for
+ removing custom scripts from the Enea Edge Management and uCPE device(s).
The /network folder contains Python scripts for
binding or unbinding a network interface to and from a uCPE device (DPDK
@@ -79,7 +79,7 @@
the path to the file describing the test cases to be performed against
the designated script.
- Steps for running the Python unit-test suite on the uCPE Manager
+ Steps for running the Python unit-test suite on the Enea Edge Management
are provided below.
@@ -88,16 +88,16 @@
$ python unittestSuite.py -h
Usage: unittestSuite.py [options]
-Run selected unit-test suite against Enea uCPE Manager.
+Run selected unit-test suite against Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-n DEVICENAME, --deviceName=DEVICENAME
Name of vCPE device (Virtual Infrastructure Manager)
-s SUITEFILE, --suite=SUITEFILE
@@ -234,8 +234,8 @@ consoleLoggingLevel = logging.INFO
username
- The user authentication used to log into the uCPE
- Manager. This can be overwritten by setting the Python
+ The user authentication used to log into the
+ Enea Edge Management. This can be overwritten by setting the Python
unit-test suite command line option
-u .
@@ -243,7 +243,7 @@ consoleLoggingLevel = logging.INFO
password
- The password used to log into the uCPE Manager. This
+ The password used to log into the Enea Edge Management. This
can be overwritten by setting the Python unit-test suite
command line option -p .
@@ -251,7 +251,7 @@ consoleLoggingLevel = logging.INFO
host
- The IP address of the uCPE Manager host. This can be
+ The IP address of the Enea Edge Management host. This can be
overwritten by setting the Python unit-test suite command line
option -H .
@@ -540,7 +540,7 @@ OK
Adding a uCPE Device
Steps for adding, configuring and running a uCPE device onto the
- uCPE manager are described below .
+ Enea Edge Management are described below .
Script Options
@@ -548,16 +548,16 @@ OK
$ python addDevice.py -h
Usage: addDevice.py [options]
-Add a uCPE device in Enea uCPE Manager.
+Add a uCPE device in Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f DEVICEFILE, --file=DEVICEFILE
File containing uCPE Information in JSON format
@@ -615,7 +615,7 @@ Options:
2019-03-07 17:33:10,756 - INFO: Add uCPE device
2019-03-07 17:33:10,975 - DEBUG: Login successful on host 'localhost'
2019-03-07 17:33:10,979 - DEBUG: Session token is: 508b6ea2-40ee-11e9-a81f525400d08e1d
-2019-03-07 17:33:11,049 - DEBUG: Add new device 'intelc3850-2' to uCPE Manager host
+2019-03-07 17:33:11,049 - DEBUG: Add new device 'intelc3850-2' to Enea Edge Management host
2019-03-07 17:33:11,483 - INFO: Done
2019-03-07 17:33:11,501 - DEBUG: Logging out and exiting....
@@ -624,7 +624,7 @@ Options:
Removing a uCPE Device
- Steps for removing a uCPE device from the uCPE manager are
+ Steps for removing a uCPE device from the Enea Edge Management are
described below.
@@ -633,16 +633,16 @@ Options:
$ python removeDevice.py -h
Usage: removeDevice.py [options]
-Remove a uCPE from Enea uCPE Manager.
+Remove a uCPE from Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f DEVICEFILE, --file=DEVICEFILE
File containing uCPE Information in JSON format
@@ -689,7 +689,7 @@ Options:
2019-03-07 17:33:56,835 - INFO: Remove uCPE device
2019-03-07 17:33:56,856 - DEBUG: Login successful on host 'localhost'
2019-03-07 17:33:56,856 - DEBUG: Session token is: 6bebcb43-40ee-11e9-a81f525400d08e1d
-2019-03-07 17:33:56,856 - DEBUG: Delete device 'intelc3850-2' from uCPE Manager
+2019-03-07 17:33:56,856 - DEBUG: Delete device 'intelc3850-2' from Enea Edge Management
host
2019-03-07 17:33:56,875 - DEBUG: Found device with name 'intelc3850-2'
2019-03-07 17:33:57,159 - INFO: Done
@@ -701,7 +701,7 @@ host
Waiting a uCPE Device
Steps and details for how to Wait a uCPE device to connect to the
- uCPE Manager after installation, are described below.
+ Enea Edge Management after installation, are described below.
Script Options
@@ -709,16 +709,16 @@ host
$ python waitDeviceUp.py -h
Usage: waitDeviceUp.py [options]
-Wait for uCPE to connect to the Enea uCPE Manager after installation.
+Wait for uCPE to connect to the Enea Edge Management after installation.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f DEVICEFILE, --file=DEVICEFILE
File containing uCPE Information in JSON format
-t TIMEOUT, --timeout=TIMEOUT
@@ -779,7 +779,7 @@ Options:
Printing the uCPE Device Log
Steps and details on how to Print the events log for a specific
- uCPE device installed in the uCPE Manager, are explained below.
+ uCPE device installed in the Enea Edge Management, are explained below.
Script Options
@@ -787,14 +787,14 @@ Options:
$ python getEventsForUcpe.py -h
Usage: getEventsForUcpe.py [options]
-Print the events log for a specific uCPE installed in Enea uCPE Manager.
+Print the events log for a specific uCPE installed in Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
--u USERNAME, --username=USERNAME Enea uCPE Manager login username
--p PASSWORD, --password=PASSWORD Enea uCPE Manager login password
--H HOST, --host=HOST Enea uCPE Manager host name or IP address
+-u USERNAME, --username=USERNAME Enea Edge Management login username
+-p PASSWORD, --password=PASSWORD Enea Edge Management login password
+-H HOST, --host=HOST Enea Edge Management host name or IP address
-f DEVICEFILE, --file=DEVICEFILE File containing uCPE Information in JSON format
-s SEVERITY, --severity=SEVERITY Event severity level (Critical|Major|Minor)
@@ -869,10 +869,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-s STATE, --state=STATE
Enable/Disable
-n DEVICENAME, --device-name=DEVICENAME
@@ -936,10 +936,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f NICFILE, --file=NICFILE
File containing network interface Information in JSON
format
@@ -1042,10 +1042,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f NICFILE, --file=NICFILE
File containing network interface Information in JSON
format
@@ -1131,9 +1131,9 @@ Usage: getNetworkInterfaces.py [options]
Options:
--version show program's version number and exit
-h, --help show this help message and exit
- -u USERNAME, --username=USERNAME Enea uCPE Manager login username
- -p PASSWORD, --password=PASSWORD Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ -u USERNAME, --username=USERNAME Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-n DEVICENAME, --device-name=DEVICENAME Name of the uCPE to get network /
interfaces from
@@ -1215,10 +1215,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f OVSFILE, --file=OVSFILE
File containing OVS bridge Information in JSON format
-n DEVICENAME, --device-name=DEVICENAME
@@ -1306,10 +1306,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f OVSFILE, --file=OVSFILE
File containing OVS bridge Information in JSON format
-n DEVICENAME, --device-name=DEVICENAME
@@ -1380,7 +1380,7 @@ Options:
Onboarding a VNF Image Raw
- How to Onboard a VNF image in the uCPE Manager based upon its raw
+ How to Onboard a VNF image in the Enea Edge Management based upon its raw
constituents, is detailed in depth below.
@@ -1389,16 +1389,16 @@ Options:
$ python onboardVNFRaw.py -h
Usage: onboardVNFRaw.py [options]
-Onboard a VNF in Enea uCPE Manager based upon its raw constituents.
+Onboard a VNF in Enea Edge Management based upon its raw constituents.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f FTPUSERNAME, --ftpUsername=FTPUSERNAME
Username for FTP
-w FTPPASSWORD, --ftpPassword=FTPPASSWORD
@@ -1497,7 +1497,7 @@ Options:
Offboarding a VNF
- Steps on how to Offboard a VNF from the uCPE Manager are detailed
+ Steps on how to Offboard a VNF from the Enea Edge Management are detailed
below.
@@ -1506,16 +1506,16 @@ Options:
$ python offboardVNF.py -h
Usage: offboardVNF.py [options]
-Offboard a VNF from Enea uCPE Manager.
+Offboard a VNF from Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-n VNFDNAME, --vnfdName=VNFDNAME
Name of VNF descriptor to offboard
@@ -1563,7 +1563,7 @@ Options:
Instantiating a VNF
- Instantiating a VNF via the uCPE Manager is detailed below.
+ Instantiating a VNF via the Enea Edge Management is detailed below.
Script Options
@@ -1571,16 +1571,16 @@ Options:
$ python instantiateVNFI.py -h
Usage: instantiateVNFI.py [options]
-Instantiate a VNF via Enea uCPE Manager.
+Instantiate a VNF via Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-t VNFTYPE, --vnfType=VNFTYPE
VNF Type (Name of VNF descriptor)
-n VIMDEVICENAME, --device-name=VIMDEVICENAME
@@ -1642,7 +1642,7 @@ License("vnf_config/fortigateImage/fortigateLicense.lic")
Controlling a VNF Instance
- How to Control a VNF instance from the Enea uCPE Manager is
+ How to Control a VNF instance from the Enea Edge Management is
detailed below.
@@ -1651,7 +1651,7 @@ License("vnf_config/fortigateImage/fortigateLicense.lic")
become unresponsive. Depending on the actual VNF, the time required
between life-cycle operations may vary from several seconds to half a
minute or even more. If a VNF becomes unresponsive, the only possible
- action is to "Force Delete" the instance from the uCPE Manager.
+ action is to "Force Delete" the instance from the Enea Edge Management.
@@ -1660,16 +1660,16 @@ License("vnf_config/fortigateImage/fortigateLicense.lic")
$ python controlVNFI.py -h
Usage: controlVNFI.py [options]
-Controls a VNF instance from Enea uCPE Manager.
+Controls a VNF instance from Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-i VNFINSTANCENAME, --vnfInstanceName=VNFINSTANCENAME
Name of VNF instance
-n VIMDEVICENAME, --device-name=VIMDEVICENAME
@@ -1736,7 +1736,7 @@ fortigateFWInstance -c stop
Destroying a VNF Instance
Steps and options on how to Destroy a VNF instance from the Enea
- uCPE Manager are described below.
+ Edge Management are described below.
Script Options
@@ -1744,16 +1744,16 @@ fortigateFWInstance -c stop
$ python destroyVNFI.py -h
Usage: destroyVNFI.py [options]
-Destroys a VNF instance from Enea uCPE Manager.
+Destroys a VNF instance from Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-i VNFINSTANCENAME, --vnfInstanceName=VNFINSTANCENAME
Name of VNF instance
-n VIMDEVICENAME, --device-name=VIMDEVICENAME
@@ -1801,28 +1801,28 @@ fortigateFWInstance
- Uploading a NFV Access image onto the Enea uCPE Manager
+ Uploading a Enea Edge image onto the Enea Edge Management
- Steps and options on how to Upload a NFV Access image onto the
- Enea uCPE Manager are described below.
+ Steps and options on how to Upload a Enea Edge image onto the
+ Enea Edge Management are described below.
Script Options
$ python uploadImage.py -h
-Upload NFVA image on uCPE Manager
+Upload NFVA image on Enea Edge Management
Usage: uploadImage.py [options]
-Upload NFVA image on uCPE Manager.
+Upload NFVA image on Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f FILENAME, --fileName=FILENAME
Path to NFVA image file name
-m MODULE, --module=MODULE
@@ -1838,7 +1838,7 @@ Options:
Configuring the JSON File
- The JSON configuration file needed to upload a NFV Access image
+ The JSON configuration file needed to upload a Enea Edge image
should contain a list of dictionaries. Each dictionary indicates the
test case name and the test case arguments passed to the
uploadImage Python module.
@@ -1846,7 +1846,7 @@ Options:
Sample unit-test JSON file
format: [
{
- "name": "Upload NFVA image on uCPE Manager",
+ "name": "Upload NFVA image on Enea Edge Management",
"args": "-f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d"
}
]
@@ -1861,7 +1861,7 @@ Options:
$ python uploadImage.py -u admin -p admin -H localhost \
-f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d
2020-02-28 11:38:42,754 - DEBUG: Started logging
-2020-02-28 11:38:42,755 - INFO: Upload NFVA image on uCPE Manager
+2020-02-28 11:38:42,755 - INFO: Upload NFVA image on Enea Edge Management
2020-02-28 11:38:43,307 - DEBUG: Login successful on host 'localhost'
2020-02-28 11:38:43,308 - DEBUG: Session token is: 7da3f960-5a16-11ea-a3de-5652b3ac1c30
2020-02-28 11:41:29,148 - INFO: Verify image validation flag
@@ -1874,29 +1874,29 @@ Options:
- Deleting a NFV Access image file from the Enea uCPE
- Manager
+ Deleting a Enea Edge image file from the
+ Enea Edge Management
- Steps and options on how to Delete a NFV Access image from the
- Enea uCPE Manager are described below.
+ Steps and options on how to Delete a Enea Edge image from the
+ Enea Edge Management are described below.
Script Options
$ python deleteUpgradeFile.py -h
-Delete NFVA image from uCPE Manager
+Delete NFVA image from Enea Edge Management
Usage: deleteUpgradeFile.py [options]
-Delete NFVA image from uCPE Manager.
+Delete NFVA image from Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-i IMAGENAME, --imageName=IMAGENAME
NFVA Image name
-m MODULE, --module=MODULE
@@ -1909,7 +1909,7 @@ Options:
Configuring the JSON File
- The JSON configuration file needed to delete a NFV Access image
+ The JSON configuration file needed to delete a Enea Edge image
should contain a list of dictionaries. Each dictionary indicates the
test case name and the test case arguments passed to the
deleteUpgradeFile Python module.
@@ -1917,7 +1917,7 @@ Options:
Sample unit-test JSON file
format: [
{
- "name": "Delete NFVA image on uCPE Manager",
+ "name": "Delete NFVA image on Enea Edge Management",
"args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2"
}
]
@@ -1932,7 +1932,7 @@ Options:
$ python deleteUpgradeFile.py -u admin -p admin -H localhost -i \
enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
2020-02-28 12:06:20,111 - DEBUG: Started logging
-2020-02-28 12:06:20,112 - INFO: Delete NFVA image from uCPE Manager
+2020-02-28 12:06:20,112 - INFO: Delete NFVA image from Enea Edge Management
2020-02-28 12:06:20,210 - DEBUG: Login successful on host 'localhost'
2020-02-28 12:06:20,211 - DEBUG: Session token is: 594b2d50-5a1a-11ea-a3de-5652b3ac1c30
2020-02-28 12:06:20,255 - INFO: The image \
@@ -1948,30 +1948,30 @@ image was successfully removed
- Installing and activating a NFV Access image on an uCPE device
- from the Enea uCPE Manager
+ Installing and activating a Enea Edge image on an uCPE device
+ from the Enea Edge Management
- Steps and options on how to Install and Activate a NFV Access
- image on an uCPE device from the Enea uCPE Manager are described
+ Steps and options on how to Install and Activate a Enea Edge
+ image on an uCPE device from the Enea Edge Management are described
below.
Script Options
$ python installAndActivate.py -h
-Install and activate NFVA image from uCPE Manager
+Install and activate NFVA image from Enea Edge Management
Usage: installAndActivate.py [options]
-Install and activate NFVA image from uCPE Manager.
+Install and activate NFVA image from Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-i IMAGENAME, --imageName=IMAGENAME
Image name
-m MODULE, --module=MODULE
@@ -1989,8 +1989,8 @@ Options:
Configuring the JSON File
- The JSON configuration file needed to install and activate a NFV
- Access image on a uCPE device from the Enea uCPE Manager should
+ The JSON configuration file needed to install and activate a Enea Edge
+ image on a uCPE device from the Enea Edge Management should
contain a list of dictionaries. Each dictionary indicates the test
case name and the test case arguments passed to the
installAndActivate Python module.
@@ -2000,7 +2000,7 @@ Options:
[
{
- "name": "Install and activate NFVA image on uCPE device from uCPE Manager",
+ "name": "Install and activate NFVA image on uCPE device from Enea Edge Management",
"args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16"
}
]
@@ -2015,7 +2015,7 @@ Options:
$ python installAndActivate.py -u admin -p admin -H localhost -i \
enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16
2020-02-28 12:36:46,137 - DEBUG: Started logging
-2020-02-28 12:36:46,138 - INFO: Install and activate NFVA image from uCPE Manager
+2020-02-28 12:36:46,138 - INFO: Install and activate NFVA image from Enea Edge Management
2020-02-28 12:36:46,288 - DEBUG: Login successful on host 'localhost'
2020-02-28 12:36:46,288 - DEBUG: Session token is: 99b7cde0-5a1e-11ea-a3de-5652b3ac1c30
2020-02-28 12:36:46,325 - DEBUG: Found device with name 'inteld1521-16'
@@ -2055,10 +2055,10 @@ enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [20]
Clearing information about completed upgrades of uCPE devices
- from the Enea uCPE Manager
+ from the Enea Edge Management
Steps and options on how to clear information about completed
- upgrades of uCPE devices from the Enea uCPE Manager are described
+ upgrades of uCPE devices from the Enea Edge Management are described
below.
@@ -2074,10 +2074,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
Mandatory options:
-H/--host
@@ -2087,7 +2087,7 @@ Options:
Configuring the JSON File
No JSON configuration file is needed to clear information about
- completed upgrades of uCPE devices from the Enea uCPE Manager. The
+ completed upgrades of uCPE devices from the Enea Edge Management. The
clearCompletedUpgradesInfo Python module can be
run without a JSON file as a parameter.
@@ -2110,10 +2110,10 @@ Options:
- Uploading a Custom Script to the uCPE Manager
+ Uploading a Custom Script to the Enea Edge Management
- Steps and options on how to upload a custom script to the uCPE
- Manager are described below.
+ Steps and options on how to upload a custom script to the
+ Enea Edge Management are described below.
Script Options
@@ -2122,16 +2122,16 @@ Options:
2020-04-14 10:26:23,582 - INFO: Upload Custom Script
Usage: upload.py [options]
-Add a Custom Script to Enea uCPE Manager
+Add a Custom Script to Enea Edge Management
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-f CUSTOMSCRIPT, --file=CUSTOMSCRIPT
Custom Script File
-e PHASE, --phase=PHASE
@@ -2147,7 +2147,7 @@ Options:
Configuring the JSON File
The JSON configuration file needed to upload a Custom Script to
- the uCPE Manager must contain a list of dictionaries. Each dictionary
+ the Enea Edge Management must contain a list of dictionaries. Each dictionary
indicates the test case name and the test case arguments passed to the
customScripts/upload Python module.
@@ -2156,7 +2156,7 @@ Options:
[
{
- "name": "Uploading a Custom Script to the uCPE Manager",
+ "name": "Uploading a Custom Script to the Enea Edge Management",
"args": "-f ../../lab_config/customScripts/test_success_after_always \
-e always-after-startup"
}
@@ -2175,7 +2175,7 @@ Options:
2020-04-14 14:08:02,915 - INFO: Upload Custom Script
2020-04-14 14:08:02,994 - DEBUG: Login successful on host '172.24.3.109'
2020-04-14 14:08:02,995 - DEBUG: Session token is: 97544990-7e48-11ea-835c-02423a1c239f
-2020-04-14 14:08:02,996 - DEBUG: Upload test_success_after_always to uCPE Manager. \
+2020-04-14 14:08:02,996 - DEBUG: Upload test_success_after_always to Enea Edge Management. \
Content: #!/bin/bash
echo test_success_after_always
2020-04-14 14:08:03,138 - INFO: Done
@@ -2184,11 +2184,11 @@ echo test_success_after_always
- Uploading a Custom Script from the uCPE Manager to a
+ Uploading a Custom Script from the Enea Edge Management to a
Device
- Steps and options on how to upload a custom script from the uCPE
- Manager to a Device are described below.
+ Steps and options on how to upload a custom script from the
+ Enea Edge Management to a Device are described below.
Script Options
@@ -2203,12 +2203,12 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
- Custom Script Name that resides on Enea uCPE Manager
+ Custom Script Name that resides on Enea Edge Management
-e PHASE, --phase=PHASE
Execution phase. Must be one of the following: once-
before-startup | always-before-startup | once-after-
@@ -2225,7 +2225,7 @@ Options:
Configuring the JSON File
The JSON configuration file needed to upload a Custom Script
- from the uCPE Manager to a Device must contain a list of dictionaries.
+ from the Enea Edge Management to a Device must contain a list of dictionaries.
Each dictionary indicates the test case name and the test case
arguments passed to the
customScripts/uploadOnDevice Python
@@ -2236,7 +2236,7 @@ Options:
[
{
-"name": "Uploading a Custom Script from uCPE Manager to device",
+"name": "Uploading a Custom Script from Enea Edge Management to device",
"args": "-c test_success_after_always -e always-after-startup -n inteld1521-6"
}
]
@@ -2263,16 +2263,16 @@ test_success_after_always -e always-after-startup -n inteld1521-6
- Removing a Custom Script from the uCPE Manager
+ Removing a Custom Script from the Enea Edge Management
- Steps and options on how to remove a custom script from the uCPE
- Manager are described below.
+ Steps and options on how to remove a custom script from the
+ Enea Edge Management are described below.
Script Options
$ python customScripts/delete.py -h
-2020-04-14 14:36:52,010 - INFO: Delete Custom Script on uCPE Manager
+2020-04-14 14:36:52,010 - INFO: Delete Custom Script on Enea Edge Management
Usage: delete.py [options]
Delete a Custom Script from a Device
@@ -2281,10 +2281,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
Custom Script Name that resides on a Device
-e PHASE, --phase=PHASE
@@ -2300,8 +2300,8 @@ Options:
Configuring the JSON File
The JSON configuration file needed to remove a Custom Script
- from the uCPE Managerdid you mean device or uCPE
- Manager? must contain a list of dictionaries. Each dictionary
+ from the Enea Edge Managementdid you mean device or
+ Enea Edge Management? must contain a list of dictionaries. Each dictionary
indicates the test case name and the test case arguments passed to the
customScripts/delete Python module.
@@ -2310,7 +2310,7 @@ Options:
[
{
-"name": "Removing a Custom Script from uCPE Manager",
+"name": "Removing a Custom Script from Enea Edge Management",
"args": "-c test_success_after_always -e always-after-startup"
}
]
@@ -2325,12 +2325,12 @@ Options:
$ python automation_framework/customScripts/delete.py -c \
test_success_after_always -e always-after-startup
2020-04-14 14:39:22,042 - DEBUG: Started logging
-2020-04-14 14:39:22,042 - INFO: Delete Custom Script on uCPE Manager
+2020-04-14 14:39:22,042 - INFO: Delete Custom Script on Enea Edge Management
2020-04-14 14:39:22,081 - DEBUG: Login successful on host '172.24.3.109'
2020-04-14 14:39:22,082 - DEBUG: Session token is: f75a83a0-7e4c-11ea-835c-02423a1c239f
2020-04-14 14:39:22,099 - DEBUG: Found custom script: 'test_success_after_always'
2020-04-14 14:39:22,099 - DEBUG: Delete script test_success_after_always, \
-phase always-after-startup from uCPE Manager
+phase always-after-startup from Enea Edge Management
2020-04-14 14:39:22,118 - INFO: Done
2020-04-14 14:39:22,135 - DEBUG: Logging out and exiting...
@@ -2355,10 +2355,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
Custom Script Name that resides on a Device
-e PHASE, --phase=PHASE
@@ -2469,7 +2469,7 @@ phase always-after-startup from inteld1521-6
- Uploading a Custom Script to the uCPE Manager
+ Uploading a Custom Script to the Enea Edge Management
$ python automation_framework/customScripts/upload.py \
-f lab_config/customScripts/test_success_after_always -e always-after-startup
@@ -2477,7 +2477,7 @@ phase always-after-startup from inteld1521-6
2020-04-14 14:08:02,915 - INFO: Upload Custom Script
2020-04-14 14:08:02,994 - DEBUG: Login successful on host '172.24.3.109'
2020-04-14 14:08:02,995 - DEBUG: Session token is: 97544990-7e48-11ea-835c-02423a1c239f
-2020-04-14 14:08:02,996 - DEBUG: Upload test_success_after_always to uCPE Manager. \
+2020-04-14 14:08:02,996 - DEBUG: Upload test_success_after_always to Enea Edge Management. \
Content: #!/bin/bash
echo test_success_after_always
2020-04-14 14:08:03,138 - INFO: Done
@@ -2485,7 +2485,7 @@ echo test_success_after_always
- Uploading a Custom Script from the uCPE Manager to a
+ Uploading a Custom Script from the Enea Edge Management to a
Device
$ python automation_framework/customScripts/uploadOnDevice.py -c \
@@ -2517,17 +2517,17 @@ phase always-after-startup from inteld1521-6
- Removing a Custom Script from the uCPE Manager
+ Removing a Custom Script from the Enea Edge Management
$ python automation_framework/customScripts/delete.py -c \
test_success_after_always -e always-after-startup
2020-04-14 14:39:22,042 - DEBUG: Started logging
-2020-04-14 14:39:22,042 - INFO: Delete Custom Script on uCPE Manager
+2020-04-14 14:39:22,042 - INFO: Delete Custom Script on Enea Edge Management
2020-04-14 14:39:22,081 - DEBUG: Login successful on host '172.24.3.109'
2020-04-14 14:39:22,082 - DEBUG: Session token is: f75a83a0-7e4c-11ea-835c-02423a1c239f
2020-04-14 14:39:22,099 - DEBUG: Found custom script: 'test_success_after_always'
2020-04-14 14:39:22,099 - DEBUG: Delete script test_success_after_always, \
-phase always-after-startup from uCPE Manager
+phase always-after-startup from Enea Edge Management
2020-04-14 14:39:22,118 - INFO: Done
2020-04-14 14:39:22,135 - DEBUG: Logging out and exiting...
@@ -2536,13 +2536,13 @@ phase always-after-startup from uCPE Manager
Adding an Offline Configuration Store
- Steps and options on how to add a Config Store in the Enea uCPE
- Manager are described below.
+ Steps and options on how to add a Config Store in the
+ Enea Edge Management are described below.
Script Options
- To add a config store in the Enea uCPE Manager use the
+ To add a config store in the Enea Edge Management use the
addConfigStore.py script detailed below. Bear in
mind a CONFIGSTORE json file is needed to
successfully run the script in order to add an offline configuration
@@ -2566,7 +2566,7 @@ phase always-after-startup from uCPE Manager
Running the Python Module
- Adding an offline config store in the Enea uCPE Manager using
+ Adding an offline config store in the Enea Edge Management using
the command line:
python automation_framework/device/addConfigStore.py -f \
@@ -2599,10 +2599,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-s STORE, --store=STORE
Offline config store name
-d DEVICE, --device=DEVICE
@@ -2645,10 +2645,10 @@ Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-d DEVICE, --device=DEVICE
Device Name
@@ -2670,15 +2670,15 @@ Options:
- Removing an Offline Configuration Store in the Enea uCPE
- Manager
+ Removing an Offline Configuration Store in the
+ Enea Edge Management
Steps and options on how to remove an upload of a Config Store
- from the uCPE Manager are described below.
+ from the Enea Edge Management are described below.
Modifications of an Offline Configurations Store are not
- possible post deployment in the uCPE Manager, as there is no option
+ possible post deployment in the Enea Edge Management, as there is no option
for changing script states (e.g. changing the DPDK state in the
configDPDK.py python script or unbinding
interfaces). The offline store must be deleted and the new
@@ -2689,23 +2689,23 @@ Options:
Script options
- To remove a config store from the uCPE Manager use the
+ To remove a config store from the Enea Edge Management use the
removeConfigStore.py script detailed
below.
python removeConfigStore.py -h
Usage: removeConfigStore.py [options]
-Remove a config store from Enea uCPE Manager.
+Remove a config store from Enea Edge Management.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USERNAME, --username=USERNAME
- Enea uCPE Manager login username
+ Enea Edge Management login username
-p PASSWORD, --password=PASSWORD
- Enea uCPE Manager login password
- -H HOST, --host=HOST Enea uCPE Manager host name or IP address
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
-o STORENAME, --store-name=STORENAME
Name of the Offline Config Store
@@ -2770,8 +2770,8 @@ Options:
Manual.
The /uCPEM_config directory stores JSON
- configuration files needed for the setup of the uCPE Manager used by TH.
- One configuration file is needed per uCPE Manager installation, to be used
+ configuration files needed for the setup of the Enea Edge Management used by TH.
+ One configuration file is needed per Enea Edge Management installation, to be used
in the TH.
The /vnf_image directory stores the VNF Images
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml
index 0b96de2..6398606 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access Automation Framework and Test Harness User Guide
+ Enea Enea Edge Automation Framework and Test Harness User Guide
Release Version
Components
- An overview of the Enea NFV Access Runtime Platform and the uCPE
- Manager in cooperation with the Automation Framework and Test Harness, will
+ An overview of the Enea Edge Runtime and the Edge Management
+ in cooperation with the Automation Framework and Test Harness, will
be presented in detail.
@@ -18,23 +18,23 @@
- Enea NFV Access
+ Enea Edge
- Enea NFV Access is comprised of the Enea uCPE Manager and the Enea
- NFV Access Runtime Platform.
+ Enea Edge is comprised of the Enea Edge Management and the Enea
+ Edge Runtime.
- Enea uCPE Manager
+ Enea Edge Management
- The Enea uCPE Manager application needs to be installed on a
+ The Enea Edge Management application needs to be installed on a
supported platform. Upon installation, the system will be set up to
- manage Enea NFV Access "devices", these are the virtualized CPE devices
+ manage Enea Edge "devices", these are the virtualized CPE devices
used in testing.
- For more on Enea uCPE Manager installation instructions, please
+ For more on Enea Edge Management installation instructions, please
refer to the section on how to Installing the Enea uCPE Manager in the
+ targetptr="install_ucpe_mg">Installing the Enea Edge Management in the
@@ -42,38 +42,37 @@
- Enea NFV Access Runtime Platform
+ Enea Edge Runtime
- One or more uCPE devices running the Enea NFV Access Runtime
- Platform are required as hosts to run the VNF(s). The uCPE device is
- known to the uCPE Manager as the "VcpeAgent" device module.
+ One or more uCPE devices running the Enea Edge Runtime
+ are required as hosts to run the VNF(s). The uCPE device is
+ known to the Enea Edge Management as the "VcpeAgent" device module.
Before running any use case with the Automation Framework or the
- Test Harness, make sure the uCPE device(s) have been added to the uCPE
- Manager.
+ Test Harness, make sure the uCPE device(s) have been added to the Edge Management.
Adding a VcpeAgent device can be done via two methods:
- Through the uCPE Manager GUI. Add the device using the
+ Through the Enea Edge Management GUI. Add the device using the
appropriate parameters by launching the UI under
Devices -> Manage in the
main screen.
- REST API. Invoke the uCPE Manager REST API to add a
+ REST API. Invoke the Enea Edge Management REST API to add a
device.
- For more on Enea NFV Access installation instructions, please
+ For more on Enea Edge installation instructions, please
refer to chapter Preparing the USB stick for installation of the
- Enea NFV Access Runtime Platform in the
@@ -85,14 +84,14 @@
Automation Framework
Testing can be performed by running the available Python scripts
- against the uCPE Manager REST API (Python samples supplied). This can be
+ against the Enea Edge Management REST API (Python samples supplied). This can be
done by using the Python scripts individually or by using the Python
unit-test suite that is able to automatically run test-cases defined for
each available Python script.
In either case, it is desirable to use a different host (instead of
- running the tests on the same system as the uCPE Manager) in order to
- ensure that the uCPE Manager is setup and installed correctly in terms of
+ running the tests on the same system as the Enea Edge Management) in order to
+ ensure that the Enea Edge Management is setup and installed correctly in terms of
allowing external users to access it and use it effectively.
@@ -102,7 +101,7 @@
The Test Harness (TH) provides a way for driving configuration with
Ansible Playbooks, by running the python modules from the Automation
Framework (AF) and by direct connection over SSH to the boards that run
- Enea NFV Access.
+ Enea Edge.
The Test Harness includes an automated test suite that
contains:
@@ -110,14 +109,14 @@
VNF, Device and Network Smoke Test Cases. A sample test suite
- that acts as basic smoke tests for Enea NFV Access and also as a
+ that acts as basic smoke tests for Enea Edge and also as a
sanity-check test suite for the AF and TH.
VNF Deployment and Lifecycle. A sample test suite that verifies
the instantiation, lifecycle control and destruction of a VNF for Enea
- NFV Access.
+ Edge.
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
index eee6636..97666cf 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
@@ -29,7 +29,7 @@
The Automation Framework and Test Harness installation may be done
- on the same machine used for uCPE Manager installation, although this is
+ on the same machine used for Enea Edge Management installation, although this is
not encouraged. For more details see section Automation Framework in the
- uCPE Manager Host
+ Enea Edge Management Host
Requirements
@@ -82,12 +82,12 @@
- uCPE Manager installed.
+ Enea Edge Management installed.
- For details on how to install the uCPE Manager, see For details on how to install the Enea Edge Management, see Installing the Enea uCPE Manager in the
+ targetptr="install_ucpe_mg">Installing the Enea Edge Management in the
@@ -111,13 +111,13 @@
- Enea NFV Access Runtime Platform installed.
+ Enea Edge Runtime installed.
- For information on how to install Enea NFV Access refer to
+ For information on how to install Enea Edge refer to
Preparing the USB stick for installation
- of the Enea NFV Access Runtime Platform in the
@@ -155,7 +155,7 @@
- Enea NFV Access Runtime Platform installed.
+ Enea Edge Runtime installed.
@@ -180,16 +180,16 @@
- Set up the uCPE Manager which will be used by the TH:
+ Set up the Enea Edge Management which will be used by the TH:
- Create the uCPE Manager JSON config file in the
+ Create the Enea Edge Management JSON config file in the
<AF-TH-install-dir>/uCPEM_config/
directory:{
-"ucpe_usr":"uCPE Manager Username",
-"ucpe_pass":"uCPE Manager Password",
-"ucpe_host":"uCPE Manager IP/Hostname",
+"ucpe_usr":"Enea Edge Management Username",
+"ucpe_pass":"Enea Edge Management Password",
+"ucpe_host":"Enea Edge Management IP/Hostname",
"ftp_usr":"FTP Username",
"ftp_pass":"FTP Password",
"ftp_port":"FTP Port"
@@ -225,10 +225,10 @@
source
<AF-TH-install-dir>/testHarness-venv/bin/activate .
- Furthermore, if a user wants to use a new uCPE Manager instance for
+ Furthermore, if a user wants to use a new Enea Edge Management instance for
a new session, the user also has to re-run the
setupuCPEManager.yml playbook with the corresponding
- JSON config for the new uCPE Manager instance.
+ JSON config for the new Enea Edge Management instance.
Automation Framework and Test Harness History Information can be
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml
index eadc1d5..b2486a0 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml
@@ -3,21 +3,20 @@
Overview
This document describes the Automation Framework and Test Harness for
- Enea NFV Access, along with instructions regarding the necessary steps to
+ Enea Edge, along with instructions regarding the necessary steps to
run these software tools.
Description
The Automation Framework provides a way for driving configuration
- with Python scripting. It complements the Enea uCPE Manager GUI and uses
- the northbound REST APIs, given to provide full usability of the Enea uCPE
- Manager features.
+ with Python scripting. It complements the Enea Edge Management GUI and uses
+ the northbound REST APIs, given to provide full usability of the Enea Management
+ features.
The Test Harness is based on running Ansible Playbooks to complete
different test cases, which make use of the Automation Framework Python
- modules and/or direct commands on the uCPE devices running the Enea NFV
- Access Runtime Platform.
+ modules and/or direct commands on the uCPE devices running the Enea Edge Runtime.
@@ -39,10 +38,10 @@
- Enea NFV Access
+ Enea Edge
- The Enea NFV Access (with ODM) Runtime Platform and the
- Enea uCPE Manager.
+ The Enea Edge (with ODM) Runtime and the
+ Enea Edge Management.
@@ -66,7 +65,7 @@
AF
- Automation Framework for Enea NFV Access.
+ Automation Framework for Enea Edge.
@@ -162,11 +161,11 @@
TH
- Test Harness for Enea NFV Access.
+ Test Harness for Enea Edge.
- uCPE Manager
+ Enea Edge Management
Enea Universal Customer Premises Equipment Manager.
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
index f51fe11..a5cd664 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
@@ -21,11 +21,11 @@
- When setting up the uCPE Manager to be used by the TH through the
+ When setting up the Enea Edge Management to be used by the TH through the
setupuCPEManager.yml Playbook, if the uCPE
username/password/host are incorrect or are missing, all the Sample test
cases will fail. If the FTP username/password/port are wrong or are
- missing, the tests that require file transfer to the uCPE Manager will
+ missing, the tests that require file transfer to the Enea Edge Management will
fail.
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk b/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk
index 9f0a075..6b65cff 100755
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-auto-fw-th-user-guide
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) Automation Framework and Test Harness User Guide"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Enea Edge $(PROD_VER) Automation Framework and Test Harness User Guide"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
index 7ba8a7b..89692b0 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
@@ -68,7 +68,7 @@
Configuring Network Interfaces on uCPE
devices:
- Add the trgt uCPE device into the uCPE Manager:
+ Add the trgt uCPE device into Enea Edge Management:
Devices -> Manage -> Add .
Fill in the required fields with the following data:
@@ -266,8 +266,8 @@
Create
The system will automatically select the
- physical interface that has access to the uCPE
- Manager.
+ physical interface that has access to Enea Edge
+ Management.
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
index 45689e5..0e207ae 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
@@ -1,6 +1,6 @@
- Running Enea Automation Framework tests
+ Running Enea Automation Framework and Test Harness
For more detailed information regarding the Automation Framework and
Test Harness please see the
Before starting the two usecases detailed in the following appendix,
- the uCPE Device needs to be added into the uCPE Manager.
+ the uCPE Device needs to be added into Enea Edge Management.
To properly set up the Automation Framework and Test Harness please
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
index 71dee09..67f38e5 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
@@ -1,6 +1,6 @@
- Example Tests Results using the Automation Framework
+ Example Tests Results using the Automation Framework and Test Harness
In order to run the following example usecases, certain configuration
file entries need to be modified according to the network setup that it will
@@ -39,7 +39,7 @@
"maintMode": "false",
"version": "2.2.3",
"deviceId": "inteld1521-17"
-}The IP address of the uCPE Manager that will be used in
+}The IP address of Enea Edge Management that will be used in
these examples is 172.24.3.92 .
The FortiGate and 128T VNF images need to be copied into the
@@ -138,7 +138,7 @@ OK
Use-case 2: Service Chaining 128T - Fortigate Example
- Usecase
+ Use-case
> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
-s 128t_FG_SFCDeploy.json -d "128T - Fortigate SFC Deployment"
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/book.xml b/doc/book-enea-nfv-access-example-usecases/doc/book.xml
index eb8b0c8..9879c28 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/book.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access Example Use-cases
+ Enea Edge Example Use-cases
Release Version
VNF Configuration files. These files are provided with your Enea
- NFV Access release:
+ Edge release:
clavister-cloudinit.conf .
@@ -333,7 +333,7 @@ root@qemux86-64:~# iperf3 -c 192.168.10.10
VNF Configuration files. These files are provided with your Enea
- NFV Access release:
+ Edge release:
clavister-cloudinit.conf .
enea-vnf-iperf-client.conf .
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/enea_test_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/enea_test_vnf_examples.xml
index 1f10dbf..bee5a63 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/enea_test_vnf_examples.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/enea_test_vnf_examples.xml
@@ -17,7 +17,7 @@
- 2 Network Interfaces. One for the uCPE manager and one for data
+ 2 Network Interfaces. One for Enea Edge Management and one for data
traffic.
@@ -35,7 +35,7 @@
VNF Configuration files. These files are provided with your Enea
- NFV Access release:
+ Edge release:
enea-vnf-testpmd-fwd.conf .
@@ -134,7 +134,7 @@
- Instantiate the Enea NFV Access TestPMD forwarding VNF on uCPE
+ Instantiate the Enea Edge TestPMD forwarding VNF on uCPE
Device 2 by filling the required fields with the following
values:
@@ -168,7 +168,7 @@
- Instantiate the Enea NFV Access TestPMD termination VNF on
+ Instantiate the Enea Edge TestPMD termination VNF on
uCPE Device 2 by filling the required fields with the following
values:
@@ -218,8 +218,8 @@
testpmd_term .
- The flow rules can be described using either the uCPE
- manager interface or the configuration files.
+ The flow rules can be described using either the Enea Edge
+ Management interface or the configuration files.
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
index 36c7114..bb38140 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
@@ -50,7 +50,7 @@
- VNF Configuration file(s), provided with your Enea NFV Access
+ VNF Configuration file(s), provided with your Enea Edge
release: fortigate-basic-fw.conf .
@@ -93,7 +93,7 @@
- Connect ETH0 to the Lab Network (for Enea uCPE Manager
+ Connect ETH0 to the Lab Network (for Enea Edge Management
communications).
@@ -302,7 +302,7 @@
- VNF Configuration file(s), provided with your Enea NFV Access
+ VNF Configuration file(s), provided with your Enea Edge
release: fortigate-sdwan<x>.conf .
@@ -359,7 +359,7 @@
Connect the ETH0 interfaces to the Lab
- Network (for Enea uCPE Manager communications).
+ Network (for Enea Edge Management communications).
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
index fc3559b..b502e8b 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
@@ -7,8 +7,8 @@
etc.
Before running any example use case make sure the uCPE device(s) have
- been added to the uCPE Manager and placed on the map. For detailed
- information on how to add a device to the uCPE Manager, how to configure the
+ been added to Enea Edge Management and placed on the map. For detailed
+ information on how to add a device to Enea Edge Management, how to configure the
network interfaces to use DPDK, PCI-passthrough or SR-IOV drivers, or VNF
configuration, please refer to the Service Chaining 128T - Fortigate Example Use-case
The following is an example of how to setup and configure a service
- chain on top of the Enea NFV Access virtualization platform, using the
+ chain on top of the Enea Edge Runtime, using the
following commercial VNFs: 128T router and FortiGate.
@@ -86,7 +86,7 @@
Configuring Network Interfaces on uCPE
devices:
- Add the trgt uCPE device into the uCPE Manager:
+ Add the trgt uCPE device into Enea Edge Management:
Devices -> Manage -> Add , and fill in the
required fields with the following data:
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
index 8b82337..24442af 100644
--- a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
+++ b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
@@ -11,9 +11,9 @@
The following is an example of how to setup and configure a
branch-to-branch service comprised on two commercial VNFs (SD-WAN +
- Firewall). This service will run in a service chain on top of the Enea NFV
- Access virtualization platform, deployed through the Enea uCPE
- Manager.
+ Firewall). This service will run in a service chain on top of the Enea
+ Edge Runtime, deployed through the Enea Edge
+ Management.
In the example setup the following commercial VNFs are used: Juniper
vSRX as the SD-WAN VNF and Fortigate as the Router/Firewall.
@@ -61,7 +61,7 @@
- VNF Configuration files, provided with your Enea NFV Access
+ VNF Configuration files, provided with your Enea Edge
Release:
@@ -152,7 +152,7 @@
The networking setup (Steps 1-3) can be modeled using the
Offline Configuration entry, so that it is automatically
provisioned on the uCPE device, once it gets enrolled into the
- management system (uCPE Manager).
+ management system (Enea Edge Management).
diff --git a/doc/book-enea-nfv-access-example-usecases/swcomp.mk b/doc/book-enea-nfv-access-example-usecases/swcomp.mk
index 972746a..5f5ab16 100755
--- a/doc/book-enea-nfv-access-example-usecases/swcomp.mk
+++ b/doc/book-enea-nfv-access-example-usecases/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-example-usecases
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) Example Use-cases"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Example Use-cases"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
index cb0ae5b..70a9978 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
@@ -1,4 +1,4 @@
-
+
@@ -12,26 +12,24 @@
Bare Metal Provisioning
Bare Metal Provisioning can be used for automated deployment of the
- Enea NFV Access Runtime Platform on a large number of uCPE devices. The
- uCPE devices may have no previous operating system installed, or are
- reinstalled without preserving any existing data. Enea NFV Access Bare
- Metal Provisioning is based on standardized Pre-Boot Execution environment
- (PXE) booting.
+ Enea Edge Runtime on a large number of uCPE devices. The uCPE devices may
+ have no previous operating system installed, or are reinstalled without
+ preserving any existing data. Enea Edge Bare Metal Provisioning is based
+ on standardized Pre-Boot Execution environment (PXE) booting.
The Bare Metal Provisioning process begins by PXE booting an Enea
- NFV Access installer initramfs image. The installer
- downloads a configuration file, as well as the Enea NFV Access Runtime
- Platform image and then proceeds to install the system by dividing the
- disk into 2 partitions: a GPT partition containing the GRUB boot loader
- and a second partition containing the Enea NFV Access Runtime Platform
- root filesystem. When the installation is complete, the uCPE device is
- automatically rebooted into Enea NFV Access Runtime Platform.
+ Edge installer initramfs image. The installer downloads
+ a configuration file, as well as the Enea Edge Runtime image and then
+ proceeds to install the system by dividing the disk into 2 partitions: a
+ GPT partition containing the GRUB boot loader and a second partition
+ containing the Enea Edge Runtime root filesystem. When the installation is
+ complete, the uCPE device is automatically rebooted into Enea Edge
+ Runtime.
The .hddimg , initramfs , and
bzImage files are available in the
- Enea_NFV_Access_Run_Time_Platform_
- <processor>_<version>-<build_number>.tar.gz
+ Enea_Edge_Runtime_<processor>_<version>-<build_number>.tar.gz
file you downloaded with your release.
@@ -56,16 +54,15 @@
The uCPE devices are preconfigured in BIOS to boot from the
- hard drive where the Enea NFV Access Runtime Platform will be
- installed.
+ hard drive where the Enea Edge Runtime will be installed.
CSM support and Dual Boot must be enabled in BIOS (i.e. PXE
- booting in legacy mode), while the final Enea NFV Access image will
- boot in UEFI mode. Doing a mass deployment using legacy PXE booting
- usually means that Secure Boot is disabled, Secure Boot will need to
- be enabled afterwards.
+ booting in legacy mode), while the final Enea Edge Runtime image
+ will boot in UEFI mode. Doing a mass deployment using legacy PXE
+ booting usually means that Secure Boot is disabled, Secure Boot will
+ need to be enabled afterwards.
@@ -80,23 +77,22 @@
@@ -205,7 +201,7 @@ ipmitool -U <user> -P <password> -H <uCPE device IPMI IP address&
Enabling UEFI Secure Boot
- All Enea NFV Access image artifacts delivered with the release are
+ All Enea Edge image artifacts delivered with the release are
signed using the Enea UEFI Secure boot private keys. These artifacts can
be used on a uCPE device that doesn't have Secure Boot enabled. To use
the Secure Boot feature, however, the user must make the Enea UEFI
@@ -247,9 +243,9 @@ ipmitool -U <user> -P <password> -H <uCPE device IPMI IP address&
The Enea UEFI Secure Boot certificates are installed together
- with the Enea NFV Access Runtime Platform onto the hard drive. They
- can be found on the EFI partition (usually the first partition of the
- drive) under /uefi_sb_keys .
+ with the Enea Edge Runtime onto the hard drive. They can be found on
+ the EFI partition (usually the first partition of the drive) under
+ /uefi_sb_keys .
These certificates need to be manually enrolled in BIOS. The
exact details on how to proceed may vary depending the version of the
@@ -278,12 +274,12 @@ ipmitool -U <user> -P <password> -H <uCPE device IPMI IP address&
are contiguous blocks of memory that come in 2MB or 1GB sizes. By using
huge page allocations, less memory is used for page tables and the
Translation Lookaside Buffer (TLB) miss rate is significantly reduced.
- Enea NFV Access uses huge page backed memory in KVM guests in order to
+ Enea Edge Runtime uses huge page backed memory in KVM guests in order to
improve performance.
- Enea NFV Access implements an automatic hugepage allocation service
- that is triggered at each startup. The service is skipped if hugepages
- have been allocated in the kernel boot command line.
+ Enea Edge Runtime implements an automatic hugepage allocation
+ service that is triggered at each startup. The service is skipped if
+ hugepages have been allocated in the kernel boot command line.
There are two strategies outlined for hugepage allocation:
@@ -422,11 +418,12 @@ node0.1048576kB = 3
- Installing the Enea uCPE Manager in High Availability Mode
+ Installing the Enea Edge Management in High Availability
+ Mode
- The following describes the setup needed for running the Enea uCPE
- Manager in High Availabilty (HA) mode, with a MariaDB database cluster. A
- setup example is illustrated in the diagram below.
+ The following describes the setup needed for running the Enea Edge
+ Management in High Availabilty (HA) mode, with a MariaDB database cluster.
+ A setup example is illustrated in the diagram below.
The High Availability setup
@@ -442,17 +439,17 @@ node0.1048576kB = 3
The setup consists of two sub-clusters, placed in different
geographical locations, each consisting of three MariaDB servers. In this
example, two of the machines are running only MariaDB, while the rest are
- hosting a MariaDB server and an Enea uCPE Manager instance. The entire
+ hosting a MariaDB server and an Enea Edge Management instance. The entire
network is hidden behind a firewall that performs NAT. While in protection
- (cluster) mode, the Enea uCPE Manager instances promote a Virtual IP (VIP)
- that represents the IP address of the entire cluster. The firewall in this
- case will allocate a public IP for the outside world that will be
+ (cluster) mode, the Enea Edge Management instances promote a Virtual IP
+ (VIP) that represents the IP address of the entire cluster. The firewall
+ in this case will allocate a public IP for the outside world that will be
translated into the VIP. Also in this example, the traffic towards the
cluster from outside the firewall is done through HTTPS, which will be
translated to HTTP inside the private network.
- By default, communication to the Enea uCPE Manager is done with
+ By default, communication to the Enea Edge Management is done with
HTTPS. To enable HTTP, go to System ,
Configuration , click on the Web Access tab and check the
- Machines running the Enea uCPE Manager and MariaDB:
+ Machines running the Enea Edge Management and MariaDB:
@@ -509,9 +506,9 @@ node0.1048576kB = 3
Please refer to Firewall Configuration in the Firewall Configuration in the
Manual. In addition, the following configuration is needed:
@@ -533,10 +530,10 @@ SELINUXTYPE=targeted
The following ports should be opened in the local firewall (not
- the one doing NAT), for each Enea uCPE Manager machine:
+ the one doing NAT), for each Enea Edge Management machine:
- Ports for Enea uCPE Manager Machines
+ Ports for Enea Edge Management Machines
@@ -590,7 +587,7 @@ SELINUXTYPE=targeted
For MariaDB, the following ports must be opened (on each MariaDB
- server, including the ones hosting the Enea uCPE Manager):
+ server, including the ones hosting the Enea Edge Management):
Ports for MariaDB Machines
@@ -685,9 +682,9 @@ SELINUXTYPE=targeted
Installing High Availability
- The Enea uCPE Manager can be installed in High Availability mode
- with a MariaDB database cluster by performing the following steps. The
- mandatory Java configuration is also detailed.
+ The Enea Edge Management can be installed in High Availability
+ mode with a MariaDB database cluster by performing the following steps.
+ The mandatory Java configuration is also detailed.
Installing and configuring the MariaDB cluster
@@ -825,20 +822,20 @@ Switch to unix_socket authentication [Y/n] Y
Enabled successfully!
Reloading privilege tables..
... Success!
-…
+…
Change the root password? [Y/n] Y
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!
-…
+…
Remove anonymous users? [Y/n] Y
... Success!
-…
+…
Disallow root login remotely? [Y/n] Y
... Success!
-…
+…
Remove test database and access to it? [Y/n] Y (optional)
- Dropping test database...
... Success!
@@ -875,9 +872,9 @@ TO 'enea'@'%' IDENTIFIED BY 'somepassword' WITH GRANT OPTION;
Please refer to Configuring OpenJDK and
- PostgreSQL in the
Manual, for details on how to install and configure Java
OpenJDK.
@@ -891,16 +888,16 @@ TO 'enea'@'%' IDENTIFIED BY 'somepassword' WITH GRANT OPTION;
- Installing the Enea uCPE Manager in High Availabilty
+ Installing the Enea Edge Management in High Availabilty
mode
These steps must be taken on each of the CentOS 7 machines that
- will host the Enea uCPE Manager. The Enea uCPE Manager will be
+ will host the Enea Edge Management. The Enea Edge Management will be
installed and the setup for the external database cluster will be
prepared.
- As the root user, go to the distribution folder of the Enea uCPE
- Manager, and run:
+ As the root user, go to the distribution folder of the Enea Edge
+ Management, and run:
[root@localhost distro]#./install.sh /opt/ \
Enea_NFV_Access_uCPEManager_2.3.0-build23.tar.gz
@@ -911,7 +908,7 @@ External database selected, getting user information ...
Press 1 for PostgreSQL, 2 for MariaDB, 3 for SQL Server, 4 for Oracle and 5 \
for MySQL: 2
Specify database server name(s) or IP Address(es): \
-192.168.10.11,192.168.10.12,…,192.168.10.16 *(see note)
+192.168.10.11,192.168.10.12,…,192.168.10.16 *(see note)
Specify database ID (or name) [ucpemanager]:
Specify database server port [3306]:
Specify database user name [root]: enea
@@ -920,11 +917,11 @@ Specify database startup thread pool size [1]:
Creating database configuration file \
/opt//ucpemanager/application/config/databaseConfig.xml ...
Done .
-…
+…
Installing ucpemanager service ..
Specify service username [ucpemanager]:
Specify service password [ucpemanager]: somepassword
-…
+…
Specify the IP address of the local interface: 192.168.10.11
Is this server part of a cluster? [Y/N]: Y
Specify the name of the cluster [ucpemanager]:
@@ -934,9 +931,9 @@ HA Configuration files modified successfully.
Configuration complete.
- For each Enea uCPE Manager installation, place the local
+ For each Enea Edge Management installation, place the local
interface IP first in the list of IPs. This will optimize database
- communication, since the Enea uCPE Manager uses the list of IPs
+ communication, since the Enea Edge Management uses the list of IPs
sequentially, therefore using the internal loopback interface for
communicating with the database.
@@ -944,8 +941,8 @@ Configuration complete.
Once the servers are up and running, log into the Primary and go to System and select Cluster
- View . The list of Enea uCPE Managers should be displayed,
- with one listed as Primary and the rest as Backup.
+ View. The list of Enea Edge Management servers should be
+ displayed, with one listed as Primary and the rest as Backup.
@@ -977,7 +974,7 @@ Configuration complete.
Run the upgrade process on ucpeManager-3
and ucpeManager-4 . This will upgrade the service
to the current release. Once the upgrade process completes, shutdown
- the Enea uCPE Manager service on both machines.
+ the Enea Edge Management service on both machines.
@@ -989,10 +986,11 @@ Configuration complete.
- Shutdown the MariaDB-2 process and run the Enea uCPE Manager
- upgrade process on ucpeManager-2 . This will
- upgrade the service to the current release. Once the upgrade process
- completes, shutdown the uCPE Manager service on the machine.
+ Shutdown the MariaDB-2 process and run the Enea Edge
+ Management upgrade process on ucpeManager-2 . This
+ will upgrade the service to the current release. Once the upgrade
+ process completes, shutdown the Enea Edge Management service on the
+ machine.
@@ -1013,7 +1011,7 @@ Configuration complete.
- Start the Enea uCPE Manager services on
+ Start the Enea Edge Management services on
ucpeManager-2 . This machine will come up as the
new "PRIMARY" with the upgraded software. As part of the startup
process, it will upgrade the database and perform any other
@@ -1026,14 +1024,14 @@ Configuration complete.
- Start the Enea uCPE Manager services on
+ Start the Enea Edge Management services on
ucpeManager-3 and
ucpeManager-4 . At this point, we are in
highly-available mode.
- Upgrade the Enea uCPE Manager on
+ Upgrade the Enea Edge Management on
ucpeManager-1 (the one that has been shut down).
Once that upgrade is complete and the service restarts, the entire
setup has been upgraded to the new version.
diff --git a/doc/book-enea-nfv-access-getting-started/doc/book.xml b/doc/book-enea-nfv-access-getting-started/doc/book.xml
index fa3fc4f..0704dd0 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/book.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access Getting Started
+ Enea Edge Getting Started
Release Version
Using Grafana and InfluxDB
-
- InfluxDB is essentially a time series database process that runs on a
- server, while Grafana is a visualization tool for time series data.
- Grafana is a very lightweight server-side application, and most of the
- monitoring runs in a browser.
+
+ InfluxDB is essentially a time series database process that runs on a
+ server, while Grafana is a visualization tool for time series data. Grafana
+ is a very lightweight server-side application, and most of the monitoring
+ runs in a browser.
Deploying Grafana and InfluxDB
-
- Grafana and InfluxDB can be deployed using images for Docker on linux.
- These images are provided by Enea along with a deploy script and
- predefined dashboards.
-
- The Grafana and InfluxDB images can be deployed on the same machine
- or on separate machines.
+
+ Grafana and InfluxDB can be deployed using images for Docker on
+ linux. These images are provided by Enea along with a deploy script and
+ predefined dashboards.
+
+ The Grafana and InfluxDB images can be deployed on the same machine
+ or on separate machines.
- Prerequisites for Deploying an Image
-
+ Prerequisites for Deploying an Image
+
The following must be present in order to deploy an image:
-
-
-
- CentOS 7 Linux.
-
-
-
- Docker for CentOS 7 installed on the machine and set to
- autostart as a service.
-
-
-
- Superuser rights on the CentOS 7 machine.
-
-
-
-
+
+
+
+ CentOS 7 Linux.
+
+
+
+ Docker for CentOS 7 installed on the machine and set to
+ autostart as a service.
+
+
+
+ Superuser rights on the CentOS 7 machine.
+
+
+
+
Deploying Grafana and InfluxDB
-
- On the CentOS 7 server open a terminal, log into a bash shell
- with the root account and perform the following:
-
-
-
- Extract
- Enea_NFV_Access_Telemetry_Deploy_<version>-build<build_number>.tar.gz .
-
- The directory in which the archive will be unpacked will be
- denoted as: <Telemetry-installdir> .
-
-
-
- Enter <Telemetry-installdir> .
-
-
-
- Run the provided telemetry_deploy.sh script.
-
-
-
- When prompted, select what images you want to deploy.
-
- If an image is already deployed, you will be prompted to replace it.
-
-
-
- During the InfluxDB deployment, you will be prompted to provide
- a username and password. These must match the ones configured in the
- Enea uCPE Manager for Telemetry.
-
-
-
- Changing the InfluxDB username and password requires redeploying
- the InfluxDB image.
-
-
-
-
- Verify the installation by running the command docker ps -a .
- The Grafana and InfluxDB containers should be present and have
- the status Up .
-
-
-
-
+
+ On the CentOS 7 server open a terminal, log into a bash shell with
+ the root account and perform the following:
+
+
+
+ Extract
+ Enea_Edge_Telemetry_Deploy_<version>-build<build_number>.tar.gz .
+
+ The directory in which the archive will be unpacked will be
+ denoted as: <Telemetry-installdir> .
+
+
+
+ Enter <Telemetry-installdir> .
+
+
+
+ Run the provided telemetry_deploy.sh
+ script.
+
+
+
+ When prompted, select what images you want to deploy.
+
+ If an image is already deployed, you will be prompted to
+ replace it.
+
+
+
+ During the InfluxDB deployment, you will be prompted to
+ provide a username and password. These must match the ones
+ configured in the Enea Edge Management for Telemetry.
+
+
+ Changing the InfluxDB username and password requires
+ redeploying the InfluxDB image.
+
+
+
+
+ Verify the installation by running the command docker
+ ps -a . The Grafana and InfluxDB containers should be
+ present and have the status Up .
+
+
+
Setting Grafana and InfluxDB parameters
Customizing InfluxDB and Grafana parameters can be done by selecting
- System , then the Configuration
- menu, accessing the Properties tab, and clicking on the
- Telemetry tab. The settings that can be changed
- are listed in the table below:
+ System , then the Configuration menu, accessing the Properties tab, and clicking on the Telemetry tab. The settings that can be changed are
+ listed in the table below:
Telemetry settings
@@ -138,7 +139,7 @@
Grafana Dashboard
The dashboard that should be used when opening Grafana
- using the Enea uCPE Manager.
+ using the Enea Edge Management.
host
@@ -183,8 +184,8 @@
When changing any of the settings in the Telemetry tab, the Enea uCPE Manager will inform all
- uCPE devices of the change if they have telemetry running.
+ role="bold">Telemetry tab, the Enea Edge Management will inform
+ all uCPE devices of the change if they have telemetry running.
Telemetry Properties
@@ -203,11 +204,11 @@
When a uCPE Device is selected, in the Operations menu, the Start
- Telemetry and Stop
- Telemetry options are available.
+ Telemetry and Stop Telemetry
+ options are available.
- When starting Telemetry for a uCPE device, the Enea uCPE Manager sends
- the following information about the InfluxDB:
+ When starting Telemetry for a uCPE device, the Enea Edge Management
+ sends the following information about the InfluxDB:
@@ -226,10 +227,10 @@
These fields are read-only and are populated with the values already
- set in the System Configuration . If one of the
- fields is not set or if it does not have the desired value, modify it in the
- System Configuration . The password is sent
- encrypted using the Base64 scheme.
+ set in the System Configuration . If one
+ of the fields is not set or if it does not have the desired value, modify
+ it in the System Configuration . The
+ password is sent encrypted using the Base64 scheme.
Telemetry Start Dialog
@@ -241,25 +242,25 @@
- When the Telemetry status is changed on a uCPE device, a notification is
- sent to the Enea uCPE Manager. These notifications can be inspected under
- Fault found in the
- Event menu.
+ When the Telemetry status is changed on a uCPE device, a
+ notification is sent to the Enea Edge Management. These notifications can
+ be inspected under Fault found in the
+ Event menu.
Launching Grafana
When a uCPE Device is selected, the Telemetry button is available. Pressing this
- button will open a new window pointing to Grafana. The current uCPE device will
+ role="bold">Telemetry button is available. Pressing this button
+ will open a new window pointing to Grafana. The current uCPE device will
be selected in Grafana.
The hostname or IP Address and the port of the Grafana installation
- can be customized by selecting System , then the
- Configuration menu, accessing the
- Properties tab, and clicking on the
- Telemetry tab. The default dashboard available when
- launching Grafana can be customized as well.
+ can be customized by selecting System ,
+ then the Configuration menu, accessing
+ the Properties tab, and clicking on the
+ Telemetry tab. The default dashboard
+ available when launching Grafana can be customized as well.
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml b/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
index be4342f..f8da56d 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
@@ -1,7 +1,6 @@
-
+
- Setting up and Installing the Enea NFV Access Base
- Configuration
+ Setting up and Installing the Enea Edge Base Configuration
The setup and installation steps detailed below will deploy a base
configuration which will be used as a reference for more complex deployment
@@ -19,11 +18,11 @@
The CentOS 7 server must be updated to the latest revision
- before installing Enea NFV Access.
+ before installing Enea Edge.
The following will detail CPU, RAM and storage requirements for
- the uCPE Manager.
+ the Enea Edge Management.
@@ -81,31 +80,30 @@
- The purpose of the CentOS 7 server is to host the Enea uCPE
- Manager. Network access between the CentOS 7 server and the uCPE
- devices is required. The Enea uCPE Manager and the uCPE devices will
- be connected on separate subnets to avoid inconsistencies.
+ The purpose of the CentOS 7 server is to host the Enea Edge
+ Management. Network access between the CentOS 7 server and the uCPE
+ devices is required. The Enea Edge Management and the uCPE devices
+ will be connected on separate subnets to avoid inconsistencies.
One or more uCPE devices.
- Whitebox devices where the Enea NFV Access Runtime Platform will
- be installed, containing a minimum of 2 cores and 4 GB RAM and at
- least two ethernet ports that will be configured as WAN and LAN during
- deployment.
+ Whitebox devices where the Enea Edge Runtime will be installed,
+ containing a minimum of 2 cores and 4 GB RAM and at least two ethernet
+ ports that will be configured as WAN and LAN during deployment.
When hosting an entire solution including one or several network
services, the hardware must also have the resources to host one or
more VNFs. During a typical evaluation, a dual VNF service on the Enea
- NFV Access Runtime Platform needs a CPU with 4-8 cores and at least 8
- GB RAM. The supported Intel CPUs of Enea NFV Access are documented in
- the
manual.
- Enea NFV Access needs EFI support in BIOS to boot. When
+ Enea Edge Runtime needs EFI support in BIOS to boot. When
configuring the uCPE device BIOS a serial connection is
required.
@@ -117,12 +115,11 @@
- Installing the Enea NFV Access Runtime Platform on uCPE
- Devices.
+ Installing the Enea Edge Runtime on uCPE Devices.
- Connecting to the GUI of the Enea uCPE Manager for
+ Connecting to the GUI of the Enea Edge Management for
management and configuration. Network access between the CentOS 7
server and the laptop is required. Please see the Any firewall running on the CentOS 7 server may block the
management protocols required to communicate between the uCPE device and
- the Enea uCPE Manager as well as between the Enea uCPE Manager and its
- northbound clients. Quick handling of a blocking firewall would be to
- disable it, typical for a lab environment, through:
+ the Enea Edge Management as well as between the Enea Edge Management and
+ its northbound clients. Quick handling of a blocking firewall would be
+ to disable it, typical for a lab environment, through:
sudo systemctl stop firewalld
sudo systemctl disable firewalld
@@ -189,7 +186,7 @@ sudo systemctl mask now firewalld
UDP
- Required for the Enea uCPE Manager High Availability
+ Required for the Enea Edge Management High Availability
Configuration.
@@ -198,7 +195,7 @@ sudo systemctl mask now firewalld
TCP
- Required for the Enea uCPE Manager High Availability
+ Required for the Enea Edge Management High Availability
Configuration.
@@ -223,7 +220,7 @@ sudo systemctl mask now firewalld
Use the following command sequence to enable the required ports
- for deployment of the Enea uCPE Manager:
+ for deployment of the Enea Edge Management:
sudo firewall-cmd --permanent --add-port=80/tcp
sudo firewall-cmd --permanent --add-port=443/tcp
@@ -234,21 +231,21 @@ sudo firewall-cmd --permanent --add-port=2021-2040/tcp
sudo firewall-cmd --reload
- If the uCPE Manager host resides behind a corporate
+ If the Enea Edge Management host resides behind a corporate
port-filtering firewall, then all the aforementioned ports need to
also be enabled on the respective firewall. As an additional
requirement, port 22/TCP also needs to be enabled for reverse SSH to
- the Enea uCPE Manager.
+ the Enea Edge Management.
No enabling and no forwarding rules are necessary for ports
- 2021-2040 if the version of Enea NFV Access is 2.4.0 or newer.
+ 2021-2040 if using Enea Edge 2.4.0 or newer.
Configuring OpenJDK and PostgreSQL
- The Enea uCPE Manager requires a specific Java version (OpenJDK
+ The Enea Edge Management requires a specific Java version (OpenJDK
11) and a PostgreSQL version to operate correctly.
Installing OpenJDK
@@ -299,8 +296,8 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
- The Enea uCPE Manager requires a specific PostgreeSQL version.
- This is embedded in the Enea uCPE Manager installation. In order to
+ The Enea Edge Management requires a specific PostgreeSQL version.
+ This is embedded in the Enea Edge Management installation. In order to
avoid conflicts, any existing PostgreeSQL installation needs to be
uninstalled.
@@ -324,8 +321,8 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
- This step is not necessary if the Enea uCPE Manager will be
- using an external database (like MariaDB).
+ This step is not necessary if the Enea Edge Management will
+ be using an external database (like MariaDB).
yum remove postgres\*
@@ -356,10 +353,10 @@ userdel postgres
- Follow the installation steps for the Enea uCPE Manager
+ Follow the installation steps for the Enea Edge Management
available in Installing the uCPE Manager in the
- Installing the Enea Edge Management in
+ the
Manual.
@@ -377,7 +374,7 @@ userdel postgres
A typical whitebox comes with multiple physical network ports,
ready to be used. The user must determine the purpose and allocation of
each port. The allocation is later aligned with the software
- configuration within the Enea NFV Access installer.
+ configuration within the Web-installer.
A common way is to allocate the left ports to WANs and the right
ports to LANs. At least one port must be allocated to WAN and one to
@@ -388,8 +385,8 @@ userdel postgres
Determining the Device ID
Each uCPE device needs a unique identifier. This identifier is
- used to match the registration in the Enea uCPE Manager and the offline
- configuration of the uCPE device during ZTP (Zero Touch
+ used to match the registration in the Enea Edge Management and the
+ offline configuration of the uCPE device during ZTP (Zero Touch
Provisioning).
Select a text string to represent the uCPE device, e.g.
@@ -404,7 +401,7 @@ userdel postgres
Configuring the BIOS
The factory configuration of the BIOS may not match the
- requirements of Enea NFV Access. The BIOS configuration needs to be
+ requirements of Enea Edge Runtime. The BIOS configuration needs to be
reviewed and potentially reconfigured to prepare for a successful
installation.
@@ -434,8 +431,8 @@ userdel postgres
The boot order may also need to be modified to support
- installation and execution of the Enea NFV Access Runtime Platform on
- the uCPE device.
+ installation and execution of the Enea Edge Runtime on the uCPE
+ device.
The following boot order is recommended for a base
configuration:
@@ -459,14 +456,14 @@ userdel postgres
Preparing the Deployment
- Installing the Enea uCPE Manager
+ Installing the Enea Edge Management
- The Enea uCPE Manager can be installed using a fresh (first-time)
- configuration or using a backup file of a previous installation, created
- within the Enea uCPE Manager GUI.
+ The Enea Edge Management can be installed using a fresh
+ (first-time) configuration or using a backup file of a previous
+ installation, created within the Enea Edge Management GUI.
- Fresh Installation of the Enea uCPE Manager
+ Fresh Installation of the Enea Edge Management
On the CentOS 7 server open a terminal, log into a bash shell
with the root account and perform the following:
@@ -474,7 +471,7 @@ userdel postgres
Extract
- Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
+ Enea_Edge_Management_<version>-build<build_number>.tar.gz
The directory in which the archive has been unpacked will be
denoted as: <uCPEM-installdir> .
@@ -510,8 +507,8 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
The same configuration values set now will need to be
- provided when upgrading or uninstalling the Enea uCPE
- Manager.
+ provided when upgrading or uninstalling the Enea Edge
+ Management.
@@ -590,13 +587,13 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
- Heap Configuration: Please enter the new Maximum Heap
- Size [4g] :
+ Heap Configuration: Please enter the new
+ Maximum Heap Size [4g] :
- Create the self-signed certificate:
- Specify IP or domain name:
+ Create the self-signed certificate: Specify IP
+ or domain name:
The certificate can be generated again by running the
@@ -619,8 +616,8 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
- Install the Enea uCPE Manager as a service with the name
- ucpemanager .
+ Install the Enea Edge Management as a service with the
+ name ucpemanager .
@@ -631,8 +628,8 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
Using the IPv4 address of the CentOS 7 Server in a web
- browser, running on the laptop, log into the Enea uCPE Manager GUI
- using the default username and password:
+ browser, running on the laptop, log into the Enea Edge Management
+ GUI using the default username and password:
admin/admin .
@@ -645,47 +642,48 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gzIf the CentOS 7 Server is installed behind NAT, the IPv4
address used will be the public IP of the NAT device and port
forwarding rules must be created to ensure the uCPE device can
- access the Enea uCPE Manager. For more details, please see Firewall Configuration.
- Installation of the Enea uCPE Manager using a System
+ Installation of the Enea Edge Management using a System
Back-up
- The Enea uCPE Manager can be restored if a backup file has been
- previously created.
+ The Enea Edge Management can be restored if a backup file has
+ been previously created.
A backup file can be created by accessing the System menu, and clicking System Backup , from the Enea uCPE Manager GUI.
- The resulting zip archive will be located in the
+ role="bold">System Backup, from the Enea Edge Management
+ GUI. The resulting zip archive will be located in the
/opt/ems/ucpemanager/application/backup folder
and will be named
SystemBackup_MMMDD_YYYY_HHMM_SS.zip (e.g
System-Backup_Feb19_2013_2257_42.zip). Save the archive to another
- location outside the Enea uCPE Manager installation folder for future
- use.
+ location outside the Enea Edge Management installation folder for
+ future use.
- The System Back-up file obtained from the Enea uCPE Manager
+ The System Back-up file obtained from the Enea Edge Management
GUI (SystemBackup_MMMDD_YYYY_HHMM_SS.zip ) is
- different from the snapshot obtained during a Enea uCPE Manager
+ different from the snapshot obtained during a Enea Edge Management
Upgrade or Uninstall operation
(ucpemanager-Backup-YYYYddMMHHmm.tar.gz ) needed
- for recovery of the Enea uCPE Manager. For more details, see Restoring a previous uCPE
- Manager installation in the Restoring a previous Enea Edge
+ Management installation in the
Manual.
- To install the Enea uCPE Manager with the restore option provide
- an additional argument as shown below during installation:
+ To install the Enea Edge Management with the restore option
+ provide an additional argument as shown below during
+ installation:
./install.sh \
/opt/ems Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz \
@@ -694,11 +692,11 @@ SystemBackup_MMMDD_YYYY_HHMM_SS.zip
- Preparing the USB stick for installation of the Enea NFV Access
- Runtime Platform
+ Preparing the USB stick for installation of the Enea Edge
+ Runtime
- To install the Enea NFV Access Runtime Platform, create a bootable
- USB stick with the image you intend to install.
+ To install the Enea Edge Runtime, create a bootable USB stick with
+ the image you intend to install.
In the example below, step by step instructions are provided for
the CentOS 7 distribution. It's possible with the appropriate tools to
@@ -706,7 +704,7 @@ SystemBackup_MMMDD_YYYY_HHMM_SS.zip
The .hddimg image is available in the
- Enea_NFV_Access_Run_Time_Platform_
+ Enea_Edge_Runtime_Platform_
<processor>_<version>-build<build_number>.tar.gz
file you downloaded with your release.
@@ -760,16 +758,16 @@ of=/dev/sdb bs=4M conv=fsync
While the uCPE device is powered off, in order to install and
- configure the Enea NFV Access Runtime Platform (using the prepared USB
- stick), connect the laptop to a uCPE device LAN port. For this purpose,
- a Layer 2 switch or direct cable connection can be used.
+ configure the Enea Edge Runtime (using the prepared USB stick), connect
+ the laptop to a uCPE device LAN port. For this purpose, a Layer 2 switch
+ or direct cable connection can be used.
- Installing Enea NFV Access - uCPE Device Installation
+ Installing Enea Edge - uCPE Device Installation
- To initiate the installation of the Enea NFV Access Runtime
- Platform do the following:
+ To initiate the installation of the Enea Edge Runtime do the
+ following:
@@ -852,24 +850,24 @@ of=/dev/sdb bs=4M conv=fsync
- On the Enea uCPE Manager
+ On the Enea Edge Management
settings page of the Web-installer, the user must fill
in:
- The static Enea uCPE Manager IP Address. This can be
+ The static Enea Edge Management IP Address. This can be
either:
- The IP address of the Enea uCPE Manager host machine,
- if the device can directly access it.
+ The IP address of the Enea Edge Management host
+ machine, if the device can directly access it.
- The IP address of the NAT device, if the Enea uCPE
- Manager host is located behind a NAT. For more details,
+ The IP address of the NAT device, if the Enea Edge
+ Management host is located behind a NAT. For more details,
please see Firewall
Configuration.
@@ -885,7 +883,7 @@ of=/dev/sdb bs=4M conv=fsync
Customer Tags. They are used for Zero Touch Provisioning
(ZTP) and can be left empty for a base configuration. What can
be entered here (if needed), are the tag(s) specified when
- creating an offline configuration in the Enea uCPE Manager. A
+ creating an offline configuration in the Enea Edge Management. A
later addition of customer tags can only be done by reinstalling
the uCPE devices.
@@ -905,7 +903,7 @@ of=/dev/sdb bs=4M conv=fsync
Select a WAN interface to use as the management network
- interface. This interface is used by the Enea uCPE Manager to
+ interface. This interface is used by the Enea Edge Management to
communicate with the uCPE device.
@@ -918,10 +916,10 @@ of=/dev/sdb bs=4M conv=fsync
When the user has completed the configuration steps in the
- Web-installer, Enea NFV Access is installed on the hard drive. At this
+ Web-installer, Enea Edge Runtime is installed on the hard drive. At this
stage, the user should remove the USB stick and the LAN cable, and
shutdown the uCPE device. It will be started after necessary
- configurations are done in the Enea uCPE Manager, as described
+ configurations are done in the Enea Edge Management, as described
below.
@@ -953,13 +951,13 @@ of=/dev/sdb bs=4M conv=fsync
- Network connection between the server running the Enea uCPE
- Manager and the laptop.
+ Network connection between the server running the Enea Edge
+ Management and the laptop.
- Network connection between the server running the Enea uCPE
- Manager and the uCPE device.
+ Network connection between the server running the Enea Edge
+ Management and the uCPE device.
@@ -969,14 +967,14 @@ of=/dev/sdb bs=4M conv=fsync
Management of uCPE Devices
When the installation is complete the uCPE device can be managed in
- the Enea uCPE Manager.
+ the Enea Edge Management.
Add a default Offline Configuration
Zero Touch Provisioning is always turned on when a uCPE device
- connects to the Enea uCPE Manager. To enable it in the Enea uCPE
- Manager, an offline configuration needs to be registered for Day-0
+ connects to the Enea Edge Management. To enable it in the Enea Edge
+ Management, an offline configuration needs to be registered for Day-0
configuration.
@@ -990,8 +988,8 @@ of=/dev/sdb bs=4M conv=fsync
The offline configuration consists of data and parameters that are
meant to be automatically set when a uCPE device connects to the Enea
- uCPE Manager for the first time. The configuration is typically focused
- on setting up the network management of the uCPE device, e.g.
+ Edge Management for the first time. The configuration is typically
+ focused on setting up the network management of the uCPE device, e.g.
configuring network interfaces, WAN and LAN networking and service
chains.
@@ -1003,14 +1001,14 @@ of=/dev/sdb bs=4M conv=fsync
If the offline configuration is not configured, an alarm will be
raised: Day-0 Config:ZTP:Major when the uCPE device
- tries to connect to the Enea uCPE Manager, informing the user that the
- ZTP setup failed for the uCPE device.
+ tries to connect to the Enea Edge Management, informing the user that
+ the ZTP setup failed for the uCPE device.
To create an offline
configuration
- In a browser access the Enea uCPE Manager, open In a browser access the Enea Edge Management, open Applications and select Offline Config .
@@ -1024,7 +1022,7 @@ of=/dev/sdb bs=4M conv=fsync
The name is user defined and can be set to any unique text
string identifying the configuration. The
- deviceVersion must match the Enea NFV Access
+ deviceVersion must match the Enea Edge Runtime
version of the uCPE device and the deviceId
must be the previously set identifier of the uCPE device
(DeviceId).
@@ -1037,8 +1035,8 @@ of=/dev/sdb bs=4M conv=fsync
In order to enroll a uCPE device in the management system and
establish a management connection, the user will add uCPE device
- information in the Enea uCPE Manager. This is accomplished by going to
- Devices , selecting Devices , selecting Manage and then clicking the Add button.
@@ -1052,7 +1050,7 @@ of=/dev/sdb bs=4M conv=fsync
Name. The name by which the
- uCPE device is referred to in the Enea uCPE Manager.
+ uCPE device is referred to in the Enea Edge Management.
(Mandatory).
@@ -1096,8 +1094,8 @@ of=/dev/sdb bs=4M conv=fsync
Booting the uCPE device and adding it to the Map
- When connectivity is established with the Enea uCPE Manager and a
- uCPE device is already registered with a matching Device
+ When connectivity is established with the Enea Edge Management and
+ a uCPE device is already registered with a matching Device
ID , the installation is complete, and the connection is
established.
@@ -1108,12 +1106,13 @@ of=/dev/sdb bs=4M conv=fsync
In case of management connection failure (e.g. due to a
misconfiguration), the uCPE device status will be seen as RED
- (disconnected) in the Enea uCPE Manager. The uCPE device configuration
- can be corrected by removing the WAN cable(s), reconnecting the laptop
- to the LAN interface of the uCPE device and rebooting it. At this point,
- the Web-installer can be accessed from the laptop as described in Installing Enea NFV Access - uCPE Device
+ targetptr="install_ena_device">Installing Enea Edge - uCPE Device
installation in the
uCPE Device Monitorization and Control
- Once the uCPE device is connected to the Enea uCPE Manager, it is
+ Once the uCPE device is connected to the Enea Edge Management, it is
ready for central management. Two important functions available in the
- Enea uCPE Manager GUI are alarm checking and resource allocation.
+ Enea Edge Management GUI are alarm checking and resource
+ allocation.
Checking Alarms
- The Enea uCPE Manager dashboard presents alarms in a specific
+ The Enea Edge Management dashboard presents alarms in a specific
window on the front page.
An alarm can be easily triggered by disconnecting and reconnecting
@@ -1141,15 +1141,15 @@ of=/dev/sdb bs=4M conv=fsync
Disconnected::Critical .
A separate Alarm Management window can be accessed from the Enea
- uCPE Manager menu for in-depth access and programming of Alarms and
+ Edge Management menu for in-depth access and programming of Alarms and
Events.
Checking uCPE device Resource Allocation
- When the uCPE device is connected to the Enea uCPE Manager it is
- of interest to check the amount of hardware resources in use.
+ When the uCPE device is connected to the Enea Edge Management it
+ is of interest to check the amount of hardware resources in use.
To check CPU, RAM and disk utilization simply select the uCPE
device and go to the Virtual Machines
@@ -1167,9 +1167,9 @@ of=/dev/sdb bs=4M conv=fsync
access. The default user and password are root and
blank, respectively.
- The Enea NFV Access CLI is a pure Linux CLI providing access to
- standard Linux CLI commands. The CLI is a central feature for running
- custom scripting.
+ This is a pure Linux CLI providing access to standard Linux CLI
+ commands. The CLI is a central feature for running custom
+ scripting.
In case the uCPE device was installed behind a NAT device, the
diff --git a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
index 5f8a5ad..4dec1e1 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
@@ -4,12 +4,12 @@
Overview
- This document describes the Enea NFV Access and provides installation
+ This document describes the Enea Edge and provides installation
steps for deploying a base configuration in order to create:
- A functional uCPE Management installation ready to manage uCPE
+ A functional Enea Edge Management installation ready to manage uCPE
devices.
@@ -23,32 +23,32 @@
following chapters.
- Enea NFV Access
+ Enea Edge
- Enea NFV Access for universal Customer Premise Equipment (uCPE) is a
+ Enea Edge for universal Customer Premise Equipment (uCPE) is a
virtualization and management platform, which allows end-users to onboard,
instantiate, and run third-party VNFs onto their systems. It is comprised
of two major components working in close cooperation:
- The Enea NFV Access Runtime Platform, which acts as the host
+ The Enea Edge Runtime, which acts as the host
for Virtualized Network Functions (VNFs) and provides management over
NETCONF.
- The Enea uCPE Manager, a solution that runs on an external
+ The Enea Edge Management, a solution that runs on an external
server, used for VNF Management and managing large numbers of uCPE
devices.
- In addition, Enea NFV Access also includes a software framework for
- Automation and Testing (AFTH). More information can be found in
+ In addition, Enea Edge includes a framework for
+ automation and testing. More information can be found in
.
+ xpointer="element(book_enea_nfv_access_auto_fw_user_guide/1)" />.
Details concerning release content, including documentation
structure, are provided in the
- Enea NFV Access Runtime Platform
+ Enea Edge Runtime
- Enea NFV Access Runtime Platform is a lightweight,
+ Enea Edge Runtime is a lightweight,
multi-architecture virtualization platform built on de-facto standards
in an SDN/NFV ecosystem. It is designed for a high networking
performance with minimal hardware footprint, by only providing relevant
@@ -87,19 +87,19 @@
- Enea uCPE Manager
+ Enea Edge Management
- The Enea uCPE Manager is centralized control system providing
+ The Enea Edge Management is centralized control system providing
uCPEs domain management capabilities through a GUI and REST API. It can
be deployed on a host or a virtual machine running 64-bit CentOS 7 on an
- x86 platform. The Enea uCPE Manager uses a southbound NETCONF protocol
+ x86 platform. The Enea Edge Management uses a southbound NETCONF protocol
to connect and manage uCPE devices.
- The Enea uCPE Manager provides the following key features:
+ The Enea Edge Management provides the following key features:
- Enea NFV Access Runtime Platform Software Management
+ Enea Edge Runtime Software Management
@@ -141,21 +141,21 @@
- Enea NFV Access
+ Enea Edge
- The Enea NFV Access Runtime Platform and the Enea uCPE
- Manager.
+ The Enea Edge Runtime and the Enea Edge
+ Management.
- Enea NFV Access Runtime Platform
+ Enea Edge Runtime
A lightweight, multi-architecture virtualization
platform, supporting Virtual Machines.
- Enea uCPE Manager
+ Enea Edge Management
Enea Universal Customer Premises Equipment
Manager.
@@ -164,8 +164,8 @@
uCPE device
- A whitebox running the Enea NFV Access Runtime
- Platform.
+ A whitebox running the Enea Edge
+ Runtime.
diff --git a/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml b/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
index 1b415a2..baa1340 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
@@ -4,13 +4,13 @@
Troubleshooting problems on the uCPE device require an analysis of a
set of information i.e. logs collected from the uCPE device and/or the Enea
- uCPE Manager. The following information describes how the log collection
+ Edge Management. The following information describes how the log collection
mechanism works.
- Log collecting using the Enea uCPE Manager
+ Log collecting using the Enea Edge Management
- The Enea uCPE Manager allows for collecting a set of logs and state
+ The Enea Edge Management allows for collecting a set of logs and state
information from a uCPE device.
@@ -53,7 +53,7 @@
It might take some time for the archive to be created. When the
operation completes, a "CollectLogsComplete" notification is sent from
- the uCPE device to the Enea uCPE Manager. This can be viewed in the
+ the uCPE device to the Enea Edge Management. This can be viewed in the
GUI in the Faults menu, after selecting
Events .
@@ -110,7 +110,7 @@
Downloading Logs from the uCPE Device
This option transfers a debug file archive from the uCPE device to
- Enea uCPE Manager.
+ Enea Edge Management.
@@ -124,8 +124,8 @@
In the Device File Listing table, select
- the archive you want to download from the uCPE device to Enea uCPE
- Manager.
+ the archive you want to download from the uCPE device to Enea Edge
+ Management.
@@ -133,7 +133,7 @@
button.
The archive will be downloaded from the uCPE device and stored
- on the Enea uCPE Manager.
+ on the Enea Edge Management.
@@ -146,9 +146,9 @@
Downloading collected Logs locally
- This option downloads a logs archive from the Enea uCPE Manager to
+ This option downloads a logs archive from the Enea Edge Management to
a local (user) machine for analysis. The archive must first be available
- in the Enea uCPE Manager in order to be downloaded.
+ in the Enea Edge Management in order to be downloaded.
@@ -236,10 +236,10 @@ select Delete Debug Log Archive .
- Deleting a Logs Archive from the Enea uCPE Manager
+ Deleting a Logs Archive from the Enea Edge Management
- This option deletes a logs archive from the Enea uCPE
- Manager.
+ This option deletes a logs archive from the Enea Edge
+ Management.
@@ -259,13 +259,13 @@ table.
Click the Delete button.
- The file will be deleted from the Enea uCPE Manager and the
+ The file will be deleted from the Enea Edge Management and the
table will be updated.
- Deleting the logs file from the Enea uCPE Manager does not
+ Deleting the logs file from the Enea Edge Management does not
affect the file located on the uCPE device.
@@ -274,7 +274,7 @@ table.
Enabling/Disabling of the Log Collector via Permissions
To disable the ability to access/download the uCPE device's
- debug-log files from the Enea uCPE Manager, the appropriate permissions
+ debug-log files from the Enea Edge Management, the appropriate permissions
must be changed:
@@ -320,19 +320,19 @@ then select Configuration .
- Downloading Enea uCPE Manager Logs
+ Downloading Enea Edge Management Logs
- Often, sending the Enea uCPE Manager logs together with collected
+ Often, sending the Enea Edge Management logs together with collected
uCPE device logs to the support team provides important information for
troubleshooting (especially in cases of connectivity issues with the
uCPE device and error popups).
- Enea uCPE Manager log files are located in
- application/logs/ in the Enea uCPE Manager's
+ Enea Edge Management log files are located in
+ application/logs/ in the Enea Edge Management's
installation folder
(e.g./opt/ems/ucpemanager/application/logs ). They
can be copied from that location, or they can be downloaded using the
- Enea uCPE Manager GUI by performing the following:
+ Enea Edge Management GUI by performing the following:
@@ -372,10 +372,10 @@ then select Configuration .
- Log collecting without using the Enea uCPE Manager
+ Log collecting without using the Enea Edge Management
Log collection from uCPE Devices can also be done when there is no
- Enea uCPE Manager connection. A SSH connection to uCPE Device is needed
+ Enea Edge Management connection. A SSH connection to uCPE Device is needed
for use of the log collector script, which can be found in the uCPE Device
file system in /usr/local/enea/ .
diff --git a/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml b/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
index f610651..65dfb2b 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
@@ -1,24 +1,24 @@
-
+
Network Configuration Options
Various Advanced Network Configuration options can be done from Enea
- uCPE Manager GUI.
+ Edge Management GUI.
Device Call Home Connection for Deployment behind NAT
The Device Call Home option enables the initiation of the connection
- between the uCPE Device and the Enea uCPE Manager, from the uCPE device.
- The Device Call Home option is required when deploying a uCPE device
- behind NAT since the IP address of the uCPE device is hidden for the Enea
- uCPE Manager.
+ between the uCPE Device and the Enea Edge Management, from the uCPE
+ device. The Device Call Home option is required when deploying a uCPE
+ device behind NAT since the IP address of the uCPE device is hidden for
+ the Enea Edge Management.
Enable Device Call Home by marking the Device Call Home checkbox
- when registering the uCPE device in Enea uCPE Manager. When using this
- mechanism, the device will initiate a connection to the Enea uCPE Manager
- for NETCONF traffic (over SSH), while the Enea uCPE Manager waits for a
- device connection.
+ when registering the uCPE device in Enea Edge Management. When using this
+ mechanism, the device will initiate a connection to the Enea Edge
+ Management for NETCONF traffic (over SSH), while the Enea Edge Management
+ waits for a device connection.
@@ -90,7 +90,7 @@
virtualization infrastructure and VNFs, they must be configured into the
management system.
- To add an interface into the Enea uCPE Manager, select the uCPE
+ To add an interface into the Enea Edge Management, select the uCPE
device, then from the top toolbar select Configuration , then External Interfaces , Wan Interface Type
WAN interfaces configured during the installation of the uCPE
- device are automatically added in the Enea uCPE manager as type
+ device are automatically added in the Enea Edge Management as type
wan . The WAN interface used for management of the
uCPE device is marked with the Management property
set to True .
@@ -207,12 +207,13 @@
- To edit an interface configuration type from the Enea uCPE
- Manager, select the uCPE device, then from the top toolbar select
- the Configuration menu, then
- External Interfaces and Configuration . The already configured
- interfaces are displayed here, as seen in the figure above.
+ To edit an interface configuration type from the Enea Edge
+ Management, select the uCPE device, then from the top toolbar
+ select the Configuration menu,
+ then External Interfaces and
+ Configuration . The already
+ configured interfaces are displayed here, as seen in the figure
+ above.
@@ -259,11 +260,11 @@
- To edit an interface configuration from the Enea uCPE
- Manager, select the uCPE device, then from the top toolbar select
- the Configuration menu then
- External Interfaces and select
- Configuration . The already
+ To edit an interface configuration from the Enea Edge
+ Management, select the uCPE device, then from the top toolbar
+ select the Configuration menu
+ then External Interfaces and
+ select Configuration . The already
configured interfaces will be displayed here.
@@ -304,9 +305,9 @@
Correct Country Code
selection is mandatory. All configuration options are available in
- the Enea uCPE Manager GUI but only the Radio Settings that conform
- with the selected country's official regulatory laws will be applied
- when the Wireless AP is started on the uCPE Device.
+ the Enea Edge Management GUI but only the Radio Settings that
+ conform with the selected country's official regulatory laws will be
+ applied when the Wireless AP is started on the uCPE Device.
@@ -319,8 +320,8 @@
role="bold">External Interfaces, where a list of available
network interfaces and their capabilities can be found.
- After networking interfaces have been added to the Enea uCPE
- Manager, the user can change the interface type (DPDK, SR-IOV,
+ After networking interfaces have been added to the Enea Edge
+ Management, the user can change the interface type (DPDK, SR-IOV,
Standard, WAN, WAP).
@@ -339,8 +340,8 @@
@@ -537,7 +538,7 @@
physically present (initially) to manage the device.
An offline configuration is usually prepared in advance for the Enea
- uCPE Manager to setup the virtualization infrastructure on the uCPE
+ Edge Management to setup the virtualization infrastructure on the uCPE
device, as soon as a device enrolls into the management system.
@@ -551,12 +552,12 @@
Alternatively, a wildcard can be used in the Device
ID field, which results in a configuration being pushed on all
- uCPE devices upon their initial connection towards the Enea uCPE
- Manager.
+ uCPE devices upon their initial connection towards the Enea Edge
+ Management.
If the offline configuration is not configured for a uCPE device,
an alarm will be raised: Day-0 Config:ZTP:Major ,
- which occurs when the uCPE device connects to the Enea uCPE Manager
+ which occurs when the uCPE device connects to the Enea Edge Management
informing that the ZTP setup failed for the specific uCPE device.
To create an offline configuration, select from the top toolbar
@@ -598,10 +599,10 @@
The Name is user defined and can be set to any unique text string
identifying the configuration. The Device Version will match the Enea
- NFV Access version of the uCPE device and the Device ID will be set to
- the previously set identifier of the uCPE device.
+ Edge version of the uCPE device and the Device ID will be set to the
+ previously set identifier of the uCPE device.
- When a device connects to the Enea uCPE Manager for the first
+ When a device connects to the Enea Edge Management for the first
time, it checks the device to see if it has been Zero Touch Provisioned
(ZTP). If not, it looks for an offline configuration that matches these
values, in the following order:
@@ -632,7 +633,7 @@
The ZTP will only be triggered the first time a uCPE device
- connects to the Enea uCPE Manager. Just changing an offline
+ connects to the Enea Edge Management. Just changing an offline
configuration will not push the new changes to the device. If an
offline configuration is changed after uCPE device registration, a
factory reset can be executed to force a new ZTP to execute. Select
@@ -654,29 +655,29 @@
Uploading Scripts
- The scripts need to be uploaded to the Enea uCPE Manager prior to
- use. When uploading scripts to the Enea uCPE Manager make sure to select
- the right script type.
+ The scripts need to be uploaded to the Enea Edge Management prior
+ to use. When uploading scripts to the Enea Edge Management make sure to
+ select the right script type.
The following script types are supported:
- Once-before-startup . This script will only
- execute once after the system has rebooted, prior to processing any
- device configuration.
+ Once-before-startup . This script will only
+ execute once after the system has rebooted, prior to processing any
+ device configuration.
- Always-before-startup . This script will always
- execute after the system has rebooted, prior to processing any device
- configuration.
+ Always-before-startup . This script will
+ always execute after the system has rebooted, prior to processing
+ any device configuration.
- Once-after-startup . The script will always
- execute after the system has rebooted, after all device configuration
- processes have completed.
+ Once-after-startup . The script will always
+ execute after the system has rebooted, after all device
+ configuration processes have completed.
@@ -734,7 +735,7 @@
Select the script you want to delete from the Uploaded Scripts tab and then click Delete , which will remove the script
- immediately from the Enea uCPE Manager.
+ immediately from the Enea Edge Management.
@@ -742,8 +743,8 @@
-
+
Wireless Access Point
- The Wireless AP Screen from the Enea uCPE Manager Configuration menu
- allows users to configure a Wireless Access Point . A
- wap-capable interface and a LAN bridge must be added
+ The Wireless AP Screen from the Enea Edge Management Configuration
+ menu allows users to configure a Wireless Access Point .
+ A wap-capable interface and a LAN bridge must be added
before doing the Wireless AP configuration. For more details see sections
Wap interface Type and Data-plane bridge.
diff --git a/doc/book-enea-nfv-access-getting-started/doc/troubleshooting.xml b/doc/book-enea-nfv-access-getting-started/doc/troubleshooting.xml
index f416f8f..4984a35 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/troubleshooting.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/troubleshooting.xml
@@ -2,19 +2,19 @@
Troubleshooting and Recovery
- In all scenarios where possible, collect the logs for
- debugging. More information on log collecting can be found in
- In all scenarios where possible, collect the logs for debugging. More
+ information on log collecting can be found in Using the Log Collector in the
Manual.
- The following is a small list of possible Enea NFV Access problems,
- and their solutions. If you encounter other issues or can't get Enea NFV Access to work
- successfully after consulting the information below, please use the The following is a small list of possible Enea Edge problems, and
+ their solutions. If you encounter other issues or can't get Enea Edge to
+ work successfully after consulting the information below, please use the
+ Enea Support Team Form, available in the
- Enea NFV Access Problem
+ Enea Edge Problem
Solution
@@ -37,11 +37,11 @@
- A uCPE device fails to connect to the Enea uCPE Manager after
- installation.
+ A uCPE device fails to connect to the Enea Edge Management
+ after installation.
- If the uCPE device is not able to connect to the Enea uCPE
- Manager after an installation, the Web-installer application is
+ If the uCPE device is not able to connect to the Enea Edge
+ Management after an installation, the Web-installer application is
started automatically on the uCPE device to change the configuration
via a web browser. Please see
Perform a hardware reboot of the uCPE Device and select
- the previous Enea NFV Access image from the GRUB menu. This
+ the previous Enea Edge Runtime image from the GRUB menu. This
action assumes physical access to the uCPE device.
@@ -77,14 +77,14 @@
- After a failed uCPE device upgrade the previous Enea NFV
- Access image (from the GRUB menu) does not boot.
+ After a failed uCPE device upgrade the previous Enea Edge
+ image (from the GRUB menu) does not boot.
- Reinstall Enea NFV Access on the uCPE device and redeploy the
+ Reinstall Enea Edge on the uCPE device and redeploy the
initial configuration and virtualized services, by following the
steps in Installing Enea NFV Access - uCPE
- Device installation in the Installing Enea Edge - uCPE Device
+ installation in the
@@ -92,8 +92,8 @@
- The Enea uCPE Manager upgrade fails and a working snapshot is
- available.
+ The Enea Edge Management upgrade fails and a working snapshot
+ is available.
If a working snapshot obtained during a previous Upgrade or
Uninstall is available
@@ -109,7 +109,7 @@
Restore the previous installation as described in Restoring a previous
- uCPE Manager installation in the
@@ -119,8 +119,8 @@
- The Enea uCPE Manager upgrade fails and no working snapshot
- is available, but a System Back-up file exists.
+ The Enea Edge Management upgrade fails and no working
+ snapshot is available, but a System Back-up file exists.
@@ -131,10 +131,10 @@
Perform an installation with the restore option of a
- previous Enea uCPE Manager configuration as described in
+ previous Enea Edge Management configuration as described in
Installation of the
- uCPE Manager using a System Back-up in the
@@ -145,7 +145,7 @@
The uCPE device is booted, the ssh connection is available
- but the device is not connected to the Enea uCPE Manager.
+ but the device is not connected to the Enea Edge Management.
@@ -155,7 +155,7 @@
Use the Reconnect
- button from the Enea uCPE Manager's GUI.
+ button from the Enea Edge Management's GUI.
@@ -169,8 +169,8 @@
If the above actions do not work, reinstall and
reconfigure the device using the steps provided in Installing Enea NFV Access -
- uCPE Device installation in the Installing Enea Edge - uCPE
+ Device installation in the
@@ -186,8 +186,8 @@
Perform a hardware reboot on the uCPE device. If the problem
is not fixed, reinstall and reconfigure the device using the steps
provided in Installing Enea NFV Access - uCPE
- Device installation in the Installing Enea Edge - uCPE Device
+ installation in the
@@ -207,16 +207,16 @@
Reboot the device by accessing Operations and then selecting Reboot from within the Enea uCPE
- Manager.
+ role="bold">Reboot from within the Enea Edge
+ Management.
If the above actions do not work, redeploy all services.
- This is done by cleaning up the existing configuration by
-accessing Operations , then selecting
-Factory Reset for a specific device and
-redeploying the VNF services.
+ This is done by cleaning up the existing configuration by
+ accessing Operations , then
+ selecting Factory Reset for a
+ specific device and redeploying the VNF services.
diff --git a/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml b/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
index 1b714f2..e833c2d 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
@@ -1,26 +1,25 @@
-
+
- Upgrading Enea NFV Access
+ Upgrading Enea Edge
Enea provides regular releases that will require the upgrading of Enea
- NFV Access components. The Enea uCPE Manager must be upgraded first,
- followed by upgrading the Enea NFV Access Runtime Platform on the uCPE
- devices.
+ Edge components. The Enea Edge Management must be upgraded first, followed
+ by upgrading the Enea Edge Runtime on the uCPE devices.
- Upgrading the Enea uCPE Manager
+ Upgrading the Enea Edge Management
It is recommended to create a system backup by accessing System and selecting System
- Backup from the Enea uCPE Manager GUI, for recovery in case
- of an upgrade failure.
+ Backup from the Enea Edge Management GUI, for recovery in
+ case of an upgrade failure.
Extract the
- Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
+ Enea_Edge_Management_<version>-build<build_number>.tar.gz
folder.
The directory in which the archive has been unpacked will be
@@ -33,8 +32,8 @@
Run the following command with the root account and change
- /opt/ems to the correct location of the Enea uCPE
- Manager installation:
+ /opt/ems to the correct location of the Enea Edge
+ Management installation:
./upgrade.sh /opt/ems \
Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
@@ -57,7 +56,7 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
The snapshot file created during the upgrade can be used for
- restoring the Enea uCPE Manager.
+ restoring the Enea Edge Management.
@@ -71,24 +70,25 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
- For an example on how to upgrade an Enea uCPE Manager installation in a
- High Availability setup, consult For an example on how to upgrade an Enea Edge Management
+ installation in a High Availability setup, consult Upgrading a High Availability Deployment in the
- Manual.
+
+ Manual.
- Restoring a previous Enea uCPE Manager Installation
+ Restoring a previous Enea Edge Management Installation
- How to restore a previous Enea uCPE Manager
- installation
+ How to restore a previous Enea Edge
+ Management installation
Extract
- Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
+ Enea_Edge_Management_<version>-build<build_number>.tar.gz
@@ -99,8 +99,8 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
Copy the snapshot file
(ucpemanager-Backup-YYYYddMMHHmm.tar.gz )
- created during a previous Enea uCPE Manager Upgrade or Enea uCPE
- Manager Uninstall Operation into the
+ created during a previous Enea Edge Management Upgrade or Enea Edge
+ Management Uninstall Operation into the
<uCPEM-installdir> directory.
@@ -110,8 +110,8 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
Run the following command with the root user and change
- /opt/ems to the correct location of the Enea uCPE
- Manager installation:
+ /opt/ems to the correct location of the Enea Edge
+ Management installation:
./restore.sh /opt/ems ucpemanager-Backup-YYYYddMMHHmm.tar.gz
@@ -126,9 +126,9 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
- Reinstall the Enea uCPE Manager application on the specified
- target location, restoring the data in the database and files in the
- process.
+ Reinstall the Enea Edge Management application on the
+ specified target location, restoring the data in the database and
+ files in the process.
@@ -137,21 +137,22 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
- Uninstalling an existing Enea uCPE Manager Installation
+ Uninstalling an existing Enea Edge Management
+ Installation
- How to uninstall an existing Enea uCPE
- Manager installation
+ How to uninstall an existing Enea Edge
+ Management installation
- Navigate to the folder where the Enea uCPE Manager is
+ Navigate to the folder where the Enea Edge Management is
installed: <uCPEM-installdir> .
Run the following command with the root user and change
- /opt/ems to the correct location of the Enea uCPE
- Manager installation:
+ /opt/ems to the correct location of the Enea Edge
+ Management installation:
./uninstall.sh /opt/ems
@@ -174,7 +175,7 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
The snapshot file created during the uninstall can be used
- for restoring the Enea uCPE Manager.
+ for restoring Enea Edge Management.
@@ -193,7 +194,7 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
- After these steps, the Enea uCPE Manager is completely removed
+ After these steps, the Enea Edge Management is completely removed
from the system.
@@ -201,7 +202,7 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
uCPE device Upgrades
- A uCPE device can be upgraded using the Enea uCPE Manager
+ A uCPE device can be upgraded using the Enea Edge Management
GUI.
@@ -266,7 +267,7 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
The uCPE Device upgrade is done with image files of the type
rootfs.ostree.tar.bz2 , which are available in the
- Enea_NFV_Access_Run_Time_Platform_<processor>_<version>-build<build_number>.tar.gz
+ Enea_Edge_Runtime_<processor>_<version>-build<build_number>.tar.gz
file you downloaded with your release.
@@ -362,7 +363,7 @@ Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
- The hour represents the local Enea uCPE Manager server
+ The hour represents the local Enea Edge Management server
hour.
diff --git a/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml b/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
index e8c65eb..fbf7091 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
@@ -2,17 +2,17 @@
VNF Management
- The Enea uCPE Manager is responsible for onboarding, configuring (e.g.
- CloudInit) and ensuring life cycle management of VNFs that are instantiated
- and run on the various uCPE devices.
+ The Enea Edge Management is responsible for onboarding, configuring
+ (e.g. CloudInit) and ensuring life cycle management of VNFs that are
+ instantiated and run on the various uCPE devices.
Onboarding a VNF
- The onboarding of a VNF means adding it to the Enea uCPE Manager VNF
- Catalogue and preparing it for instantiation (deployment on connected uCPE
- devices). This is accomplished using the Enea uCPE Manager Onboarding
- graphical user interface.
+ The onboarding of a VNF means adding it to the Enea Edge Management
+ VNF Catalogue and preparing it for instantiation (deployment on connected
+ uCPE devices). This is accomplished using the Enea Edge Management
+ Onboarding graphical user interface.
Typically, the Getting Started Guide of a VNF, provided by the VNF
vendor, contains all necessary information needed to onboard a VNF.
@@ -35,8 +35,8 @@
There are no standard ways of managing VNF licenses,
therefore no general guidelines can be provided. One example of
- license handling that can be employed in the Enea uCPE Manager is
- the adding of a license during the Cloud-Init setup.
+ license handling that can be employed in the Enea Edge Management
+ is the adding of a license during the Cloud-Init setup.
@@ -109,32 +109,35 @@
- Onboarding into the Enea uCPE Manager
+ Onboarding into the Enea Edge Management
- How to onboard a VNF into the Enea uCPE
- Manager
+ How to onboard a VNF into the Enea Edge
+ Management
- Select from the top toolbar VNF
- and then Descriptors .
+ Select from the top toolbar VNF and then Descriptors .
- Click the On-board button.
+ Click the On-board
+ button.
- When prompted by the UI, make sure the VM
- Image radio button at the top of the onboarding screen is
- selected, it will trigger a popup menu window.
+ When prompted by the UI, make sure the VM Image radio button at the top of the
+ onboarding screen is selected, it will trigger a popup menu
+ window.
This window contains data fields where both necessary and optional
information about the VNF can be supplied. After doing so, press the
- Onboard button, the Enea uCPE Manager will create the VNF descriptor and
- add it to its VNF Catalog.
+ Onboard button, the Enea Edge Management will create the VNF descriptor
+ and add it to its VNF Catalog.
Onboard a VNF
@@ -153,8 +156,8 @@
VM Image File . This is the
Virtual Machine image file for the VNF. Typically, it is a QCOW
- image. Press Choose File and select the image you
- wish to upload.
+ image. Press Choose File and select
+ the image you wish to upload.
@@ -171,7 +174,7 @@
Description . This field
contains any description provided and is only displayed in the GUI
- tables in the Enea uCPE Manager.
+ tables in the Enea Edge Management.
@@ -203,14 +206,14 @@
Interfaces Tab
- Click on the Interfaces tab to show the
- Interfaces table.
+ Click on the Interfaces tab to
+ show the Interfaces table.
This table will contain the interfaces required by this VNF to be
configured, when creating an instance. Consult the VNF vendor to
determine which and how many are required. Each interface requires a
- name, and optionally a description, used only by the Enea uCPE
- Manager.
+ name, and optionally a description, used only by the Enea Edge
+ Management.
CAUTION: The user MUST conserve the same order for the virtual
@@ -219,9 +222,9 @@
Cloud Init Tab
- Click the Cloud Init tab to provide the
- Cloud-Init configuration. There are three fields that need to be
- populated:
+ Click the Cloud Init tab to
+ provide the Cloud-Init configuration. There are three fields that need
+ to be populated:
@@ -273,7 +276,7 @@
The Content Files Table is ONLY used if
ConfigDrive is chosen as the Cloud-Init
Datasource. For each content file added, a Path
- must be provided. When the Enea uCPE Manager is used to create an
+ must be provided. When the Enea Edge Management is used to create an
instance for multiple VNFs, the user will be prompted to provide a
data file for each entry in this table. Each type of VNF will
require different cloud-init files, e.g.: a license file. The data
@@ -292,9 +295,9 @@
In this table, you can enter values for properties that will be
used during instantiation of the VNF. The values will augment the
default values in the domain.xml file used by
- libvirt/virsh (running in Enea NFV Access) when
- creating an instance of the VNF. Consult with the VNF Vendor or ENEA
- support for values needed by specific VNFs.
+ libvirt/virsh (running in Enea Edge) when creating an
+ instance of the VNF. Consult with the VNF Vendor or ENEA support for
+ values needed by specific VNFs.
Property Values
@@ -349,8 +352,8 @@
- Select from the top toolbar VNF and
- choose Instances .
+ Select from the top toolbar VNF
+ and choose Instances .
@@ -406,13 +409,14 @@
- Hit the Create button to deploy the VNF and
- run it on the specified uCPE device.
+ Hit the Create button to deploy
+ the VNF and run it on the specified uCPE device.
- Selecting the VNF menu then choosing Events
- will show that the VNF was created and a connection was established.
+ Selecting the VNF menu then
+ choosing Events will show that the VNF
+ was created and a connection was established.
@@ -425,8 +429,9 @@
- SSH to the uCPE device from the Enea uCPE Manager
- (Access the Device menu and select SSH ) using:
+ SSH to the uCPE device from the Enea Edge Management (Access the
+ Device menu and select SSH ) using:
@@ -440,12 +445,13 @@
For reverse ssh connections (ssh to a uCPE device behind
NAT): the Username (default: root) and the
Reverse ssh checkbox checked. The port will be
- automatically choosen by the Enea uCPE Manager in the range
- defined in the SSH configuration panel,
- available when accessing System , then
- Configuration and choosing Reverse
- SSH . By default, the start port will
- be 7000 and the maximum number of ports
+ automatically chosen by the Enea Edge Management in the range
+ defined in the SSH configuration
+ panel, available when accessing System , then Configuration and choosing Reverse SSH . By default, the start port
+ will be 7000 and the maximum number of ports
allocated to all devices is 10. Only one port per device is
allowed.
diff --git a/doc/book-enea-nfv-access-getting-started/swcomp.mk b/doc/book-enea-nfv-access-getting-started/swcomp.mk
index ca6439f..52b433e 100755
--- a/doc/book-enea-nfv-access-getting-started/swcomp.mk
+++ b/doc/book-enea-nfv-access-getting-started/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-getting-started
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) Getting Started"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Getting Started"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/about.xml b/doc/book-enea-nfv-access-platform-open-source/doc/about.xml
index 377562c..2a8bf01 100644
--- a/doc/book-enea-nfv-access-platform-open-source/doc/about.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/about.xml
@@ -4,5 +4,5 @@
About this Report
- This document contains the open source and license information pertaining to packages provided with this release of the Enea NFV Access Runtime Platform and the Installer.
+ This document contains the open source and license information pertaining to packages provided with this release of the Enea Edge Runtime and the Installer.
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/book.xml b/doc/book-enea-nfv-access-platform-open-source/doc/book.xml
index a17bb3d..1150b11 100644
--- a/doc/book-enea-nfv-access-platform-open-source/doc/book.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access Runtime Platform Open Source Report
+ Enea Edge Runtime Open Source Report
Release Version
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
index 352f820..6f9aa06 100644
--- a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
@@ -538,13 +538,13 @@ specific documentation.-->
enea-nfv-access-vnf
1.0
- VNF image of the Enea NFV Access Platform includes kernel rootfs and boot parameters
+ VNF image of the Enea Edge Runtime includes kernel rootfs and boot parameters
MIT
enea-nfv-access
1.0
- Image for the host side of the Enea NFV Access Platform with ODM and NETCONF Edgelink customizations
+ Image for the host side of the Enea Edge Runtime with ODM and NETCONF Edgelink customizations
MIT
@@ -1738,13 +1738,13 @@ specific documentation.-->
nfv-installer
1.0
- Enea NFV Access installer
+ Enea Edge installer
Enea
nfva-cfgtool
1.0
- Command line tool to for accessing the Enea NFV Access install configuration json file
+ Command line tool to for accessing the Enea Edge install configuration json file
Enea
@@ -1960,7 +1960,7 @@ specific documentation.-->
packagegroup-enea-wifi
1.0
- This package group includes packages and packagegroups that enable WiFi connectivity in the Enea NFV Access platform
+ This package group includes packages and packagegroups that enable WiFi connectivity in the Enea Edge Runtime
MIT
diff --git a/doc/book-enea-nfv-access-platform-open-source/swcomp.mk b/doc/book-enea-nfv-access-platform-open-source/swcomp.mk
index fc62acc..20202e4 100644
--- a/doc/book-enea-nfv-access-platform-open-source/swcomp.mk
+++ b/doc/book-enea-nfv-access-platform-open-source/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-platform-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access Runtime Platform Open Source Report"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Runtime Open Source Report"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
index 2078a30..960f136 100644
--- a/doc/book-enea-nfv-access-release-info/doc/about_release.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
@@ -4,13 +4,13 @@
About This Release
- Enea NFV Access is a complete NFVI software platform designed for
+ Enea Edge is a complete NFVI software platform designed for
deployment on any white box uCPE device, and optimized for common use cases.
- Enea NFV Access includes both the Runtime Platform deployed on a white box,
+ Enea Edge includes both the Enea Edge Runtime deployed on a white box,
and a management component with automation tools deployed in a private or
public cloud.
- The Enea NFV Access The Enea Edge Release includes a new version of
@@ -20,29 +20,29 @@
Improvements.
- Enea NFV Access Release Content
+ Enea Edge Release Content
The release content is detailed below:
- Enea_NFV_Access_Run_Time_Platform_C3000_<version>-build<build_number>.tar.gz
+ Enea_Edge_Runtime_C3000_<version>-build<build_number>.tar.gz
- Enea_NFV_Access_Run_Time_Platform_XeonD_<version>-build<build_number>.tar.gz
+ Enea_Edge_Runtime_XeonD_<version>-build<build_number>.tar.gz
- Enea_NFV_Access_AutomationFramework_<version>-build<build_number>.zip
+ Enea_Edge_Automation_<version>-build<build_number>.zip
- Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
+ Enea_Edge_Management_<version>-build<build_number>.tar.gz
- Enea_NFV_Access_Telemetry_Deploy_<version>-build<build_number>.tar.gz
+ Enea_Edge_Telemetry_Deploy_<version>-build<build_number>.tar.gz
@@ -50,14 +50,14 @@
- Enea_NFV_Access_AF-TH_<version>-build<build_number>.zip
+ Enea_Edge_AF-TH_<version>-build<build_number>.zip
(deprecated, see Section 2.1 New Features and
Improvements .)
-- documentation/
- /* Enea NFV Access documentation */
+ /* Enea Edge documentation */
-- README
-- aarch64 /* architecture */
-- cn8304/
@@ -104,13 +104,13 @@
User Documentation
- This release of Enea NFV Access contains the following set of
+ This release of Enea Edge contains the following set of
documents:
- Enea NFV Access Release Information. Describes the Enea NFV
- Access release content, main changes, the list of known issues and
+ Enea Edge Release Information. Describes the Enea Edge
+ release content, main changes, the list of known issues and
limitations.
@@ -118,7 +118,7 @@
.
- Describes how to deploy and upgrade an Enea NFV Access base
+ Describes how to deploy and upgrade an Enea Edge base
configuration, advanced configurations of the system and
troubleshooting information.
@@ -135,14 +135,14 @@
.
- Describes the Automation Framework for Enea NFV Access.
+ Describes the Automation Framework for Enea Edge.
. Describes the
- Automation Framework and Test Harness for Enea NFV Access and
+ Automation Framework and Test Harness for Enea Edge and
provides instructions regarding the necessary steps to run these
software tools (deprecated, see
Section 2.1 New Features
@@ -153,7 +153,7 @@
.
- Describes a sample Test Suite for System Testing of Enea NFV Access.
+ Describes a sample Test Suite for System Testing of Enea Edge.
(deprecated, see Section 2.1
New Features and Improvements ).
diff --git a/doc/book-enea-nfv-access-release-info/doc/book.xml b/doc/book-enea-nfv-access-release-info/doc/book.xml
index 4a1e390..cffe9b5 100644
--- a/doc/book-enea-nfv-access-release-info/doc/book.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access Release
+ Enea Edge Release
Information
Release Version
diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
index 31d3a03..d71deff 100644
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
@@ -9,7 +9,7 @@
- LXCR-9904 Enea NFV Access cannot be installed on
+ LXCR-9904 Enea Edge Runtime cannot be installed on
USB storage devices.
@@ -20,13 +20,13 @@
ELCCR-527 Cancelling a file upload in the Enea
- uCPE Manager will require the user to close and reopen the upload window
+ Edge Management will require the user to close and reopen the upload window
for the next upload to work.
- ELCCR-577 If a uCPEM is restored from a backup
- made on a release version older than 2.2.3, VNFs cannot be instantiated
+ ELCCR-577 If Enea Edge Management is restored from a backup
+ made on a release version older than Enea NFV Access 2.2.3, VNFs cannot be instantiated
from the GUI.
@@ -45,8 +45,7 @@
ELCCR-847 The Juniper vSRX VNF cannot be
instantiated on the Xeon-D architectures due to missing CPU features in
- the VNF's domain XML. This impacts all example use cases and AF&TH
- tests where the Juniper VNF is used.
+ the VNF's domain XML. This impacts all example use cases where the Juniper VNF is used.
@@ -58,33 +57,33 @@
LXCR-9992 Depending on hardware capabilities,
there are certain limitations regarding the vfio-pci
- and igb_uio drivers. While the Enea NFV Access Run
- Time Platform uses the vfio-pci driver by default,
+ and igb_uio drivers. While the Enea Edge
+ Runtime uses the vfio-pci driver by default,
for certain hardware configurations, igb_uio should
be used instead, by providing custom scripting. Please contact Enea for
further details.
- STCR-6224 The Enea NFV Access Automation Framework
- and the Enea NFV Access Automation Framework and Test Harness do not
+ STCR-6224 The Enea Edge Automation
+ and the Enea Edge Automation Framework and Test Harness do not
support multiple custom scripts uploaded to a uCPE device at the same
time.
STCR-6292 Management of WAN Interfaces is not
- implemented in the Automation Framework and Test Harness.
+ implemented in the Enea Edge Automation Framework and Test Harness.
- USERDOCAP-628 Enea NFV Access Automation Framework
+ USERDOCAP-628 Enea Edge Automation Framework
and Test Harness does not have support for product features implemented
- in Enea NFV Access 2.4.0 or newer.
+ in Enea Edge 2.4.0 or newer.
- ELCCR-912 When the Enea uCPE Manager is installed
+ ELCCR-912 When the Enea Edge Management is installed
on CentOS 7, prior to C7.1804 (kernel version 3.10.0-862), adding an
upgrade image fails. As a workaround, please update glib2
to version 2.54.2 or later, using #yum update glib2 .
@@ -101,8 +100,8 @@
- USERDOCAP-641 Enea NFV Access does not have support
- for IPv6 addresses on both uCPE devices and the Enea uCPE Manager
+ USERDOCAP-641 Enea Edge does not have support
+ for IPv6 addresses on both uCPE devices and the Enea Edge Management
installation.
@@ -125,14 +124,14 @@
ELCCR-1371 The current self-signed certificate for
- the Enea uCPE Manager is generated at build time, with a hard-coded common-name
+ the Enea Edge Management is generated at build time, with a hard-coded common-name
causing the uCPE device upgrade to fail in HTTPS mode. As a workaround,
another certificate (containing an IP based common-name) must be generated.
Perform the following the steps to generate the certificate:
- Stop the uCPE Manager service.
+ Stop the Enea Edge Management service.
Create the certificate using the
createCertificate.sh script from distribution
@@ -141,7 +140,7 @@
/opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates
folder.
- Start the Enea uCPE Manager, the new certificate
+ Start the Enea Edge Management, the new certificate
should now take effect.
diff --git a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
index 10faf28..c01a149 100644
--- a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
@@ -6,8 +6,7 @@
Below you'll find information about the new features and updates made
in this release, as well as details on the provided packages and the
- backwards compatibility with previous versions of Enea NFV Access if
- applicable.
+ backwards compatibility with previous versions.
New Features and Improvements
@@ -27,22 +26,22 @@
CPDX-3498 High Availability support with redundant
- Enea uCPE Managers in active standby configuration.
+ Enea Edge Management in active standby configuration.
CPDX-3407 HTTPS based downloads of VNFs for
- simplified deployment of the Enea uCPE Manager in cloud
+ simplified deployment of the Enea Edge Management in cloud
environments.
- CPDX-3500 The Enea NFV Access Automation
- Framework, a tool for automatic system configuration based on Python
- scripting that will replace the existing Enea NFV Access Automation
+ CPDX-3500 The Enea Edge Automation,
+ a tool for automatic system configuration based on Python
+ scripting that will replace the existing Enea Edge Automation
Framework and Test Harness in the next major release.
- The Enea NFV Access Automation Framework and Test Harness, and
+ The Enea Edge Automation Framework and Test Harness, and
its related documentation the
- are deprecated starting with Enea NFV Access 2.4.0.
+ are deprecated starting with Enea Edge 2.4.0.
@@ -85,15 +84,15 @@
Platform Snapshots allow users to store, manage and restore
- snapshots of the Enea NFV Access Runtime Platform configuration,
+ snapshots of the Enea Edge Runtime configuration,
with the purpose of recovering after a failed reconfiguration.
This feature is disabled by default.
VNF Snapshots allow users to store, manage and restore
- snapshots of VNFs deployed on the Enea NFV Access Runtime
- Platform, with the purpose of restoring the VNF after a persistent
+ snapshots of VNFs deployed on the Enea Edge
+ Runtime, with the purpose of restoring the VNF after a persistent
VNF failure. This feature is disabled by default.
@@ -117,39 +116,39 @@
Open Source
For more information about the Open Source packages included, please
- refer to the Enea NFV Access Open Source Reports listed below. Each report
+ refer to the Enea Edge Open Source Reports listed below. Each report
contains open source and license information pertaining to packages
provided with this release, for their respective component.
- .
+ xmlns:xi="http://www.w3.org/2001/XInclude" />.
- .
+ xmlns:xi="http://www.w3.org/2001/XInclude" />.
- .
+ xmlns:xi="http://www.w3.org/2001/XInclude" />.
- .
+ xmlns:xi="http://www.w3.org/2001/XInclude" />.
- .
+ xmlns:xi="http://www.w3.org/2001/XInclude" />.
diff --git a/doc/book-enea-nfv-access-release-info/swcomp.mk b/doc/book-enea-nfv-access-release-info/swcomp.mk
index 3ba7c8d..76991ee 100644
--- a/doc/book-enea-nfv-access-release-info/swcomp.mk
+++ b/doc/book-enea-nfv-access-release-info/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-release-info
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) Release Information"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Release Information"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/book.xml b/doc/book-enea-nfv-access-system-test-specification/doc/book.xml
index 2620554..9192ef5 100644
--- a/doc/book-enea-nfv-access-system-test-specification/doc/book.xml
+++ b/doc/book-enea-nfv-access-system-test-specification/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access System Test Specification
+ Enea Edge System Test Specification
Release Version
Test Objects
- The test objects for the Test Harness are the Enea NFV Access and
- Enea uCPE Manager installations performed as indicated in the The test objects for the Test Harness are the Enea Edge and
+ Enea Edge Management installations performed as indicated in the Components chapter of the
Before running any test case, make sure the uCPE device(s) needed
- have been added to the uCPE Manager.
+ have been added to the Enea Edge Management.
For detailed execution steps of the sample test cases included with
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml b/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml
index 5a04673..07c5ef7 100644
--- a/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml
+++ b/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml
@@ -3,7 +3,7 @@
Overview
This document describes the Test Harness (TH) sample test cases for
- the System Testing of Enea NFV Access, and the necessary environment setup
+ the System Testing of Enea Edge, and the necessary environment setup
to run these tests successfully.
@@ -25,10 +25,10 @@
- Enea NFV Access
+ Enea Edge
- The Enea NFV Access (with ODM) Runtime Platform and the
- Enea uCPE Manager.
+ The Enea Edge (with ODM) Runtime and the
+ Enea Edge Management.
@@ -52,7 +52,7 @@
AF
- Automation Framework for Enea NFV Access.
+ Automation Framework for Enea Edge.
@@ -88,11 +88,11 @@
TH
- Test Harness for Enea NFV Access.
+ Test Harness for Enea Edge.
- uCPE Manager
+ Enea Edge Management
Enea Universal Customer Premises Equipment Manager.
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
index 2fa087b..b1bfa1e 100644
--- a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
+++ b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
@@ -9,14 +9,14 @@
VNF, Device and Network Smoke Test Cases
The following is an automated test suite that acts as basic smoke
- tests for Enea NFV Access, and as a sanity-check test suite for the AF and
+ tests for Enea Edge, and as a sanity-check test suite for the AF and
TH.
VNF - Onboard a VNF Image
Description: Onboarding a VNF
- Image into the uCPE Manager. For details please refer to:
+ Image into the Enea Edge Management. For details please refer to:
@@ -61,7 +61,7 @@ vnfd=<VNF-Descriptor-name>"
VNF - Offboard a VNF
Description: Removing a VNF
- Descriptor from the uCPE Manager. For details please refer to:
+ Descriptor from the Enea Edge Management. For details please refer to:
@@ -74,7 +74,7 @@ vnfd=<VNF-Descriptor-name>"
Precondition: The VNF has been
- previously onboarded in the uCPE Manager instance.
+ previously onboarded in the Enea Edge Management instance.
Action: Run the
offboardVNF.yml Ansible Playbook with the
@@ -93,7 +93,7 @@ vnfd=<VNF-Descriptor-name>"
Device - Add a device
Description: Adding a uCPE device
- to the uCPE Manager. For details please refer to:
+ to the Enea Edge Management. For details please refer to:
@@ -123,10 +123,10 @@ vnfd=<VNF-Descriptor-name>"
- Device - Upload a NFV Access image
+ Device - Upload a Edge image
- Description: Upload a NFV Access
- image file onto the uCPE Manager. For details please refer to:
+ Description: Upload a Edge
+ image file onto the Enea Edge Management. For details please refer to:
@@ -172,7 +172,7 @@ A file with the same name is already uploaded.
Device - Delete Upgraded File
Description: Deleting an uploaded
- NFV Access image file from the uCPE Manager. For details please refer
+ Edge image file from the Enea Edge Management. For details please refer
to:
@@ -186,7 +186,7 @@ A file with the same name is already uploaded.
Preconditions: The image file
- must already be uploaded onto the uCPE Manager.
+ must already be uploaded onto the Enea Edge Management.
Action: Run the
deleteUpgradeFile.yml Ansible Playbook with the
@@ -237,10 +237,10 @@ localhost : ok=1 changed=1 unreachable=0 failed=0
- Device - Install and Activate a NFV Access image
+ Device - Install and Activate a Edge image
Description: Installing and
- Activating a NFV Access image on a uCPE device from the uCPE Manager.
+ Activating a Edge image on a uCPE device from the Enea Edge Management.
For details please refer to:
@@ -255,13 +255,13 @@ localhost : ok=1 changed=1 unreachable=0 failed=0Preconditions:
- The device must be previously added to the uCPE Manager
+ The device must be previously added to the Enea Edge Management
instance.
- The image file must already be uploaded onto the uCPE
- Manager.
+ The image file must already be uploaded onto the Enea Edge
+ Management.
@@ -291,11 +291,11 @@ Duplicate entry - Release already installed
- Device - Upload, Install and Activate a NFV Access image on a
+ Device - Upload, Install and Activate a Edge image on a
uCPE device
Description: Upload, install and
- activate a NFV Access image on a uCPE device from the uCPE Manager. For
+ activate a Edge image on a uCPE device from the Enea Edge Management. For
details please refer to:
@@ -335,7 +335,7 @@ Duplicate entry - Release already installed
- The device has to be previously added to the uCPE Manager
+ The device has to be previously added to the Enea Edge Management
instance.
@@ -371,7 +371,7 @@ upgrade_type=xeon_d
Device - Wait a Device
Description: Wait for a uCPE
- device to connect to the uCPE Manager. For details please refer
+ device to connect to the Enea Edge Management. For details please refer
to:
@@ -388,7 +388,7 @@ upgrade_type=xeon_d
- The device has to be previously added to the uCPE Manager
+ The device has to be previously added to the Enea Edge Management
instance.
@@ -413,7 +413,7 @@ upgrade_type=xeon_d
Device - Remove a Device
Description: Removing a uCPE
- device from the uCPE Manager. For details please refer to:
+ device from the Enea Edge Management. For details please refer to:
@@ -429,7 +429,7 @@ upgrade_type=xeon_d
- The device has to be previously added to the uCPE Manager
+ The device has to be previously added to the Enea Edge Management
instance.
@@ -472,7 +472,7 @@ upgrade_type=xeon_d
A device must have been previously added and connected to the
- uCPE Manager instance.
+ Enea Edge Management instance.
@@ -517,7 +517,7 @@ upgrade_type=xeon_d
- A NIC is bound to a device in a uCPE Manager instance.
+ A NIC is bound to a device in a Enea Edge Management instance.
@@ -556,7 +556,7 @@ upgrade_type=xeon_d
Preconditions:
- A NIC is bound to a device in a uCPE Manager
+ A NIC is bound to a device in a Enea Edge Management
instance.
@@ -599,7 +599,7 @@ upgrade_type=xeon_d
Preconditions:
- A Bridge exists for a device in a uCPE Manager
+ A Bridge exists for a device in a Enea Edge Management
instance.
@@ -638,8 +638,8 @@ bridge=<Bridge-name>"
Precondition:
- A device must have been previously added and connected to the uCPE
- Manager instance.
+ A device must have been previously added and connected to the Enea Edge
+ Management instance.
Action: Run the
configDPDK.yml Ansible Playbook with the
@@ -657,11 +657,11 @@ DEBUG: Set DPDK state to <enable/disable>
- Custom Scripts - Upload a Custom Script to the uCPE
- Manager
+ Custom Scripts - Upload a Custom Script to the Enea Edge
+ Management
Description: Upload a Custom
- Script to the uCPE Manager. For details please refer to:
+ Script to the Enea Edge Management. For details please refer to:
@@ -689,15 +689,15 @@ phase=
run using the Test Harness:
# Upload Custom Script task result
-DEBUG: "{{ scriptName }} was uploaded to uCPE Manager!"
+DEBUG: "{{ scriptName }} was uploaded to Enea Edge Management!"
- Custom Scripts - Upload a Custom Script from the uCPE Manager to
+ Custom Scripts - Upload a Custom Script from the Enea Edge Management to
a Device
Description: Upload a Custom
- Script from the uCPE Manager to a Device. For details please refer
+ Script from the Enea Edge Management to a Device. For details please refer
to:
@@ -715,12 +715,12 @@ DEBUG: "{{ scriptName }} was uploaded to uCPE Manager!"
A device must have been previously added and connected to the
- uCPE Manager instance.
+ Enea Edge Management instance.
- A Custom Script must have been previously added to the uCPE
- Manager instance.
+ A Custom Script must have been previously added to the Enea Edge
+ Management instance.
@@ -741,11 +741,11 @@ DEBUG: "{{ scriptName }} was uploaded to {{ device }}!"
- Custom Scripts - Remove a Custom Script from the uCPE
- Manager
+ Custom Scripts - Remove a Custom Script from the Enea Edge
+ Management
Description: Remove a Custom
- Script from the uCPE Manager. For details please refer to:
+ Script from the Enea Edge Management. For details please refer to:
@@ -759,8 +759,8 @@ DEBUG: "{{ scriptName }} was uploaded to {{ device }}!"
Precondition:
- A Custom Script must have been previously added to the uCPE
- Manager.
+ A Custom Script must have been previously added to the Enea Edge
+ Management.
Action: Run the
removeCustomScript.yml Ansible Playbook with the
@@ -772,8 +772,8 @@ phase=
Result: Output of the test case
run using the Test Harness:
- # Remove Custom Script in phase from uCPE Manager task result
-DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from uCPE Manager!"
+ # Remove Custom Script in phase from Enea Edge Management task result
+DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from Enea Edge Management!"
@@ -797,7 +797,7 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from uCPE Manager!"<
A device must have been previously added and connected to the
- uCPE Manager instance.
+ Enea Edge Management instance.
@@ -827,7 +827,7 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
Store
Description: Adding an Offline
- Config Store to the uCPE Manager. For details please refer to:
+ Config Store to the Enea Edge Management. For details please refer to:
@@ -842,7 +842,7 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
Precondition:
The Offline Configuration Store should not already exist on
- the uCPE Manager. If it exists, the test will report a
+ the Enea Edge Management. If it exists, the test will report a
duplicate.
@@ -872,7 +872,7 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
Store
Description: Removing an Offline
- Config Store from the uCPE Manager. For details please refer to:
+ Config Store from the Enea Edge Management. For details please refer to:
@@ -887,7 +887,7 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
Precondition:
The Offline Configuration Store the user wishes to remove should
- exist in the uCPE Manager. If it does not, the test will say so.
+ exist in the Enea Edge Management. If it does not, the test will say so.
Action: Run the
removeConfigStore.yml Ansible Playbook with the
@@ -908,7 +908,7 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
Configuration Store
Description: Adding a network
- bridge to an Offline Config Store in uCPE Manager. For details please
+ bridge to an Offline Config Store in Enea Edge Management. For details please
refer to:
@@ -925,8 +925,8 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
- The Offline Configuration Store should exist in the uCPE
- Manager. If it does not, the test will say so.
+ The Offline Configuration Store should exist in the Enea Edge
+ Management. If it does not, the test will say so.
@@ -980,8 +980,8 @@ DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"<
Precondition:
- An empty Offline Configuration Store should exist in uCPE
- Manager.
+ An empty Offline Configuration Store should exist in Enea Edge
+ Management.
Action: Run the
configOfflineDPDK.yml Ansible Playbook with the
@@ -1022,12 +1022,12 @@ INFO: Done
- The Offline Configuration Store should exist in the uCPE
- Manager.
+ The Offline Configuration Store should exist in the Enea Edge
+ Management.
- The device should be connected to the uCPE Manager.
+ The device should be connected to the Enea Edge Management.
@@ -1078,7 +1078,7 @@ INFO: Done
- The device should be connected to the uCPE Manager.
+ The device should be connected to the Enea Edge Management.
@@ -1109,8 +1109,7 @@ INFO: Done
VNF Deployment and Lifecycle
The following details the automated suite that handles the testing
- of the instantiation, lifecycle and destruction of a VNF for Enea NFV
- Access.
+ of the instantiation, lifecycle and destruction of a VNF for Enea Edge.
Instantiating a VNFI
@@ -1131,7 +1130,7 @@ INFO: Done
Preconditions:
A VNF Image is onboarded and a device is added and connected
- to the uCPE Manager. Depending on the VNF, other steps may be
+ to the Enea Edge Management. Depending on the VNF, other steps may be
required.
@@ -1250,8 +1249,8 @@ vnfi=<VNFI-name>"
- Wait for the uCPE device to be connected in the Enea uCPE
- Manager.
+ Wait for the uCPE device to be connected in the Enea Edge
+ Management.
@@ -1272,7 +1271,7 @@ vnfi=<VNFI-name>"
Instantiate the FortiGate VNF using the basic Firewall
- configuration provided with your Enea NFV Access Release, and the
+ configuration provided with your Enea Edge Release, and the
Fortigate License file.
@@ -1323,7 +1322,7 @@ vnfi=<VNFI-name>"
A device must have been previously added and connected to
- the uCPE Manager instance.
+ the Enea Edge Management instance.
@@ -1447,7 +1446,7 @@ FortigateFWInstance tested successfully!
A device must have been previously added and connected to
- the uCPE Manager instance.
+ the Enea Edge Management instance.
@@ -1500,9 +1499,9 @@ FortigateFWInstance tested successfully!
FortiGate VNF as a
- Firewall in the
Manual.
@@ -1511,8 +1510,8 @@ FortigateFWInstance tested successfully!
Python Unit-Test Suite in
- .
@@ -1542,7 +1541,7 @@ FortigateFW Scenario deployed successfully!
Description: This sample test
case corresponds to the "VNF Chaining Example Use-case" from the Enea
- NFV Access Example Use-cases manual.
+ Edge Example Use-cases manual.
For details please refer to:
@@ -1565,7 +1564,7 @@ FortigateFW Scenario deployed successfully!
Two devices must have been previously added and connected to
- the uCPE Manager instance.
+ the Enea Edge Management instance.
@@ -1726,7 +1725,7 @@ LAN-to-LAN connectivity (through VPN tunnel)tested successfully!
- Upload a Custom Script onto the uCPE Manager.
+ Upload a Custom Script onto the Enea Edge Management.
@@ -1746,7 +1745,7 @@ LAN-to-LAN connectivity (through VPN tunnel)tested successfully!
- Remove the Custom Script from the uCPE Manager.
+ Remove the Custom Script from the Enea Edge Management.
@@ -1755,7 +1754,7 @@ LAN-to-LAN connectivity (through VPN tunnel)tested successfully!
A device must have been previously added and connected to the
- uCPE Manager.
+ Enea Edge Management.
@@ -1792,7 +1791,7 @@ inteld1521-1 ansible_host=172.24.12.73 ansible_port=22 ansible_user=root \
Result: Output of
basicTest.yml :
- test_success_after_always was uploaded to uCPE Manager!
+ test_success_after_always was uploaded to Enea Edge Management!
test_success_after_always was uploaded to <Device-name>!
<Device-name> device is connected!
@@ -1800,6 +1799,6 @@ test_success_after_always from phase always-after-startup was removed \
from <Device-name>!
test_success_after_always from phase always-after-startup was removed \
-from uCPE Manager!
+from Enea Edge Management!
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-system-test-specification/swcomp.mk b/doc/book-enea-nfv-access-system-test-specification/swcomp.mk
index aea86ca..6e08a56 100755
--- a/doc/book-enea-nfv-access-system-test-specification/swcomp.mk
+++ b/doc/book-enea-nfv-access-system-test-specification/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-system-test-specification
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) System Test Specification"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) System Test Specification"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-telemetry-open-source/doc/about.xml b/doc/book-enea-nfv-access-telemetry-open-source/doc/about.xml
index 781b0bd..5366626 100644
--- a/doc/book-enea-nfv-access-telemetry-open-source/doc/about.xml
+++ b/doc/book-enea-nfv-access-telemetry-open-source/doc/about.xml
@@ -5,7 +5,7 @@
About this Report
This document contains the open source and license information
- pertaining to telemetry packages provided with Enea NFV Access .
diff --git a/doc/book-enea-nfv-access-telemetry-open-source/doc/book.xml b/doc/book-enea-nfv-access-telemetry-open-source/doc/book.xml
index b005dae..c671fd7 100644
--- a/doc/book-enea-nfv-access-telemetry-open-source/doc/book.xml
+++ b/doc/book-enea-nfv-access-telemetry-open-source/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access Telemetry Open Source Report
+ Enea Edge Telemetry Open Source Report
Release Version
diff --git a/doc/book-enea-nfv-access-telemetry-open-source/swcomp.mk b/doc/book-enea-nfv-access-telemetry-open-source/swcomp.mk
index 0314da2..332d0c8 100644
--- a/doc/book-enea-nfv-access-telemetry-open-source/swcomp.mk
+++ b/doc/book-enea-nfv-access-telemetry-open-source/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-telemetry-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access Telemetry Open Source Report"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Telemetry Open Source Report"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-ucpem-open-source/doc/about.xml b/doc/book-enea-nfv-access-ucpem-open-source/doc/about.xml
index d443886..05cea19 100644
--- a/doc/book-enea-nfv-access-ucpem-open-source/doc/about.xml
+++ b/doc/book-enea-nfv-access-ucpem-open-source/doc/about.xml
@@ -5,7 +5,7 @@
About this Report
This document contains the open source and license information
- pertaining to packages provided with Enea NFV Access .
diff --git a/doc/book-enea-nfv-access-ucpem-open-source/doc/book.xml b/doc/book-enea-nfv-access-ucpem-open-source/doc/book.xml
index d140047..7401818 100644
--- a/doc/book-enea-nfv-access-ucpem-open-source/doc/book.xml
+++ b/doc/book-enea-nfv-access-ucpem-open-source/doc/book.xml
@@ -4,7 +4,7 @@
]>
- Enea NFV Access uCPE Manager Open Source Report
+ Enea Edge Management Open Source Report
Release Version
diff --git a/doc/book-enea-nfv-access-ucpem-open-source/swcomp.mk b/doc/book-enea-nfv-access-ucpem-open-source/swcomp.mk
index 15d7a6d..a7e39ab 100644
--- a/doc/book-enea-nfv-access-ucpem-open-source/swcomp.mk
+++ b/doc/book-enea-nfv-access-ucpem-open-source/swcomp.mk
@@ -6,5 +6,5 @@ BOOK_VER ?= $(REL_VER)-dev
DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
BOOKPACKAGES := book-enea-nfv-access-ucpem-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access uCPE Manager Open Source Report"
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Management Open Source Report"
BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
--
cgit v1.2.3-54-g00ecf
From adc6872c65a4b266a67ab20770c29916ca79cb04 Mon Sep 17 00:00:00 2001
From: iosc
Date: Mon, 22 Mar 2021 15:28:31 +0100
Subject: USERDOCAP-636 - all books renamed into enea edge
Change-Id: I3ce4380c19653ef14792960ad968664b70f3c2bf
---
doc/Makefile | 2 +-
.../doc/README | 3 +
.../doc/about.xml | 14 +
.../doc/book.xml | 18 +
.../doc/licenses.xml | 112 +
.../swcomp.mk | 10 +
.../doc/automation_framework_test_harness.xml | 2800 ++++++
.../doc/book.xml | 33 +
.../doc/components.xml | 137 +
.../doc/getting_started.xml | 239 +
.../doc/images/ChainedVNFsService_setup.png | Bin 0 -> 83776 bytes
.../doc/images/autofw_testh_overview.png | Bin 0 -> 60150 bytes
.../doc/images/environment_basicsetup.png | Bin 0 -> 79325 bytes
.../doc/overview.xml | 188 +
.../doc/troubleshooting_guide.xml | 43 +
doc/book-enea-edge-auto-fw-th-user-guide/swcomp.mk | 10 +
.../doc/128t_vnf_router.xml | 715 ++
.../doc/appendix_1.xml | 63 +
.../doc/appendix_2.xml | 326 +
.../doc/appendix_3.xml | 7 +
.../doc/appendix_4.xml | 103 +
.../doc/appendix_5.xml | 243 +
doc/book-enea-edge-example-usecases/doc/book.xml | 44 +
.../doc/clav_vnf_examples.xml | 396 +
.../doc/enea_test_vnf_examples.xml | 308 +
.../doc/forti_vnf_examples.xml | 627 ++
.../doc/images/fortinet_interface.png | Bin 0 -> 55312 bytes
.../doc/images/trgt.png | Bin 0 -> 50826 bytes
.../doc/images/trgt.svg | 1231 +++
.../doc/images/trgt_servicechain.png | Bin 0 -> 69317 bytes
.../doc/images/trgt_servicechain.svg | 1402 +++
.../doc/images/uc_clavister_bridge.png | Bin 0 -> 36145 bytes
.../doc/images/uc_clavister_bridge.svg | 966 ++
.../doc/images/uc_clavister_sriov.png | Bin 0 -> 40185 bytes
.../doc/images/uc_clavister_sriov.svg | 1152 +++
.../doc/images/uc_enea_test_vnf.png | Bin 0 -> 37660 bytes
.../doc/images/uc_enea_test_vnf.svg | 1002 ++
.../doc/images/uc_fortigate_fw.png | Bin 0 -> 27026 bytes
.../doc/images/uc_fortigate_fw.svg | 940 ++
.../doc/images/uc_fortigate_sdwan.png | Bin 0 -> 45248 bytes
.../doc/images/uc_fortigate_sdwan.svg | 1449 +++
.../doc/images/uc_vnf_chaining.png | Bin 0 -> 41097 bytes
.../doc/images/uc_vnf_chaining.svg | 1186 +++
.../doc/introduction.xml | 27 +
.../doc/service_chaining_128t_fortigate.xml | 1064 +++
.../doc/vnf_chaining.xml | 407 +
doc/book-enea-edge-example-usecases/swcomp.mk | 10 +
.../doc/advanced_configurations.xml | 1042 ++
doc/book-enea-edge-getting-started/doc/book.xml | 44 +
doc/book-enea-edge-getting-started/doc/grafana.xml | 266 +
.../doc/images/archive_list.png | Bin 0 -> 87667 bytes
.../doc/images/collect_debug_logs.png | Bin 0 -> 47994 bytes
.../doc/images/debug_settings.png | Bin 0 -> 32833 bytes
.../doc/images/dev_file_mg.png | Bin 0 -> 138952 bytes
.../doc/images/download_files.png | Bin 0 -> 79979 bytes
.../doc/images/edit_inter.png | Bin 0 -> 9000 bytes
.../doc/images/edit_inter_config.png | Bin 0 -> 37721 bytes
.../doc/images/fault_events.png | Bin 0 -> 46986 bytes
.../doc/images/high_av_setup.png | Bin 0 -> 66687 bytes
.../doc/images/onboard_a_vnf_image.png | Bin 0 -> 19864 bytes
.../doc/images/ovs_bridges_tab.png | Bin 0 -> 55326 bytes
.../doc/images/prep_deploy.png | Bin 0 -> 127794 bytes
.../doc/images/prep_execution.png | Bin 0 -> 121264 bytes
.../doc/images/telemetry_settings.png | Bin 0 -> 28977 bytes
.../doc/images/telemetry_start.png | Bin 0 -> 14763 bytes
.../doc/images/vnf_space.png | Bin 0 -> 39641 bytes
.../doc/images/wap_external_interface.png | Bin 0 -> 18534 bytes
.../doc/images/wap_wireless_ap.png | Bin 0 -> 21250 bytes
.../doc/installation_guide.xml | 1193 +++
.../doc/introduction.xml | 264 +
.../doc/log_collector.xml | 401 +
.../doc/net_config_options.xml | 886 ++
.../doc/troubleshooting.xml | 226 +
.../doc/upgrade_ena.xml | 588 ++
doc/book-enea-edge-getting-started/doc/vnf_mg.xml | 477 +
doc/book-enea-edge-getting-started/swcomp.mk | 10 +
.../doc/README | 4 +
.../doc/about.xml | 12 +
.../doc/book.xml | 15 +
.../doc/licenses.xml | 5872 ++++++++++++
.../swcomp.mk | 10 +
.../doc/about_release.xml | 184 +
doc/book-enea-edge-release-info/doc/book.xml | 30 +
.../doc/getting_enea_nfv_access.xml | 54 +
.../doc/jiraissues_override.xml | 36 +
.../doc/known_bugs_and_limitations.xml | 217 +
.../doc/main_changes.xml | 162 +
.../doc/system_requirements_prerequisites.xml | 62 +
doc/book-enea-edge-release-info/swcomp.mk | 10 +
doc/book-enea-edge-runtime-open-source/doc/README | 4 +
.../doc/about.xml | 8 +
.../doc/book.xml | 15 +
.../doc/licenses.xml | 9936 ++++++++++++++++++++
doc/book-enea-edge-runtime-open-source/swcomp.mk | 10 +
.../doc/book.xml | 27 +
.../doc/configuration.xml | 53 +
.../doc/overview.xml | 109 +
.../doc/sample_test_cases.xml | 1804 ++++
.../swcomp.mk | 10 +
.../doc/README | 4 +
.../doc/about.xml | 12 +
.../doc/book.xml | 15 +
.../doc/licenses.xml | 290 +
doc/book-enea-edge-telemetry-open-source/swcomp.mk | 10 +
.../doc/README | 3 -
.../doc/about.xml | 14 -
.../doc/book.xml | 18 -
.../doc/licenses.xml | 112 -
.../swcomp.mk | 10 -
.../doc/automation_framework_test_harness.xml | 2800 ------
.../doc/book.xml | 33 -
.../doc/components.xml | 137 -
.../doc/getting_started.xml | 239 -
.../doc/images/ChainedVNFsService_setup.png | Bin 83776 -> 0 bytes
.../doc/images/autofw_testh_overview.png | Bin 60150 -> 0 bytes
.../doc/images/environment_basicsetup.png | Bin 79325 -> 0 bytes
.../doc/overview.xml | 188 -
.../doc/troubleshooting_guide.xml | 43 -
.../swcomp.mk | 10 -
.../doc/128t_vnf_router.xml | 715 --
.../doc/appendix_1.xml | 63 -
.../doc/appendix_2.xml | 326 -
.../doc/appendix_3.xml | 7 -
.../doc/appendix_4.xml | 103 -
.../doc/appendix_5.xml | 243 -
.../doc/book.xml | 44 -
.../doc/clav_vnf_examples.xml | 396 -
.../doc/enea_test_vnf_examples.xml | 308 -
.../doc/forti_vnf_examples.xml | 627 --
.../doc/images/fortinet_interface.png | Bin 55312 -> 0 bytes
.../doc/images/trgt.png | Bin 50826 -> 0 bytes
.../doc/images/trgt.svg | 1231 ---
.../doc/images/trgt_servicechain.png | Bin 69317 -> 0 bytes
.../doc/images/trgt_servicechain.svg | 1402 ---
.../doc/images/uc_clavister_bridge.png | Bin 36145 -> 0 bytes
.../doc/images/uc_clavister_bridge.svg | 966 --
.../doc/images/uc_clavister_sriov.png | Bin 40185 -> 0 bytes
.../doc/images/uc_clavister_sriov.svg | 1152 ---
.../doc/images/uc_enea_test_vnf.png | Bin 37660 -> 0 bytes
.../doc/images/uc_enea_test_vnf.svg | 1002 --
.../doc/images/uc_fortigate_fw.png | Bin 27026 -> 0 bytes
.../doc/images/uc_fortigate_fw.svg | 940 --
.../doc/images/uc_fortigate_sdwan.png | Bin 45248 -> 0 bytes
.../doc/images/uc_fortigate_sdwan.svg | 1449 ---
.../doc/images/uc_vnf_chaining.png | Bin 41097 -> 0 bytes
.../doc/images/uc_vnf_chaining.svg | 1186 ---
.../doc/introduction.xml | 27 -
.../doc/service_chaining_128t_fortigate.xml | 1064 ---
.../doc/vnf_chaining.xml | 407 -
.../swcomp.mk | 10 -
.../doc/advanced_configurations.xml | 1042 --
.../doc/book.xml | 44 -
.../doc/grafana.xml | 266 -
.../doc/images/archive_list.png | Bin 87667 -> 0 bytes
.../doc/images/collect_debug_logs.png | Bin 47994 -> 0 bytes
.../doc/images/debug_settings.png | Bin 32833 -> 0 bytes
.../doc/images/dev_file_mg.png | Bin 138952 -> 0 bytes
.../doc/images/download_files.png | Bin 79979 -> 0 bytes
.../doc/images/edit_inter.png | Bin 9000 -> 0 bytes
.../doc/images/edit_inter_config.png | Bin 37721 -> 0 bytes
.../doc/images/fault_events.png | Bin 46986 -> 0 bytes
.../doc/images/high_av_setup.png | Bin 66687 -> 0 bytes
.../doc/images/onboard_a_vnf_image.png | Bin 19864 -> 0 bytes
.../doc/images/ovs_bridges_tab.png | Bin 55326 -> 0 bytes
.../doc/images/prep_deploy.png | Bin 127794 -> 0 bytes
.../doc/images/prep_execution.png | Bin 121264 -> 0 bytes
.../doc/images/telemetry_settings.png | Bin 28977 -> 0 bytes
.../doc/images/telemetry_start.png | Bin 14763 -> 0 bytes
.../doc/images/vnf_space.png | Bin 39641 -> 0 bytes
.../doc/images/wap_external_interface.png | Bin 18534 -> 0 bytes
.../doc/images/wap_wireless_ap.png | Bin 21250 -> 0 bytes
.../doc/installation_guide.xml | 1193 ---
.../doc/introduction.xml | 264 -
.../doc/log_collector.xml | 401 -
.../doc/net_config_options.xml | 886 --
.../doc/troubleshooting.xml | 226 -
.../doc/upgrade_ena.xml | 588 --
.../doc/vnf_mg.xml | 477 -
doc/book-enea-nfv-access-getting-started/swcomp.mk | 10 -
.../doc/README | 4 -
.../doc/about.xml | 8 -
.../doc/book.xml | 15 -
.../doc/licenses.xml | 9936 --------------------
.../swcomp.mk | 10 -
.../doc/about_release.xml | 184 -
doc/book-enea-nfv-access-release-info/doc/book.xml | 30 -
.../doc/getting_enea_nfv_access.xml | 54 -
.../doc/jiraissues_override.xml | 36 -
.../doc/known_bugs_and_limitations.xml | 217 -
.../doc/main_changes.xml | 162 -
.../doc/system_requirements_prerequisites.xml | 62 -
doc/book-enea-nfv-access-release-info/swcomp.mk | 10 -
.../doc/book.xml | 27 -
.../doc/configuration.xml | 53 -
.../doc/overview.xml | 109 -
.../doc/sample_test_cases.xml | 1804 ----
.../swcomp.mk | 10 -
.../doc/README | 4 -
.../doc/about.xml | 12 -
.../doc/book.xml | 15 -
.../doc/licenses.xml | 290 -
.../swcomp.mk | 10 -
.../doc/README | 4 -
.../doc/about.xml | 12 -
.../doc/book.xml | 15 -
.../doc/licenses.xml | 5872 ------------
.../swcomp.mk | 10 -
207 files changed, 41648 insertions(+), 41648 deletions(-)
create mode 100644 doc/book-enea-edge-auto-fw-th-open-source/doc/README
create mode 100644 doc/book-enea-edge-auto-fw-th-open-source/doc/about.xml
create mode 100644 doc/book-enea-edge-auto-fw-th-open-source/doc/book.xml
create mode 100644 doc/book-enea-edge-auto-fw-th-open-source/doc/licenses.xml
create mode 100644 doc/book-enea-edge-auto-fw-th-open-source/swcomp.mk
create mode 100644 doc/book-enea-edge-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
create mode 100644 doc/book-enea-edge-auto-fw-th-user-guide/doc/book.xml
create mode 100644 doc/book-enea-edge-auto-fw-th-user-guide/doc/components.xml
create mode 100644 doc/book-enea-edge-auto-fw-th-user-guide/doc/getting_started.xml
create mode 100755 doc/book-enea-edge-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png
create mode 100755 doc/book-enea-edge-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png
create mode 100755 doc/book-enea-edge-auto-fw-th-user-guide/doc/images/environment_basicsetup.png
create mode 100644 doc/book-enea-edge-auto-fw-th-user-guide/doc/overview.xml
create mode 100644 doc/book-enea-edge-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
create mode 100755 doc/book-enea-edge-auto-fw-th-user-guide/swcomp.mk
create mode 100644 doc/book-enea-edge-example-usecases/doc/128t_vnf_router.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/appendix_1.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/appendix_2.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/appendix_3.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/appendix_4.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/appendix_5.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/book.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/clav_vnf_examples.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/enea_test_vnf_examples.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/forti_vnf_examples.xml
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/fortinet_interface.png
create mode 100644 doc/book-enea-edge-example-usecases/doc/images/trgt.png
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/trgt.svg
create mode 100644 doc/book-enea-edge-example-usecases/doc/images/trgt_servicechain.png
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/trgt_servicechain.svg
create mode 100644 doc/book-enea-edge-example-usecases/doc/images/uc_clavister_bridge.png
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/uc_clavister_bridge.svg
create mode 100644 doc/book-enea-edge-example-usecases/doc/images/uc_clavister_sriov.png
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/uc_clavister_sriov.svg
create mode 100644 doc/book-enea-edge-example-usecases/doc/images/uc_enea_test_vnf.png
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/uc_enea_test_vnf.svg
create mode 100644 doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_fw.png
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_fw.svg
create mode 100644 doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_sdwan.png
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_sdwan.svg
create mode 100644 doc/book-enea-edge-example-usecases/doc/images/uc_vnf_chaining.png
create mode 100755 doc/book-enea-edge-example-usecases/doc/images/uc_vnf_chaining.svg
create mode 100644 doc/book-enea-edge-example-usecases/doc/introduction.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml
create mode 100644 doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml
create mode 100755 doc/book-enea-edge-example-usecases/swcomp.mk
create mode 100644 doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
create mode 100644 doc/book-enea-edge-getting-started/doc/book.xml
create mode 100644 doc/book-enea-edge-getting-started/doc/grafana.xml
create mode 100755 doc/book-enea-edge-getting-started/doc/images/archive_list.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/collect_debug_logs.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/debug_settings.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/dev_file_mg.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/download_files.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/edit_inter.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/edit_inter_config.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/fault_events.png
create mode 100644 doc/book-enea-edge-getting-started/doc/images/high_av_setup.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/onboard_a_vnf_image.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/ovs_bridges_tab.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/prep_deploy.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/prep_execution.png
create mode 100644 doc/book-enea-edge-getting-started/doc/images/telemetry_settings.png
create mode 100644 doc/book-enea-edge-getting-started/doc/images/telemetry_start.png
create mode 100755 doc/book-enea-edge-getting-started/doc/images/vnf_space.png
create mode 100644 doc/book-enea-edge-getting-started/doc/images/wap_external_interface.png
create mode 100644 doc/book-enea-edge-getting-started/doc/images/wap_wireless_ap.png
create mode 100644 doc/book-enea-edge-getting-started/doc/installation_guide.xml
create mode 100644 doc/book-enea-edge-getting-started/doc/introduction.xml
create mode 100644 doc/book-enea-edge-getting-started/doc/log_collector.xml
create mode 100644 doc/book-enea-edge-getting-started/doc/net_config_options.xml
create mode 100644 doc/book-enea-edge-getting-started/doc/troubleshooting.xml
create mode 100644 doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
create mode 100644 doc/book-enea-edge-getting-started/doc/vnf_mg.xml
create mode 100755 doc/book-enea-edge-getting-started/swcomp.mk
create mode 100644 doc/book-enea-edge-management-open-source/doc/README
create mode 100644 doc/book-enea-edge-management-open-source/doc/about.xml
create mode 100644 doc/book-enea-edge-management-open-source/doc/book.xml
create mode 100644 doc/book-enea-edge-management-open-source/doc/licenses.xml
create mode 100644 doc/book-enea-edge-management-open-source/swcomp.mk
create mode 100644 doc/book-enea-edge-release-info/doc/about_release.xml
create mode 100644 doc/book-enea-edge-release-info/doc/book.xml
create mode 100644 doc/book-enea-edge-release-info/doc/getting_enea_nfv_access.xml
create mode 100644 doc/book-enea-edge-release-info/doc/jiraissues_override.xml
create mode 100644 doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
create mode 100644 doc/book-enea-edge-release-info/doc/main_changes.xml
create mode 100644 doc/book-enea-edge-release-info/doc/system_requirements_prerequisites.xml
create mode 100644 doc/book-enea-edge-release-info/swcomp.mk
create mode 100644 doc/book-enea-edge-runtime-open-source/doc/README
create mode 100644 doc/book-enea-edge-runtime-open-source/doc/about.xml
create mode 100644 doc/book-enea-edge-runtime-open-source/doc/book.xml
create mode 100644 doc/book-enea-edge-runtime-open-source/doc/licenses.xml
create mode 100644 doc/book-enea-edge-runtime-open-source/swcomp.mk
create mode 100644 doc/book-enea-edge-system-test-specification/doc/book.xml
create mode 100644 doc/book-enea-edge-system-test-specification/doc/configuration.xml
create mode 100644 doc/book-enea-edge-system-test-specification/doc/overview.xml
create mode 100644 doc/book-enea-edge-system-test-specification/doc/sample_test_cases.xml
create mode 100755 doc/book-enea-edge-system-test-specification/swcomp.mk
create mode 100644 doc/book-enea-edge-telemetry-open-source/doc/README
create mode 100644 doc/book-enea-edge-telemetry-open-source/doc/about.xml
create mode 100644 doc/book-enea-edge-telemetry-open-source/doc/book.xml
create mode 100644 doc/book-enea-edge-telemetry-open-source/doc/licenses.xml
create mode 100644 doc/book-enea-edge-telemetry-open-source/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-open-source/doc/README
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-open-source/doc/about.xml
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-open-source/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-open-source/doc/licenses.xml
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-open-source/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
delete mode 100755 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png
delete mode 100755 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png
delete mode 100755 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/environment_basicsetup.png
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml
delete mode 100644 doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
delete mode 100755 doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/appendix_1.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/appendix_2.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/appendix_3.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/enea_test_vnf_examples.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/fortinet_interface.png
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/images/trgt.png
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/trgt.svg
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.png
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.svg
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_bridge.png
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_bridge.svg
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_sriov.png
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_sriov.svg
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/images/uc_enea_test_vnf.png
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/uc_enea_test_vnf.svg
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_fw.png
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_fw.svg
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_sdwan.png
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_sdwan.svg
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/images/uc_vnf_chaining.png
delete mode 100755 doc/book-enea-nfv-access-example-usecases/doc/images/uc_vnf_chaining.svg
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
delete mode 100644 doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
delete mode 100755 doc/book-enea-nfv-access-example-usecases/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/grafana.xml
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/archive_list.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/collect_debug_logs.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/debug_settings.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/dev_file_mg.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/download_files.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/edit_inter.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/edit_inter_config.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/fault_events.png
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/images/high_av_setup.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/ovs_bridges_tab.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/images/telemetry_settings.png
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/images/telemetry_start.png
delete mode 100755 doc/book-enea-nfv-access-getting-started/doc/images/vnf_space.png
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/images/wap_external_interface.png
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/images/wap_wireless_ap.png
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/introduction.xml
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/troubleshooting.xml
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
delete mode 100644 doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
delete mode 100755 doc/book-enea-nfv-access-getting-started/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-platform-open-source/doc/README
delete mode 100644 doc/book-enea-nfv-access-platform-open-source/doc/about.xml
delete mode 100644 doc/book-enea-nfv-access-platform-open-source/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
delete mode 100644 doc/book-enea-nfv-access-platform-open-source/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-release-info/doc/about_release.xml
delete mode 100644 doc/book-enea-nfv-access-release-info/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml
delete mode 100644 doc/book-enea-nfv-access-release-info/doc/jiraissues_override.xml
delete mode 100644 doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
delete mode 100644 doc/book-enea-nfv-access-release-info/doc/main_changes.xml
delete mode 100644 doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml
delete mode 100644 doc/book-enea-nfv-access-release-info/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-system-test-specification/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml
delete mode 100644 doc/book-enea-nfv-access-system-test-specification/doc/overview.xml
delete mode 100644 doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
delete mode 100755 doc/book-enea-nfv-access-system-test-specification/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-telemetry-open-source/doc/README
delete mode 100644 doc/book-enea-nfv-access-telemetry-open-source/doc/about.xml
delete mode 100644 doc/book-enea-nfv-access-telemetry-open-source/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-telemetry-open-source/doc/licenses.xml
delete mode 100644 doc/book-enea-nfv-access-telemetry-open-source/swcomp.mk
delete mode 100644 doc/book-enea-nfv-access-ucpem-open-source/doc/README
delete mode 100644 doc/book-enea-nfv-access-ucpem-open-source/doc/about.xml
delete mode 100644 doc/book-enea-nfv-access-ucpem-open-source/doc/book.xml
delete mode 100644 doc/book-enea-nfv-access-ucpem-open-source/doc/licenses.xml
delete mode 100644 doc/book-enea-nfv-access-ucpem-open-source/swcomp.mk
(limited to 'doc/book-enea-nfv-access-platform-open-source')
diff --git a/doc/Makefile b/doc/Makefile
index 38c3569..1a1bd48 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -50,7 +50,7 @@ DOCBOOK_TO_BOOKDIR ?= yes
DOCBOOK_CLEANTMP ?= yes
#Components (books) in this subsystem. Now use all books found here
-COMPONENTS := book-enea-nfv-access-auto-fw-th-open-source book-enea-nfv-access-auto-fw-th-user-guide book-enea-nfv-access-evalkit book-enea-nfv-access-example-usecases book-enea-nfv-access-getting-started book-enea-nfv-access-platform-open-source book-enea-nfv-access-release-info book-enea-nfv-access-system-test-specification book-enea-nfv-access-telemetry-open-source book-enea-nfv-access-ucpem-open-source
+COMPONENTS := book-enea-edge-auto-fw-th-open-source book-enea-edge-auto-fw-th-user-guide book-enea-nfv-access-evalkit book-enea-edge-example-usecases book-enea-edge-getting-started book-enea-edge-runtime-open-source book-enea-edge-release-info book-enea-edge-system-test-specification book-enea-edge-telemetry-open-source book-enea-edge-management-open-source
# --------------------------------------------------------------
diff --git a/doc/book-enea-edge-auto-fw-th-open-source/doc/README b/doc/book-enea-edge-auto-fw-th-open-source/doc/README
new file mode 100644
index 0000000..e546e6f
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-open-source/doc/README
@@ -0,0 +1,3 @@
+The licenses.xml in the git repository of Enea NFV Access AFTH Open Source Report
+is the frozen version belonging to the last official release of Enea NFV Access.
+
diff --git a/doc/book-enea-edge-auto-fw-th-open-source/doc/about.xml b/doc/book-enea-edge-auto-fw-th-open-source/doc/about.xml
new file mode 100644
index 0000000..4dc19aa
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-open-source/doc/about.xml
@@ -0,0 +1,14 @@
+
+
+
+ About this Report
+
+ This document contains the open source and license information
+ pertaining to the Automation Framework and Test Harness provided with
+ Enea Edge .
+
+
diff --git a/doc/book-enea-edge-auto-fw-th-open-source/doc/book.xml b/doc/book-enea-edge-auto-fw-th-open-source/doc/book.xml
new file mode 100644
index 0000000..df5e029
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-open-source/doc/book.xml
@@ -0,0 +1,18 @@
+
+
+]>
+
+ Enea Edge Automation Framework and Test Harness Open Source Report
+
+ Release Version
+
+
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-auto-fw-th-open-source/doc/licenses.xml b/doc/book-enea-edge-auto-fw-th-open-source/doc/licenses.xml
new file mode 100644
index 0000000..76a34e2
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-open-source/doc/licenses.xml
@@ -0,0 +1,112 @@
+
+
+
+ Packages and Licenses
+
+
+ Packages
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Package Name
+
+ Version
+
+ Description
+
+ License
+
+
+
+
+
+ Automation Framework and Test Harness
+
+
+
+ Configuration and Automation Framework for the Edge Manager
+ GUI.
+
+ ENEA-SRC-R2
+
+
+
+ Automation Framework and Test Harness
+
+
+
+ Configuration and Automation Framework for the Edge Manager
+ GUI.
+
+ ENEA-EXAMPLE-R2
+
+
+
+
+
+
+
+
+
+ Proprietary Licenses
+
+
+ ENEA-SRC-R2
+
+ Copyright (C) 2019 by Enea.
+ All rights reserved.
+
+ This Software is furnished under a software license agreement and
+ may be used only in accordance with the terms of such agreement.
+ Any other use or reproduction is prohibited. No title to and
+ ownership of the Software is hereby transferred.
+
+ PROPRIETARY NOTICE
+ This Software consists of confidential information.
+ Trade secret law and copyright law protect this Software.
+ The above notice of copyright on this Software does not indicate
+ any actual or intended publication of such Software.
+
+
+
+ ENEA-EXAMPLE-R2
+
+ Copyright (C) 2019 by Enea Software AB.
+ All rights reserved.
+
+ This Example is furnished under a Software License Agreement and
+ may be used only in accordance with the terms of such agreement.
+ No title to and ownership of the Example is hereby transferred.
+
+ The information in this Example is subject to change
+ without notice and should not be construed as a commitment
+ by Enea Software AB.
+
+ DISCLAIMER
+ This Example is delivered "AS IS", consequently
+ Enea Software AB makes no representations or warranties,
+ expressed or implied, for the Example.
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-auto-fw-th-open-source/swcomp.mk b/doc/book-enea-edge-auto-fw-th-open-source/swcomp.mk
new file mode 100644
index 0000000..24463ac
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-open-source/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-auto-fw-th-open-source
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Automation Framework and Test Harness Open Source Report"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-edge-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
new file mode 100644
index 0000000..a569d59
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
@@ -0,0 +1,2800 @@
+
+
+ Automation Framework and Test Harness
+
+
+ Automation Framework
+
+ All Automation Framework sources are under the
+ <AF-TH-install-dir>/automation_framework
+ directory.
+
+ The /device folder contains Python scripts for
+ adding uCPE device(s), receiving uCPE events' reports, removing a uCPE
+ device, waiting for a uCPE device to connect to the Enea Edge Management, as well
+ as scripts for adding and removing an offline configuration store. This
+ folder also contains scripts for uploading and removing an NFVA image into
+ the Enea Edge Management, and for installing and activating a NFVA image on a uCPE
+ Device.
+
+ The /customScripts folder contains Python scripts
+ for uploading custom scripts onto the Enea Edge Management and uCPE device(s), for
+ removing custom scripts from the Enea Edge Management and uCPE device(s).
+
+ The /network folder contains Python scripts for
+ binding or unbinding a network interface to and from a uCPE device (DPDK
+ or SR-IOV), creating or deleting an OVS network bridge, or dumping network
+ interface information about the available interfaces. Three of the scripts
+ mentioned here (binding, creating, deleting) are also applicable for an
+ Offline Configuration Store.
+
+
+ Commands within the network folder that include the option
+ -o allow the user to perform the action
+ in an offline configuration store alternative available for use at a
+ later setup time. Commands that include the -n option refer to a uCPE device, with the
+ operation being performed on uCPE device. All options contain either
+ -n , -o
+ or both. One of them must always be provided, if both are provided, -o
+ has priority, and -n is thus ignored.
+
+
+ The /unittestSuite folder contains JSON files for
+ complex scenarios (multiple operations), as well as Python unit-test class
+ and loader scripts for generating specific test cases for the available
+ Python scripts. The generated test cases are injected into the Python
+ unit-test suite class to be run using the Python unit-test
+ framework.
+
+ The /unittestSuite/config folder contains
+ configuration files in JSON format that describe the list of test cases
+ for a particular Python script. Each defined test case is a dictionary
+ that must contain the test case name and arguments to be passed to the
+ Python script for running the test case.
+
+ The /unittestSuite/vnf_config directory contains
+ symlinks for the Fortigate license file and for the
+ /vnf_config/fortigateImage folder.
+
+ The /vnf folder contains Python scripts for
+ onboarding and offboarding a VNF image, instantiating a VNF, controlling a
+ VNF instance or destroying an existing one.
+
+ The eneaUcpeMgr.py file acts as a library for
+ the (Python) Automation Framework scripts. It contains common functions
+ and unit-test configuration options.
+
+
+ Python Unit-Test Suite
+
+ The Python unit-test class defined in the
+ unittestSuite.py script provides a way to automate
+ the execution of specific test cases for each supported Python
+ script.
+
+ This class requires a test suite configuration JSON file that
+ contains a dictionary list of the Python scripts to be processed. Each
+ dictionary must contain the path of the Python script to be loaded and
+ the path to the file describing the test cases to be performed against
+ the designated script.
+
+ Steps for running the Python unit-test suite on the Enea Edge Management
+ are provided below.
+
+
+ Script Options
+
+ $ python unittestSuite.py -h
+Usage: unittestSuite.py [options]
+
+Run selected unit-test suite against Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -n DEVICENAME, --deviceName=DEVICENAME
+ Name of vCPE device (Virtual Infrastructure Manager)
+ -s SUITEFILE, --suite=SUITEFILE
+ Test suite configuration file in JSON format
+ -d DESCRIPTION, --description=DESCRIPTION
+ Test suite description
+ -o OFFLINE, --offline=OFFLINE
+ Offline Configuration(ZTP)
+
+ Mandatory options:
+ -H/--host, -n/--deviceName, -s/--suiteFile, -d/--description
+
+
+
+ Configuring Unit-Test JSON File
+
+ The Unit-Test suite JSON configuration file contains a list of
+ dictionaries. Each dictionary indicates the path of the Python module
+ to load and the test case's configuration file to be executed against
+ the loaded module.
+
+ Below is a sample unit-test configuration file, describing the
+ Fortigate deployment scenario
+ fortigateDeploy.json , found in
+ <AF-TH-install-dir>/automation_framework/unittestSuite :
+
+ [
+ {
+ "config": "config/waitDeviceUp.json",
+ "module": "../device/waitDeviceUp.py"
+ },
+ {
+ "config": "config/bindNetworkInterface.json",
+ "module": "../network/bindNetworkInterface.py"
+ },
+ {
+ "config": "config/newNetworkBridge.json",
+ "module": "../network/newNetworkBridge.py"
+ },
+ {
+ "config": "config/onboardVNFRaw.json",
+ "module": "../vnf/onboardVNFRaw.py"
+ },
+ {
+ "config": "config/instantiateVNFI.json",
+ "module": "../vnf/instantiateVNFI.py"
+ },
+ {
+ "config": "config/controlVNFI.json",
+ "module": "../vnf/controlVNFI.py"
+ }
+]
+
+ Below is a sample unit-test configuration file, describing the
+ Fortigate cleanup scenario
+ fortigateCleanup.json :
+
+ [
+ {
+ "config": "config/destroyVNFI.json",
+ "module": "../vnf/destroyVNFI.py"
+ },
+ {
+ "config": "config/delNetworkBridge.json",
+ "module": "../network/delNetworkBridge.py"
+ },
+ {
+ "config": "config/unbindNetworkInterface.json",
+ "module": "../network/unbindNetworkInterface.py"
+ },
+ {
+ "config": "config/offboardVNF.json",
+ "module": "../vnf/offboardVNF.py"
+ }
+]
+
+ The config key contains the path to the test
+ case's configuration file.
+
+ The module key contains the path to the
+ Python script to be executed.
+
+
+
+ Unit-Test Configuration Options
+
+ Unit-test behavior can be tweaked through setting any of the
+ following options. This is done through the
+ eneaUcpeMgr.py file:
+
+ # Defaults for the framework
+username = "admin"
+password = "admin"
+host = None
+deviceName = None
+directory = "."
+ftpUsername = "ftp"
+ftpPassword = "ftp"
+ftpPort = "2021"
+
+# Stop the test run on the first error or failure
+failfast = True
+
+# Logging levels ordered by the highest severity:
+# CRITICAL 50
+# ERROR 40
+# WARNING 30
+# INFO 20
+# DEBUG 10
+# NOTSET 0
+fileLoggingLevel = logging.DEBUG
+consoleLoggingLevel = logging.INFO
+
+
+
+ eneaUcpeMgr.py Options
+
+
+
+
+
+
+
+
+
+
+ Option
+
+ Description
+
+
+
+
+
+ username
+
+ The user authentication used to log into the
+ Enea Edge Management. This can be overwritten by setting the Python
+ unit-test suite command line option
+ -u .
+
+
+
+ password
+
+ The password used to log into the Enea Edge Management. This
+ can be overwritten by setting the Python unit-test suite
+ command line option -p .
+
+
+
+ host
+
+ The IP address of the Enea Edge Management host. This can be
+ overwritten by setting the Python unit-test suite command line
+ option -H .
+
+
+
+ devicename
+
+ The name of the vCPE agent against which tests will be
+ performed. This can be overwritten by setting the Python
+ unit-test suite command line option
+ -n .
+
+
+
+ ftpUsername
+
+ The user authentication used for the FTP connection
+ when onboarding a VNF image. This can be overwritten by
+ setting the Python script command line option
+ -f .
+
+
+
+ ftpPassword
+
+ The password used for the FTP connection when
+ onboarding a VNF image. This can be overwritten by setting the
+ Python script command line option
+ -w .
+
+
+
+ ftpPort
+
+ The port used for the FTP connection when onboarding a
+ VNF image. This can be overwritten by setting the Python
+ script command line option -P .
+
+
+
+ failfast
+
+ Describes the unit-test execution behavior on the first
+ error or failure encountered.
+
+
+
+ fileLoggingLevel
+
+ Sets the file logging level.
+
+
+
+ consoleLoggingLevel
+
+ Sets the console logging level.
+
+
+
+
+
+
+
+ Python Unit-Test Suite Logging
+
+ Logging messages are displayed in the console and also saved to
+ the specified log file. They are shown depending on the chosen logging
+ level.
+
+ Logging messages are ranked by their severity
+ level:CRITICAL 50
+ERROR 40
+WARNING 30
+INFO 20
+DEBUG 10
+NOTSET 0
+
+
+ Logging messages less severe than the set logging level will
+ be ignored.
+
+
+ Setting the console logging level to INFO is done through the
+ consoleLoggingLevel option:consoleLoggingLevel = logging.INFO Setting
+ the file logging level to DEBUG is done through the
+ fileLoggingLevel option:fileLoggingLevel = logging.DEBUG
+
+
+
+ Running Python Unit-Test Suite
+
+
+ Please update all JSON configuration files to use the name of
+ your vCPE agent device. In the following chapters, intelc3850-2 is
+ used as an example.
+
+
+ Below you'll find sample unit-test command line options for
+ running the Fortigate deployment
+ scenario:
+
+ $ python unittestSuite.py -u admin -p admin -H localhost -n intelc3850-2 -s
+fortigateDeploy.json -d "Fortigate deployment scenario"
+
+ Setting the console logging level to DEBUG:
+
+ consoleLoggingLevel = logging.DEBUG
+ Expected Output:
+
+ 2020-04-15 07:58:40,668 - DEBUG: Started logging
+
+Running Fortigate deployment scenario...
+
+test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ...
+2020-04-15 07:58:40,681 - INFO: Wait uCPE device
+2020-04-15 07:58:40,722 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:58:40,723 - DEBUG: Session token is: 280028c0-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:58:40,746 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:58:40,747 - DEBUG: Wait for device 'intelc3850-2' to connect
+2020-04-15 07:58:41,769 - DEBUG: HACK: sleep 30s more
+2020-04-15 07:59:11,791 - DEBUG: HACK: continue
+2020-04-15 07:59:11,792 - INFO: Status: Connected
+2020-04-15 07:59:11,793 - INFO: Done
+2020-04-15 07:59:11,827 - DEBUG: Logging out and exiting...
+ok
+test 002: Bind lan NIC to DPDK (__main__.UnittestSuite) ...
+2020-04-15 07:59:11,832 - INFO: Bind NIC
+2020-04-15 07:59:11,868 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:11,870 - DEBUG: Session token is: 3a90a960-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:11,897 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:11,898 - DEBUG: Bind NIC 'eno6' to dpdk
+2020-04-15 07:59:12,952 - INFO: Done
+2020-04-15 07:59:12,983 - DEBUG: Logging out and exiting...
+ok
+test 003: Bind wan NIC to DPDK (__main__.UnittestSuite) ...
+2020-04-15 07:59:12,986 - INFO: Bind NIC
+2020-04-15 07:59:13,023 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:13,025 - DEBUG: Session token is: 3b410da0-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:13,048 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:13,050 - DEBUG: Bind NIC 'eno8' to dpdk
+2020-04-15 07:59:14,365 - INFO: Done
+2020-04-15 07:59:14,392 - DEBUG: Logging out and exiting...
+ok
+test 004: Creating network bridge LAN (__main__.UnittestSuite) ...
+2020-04-15 07:59:14,395 - INFO: New OVS network bridge
+2020-04-15 07:59:14,428 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:14,429 - DEBUG: Session token is: 3c174961-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:14,452 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:14,453 - DEBUG: Create new OVS network bridge 'lan_br'
+2020-04-15 07:59:14,454 - DEBUG: Attaching interface 'eno6' to bridge 'lan_br'
+2020-04-15 07:59:21,751 - INFO: Done
+2020-04-15 07:59:21,779 - DEBUG: Logging out and exiting...
+ok
+test 005: Creating network bridge WAN (__main__.UnittestSuite) ...
+2020-04-15 07:59:21,782 - INFO: New OVS network bridge
+2020-04-15 07:59:21,818 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:21,819 - DEBUG: Session token is: 407ec231-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:21,845 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:21,846 - DEBUG: Create new OVS network bridge 'wan_br'
+2020-04-15 07:59:21,847 - DEBUG: Attaching interface 'eno8' to bridge 'wan_br'
+2020-04-15 07:59:22,813 - INFO: Done
+2020-04-15 07:59:22,845 - DEBUG: Logging out and exiting...
+ok
+test 006: Onboarding Fortigate VNF (wizard API) (__main__.UnittestSuite) ...
+2020-04-15 07:59:22,849 - INFO: Onboard wizard
+2020-04-15 07:59:22,885 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:22,886 - DEBUG: Session token is: 4121b8f1-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:22,890 - DEBUG: FTP file '../../vnf_image/fortios.qcow2' on host \
+'localhost', port '2021'
+2020-04-15 07:59:23,127 - DEBUG: Onboard VNF raw: fortios.qcow2
+2020-04-15 07:59:27,107 - INFO: Done
+2020-04-15 07:59:27,140 - DEBUG: Logging out and exiting...
+ok
+test 007: Instantiate Fortigate VNF (__main__.UnittestSuite) ...
+2020-04-15 07:59:27,144 - INFO: Instantiate VNF
+2020-04-15 07:59:27,182 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:27,184 - DEBUG: Session token is: 43b16480-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:27,207 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:27,281 - DEBUG: Found VNF descriptor with name 'fortigateImage'
+2020-04-15 07:59:27,286 - DEBUG: Reading file content as text: \
+vnf_config/fortigateImage/fortigateFW.conf
+2020-04-15 07:59:27,359 - DEBUG: Encrypt file content: \
+vnf_config/fortigateImage/fortigateFW.conf
+2020-04-15 07:59:27,364 - DEBUG: Reading file content as text: \
+vnf_config/fortigateImage/fortigateLicense.lic
+2020-04-15 07:59:27,407 - DEBUG: Encrypt file content: \
+vnf_config/fortigateImage/fortigateLicense.lic
+2020-04-15 07:59:27,409 - DEBUG: Instantiate fortigateImage VNF on 'intelc3850-2'
+2020-04-15 07:59:32,720 - INFO: Done
+2020-04-15 07:59:32,747 - DEBUG: Logging out and exiting...
+ok
+test 008: Pause Fortigate VNF instance (__main__.UnittestSuite) ...
+2020-04-15 07:59:32,840 - INFO: Control VNF
+2020-04-15 07:59:32,877 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:32,880 - DEBUG: Session token is: 47166170-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:32,904 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:32,954 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
+2020-04-15 07:59:32,955 - DEBUG: Control VNF instance 'intelc3850-2', command: pause
+2020-04-15 07:59:33,114 - INFO: Done
+2020-04-15 07:59:33,138 - DEBUG: Logging out and exiting...
+ok
+test 009: Resume Fortigate VNF instance (__main__.UnittestSuite) ...
+2020-04-15 07:59:33,142 - INFO: Control VNF
+2020-04-15 07:59:33,174 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:33,177 - DEBUG: Session token is: 4743b300-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:33,209 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:33,257 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
+2020-04-15 07:59:33,258 - DEBUG: Control VNF instance 'intelc3850-2', command: resume
+2020-04-15 07:59:33,365 - INFO: Done
+2020-04-15 07:59:33,389 - DEBUG: Logging out and exiting...
+ok
+test 010: Stop Fortigate VNF instance (__main__.UnittestSuite) ...
+2020-04-15 07:59:33,393 - INFO: Control VNF
+2020-04-15 07:59:33,436 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:33,438 - DEBUG: Session token is: 476aea10-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:33,467 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:33,511 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
+2020-04-15 07:59:33,513 - DEBUG: Control VNF instance 'intelc3850-2', command: stop
+2020-04-15 07:59:33,865 - INFO: Done
+2020-04-15 07:59:33,891 - DEBUG: Logging out and exiting...
+ok
+test 011: Start Fortigate VNF instance (__main__.UnittestSuite) ...
+2020-04-15 07:59:33,895 - INFO: Control VNF
+2020-04-15 07:59:33,931 - DEBUG: Login successful on host 'localhost'
+2020-04-15 07:59:33,932 - DEBUG: Session token is: 47b70e41-7ede-11ea-a9a8-02429dc76bdd
+2020-04-15 07:59:33,956 - DEBUG: Found device with name 'intelc3850-2'
+2020-04-15 07:59:34,013 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
+2020-04-15 07:59:34,015 - DEBUG: Control VNF instance 'intelc3850-2', command: start
+2020-04-15 07:59:36,599 - INFO: Done
+2020-04-15 07:59:36,623 - DEBUG: Logging out and exiting...
+ok
+
+----------------------------------------------------------------------
+Ran 11 tests in 55.946s
+
+OK
+
+ Below you'll find sample unit-test command line options for
+ running the Fortigate cleanup
+ scenario:
+
+ $ python unittestSuite.py -u admin -p admin -H localhost -n intelc3850-2 -s
+fortigateCleanup.json -d "Fortigate cleanup scenario"
+
+ Setting the console logging level to INFO:
+
+ consoleLoggingLevel = logging.INFO
+
+ Expected Output:
+
+ Running Fortigate cleanup scenario...
+
+test 001: Destroying Fortigate VNF (__main__.UnittestSuite) ...
+2020-04-15 08:03:40,756 - INFO: Destroy VNF
+2020-04-15 08:03:41,358 - INFO: Done
+ok
+test 002: Deleting network bridge LAN (__main__.UnittestSuite) ...
+2020-04-15 08:03:41,494 - INFO: Delete OVS network bridge
+2020-04-15 08:03:41,731 - INFO: Done
+ok
+test 003: Deleting network bridge WAN (__main__.UnittestSuite) ...
+2020-04-15 08:03:41,766 - INFO: Delete OVS network bridge
+2020-04-15 08:03:43,270 - INFO: Done
+ok
+test 004: Unbind lan NIC from DPDK (__main__.UnittestSuite) ...
+2020-04-15 08:03:43,375 - INFO: Unbind NIC
+2020-04-15 08:03:45,405 - INFO: Done
+ok
+test 005: Unbind wan NIC from DPDK (__main__.UnittestSuite) ...
+2020-04-15 08:03:45,434 - INFO: Unbind NIC
+2020-04-15 08:03:47,633 - INFO: Done
+ok
+test 006: Offboarding Fortigate VNF (__main__.UnittestSuite) ...
+2020-04-15 08:03:47,701 - INFO: Offboard VNF
+2020-04-15 08:03:47,919 - INFO: Done
+ok
+
+----------------------------------------------------------------------
+Ran 6 tests in 7.192s
+
+OK
+
+
+
+
+ Adding a uCPE Device
+
+ Steps for adding, configuring and running a uCPE device onto the
+ Enea Edge Management are described below .
+
+
+ Script Options
+
+ $ python addDevice.py -h
+Usage: addDevice.py [options]
+
+Add a uCPE device in Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f DEVICEFILE, --file=DEVICEFILE
+ File containing uCPE Information in JSON format
+
+ Mandatory options:
+ -H/--host, -f/--file
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed for adding a uCPE device
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the arguments passed to the
+ addDevice Python module.
+
+ Sample configuration file in JSON
+ format:
+
+ [
+ {
+ "name": "Add VCPE Agent device ",
+ "args": "-f ../../lab_config/intelc3850-2/intelc3850-2.json"
+ }
+]
+
+ Sample
+ intelc3850-2.json configuration
+ file:
+
+ {
+ "name": "intelc3850-2",
+ "deviceGroupingTags": " ",
+ "description": "",
+ "address": "172.24.12.114",
+ "version": "2.4.0",
+ "port": "22",
+ "username": "root",
+ "password": "root",
+ "certificate": null,
+ "passphrase": null,
+ "callHome": "false",
+ "maintMode": "false",
+ "deviceId": "intelc3850-2"
+}
+
+
+
+ Running the Python Module
+
+ The addDevice Python module can be executed
+ independently by running the following command:
+
+ $ python addDevice.py -u admin -p admin -H localhost -f config/device.json
+2019-03-07 17:33:10,755 - DEBUG: Started logging
+2019-03-07 17:33:10,756 - INFO: Add uCPE device
+2019-03-07 17:33:10,975 - DEBUG: Login successful on host 'localhost'
+2019-03-07 17:33:10,979 - DEBUG: Session token is: 508b6ea2-40ee-11e9-a81f525400d08e1d
+2019-03-07 17:33:11,049 - DEBUG: Add new device 'intelc3850-2' to Enea Edge Management host
+2019-03-07 17:33:11,483 - INFO: Done
+2019-03-07 17:33:11,501 - DEBUG: Logging out and exiting....
+
+
+
+
+ Removing a uCPE Device
+
+ Steps for removing a uCPE device from the Enea Edge Management are
+ described below.
+
+
+ Script Options
+
+ $ python removeDevice.py -h
+Usage: removeDevice.py [options]
+
+Remove a uCPE from Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f DEVICEFILE, --file=DEVICEFILE
+ File containing uCPE Information in JSON format
+
+ Mandatory options:
+ -H/--host, -f/--file
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to remove a uCPE device
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the arguments passed to the
+ removeDevice Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Remove VCPE Agent device ",
+ "args": "-f ../../lab_config/intelc3850-2/intelc3850-2.json"
+ }
+]
+
+ Sample
+ intelc3850-2.json configuration
+ file:
+
+ {
+ "name": "intelc3850-2"
+}
+
+
+
+ Running the Python Module
+
+ The removeDevice Python module can be
+ executed individually by running the following command:
+
+ $ python removeDevice.py -u admin -p admin -H localhost -f
+../../lab_config/intelc3850-2/intelc3850-2.json
+2019-03-07 17:33:56,834 - DEBUG: Started logging
+2019-03-07 17:33:56,835 - INFO: Remove uCPE device
+2019-03-07 17:33:56,856 - DEBUG: Login successful on host 'localhost'
+2019-03-07 17:33:56,856 - DEBUG: Session token is: 6bebcb43-40ee-11e9-a81f525400d08e1d
+2019-03-07 17:33:56,856 - DEBUG: Delete device 'intelc3850-2' from Enea Edge Management
+host
+2019-03-07 17:33:56,875 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 17:33:57,159 - INFO: Done
+2019-03-07 17:33:57,171 - DEBUG: Logging out and exiting...
+
+
+
+
+ Waiting a uCPE Device
+
+ Steps and details for how to Wait a uCPE device to connect to the
+ Enea Edge Management after installation, are described below.
+
+
+ Script Options
+
+ $ python waitDeviceUp.py -h
+Usage: waitDeviceUp.py [options]
+
+Wait for uCPE to connect to the Enea Edge Management after installation.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f DEVICEFILE, --file=DEVICEFILE
+ File containing uCPE Information in JSON format
+ -t TIMEOUT, --timeout=TIMEOUT
+ Time in seconds for maximum wait period, default =
+ instant
+
+ Mandatory options:
+ -H/--host, -f/--file
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to wait a uCPE device should
+ contain a list of dictionaries. Each dictionary indicates the test
+ case name and the test case arguments passed to the
+ waitDeviceUp Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Wait VCPE Agent device be up",
+ "args": "-f ../../lab_config/intelc3850-2/intelc3850-2.json -t 60"
+ }
+]
+
+ Sample
+ intelc3850-2.json configuration
+ file:
+
+ {
+ "name": "intelc3850-2"
+}
+
+
+
+ Running the Python Module
+
+ The waitDeviceUp Python module can be
+ executed individually by running the following command
+ line:$ python waitDeviceUp.py -u admin -p admin -H localhost -t 60 -f
+../../lab_config/intelc3850-2/intelc3850-2.json
+2019-03-07 18:03:21,132 - DEBUG: Started logging
+2019-03-07 18:03:21,133 - INFO: Wait uCPE device
+2019-03-07 18:03:21,149 - DEBUG: Login successful on host 'localhost'
+2019-03-07 18:03:21,149 - DEBUG: Session token is: 8785b1a0-40f2-11e9-a81f525400d08e1d
+2019-03-07 18:03:21,157 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 18:03:21,157 - DEBUG: Wait for device 'intelc3850-2' to connect
+2019-03-07 18:03:29,356 - DEBUG: Status: Connected
+2019-03-07 18:03:29,356 - INFO: Done
+2019-03-07 18:03:29,365 - DEBUG: Logging out and exiting...
+
+
+
+
+ Printing the uCPE Device Log
+
+ Steps and details on how to Print the events log for a specific
+ uCPE device installed in the Enea Edge Management, are explained below.
+
+
+ Script Options
+
+ $ python getEventsForUcpe.py -h
+Usage: getEventsForUcpe.py [options]
+
+Print the events log for a specific uCPE installed in Enea Edge Management.
+
+Options:
+--version show program's version number and exit
+-h, --help show this help message and exit
+-u USERNAME, --username=USERNAME Enea Edge Management login username
+-p PASSWORD, --password=PASSWORD Enea Edge Management login password
+-H HOST, --host=HOST Enea Edge Management host name or IP address
+-f DEVICEFILE, --file=DEVICEFILE File containing uCPE Information in JSON format
+-s SEVERITY, --severity=SEVERITY Event severity level (Critical|Major|Minor)
+
+Mandatory options:
+-H/--host, -f/--file
+
+
+
+ Configuring the JSON File
+
+ Sample
+ intelc3850-2.json configuration
+ file:
+
+ {
+ "name": "intelc3850-2",
+ "deviceId": "intelc3850-2",
+ "deviceGroupingTags": " ",
+ "description": "",
+"address": "172.24.12.114",
+ "port": "22",
+ "username": "root",
+ "password": "root",
+ "certificate": null,
+ "passphrase": null,
+ "callHome": "false",
+ "maintMode": "false"
+}
+
+
+
+
+ Running the Python Module
+
+ The getEventsForUcpe Python module can be
+ executed individually by running the following command:
+
+ $ python getEventsForUcpe.py -H localhost -f \
+../../lab_config/intelc3850-2/intelc3850-2.json
+
+2019-07-04 13:48:31,289 - DEBUG: Started logging
+2019-07-04 13:48:31,290 - INFO: Dump uCPE events
+2019-07-04 13:48:31,336 - DEBUG: Login successful on host '172.24.3.108'
+2019-07-04 13:48:31,336 - DEBUG: Session token is: a53c68d3-9e51-11e9-a715-5254007632e2
+2019-07-04 13:48:31,356 - DEBUG: Found device with name 'intelc3850-2'
+2019-07-04 13:48:31,357 - DEBUG:
+Events on device: intelc3850-2 and severity: 1000
+2019-07-04 13:48:31,450 - DEBUG: Dumping 1 events
+2019-07-04 13:48:31,450 - DEBUG: Device Disconnected | Alarm | Device | None | \
+ 2019-07-04 09:57:40.042
+2019-07-04 13:48:31,469 - DEBUG: Dumping 0 events
+2019-07-04 13:48:31,469 - INFO: Done
+2019-07-04 13:48:31,488 - DEBUG: Logging out and exiting...
+
+
+
+
+ Enabling or Disabling the DPDK
+
+ Steps and details on how to enable or disable the DPDK are
+ explained below.
+
+
+ Script Options
+
+ $ python configDPDK.py -h
+Usage: configDPDK.py [options]
+
+Configure DPDK
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -s STATE, --state=STATE
+ Enable/Disable
+ -n DEVICENAME, --device-name=DEVICENAME
+ Name of the device
+ -o STORENAME, --store-name=STORENAME
+ Name of the store
+
+ Mandatory options:
+ -H/--host, -s/--state, -n/--device-name or -o/--store-name
+
+
+
+ Running the Python Module
+
+ The configDPDK Python module can be executed
+ individually by running the following command lines:
+
+ To Enable DPDK:
+
+ $ python configDPDK.py -s enable -n intelc3850-2
+
+2020-01-06 08:35:16,820 - DEBUG: Started logging
+2020-01-06 08:35:16,821 - INFO: Configure DPDK
+2020-01-06 08:35:16,870 - DEBUG: Login successful on host '172.24.3.90'
+2020-01-06 08:35:16,871 - DEBUG: Session token is: 601149e0-3089-11ea-b0c7-525400b7889f
+2020-01-06 08:35:16,894 - DEBUG: Found device with name 'inteld1521-1'
+2020-01-06 08:35:16,895 - DEBUG: Set DPDK state to enable
+2020-01-06 08:35:16,936 - INFO: Done
+2020-01-06 08:35:16,961 - DEBUG: Logging out and exiting...
+
+ To Disable DPDK:
+
+ $ python configDPDK.py -s disable -n intelc3850-2
+
+2020-01-06 08:33:57,157 - DEBUG: Started logging
+2020-01-06 08:33:57,158 - INFO: Configure DPDK
+2020-01-06 08:33:57,215 - DEBUG: Login successful on host '172.24.3.90'
+2020-01-06 08:33:57,216 - DEBUG: Session token is: 3096e670-3089-11ea-b0c7-525400b7889f
+2020-01-06 08:33:57,239 - DEBUG: Found device with name 'inteld1521-1'
+2020-01-06 08:33:57,241 - DEBUG: Set DPDK state to disable
+2020-01-06 08:33:57,284 - INFO: Done
+2020-01-06 08:33:57,310 - DEBUG: Logging out and exiting...
+
+
+
+
+ Binding a Network Interface
+
+ How to Bind a physical network interface to a DPDK, Standard or
+ SR-IOV is detailed below.
+
+
+ Script Options
+
+ $ python bindNetworkInterface.py -h
+Usage: bindNetworkInterface.py [options]
+
+Binds a physical network interface to a DPDK or SR-IOV.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f NICFILE, --file=NICFILE
+ File containing network interface Information in JSON
+ format
+ -n DEVICENAME, --device-name=DEVICENAME
+ Name of the device
+ -o STORENAME, --store-name=STORENAME
+ Name of the store
+
+ Mandatory options:
+ -H/--host, -f/--file, -n/--device-name or -o/--store-name
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to bind a physical network
+ interface should contain a list of dictionaries. Each dictionary
+ indicates the test case name and the test case arguments passed to the
+ bindNetworkInterface Python module.
+
+ Sample unit-test JSON file
+ format: [
+ {
+ "name": "Bind lan NIC to DPDK",
+ "args": "-f ../../lab_config/intelc3850-2/lan_nic.json"
+ },
+ {
+ "name": "Bind wan NIC to DPDK",
+ "args": "-f ../../lab_config/intelc3850-2/wan_nic.json"
+ },
+ {
+ "name": "Bind wan/lan NIC to SR-IOV",
+ "args": "-f ../../lab_config/intelc3850-2/sriov_nic.json"
+ },
+ {
+ "name": "Bind wan/lan NIC to Standard",
+ "args": "-f ../../lab_config/intelc3850-2/std_nic.json"
+ }
+] Sample
+ lan_nic.json configuration
+ file: {
+ "name": "enp4s0f0",
+ "type": "dpdk",
+ "subType": "vfio-pci"
+} Sample
+ wan_nic.json configuration
+ file: {
+ "name": "enp4s0f1",
+ "type": "dpdk",
+ "subType": "vfio-pci"
+} Sample
+ sriov_nic.json configuration
+ file: {
+ "name": "enp4s0f1",
+ "type": "sr-iov",
+ "subType": "adapter-pool",
+ "sriovNumVfs": "2"
+} Sample
+ std_nic.json configuration
+ file: {
+ "name": "eno2",
+ "type": "standard"
+}
+
+
+
+ Running the Python Module
+
+ The bindNetworkInterface Python module can be
+ executed individually by running the following command line:
+
+ $ python bindNetworkInterface.py -u admin -p admin -H localhost -f
+../../lab_config/intelc3850-2/lan_nic.json -n intelc3850-2
+2019-03-07 18:03:29,365 - DEBUG: Started logging
+2019-03-07 18:03:29,366 - INFO: Bind NIC
+2019-03-07 18:03:29,406 - DEBUG: Login successful on host 'localhost'
+2019-03-07 18:03:29,406 - DEBUG: Session token is: 8c719cb0-40f2-11e9-a81f525400d08e1d
+2019-03-07 18:03:29,415 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 18:03:29,415 - DEBUG: Bind NIC '0000:01:00.1'
+2019-03-07 18:03:30,030 - INFO: Done
+2019-03-07 18:03:30,067 - DEBUG: Logging out and exiting...
+
+
+
+
+ Unbinding a Network Interface
+
+ How to Unbind a physical network interface from a DPDK or SR-IOV
+ is described below.
+
+
+ Script Options
+
+ $ python unbindNetworkInterface.py -h
+Usage: unbindNetworkInterface.py [options]
+
+Unbinds a physical interface to the DPDK or SR-IOV.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f NICFILE, --file=NICFILE
+ File containing network interface Information in JSON
+ format
+ -n DEVICENAME, --device-name=DEVICENAME
+ Name of the device
+
+ Mandatory options:
+ -H/--host, -f/--file, -n/--device-name
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to unbind a network interface
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the test case arguments passed to the
+ unbindNetworkInterface Python module.
+
+ Sample unit-test JSON file
+ format: [
+ {
+ "name": "Unbind lan NIC from DPDK",
+ "args": "-f ../../lab_config/intelc3850-2/lan_nic.json"
+ },
+ {
+ name": "Unbind wan NIC from DPDK",
+ "args": "-f ../../lab_config/intelc3850-2/wan_nic.json"
+ }
+]
+
+ Sample lan_nic.json
+ configuration file:
+
+ {
+ "name": "enp4s0f0",
+ "type": "dpdk"
+}
+
+ Sample wan_nic.json
+ configuration file:
+
+ {
+ "name": "enp4s0f1",
+ "type": "dpdk",
+}
+
+
+
+
+ Running the Python Module
+
+ The unbindNetworkInterface Python module
+ can be executed individually by running the following command
+ line:
+
+ $ python unbindNetworkInterface.py -u admin -p admin -H localhost -f
+../../lab_config/intelc3850-2/lan_nic.json -n intelc3850-2
+2019-03-07 17:33:54,377 - DEBUG: Started logging
+2019-03-07 17:33:54,378 - INFO: Unbind NIC
+2019-03-07 17:33:54,431 - DEBUG: Login successful on host 'localhost'
+2019-03-07 17:33:54,432 - DEBUG: Session token is: 6a77a1d1-40ee-11e9-a81f525400d08e1d
+2019-03-07 17:33:54,467 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 17:33:54,468 - DEBUG: Unbind NIC '0000:01:00.1'
+2019-03-07 17:33:55,616 - INFO: Done
+2019-03-07 17:33:55,659 - DEBUG: Logging out and exiting...
+
+
+
+
+ Getting a Network Interface
+
+ Details and steps on how to List the network interfaces for a
+ device, are described below.
+
+
+ Script Options
+
+ $ python getNetworkInterfaces.py -h
+2019-07-04 16:35:50,496 - DEBUG: Started logging
+2019-07-04 16:35:50,496 - INFO: Dump NICs
+Usage: getNetworkInterfaces.py [options]
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -n DEVICENAME, --device-name=DEVICENAME Name of the uCPE to get network /
+ interfaces from
+
+ Mandatory options:
+ -H/--host, -n/--device-name
+
+
+
+ Running the Python Module
+
+ The getNetworkInterfaces Python module can be
+ executed individually by running the following command:
+
+ $ python getNetworkInterfaces.py -H localhost -n intelc3850-2
+2020-01-07 05:58:03,630 - DEBUG: Started logging
+2020-01-07 05:58:03,630 - INFO: Dump NICs
+2020-01-07 05:58:03,687 - DEBUG: Login successful on host '172.24.3.90'
+2020-01-07 05:58:03,688 - DEBUG: Session token is: 93dd3cd0-313c-11ea-b0c7-525400b7889f
+2020-01-07 05:58:03,715 - DEBUG: Found device with name 'intelc3850-2'
+2020-01-07 05:58:03,717 - DEBUG:
+----------------External Network Interfaces for intelc3850-2----------------
+2020-01-07 05:58:07,622 - DEBUG: eno4 DpdkTypes: [u'igb_uio', u'vfio-pci'] \
+MacAddress: 0c:c4:7a:fb:85:dfsriov(7)
+2020-01-07 05:58:07,624 - DEBUG:
+2020-01-07 05:58:07,656 - DEBUG:
+----------------Configured External Network Interfaces for intelc3850-2----------------
+2020-01-07 05:58:07,657 - DEBUG: eno3 DpdkType: vfio-pci ID: \
+47556b22-b5c2-4acb-b3cb-09b1f024b3a7
+2020-01-07 05:58:07,658 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \
+2c06b4f7-6814-4432-8765-a9d0cd5303c1
+2020-01-07 05:58:07,659 - DEBUG: enp1s0f0 DpdkTypes: [u'igb_uio', u'vfio-pci'] \
+MacAddress: ac:1f:6b:2d:ee:58sriov(63)
+2020-01-07 05:58:07,660 - DEBUG:
+2020-01-07 05:58:07,690 - DEBUG:
+----------------Configured External Network Interfaces for intelc3850-2----------------
+2020-01-07 05:58:07,691 - DEBUG: eno3 DpdkType: vfio-pci ID: \
+47556b22-b5c2-4acb-b3cb-09b1f024b3a7
+2020-01-07 05:58:07,692 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \
+2c06b4f7-6814-4432-8765-a9d0cd5303c1
+2020-01-07 05:58:07,693 - DEBUG: eno2 DpdkTypes: [u'igb_uio', u'vfio-pci'] \
+MacAddress: 0c:c4:7a:fb:85:ddsriov(7)
+2020-01-07 05:58:07,695 - DEBUG:
+2020-01-07 05:58:07,724 - DEBUG:
+----------------Configured External Network Interfaces for intelc3850-2----------------
+2020-01-07 05:58:07,725 - DEBUG: eno3 DpdkType: vfio-pci ID: \
+47556b22-b5c2-4acb-b3cb-09b1f024b3a7
+2020-01-07 05:58:07,726 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \
+2c06b4f7-6814-4432-8765-a9d0cd5303c1
+2020-01-07 05:58:07,727 - DEBUG: eno1 DpdkTypes: [u'igb_uio', u'vfio-pci'] \
+MacAddress: 0c:c4:7a:fb:85:dcsriov(7)
+2020-01-07 05:58:07,728 - DEBUG:
+2020-01-07 05:58:07,760 - DEBUG:
+----------------Configured External Network Interfaces for intelc3850-2----------------
+2020-01-07 05:58:07,761 - DEBUG: eno3 DpdkType: vfio-pci ID: \
+47556b22-b5c2-4acb-b3cb-09b1f024b3a7
+2020-01-07 05:58:07,761 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \
+2c06b4f7-6814-4432-8765-a9d0cd5303c1
+2020-01-07 05:58:07,762 - DEBUG:
+2020-01-07 05:58:07,763 - INFO: Done
+2020-01-07 05:58:07,787 - DEBUG: Logging out and exiting...
+
+
+
+
+ Creating an OVS Network Bridge
+
+ Instructions on how to Create an OVS Bridge on a device are
+ detailed below.
+
+
+ Script Options
+
+ $ python newNetworkBridge.py -h
+Usage: newNetworkBridge.py [options]
+
+Create an OVS Bridge on a device.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f OVSFILE, --file=OVSFILE
+ File containing OVS bridge Information in JSON format
+ -n DEVICENAME, --device-name=DEVICENAME
+ Name of the device
+ -o STORENAME, --store-name=STORENAME
+ Name of the store
+
+ Mandatory options:
+ -H/--host, -f/--file, -n/--device-name or -o/--store-name
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to create a new network
+ bridge should contain a list of dictionaries. Each dictionary
+ indicates the test case name and the test case arguments passed to the
+ newNetworkBridge Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Creating network bridge LAN ",
+ "args": "-f ../../lab_config/intelc3850-2/lan_br.json"
+ },
+ {
+ "name": "Creating network bridge WAN ",
+ "args": "-f ../../lab_config/intelc3850-2/wan_br.json"
+ }
+]
+
+ Sample lan_br.json
+ configuration file:
+
+ {
+ "name": "lan_br",
+ "interfaces": ["enp4s0f0"]
+}
+
+ Sample wan_br.json
+ configuration file:
+
+ {
+ "name": "wan_br",
+ "interfaces": ["enp4s0f1"]
+}
+
+
+
+ Running the Python Module
+
+ The newNetworkBridge Python module can be
+ executed individually by running the following command line:
+
+ $ python newNetworkBridge.py -u admin -p admin -H localhost -f
+../../lab_config/intelc3850-2/lan_br.json -n intelc3850-2
+2019-03-07 18:03:30,767 - DEBUG: Started logging
+2019-03-07 18:03:30,768 - INFO: New OVS network bridge
+2019-03-07 18:03:30,801 - DEBUG: Login successful on host 'localhost'
+2019-03-07 18:03:30,801 - DEBUG: Session token is: 8d454061-40f2-11e9-a81f525400d08e1d
+2019-03-07 18:03:30,811 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 18:03:30,812 - DEBUG: Create new OVS network bridge 'lan_br'
+2019-03-07 18:03:37,358 - INFO: Done
+2019-03-07 18:03:37,402 - DEBUG: Logging out and exiting...
+
+
+
+
+ Deleting an OVS Network Bridge
+
+ How to Delete an OVS Bridge from a device is detailed in the
+ following.
+
+
+ Script Options
+
+ $ python delNetworkBridge.py -h
+Usage: delNetworkBridge.py [options]
+
+Delete an OVS Bridge from a device.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f OVSFILE, --file=OVSFILE
+ File containing OVS bridge Information in JSON format
+ -n DEVICENAME, --device-name=DEVICENAME
+ Name of the device
+ -o STORENAME, --store-name=STORENAME
+ Name of the store
+
+ Mandatory options:
+ -H/--host, -f/--file, -n/--device-name or -o/--store-name
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to delete a network bridge
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the test case arguments passed to the
+ delNetworkBridge Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Deleting network bridge LAN ",
+ "args": "-f ../../lab_config/intelc3850-2/lan_br.json"
+ },
+ {
+ "name": "Deleting network bridge WAN ",
+ "args": "-f ../../lab_config/intelc3850-2/wan_br.json"
+ }
+]
+
+ Sample lan_br.json
+ configuration file:
+
+ {
+ "name" : "lan_br"
+}
+
+ Sample wan_br.json
+ configuration file:
+
+ {
+ "name" : "wan_br"
+}
+
+
+
+ Running the Python Module
+
+ The delNetworkBridge Python module can be
+ executed individually by running the following command line:
+
+ $ python delNetworkBridge.py -u admin -p admin -H localhost -f
+../../lab_config/intelc3850-2/lan_br.json -n intelc3850-2
+2019-03-07 17:33:51,712 - DEBUG: Started logging
+2019-03-07 17:33:51,713 - INFO: Delete OVS network bridge
+2019-03-07 17:33:51,751 - DEBUG: Login successful on host 'localhost'
+2019-03-07 17:33:51,752 - DEBUG: Session token is: 68e08711-40ee-11e9-a81f525400d08e1d
+2019-03-07 17:33:51,768 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 17:33:51,768 - DEBUG: Delete OVS network bridge 'lan_br'
+2019-03-07 17:33:52,839 - INFO: Done
+2019-03-07 17:33:52,872 - DEBUG: Logging out and exiting...
+
+
+
+
+ Onboarding a VNF Image Raw
+
+ How to Onboard a VNF image in the Enea Edge Management based upon its raw
+ constituents, is detailed in depth below.
+
+
+ Script Options
+
+ $ python onboardVNFRaw.py -h
+Usage: onboardVNFRaw.py [options]
+
+Onboard a VNF in Enea Edge Management based upon its raw constituents.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f FTPUSERNAME, --ftpUsername=FTPUSERNAME
+ Username for FTP
+ -w FTPPASSWORD, --ftpPassword=FTPPASSWORD
+ FTP password
+ -P FTPPORT, --ftpPort=FTPPORT
+ FTP port
+ -i IMAGEPATH, --imagePath=IMAGEPATH
+ VNF image path
+ -b IMAGEINFO, --imageInfo=IMAGEINFO
+ File name of VNF image information in JSON format
+
+ Mandatory options:
+ -H/--host, -b/--imageInfo, -i/--imagePath
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to onboard a VNF image Raw
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the test case arguments passed to the
+ onboardVNFRaw Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Onboarding Fortigate VNF (wizard API)",
+ "args": "-b ../../vnf_config/fortigateImage/fortigateImage.json -i
+../../vnf_images/fortios.qcow2"
+ }
+]
+
+ Sample
+ fortigateImage.json configuration
+ file: {
+ "name" : "fortigateImage",
+ "version" : "1.0",
+ "description" : "Fortigate VNF Image",
+ "provider" : "Fortinet, Inc",
+ "numVcpus" : 1,
+ "imageFormat" : "QCOW2",
+ "memoryInMb" : 1024,
+ "storageInGb" : 20,
+ "image" : "fortios.qcow2",
+ "interfaces" : [
+ {
+ "name" : "external",
+ "type" : "PhysicalPort",
+ "description" : "External interface"
+ },
+ {
+ "name" : "in",
+ "type" : "PhysicalPort",
+ "description" : "Incoming interface"
+ },
+ {
+ "name" : "out",
+ "type" : "PhysicalPort",
+ "description" : "Outgoing interface"
+ }
+ ],
+ "cloudInitDataSource" : "ConfigDrive",
+ "cloudInitDriveType" : "cdrom",
+ "cloudInitContentParams" : [
+ {
+ "path" : "License",
+ "description" : "Operational license"
+ }
+ ]
+}
+
+
+
+ Running the Python Module
+
+ The onboardVNFRaw Python module can be
+ executed individually by running the following command line:
+
+ $ python onboardVNFRaw.py -u admin -p admin -f ftp -w ftp -H localhost -b b
+../../vnf_config/fortigateImage/fortigateImage.json -i
+../../vnf_images/fortios.qcow2
+2019-03-07 18:03:37,791 - DEBUG: Started logging
+2019-03-07 18:03:37,792 - INFO: Onboard wizard
+2019-03-07 18:03:37,859 - DEBUG: Login successful on host 'localhost'
+2019-03-07 18:03:37,859 - DEBUG: Session token is: 91770330-40f2-11e9-a81f525400d08e1d
+2019-03-07 18:03:37,860 - DEBUG: FTP file '../../vnf_images/fortios.qcow2' on host
+'localhost', port '2021'
+2019-03-07 18:03:38,027 - DEBUG: Onboard VNF raw: fortios.qcow2
+2019-03-07 18:03:41,701 - INFO: Done
+2019-03-07 18:03:41,748 - DEBUG: Logging out and exiting...
+
+
+
+
+ Offboarding a VNF
+
+ Steps on how to Offboard a VNF from the Enea Edge Management are detailed
+ below.
+
+
+ Script Options
+
+ $ python offboardVNF.py -h
+Usage: offboardVNF.py [options]
+
+Offboard a VNF from Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -n VNFDNAME, --vnfdName=VNFDNAME
+ Name of VNF descriptor to offboard
+
+ Mandatory options:
+ -H/--host, -n/--vnfdName
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to offboard a VNF should
+ contain a list of dictionaries. Each dictionary indicates the test
+ case name and the test case arguments passed to the
+ offboardVNF Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Offboarding Fortigate VNF ",
+ "args": "-n fortigateImage"
+ }
+]
+
+
+
+ Running the Python Module
+
+ The offboardVNF Python module can be
+ executed individually by running the following command line:
+
+ $ python offboardVNF.py -u admin -p admin -H localhost -n fortigateImage
+2019-03-07 17:33:56,523 - DEBUG: Started logging
+2019-03-07 17:33:56,524 - INFO: Offboard VNF
+2019-03-07 17:33:56,557 - DEBUG: Login successful on host 'localhost'
+2019-03-07 17:33:56,557 - DEBUG: Session token is: 6bbe2b90-40ee-11e9-a81f525400d08e1d
+2019-03-07 17:33:56,682 - DEBUG: Found VNF descriptor with name 'fortigateImage'
+2019-03-07 17:33:56,683 - DEBUG: Offboard VNF: fortigateImage
+2019-03-07 17:33:56,811 - INFO: Done
+2019-03-07 17:33:56,834 - DEBUG: Logging out and exiting...
+
+
+
+
+ Instantiating a VNF
+
+ Instantiating a VNF via the Enea Edge Management is detailed below.
+
+
+ Script Options
+
+ $ python instantiateVNFI.py -h
+Usage: instantiateVNFI.py [options]
+
+Instantiate a VNF via Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -t VNFTYPE, --vnfType=VNFTYPE
+ VNF Type (Name of VNF descriptor)
+ -n VIMDEVICENAME, --device-name=VIMDEVICENAME
+ Name of the device
+ -f PROPSFILE, --file=PROPSFILE
+ File containing VNF instance properties in JSON format
+
+ Mandatory options:
+ -H/--host, -t/--vnfType, -n/--device-name, -f/--file
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to instantiate a VNF should
+ contain a list of dictionaries. Each dictionary indicates the test
+ case name and the test case arguments passed to the
+ instantiateVNFI Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Instantiate Fortigate VNF ",
+ "args": "-t fortigateImage -f
+../../vnf_config/fortigateImage/fortigateFWInstance.json"
+ }
+]
+
+ The VNF instance JSON configuration file is specific to each
+ VNF.
+
+
+
+ Running the Python Module
+
+ The instantiateVNFI Python module can be
+ executed individually by running the following command line:
+
+ $ python instantiateVNFI.py -u admin -p admin -H localhost -n intelc3850-2 -t
+fortigateImage -f ../../vnf_config/fortigateImage/fortigateFWInstance.json
+2019-03-07 18:03:41,777 - DEBUG: Started logging
+2019-03-07 18:03:41,778 - INFO: Instantiate VNF
+2019-03-07 18:03:41,813 - DEBUG: Login successful on host 'localhost'
+2019-03-07 18:03:41,815 - DEBUG: Session token is: 93d69e10-40f2-11e9-a81f525400d08e1d
+2019-03-07 18:03:41,834 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 18:03:41,878 - DEBUG: Found VNF descriptor with name 'fortigateImage'
+2019-03-07 18:03:41,888 - DEBUG: Encrypt string content:
+cloudInit("vnf_config/fortigateImage/fortigateFW.conf")
+2019-03-07 18:03:41,889 - DEBUG: Encrypt string content:
+License("vnf_config/fortigateImage/fortigateLicense.lic")
+2019-03-07 18:03:41,889 - DEBUG: Instantiate fortigateImage VNF on 'intelc3850-2'
+2019-03-07 18:03:49,887 - INFO: Done
+2019-03-07 18:03:49,921 - DEBUG: Logging out and exiting...
+
+
+
+
+ Controlling a VNF Instance
+
+ How to Control a VNF instance from the Enea Edge Management is
+ detailed below.
+
+
+ If a sequence of commands aiming to change the state of the VNF
+ (start/stop/suspend/shutdown) is issued rapidly, certain VNFs might
+ become unresponsive. Depending on the actual VNF, the time required
+ between life-cycle operations may vary from several seconds to half a
+ minute or even more. If a VNF becomes unresponsive, the only possible
+ action is to "Force Delete" the instance from the Enea Edge Management.
+
+
+
+ Script Options
+
+ $ python controlVNFI.py -h
+Usage: controlVNFI.py [options]
+
+Controls a VNF instance from Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -i VNFINSTANCENAME, --vnfInstanceName=VNFINSTANCENAME
+ Name of VNF instance
+ -n VIMDEVICENAME, --device-name=VIMDEVICENAME
+ Name of the device
+ -c COMMAND, --command=COMMAND
+ Control command (stop, start, pause or resume)
+
+ Mandatory options:
+ -H/--host, -i/--vnfInstanceName, -n/--device-name, -c/--command
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to control a VNF instance
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the test case arguments passed to the
+ controlVNFI Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Pause Fortigate VNF instance",
+ "args": "-i fortigateFWInstance -c pause"
+ },
+ {
+ "name": "Resume Fortigate VNF instance",
+ "args": "-i fortigateFWInstance -c resume"
+ },
+ {
+ "name": "Stop Fortigate VNF instance ",
+ "args": "-i fortigateFWInstance -c stop"
+ },
+ {
+ "name": "Start Fortigate VNF instance",
+ "args": "-i fortigateFWInstance -c start"
+ }
+]
+
+
+
+ Running the Python Module
+
+ The controlVNFI Python module can be
+ executed individually by running the following command line:
+
+ $ python controlVNFI.py -u admin -p admin -H localhost -n intelc3850-2 -i
+fortigateFWInstance -c stop
+2019-03-07 18:03:51,991 - DEBUG: Started logging
+2019-03-07 18:03:51,992 - INFO: Control VNF
+2019-03-07 18:03:52,031 - DEBUG: Login successful on host 'localhost'
+2019-03-07 18:03:52,031 - DEBUG: Session token is: 99ed9ba3-40f2-11e9-a81f525400d08e1d
+2019-03-07 18:03:52,046 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 18:03:52,073 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
+2019-03-07 18:03:52,073 - DEBUG: Control VNF instance 'intelc3850-2', command: stop
+2019-03-07 18:03:53,011 - INFO: Done
+2019-03-07 18:03:53,047 - DEBUG: Logging out and exiting...
+
+
+
+
+ Destroying a VNF Instance
+
+ Steps and options on how to Destroy a VNF instance from the Enea
+ Edge Management are described below.
+
+
+ Script Options
+
+ $ python destroyVNFI.py -h
+Usage: destroyVNFI.py [options]
+
+Destroys a VNF instance from Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -i VNFINSTANCENAME, --vnfInstanceName=VNFINSTANCENAME
+ Name of VNF instance
+ -n VIMDEVICENAME, --device-name=VIMDEVICENAME
+ Name of the device
+
+ Mandatory options:
+ -H/--host, -i/--vnfInstanceName, -n/--device-name
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to destroy a VNF instance
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the test case arguments passed to the
+ destroyVNFI Python module.
+
+ Sample unit-test JSON file
+ format: [
+ {
+ "name": "Destroying Fortigate VNF ",
+ "args": "-i fortigateFWInstance"
+ }
+]
+
+
+
+ Running the Python Module
+
+ The destroyVNFI Python module can be
+ executed individually by running the following command line:
+
+ $ python destroyVNFI.py -u admin -p admin -H localhost -n intelc3850-2 -i
+fortigateFWInstance
+2019-03-07 17:33:51,025 - DEBUG: Started logging
+2019-03-07 17:33:51,026 - INFO: Destroy VNF
+2019-03-07 17:33:51,119 - DEBUG: Login successful on host 'localhost'
+2019-03-07 17:33:51,119 - DEBUG: Session token is: 68803ea5-40ee-11e9-a81f525400d08e1d
+2019-03-07 17:33:51,128 - DEBUG: Found device with name 'intelc3850-2'
+2019-03-07 17:33:51,148 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
+2019-03-07 17:33:51,149 - DEBUG: Destroy VNF: fortigateFWInstance
+2019-03-07 17:33:51,655 - INFO: Done
+2019-03-07 17:33:51,712 - DEBUG: Logging out and exiting...
+
+
+
+
+ Uploading a Enea Edge image onto the Enea Edge Management
+
+ Steps and options on how to Upload a Enea Edge image onto the
+ Enea Edge Management are described below.
+
+
+ Script Options
+
+ $ python uploadImage.py -h
+Upload NFVA image on Enea Edge Management
+Usage: uploadImage.py [options]
+
+Upload NFVA image on Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f FILENAME, --fileName=FILENAME
+ Path to NFVA image file name
+ -m MODULE, --module=MODULE
+ Module name (default is: VcpeAgent)
+ -t UPGRADETYPE, --upgradeType=UPGRADETYPE
+ Upgrade Type depends on architecture: xeon_d or
+ atom_c3000
+
+ Mandatory options:
+ -H/--host, -f/--fileName, -m/--module, -t/--upgradeType
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to upload a Enea Edge image
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the test case arguments passed to the
+ uploadImage Python module.
+
+ Sample unit-test JSON file
+ format: [
+ {
+ "name": "Upload NFVA image on Enea Edge Management",
+ "args": "-f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d"
+ }
+]
+
+
+
+ Running the Python Module
+
+ The uploadImage Python module can be
+ executed individually by running the following command line:
+
+ $ python uploadImage.py -u admin -p admin -H localhost \
+-f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d
+2020-02-28 11:38:42,754 - DEBUG: Started logging
+2020-02-28 11:38:42,755 - INFO: Upload NFVA image on Enea Edge Management
+2020-02-28 11:38:43,307 - DEBUG: Login successful on host 'localhost'
+2020-02-28 11:38:43,308 - DEBUG: Session token is: 7da3f960-5a16-11ea-a3de-5652b3ac1c30
+2020-02-28 11:41:29,148 - INFO: Verify image validation flag
+2020-02-28 11:41:29,149 - INFO: Valid flag: True
+2020-02-28 11:41:29,344 - INFO: The image \
+'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' was successfully uploaded
+2020-02-28 11:41:29,344 - INFO: Done
+2020-02-28 11:41:29,388 - DEBUG: Logging out and exiting...
+
+
+
+
+ Deleting a Enea Edge image file from the
+ Enea Edge Management
+
+ Steps and options on how to Delete a Enea Edge image from the
+ Enea Edge Management are described below.
+
+
+ Script Options
+
+ $ python deleteUpgradeFile.py -h
+Delete NFVA image from Enea Edge Management
+Usage: deleteUpgradeFile.py [options]
+
+Delete NFVA image from Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -i IMAGENAME, --imageName=IMAGENAME
+ NFVA Image name
+ -m MODULE, --module=MODULE
+ Module name - default is VcpeAgent
+
+ Mandatory options:
+ -H/--host, -i/--imageName, -m/--module.
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to delete a Enea Edge image
+ should contain a list of dictionaries. Each dictionary indicates the
+ test case name and the test case arguments passed to the
+ deleteUpgradeFile Python module.
+
+ Sample unit-test JSON file
+ format: [
+ {
+ "name": "Delete NFVA image on Enea Edge Management",
+ "args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2"
+ }
+]
+
+
+
+ Running the Python Module
+
+ The deleteUpgradeFile Python module can be
+ executed individually by running the following command line:
+
+ $ python deleteUpgradeFile.py -u admin -p admin -H localhost -i \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
+2020-02-28 12:06:20,111 - DEBUG: Started logging
+2020-02-28 12:06:20,112 - INFO: Delete NFVA image from Enea Edge Management
+2020-02-28 12:06:20,210 - DEBUG: Login successful on host 'localhost'
+2020-02-28 12:06:20,211 - DEBUG: Session token is: 594b2d50-5a1a-11ea-a3de-5652b3ac1c30
+2020-02-28 12:06:20,255 - INFO: The image \
+'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' was successfully found
+2020-02-28 12:06:20,256 - INFO: The oid for \
+'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' image name is as follows: \
+VcpeAgent/xeon_d/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
+2020-02-28 12:06:20,449 - INFO: The 'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' \
+image was successfully removed
+2020-02-28 12:06:20,479 - INFO: Done
+2020-02-28 12:06:20,517 - DEBUG: Logging out and exiting...
+
+
+
+
+ Installing and activating a Enea Edge image on an uCPE device
+ from the Enea Edge Management
+
+ Steps and options on how to Install and Activate a Enea Edge
+ image on an uCPE device from the Enea Edge Management are described
+ below.
+
+
+ Script Options
+
+ $ python installAndActivate.py -h
+Install and activate NFVA image from Enea Edge Management
+Usage: installAndActivate.py [options]
+
+Install and activate NFVA image from Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -i IMAGENAME, --imageName=IMAGENAME
+ Image name
+ -m MODULE, --module=MODULE
+ Module name -- VcpeAgent
+ -t UPGRADETYPE, --upgradeType=UPGRADETYPE
+ Upgrade Type -- xeon_d or atom_c3000
+ -d DEVICENAME, --deviceName=DEVICENAME
+ Device Name
+
+ Mandatory options:
+ -H/--host, -i/--imageName, -t/--upgradeType, -d/--deviceName,
+ -m/--module
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to install and activate a Enea Edge
+ image on a uCPE device from the Enea Edge Management should
+ contain a list of dictionaries. Each dictionary indicates the test
+ case name and the test case arguments passed to the
+ installAndActivate Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Install and activate NFVA image on uCPE device from Enea Edge Management",
+ "args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16"
+ }
+]
+
+
+
+ Running the Python Module
+
+ The installAndActivate Python module can be
+ executed individually by running the following command line:
+
+ $ python installAndActivate.py -u admin -p admin -H localhost -i \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16
+2020-02-28 12:36:46,137 - DEBUG: Started logging
+2020-02-28 12:36:46,138 - INFO: Install and activate NFVA image from Enea Edge Management
+2020-02-28 12:36:46,288 - DEBUG: Login successful on host 'localhost'
+2020-02-28 12:36:46,288 - DEBUG: Session token is: 99b7cde0-5a1e-11ea-a3de-5652b3ac1c30
+2020-02-28 12:36:46,325 - DEBUG: Found device with name 'inteld1521-16'
+2020-02-28 12:36:46,459 - INFO: Display info about NFVA installation \
+[inteld1521-16:1001:172.24.12.152] Install Started
+2020-02-28 12:36:46,492 - INFO: Transferring Image: \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
+2020-02-28 12:36:56,552 - INFO: Verifying Release [1]
+2020-02-28 12:37:06,599 - INFO: Verifying Release [2]
+2020-02-28 12:37:16,652 - INFO: Validating Upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
+2020-02-28 12:37:26,713 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [3]
+2020-02-28 12:37:36,770 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [5]
+2020-02-28 12:37:46,819 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [7]
+2020-02-28 12:37:56,879 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [9]
+2020-02-28 12:38:06,920 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [11]
+2020-02-28 12:38:16,975 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [13]
+2020-02-28 12:38:27,019 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [15]
+2020-02-28 12:38:37,091 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [18]
+2020-02-28 12:38:47,133 - INFO: Validating upgrade to \
+enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [20]
+2020-02-28 12:38:57,186 - INFO: Waiting for release to become active
+2020-02-28 12:39:07,231 - INFO: Upgrade Request Complete
+2020-02-28 12:39:17,242 - INFO: Installation completed!
+2020-02-28 12:39:17,243 - INFO: Done
+2020-02-28 12:39:17,294 - DEBUG: Logging out and exiting...
+
+
+
+
+ Clearing information about completed upgrades of uCPE devices
+ from the Enea Edge Management
+
+ Steps and options on how to clear information about completed
+ upgrades of uCPE devices from the Enea Edge Management are described
+ below.
+
+
+ Script Options
+
+ $ python clearCompletedUpgradesInfo.py -h
+Clear info about completed upgrades
+Usage: clearCompletedUpgradesInfo.py [options]
+
+Clear info about completed upgrades
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+
+ Mandatory options:
+ -H/--host
+
+
+
+ Configuring the JSON File
+
+ No JSON configuration file is needed to clear information about
+ completed upgrades of uCPE devices from the Enea Edge Management. The
+ clearCompletedUpgradesInfo Python module can be
+ run without a JSON file as a parameter.
+
+
+
+ Running the Python Module
+
+ The clearCompletedUpgradesInfo Python
+ module can be executed individually by running the following command
+ line:
+
+ $ python clearCompletedUpgradesInfo.py -u admin -p admin -H localhost
+2020-02-28 12:51:55,861 - DEBUG: Started logging
+2020-02-28 12:51:55,862 - INFO: Clear info about completed upgrades
+2020-02-28 12:51:55,950 - DEBUG: Login successful on host 'localhost'
+2020-02-28 12:51:55,951 - DEBUG: Session token is: b7eb83e0-5a20-11ea-a3de-5652b3ac1c30
+2020-02-28 12:51:55,993 - INFO: Done
+2020-02-28 12:51:56,025 - DEBUG: Logging out and exiting...
+
+
+
+
+ Uploading a Custom Script to the Enea Edge Management
+
+ Steps and options on how to upload a custom script to the
+ Enea Edge Management are described below.
+
+
+ Script Options
+
+ $ python customScripts/upload.py -h
+2020-04-14 10:26:23,582 - INFO: Upload Custom Script
+Usage: upload.py [options]
+
+Add a Custom Script to Enea Edge Management
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -f CUSTOMSCRIPT, --file=CUSTOMSCRIPT
+ Custom Script File
+ -e PHASE, --phase=PHASE
+ Execution phase. Must be one of the following: once-
+ before-startup | always-before-startup | once-after-
+ startup | always-after-startup
+
+ Mandatory options:
+ -H/--host, -f/--file, -e/--phase
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to upload a Custom Script to
+ the Enea Edge Management must contain a list of dictionaries. Each dictionary
+ indicates the test case name and the test case arguments passed to the
+ customScripts/upload Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+ {
+ "name": "Uploading a Custom Script to the Enea Edge Management",
+ "args": "-f ../../lab_config/customScripts/test_success_after_always \
+ -e always-after-startup"
+ }
+]
+
+
+
+ Running the Python Module
+
+ The customScripts/upload Python module can
+ be executed individually by running the following command line:
+
+ $ python automation_framework/customScripts/upload.py \
+-f lab_config/customScripts/test_success_after_always -e always-after-startup
+2020-04-14 14:08:02,824 - DEBUG: Started logging
+2020-04-14 14:08:02,915 - INFO: Upload Custom Script
+2020-04-14 14:08:02,994 - DEBUG: Login successful on host '172.24.3.109'
+2020-04-14 14:08:02,995 - DEBUG: Session token is: 97544990-7e48-11ea-835c-02423a1c239f
+2020-04-14 14:08:02,996 - DEBUG: Upload test_success_after_always to Enea Edge Management. \
+Content: #!/bin/bash
+echo test_success_after_always
+2020-04-14 14:08:03,138 - INFO: Done
+2020-04-14 14:08:03,169 - DEBUG: Logging out and exiting...
+
+
+
+
+ Uploading a Custom Script from the Enea Edge Management to a
+ Device
+
+ Steps and options on how to upload a custom script from the
+ Enea Edge Management to a Device are described below.
+
+
+ Script Options
+
+ $ python customScripts/uploadOnDevice.py -h
+2020-04-14 10:27:05,614 - INFO: Upload Custom Script on Device
+Usage: uploadOnDevice.py [options]
+
+Add a Custom Script to a Device
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
+ Custom Script Name that resides on Enea Edge Management
+ -e PHASE, --phase=PHASE
+ Execution phase. Must be one of the following: once-
+ before-startup | always-before-startup | once-after-
+ startup | always-after-startup
+ -n DEVICENAME, --device-name=DEVICENAME
+ Name of the device
+ -r, --reboot Reboot the device after uploading
+
+ Mandatory options:
+ -H/--host, -c/--customScriptName, -e/--phase, -n/--device-name
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to upload a Custom Script
+ from the Enea Edge Management to a Device must contain a list of dictionaries.
+ Each dictionary indicates the test case name and the test case
+ arguments passed to the
+ customScripts/uploadOnDevice Python
+ module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+{
+"name": "Uploading a Custom Script from Enea Edge Management to device",
+"args": "-c test_success_after_always -e always-after-startup -n inteld1521-6"
+}
+]
+
+
+
+ Running the Python Module
+
+ The customScripts/uploadOnDevice Python
+ module can be executed individually by running the following command
+ line:
+
+ $ python automation_framework/customScripts/uploadOnDevice.py -c \
+test_success_after_always -e always-after-startup -n inteld1521-6
+2020-04-14 14:26:26,205 - DEBUG: Started logging
+2020-04-14 14:26:26,206 - INFO: Upload Custom Script on Device
+2020-04-14 14:26:26,251 - DEBUG: Login successful on host '172.24.3.109'
+2020-04-14 14:26:26,252 - DEBUG: Session token is: 28ebcb10-7e4b-11ea-835c-02423a1c239f
+2020-04-14 14:26:26,286 - DEBUG: Found device with name 'inteld1521-6'
+2020-04-14 14:26:26,287 - DEBUG: Upload test_success_after_always to inteld1521-6
+2020-04-14 14:26:26,314 - INFO: Done
+2020-04-14 14:26:26,341 - DEBUG: Logging out and exiting...
+
+
+
+
+ Removing a Custom Script from the Enea Edge Management
+
+ Steps and options on how to remove a custom script from the
+ Enea Edge Management are described below.
+
+
+ Script Options
+
+ $ python customScripts/delete.py -h
+2020-04-14 14:36:52,010 - INFO: Delete Custom Script on Enea Edge Management
+Usage: delete.py [options]
+
+Delete a Custom Script from a Device
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
+ Custom Script Name that resides on a Device
+ -e PHASE, --phase=PHASE
+ Execution phase. Must be one of the following: once-
+ before-startup | always-before-startup | once-after-
+ startup | always-after-startup
+
+ Mandatory options:
+ -H/--host, -e/--phase
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to remove a Custom Script
+ from the Enea Edge Managementdid you mean device or
+ Enea Edge Management? must contain a list of dictionaries. Each dictionary
+ indicates the test case name and the test case arguments passed to the
+ customScripts/delete Python module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+{
+"name": "Removing a Custom Script from Enea Edge Management",
+"args": "-c test_success_after_always -e always-after-startup"
+}
+]
+
+
+
+ Running the Python Module
+
+ The customScripts/delete Python module can
+ be executed individually by running the following command line:
+
+ $ python automation_framework/customScripts/delete.py -c \
+test_success_after_always -e always-after-startup
+2020-04-14 14:39:22,042 - DEBUG: Started logging
+2020-04-14 14:39:22,042 - INFO: Delete Custom Script on Enea Edge Management
+2020-04-14 14:39:22,081 - DEBUG: Login successful on host '172.24.3.109'
+2020-04-14 14:39:22,082 - DEBUG: Session token is: f75a83a0-7e4c-11ea-835c-02423a1c239f
+2020-04-14 14:39:22,099 - DEBUG: Found custom script: 'test_success_after_always'
+2020-04-14 14:39:22,099 - DEBUG: Delete script test_success_after_always, \
+phase always-after-startup from Enea Edge Management
+2020-04-14 14:39:22,118 - INFO: Done
+2020-04-14 14:39:22,135 - DEBUG: Logging out and exiting...
+
+
+
+
+ Removing a Custom Script from a Device
+
+ Steps and options on how to remove a custom script from a device
+ are described below.
+
+
+ Script Options
+
+ $ python customScripts/deleteOnDevice.py -h
+2020-04-14 10:27:23,536 - INFO: Delete Custom Script on Device
+Usage: deleteOnDevice.py [options]
+
+Delete a Custom Script from a Device
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
+ Custom Script Name that resides on a Device
+ -e PHASE, --phase=PHASE
+ Execution phase. Must be one of the following: once-
+ before-startup | always-before-startup | once-after-
+ startup | always-after-startup
+ -n DEVICENAME, --device-name=DEVICENAME
+ Name of the device
+
+ Mandatory options:
+ -H/--host, -n/--device-name
+
+
+
+ Configuring the JSON File
+
+ The JSON configuration file needed to remove a Custom Script
+ from a device must contain a list of dictionaries. Each dictionary
+ indicates the test case name and the test case arguments passed to the
+ customScripts/deleteOnDevice Python
+ module.
+
+ Sample unit-test JSON file
+ format:
+
+ [
+{
+"name": "Removing a Custom Script from device",
+"args": "-c test_success_after_always -e always-after-startup -n inteld1521-6"
+}
+]
+
+
+
+ Running the Python Module
+
+ The customScripts/deleteOnDevice Python
+ module can be executed individually by running the following command
+ line:
+
+ $ python automation_framework/customScripts/deleteOnDevice.py -c \
+test_success_after_always -e always-after-startup -n inteld1521-6
+2020-04-14 14:33:52,288 - DEBUG: Started logging
+2020-04-14 14:33:52,288 - INFO: Delete Custom Script on Device
+2020-04-14 14:33:52,327 - DEBUG: Login successful on host '172.24.3.109'
+2020-04-14 14:33:52,327 - DEBUG: Session token is: 32cde4f0-7e4c-11ea-835c-02423a1c239f
+2020-04-14 14:33:52,349 - DEBUG: Found device with name 'inteld1521-6'
+2020-04-14 14:33:52,349 - DEBUG: Delete test_success_after_always, \
+phase always-after-startup from inteld1521-6
+2020-04-14 14:33:52,373 - INFO: Done
+2020-04-14 14:33:52,391 - DEBUG: Logging out and exiting...
+
+
+
+
+ Custom Script - Full Example
+
+ All Python API used in this example are described in detail in the following sections.
+
+ The list of custom scripts can be found in
+ <AF-TH-install-dir>/lab_config/customScripts :
+
+
+
+ test_fail_after_always . Phase:
+ always-after-startup.
+
+
+
+ test_fail_after_once . Phase:
+ once-after-startup.
+
+
+
+ test_fail_before_always . Phase:
+ always-before-startup.
+
+
+
+ test_fail_before_once . Phase:
+ once-before-startup.
+
+
+
+ test_success_after_always . Phase:
+ always-after-startup.
+
+
+
+ test_success_after_once . Phase:
+ once-after-startup.
+
+
+
+ test_success_before_always . Phase:
+ always-before-startup.
+
+
+
+ test_success_before_once . Phase:
+ once-before-startup.
+
+
+
+
+ The following example uses the
+ test_success_after_always custom script.
+
+
+
+ Uploading a Custom Script to the Enea Edge Management
+
+ $ python automation_framework/customScripts/upload.py \
+-f lab_config/customScripts/test_success_after_always -e always-after-startup
+2020-04-14 14:08:02,824 - DEBUG: Started logging
+2020-04-14 14:08:02,915 - INFO: Upload Custom Script
+2020-04-14 14:08:02,994 - DEBUG: Login successful on host '172.24.3.109'
+2020-04-14 14:08:02,995 - DEBUG: Session token is: 97544990-7e48-11ea-835c-02423a1c239f
+2020-04-14 14:08:02,996 - DEBUG: Upload test_success_after_always to Enea Edge Management. \
+Content: #!/bin/bash
+echo test_success_after_always
+2020-04-14 14:08:03,138 - INFO: Done
+2020-04-14 14:08:03,169 - DEBUG: Logging out and exiting...
+
+
+
+ Uploading a Custom Script from the Enea Edge Management to a
+ Device
+
+ $ python automation_framework/customScripts/uploadOnDevice.py -c \
+test_success_after_always -e always-after-startup -n inteld1521-6
+2020-04-14 14:26:26,205 - DEBUG: Started logging
+2020-04-14 14:26:26,206 - INFO: Upload Custom Script on Device
+2020-04-14 14:26:26,251 - DEBUG: Login successful on host '172.24.3.109'
+2020-04-14 14:26:26,252 - DEBUG: Session token is: 28ebcb10-7e4b-11ea-835c-02423a1c239f
+2020-04-14 14:26:26,286 - DEBUG: Found device with name 'inteld1521-6'
+2020-04-14 14:26:26,287 - DEBUG: Upload test_success_after_always to inteld1521-6
+2020-04-14 14:26:26,314 - INFO: Done
+2020-04-14 14:26:26,341 - DEBUG: Logging out and exiting...
+
+
+
+ Removing a Custom Script from a Device
+
+ $ python automation_framework/customScripts/deleteOnDevice.py -c \
+test_success_after_always -e always-after-startup -n inteld1521-6
+2020-04-14 14:33:52,288 - DEBUG: Started logging
+2020-04-14 14:33:52,288 - INFO: Delete Custom Script on Device
+2020-04-14 14:33:52,327 - DEBUG: Login successful on host '172.24.3.109'
+2020-04-14 14:33:52,327 - DEBUG: Session token is: 32cde4f0-7e4c-11ea-835c-02423a1c239f
+2020-04-14 14:33:52,349 - DEBUG: Found device with name 'inteld1521-6'
+2020-04-14 14:33:52,349 - DEBUG: Delete test_success_after_always, \
+phase always-after-startup from inteld1521-6
+2020-04-14 14:33:52,373 - INFO: Done
+2020-04-14 14:33:52,391 - DEBUG: Logging out and exiting...
+
+
+
+ Removing a Custom Script from the Enea Edge Management
+
+ $ python automation_framework/customScripts/delete.py -c \
+test_success_after_always -e always-after-startup
+2020-04-14 14:39:22,042 - DEBUG: Started logging
+2020-04-14 14:39:22,042 - INFO: Delete Custom Script on Enea Edge Management
+2020-04-14 14:39:22,081 - DEBUG: Login successful on host '172.24.3.109'
+2020-04-14 14:39:22,082 - DEBUG: Session token is: f75a83a0-7e4c-11ea-835c-02423a1c239f
+2020-04-14 14:39:22,099 - DEBUG: Found custom script: 'test_success_after_always'
+2020-04-14 14:39:22,099 - DEBUG: Delete script test_success_after_always, \
+phase always-after-startup from Enea Edge Management
+2020-04-14 14:39:22,118 - INFO: Done
+2020-04-14 14:39:22,135 - DEBUG: Logging out and exiting...
+
+
+
+
+ Adding an Offline Configuration Store
+
+ Steps and options on how to add a Config Store in the
+ Enea Edge Management are described below.
+
+
+ Script Options
+
+ To add a config store in the Enea Edge Management use the
+ addConfigStore.py script detailed below. Bear in
+ mind a CONFIGSTORE json file is needed to
+ successfully run the script in order to add an offline configuration
+ store.
+
+
+
+ Configuring the JSON file
+
+ Example of a CONFIGSTORE json file:
+
+ {
+ "descr": "intelc3850-2",
+ "version": "2.4.0",
+ "deviceGroupingTags": "",
+ "deviceId": "intelc3850-2",
+ "name": "intelc3850-2"
+}
+
+
+
+ Running the Python Module
+
+ Adding an offline config store in the Enea Edge Management using
+ the command line:
+
+ python automation_framework/device/addConfigStore.py -f \
+lab_config/inteld1521-16/store.json
+2020-10-16 09:35:51,084 - INFO: Add offline config store
+2020-10-16 09:35:51,160 - INFO: Done
+
+
+
+
+ Uploading an Offline Configuration Store to an uCPE
+ Device
+
+ Steps and options on how to upload a config store to a device are
+ described below.
+
+
+ Script options
+
+ To upload a config store to a uCPE Device use the
+ uploadConfigStore.py script detailed
+ below.
+
+ python uploadConfigStore.py -h
+Usage: uploadConfigStore.py [options]
+
+Upload offline configuration to uCPE Device.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -s STORE, --store=STORE
+ Offline config store name
+ -d DEVICE, --device=DEVICE
+ Device Name
+
+ Mandatory options:
+ -H/--host, -s/--store, -d/--device
+
+
+
+ Running the Python Modules
+
+ python automation_framework/device/uploadConfigStore.py -s inteld1521-16 \
+-d inteld1521-16
+2020-10-16 09:37:29,074 - INFO: Upload offline configuration to uCPE Device
+2020-10-16 09:37:49,321 - INFO: The 'inteld1521-16' config store was successfully \
+uploaded on device!
+2020-10-16 09:37:49,322 - INFO: Done
+
+
+
+
+ Checking the Upload of an Offline Configuration Store
+
+ Steps and options on how to check an upload of a Config Store to a
+ Device are described below.
+
+
+ Script options
+
+ To check an upload a config store to a uCPE Device use the
+ getUploadStatus.py script detailed below.
+
+ python getUploadStatus.py -h
+Usage: getUploadStatus.py [options]
+
+Get upload offline configure status on uCPE Device.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -d DEVICE, --device=DEVICE
+ Device Name
+
+ Mandatory options:
+ -H/--host, -d/--device
+
+
+
+ Running the Python Modules
+
+ python automation_framework/device/getUploadStatus.py -d inteld1521-16
+2020-10-16 09:38:33,388 - INFO: Get upload offline configure status on uCPE Device
+2020-10-16 09:38:33,486 - INFO: Successful: True
+2020-10-16 09:38:33,487 - INFO: Store name: inteld1521-16
+2020-10-16 09:38:33,488 - INFO: In progress: False
+2020-10-16 09:38:33,489 - INFO: A config store was successfully uploaded on device!
+2020-10-16 09:38:33,490 - INFO: Done
+
+
+
+
+ Removing an Offline Configuration Store in the
+ Enea Edge Management
+
+ Steps and options on how to remove an upload of a Config Store
+ from the Enea Edge Management are described below.
+
+
+ Modifications of an Offline Configurations Store are not
+ possible post deployment in the Enea Edge Management, as there is no option
+ for changing script states (e.g. changing the DPDK state in the
+ configDPDK.py python script or unbinding
+ interfaces). The offline store must be deleted and the new
+ state(s)/changes added in, before being deployed anew. This was not
+ deemed necessary for the current ZTP functionality.
+
+
+
+ Script options
+
+ To remove a config store from the Enea Edge Management use the
+ removeConfigStore.py script detailed
+ below.
+
+ python removeConfigStore.py -h
+Usage: removeConfigStore.py [options]
+
+Remove a config store from Enea Edge Management.
+
+Options:
+ --version show program's version number and exit
+ -h, --help show this help message and exit
+ -u USERNAME, --username=USERNAME
+ Enea Edge Management login username
+ -p PASSWORD, --password=PASSWORD
+ Enea Edge Management login password
+ -H HOST, --host=HOST Enea Edge Management host name or IP address
+ -o STORENAME, --store-name=STORENAME
+ Name of the Offline Config Store
+
+ Mandatory options:
+ -H/--host, -o/--store-name
+
+
+
+ Running the Python Modules
+
+ python automation_framework/device/removeConfigStore.py -o inteld1521-16
+2020-10-16 09:39:39,127 - INFO: Remove offline config store
+2020-10-16 09:39:39,289 - INFO: Done
+
+
+
+
+
+ Test Harness
+
+ All Test Harness sources are under the
+ <AF-TH-install-dir> directory and the host file
+ is the Ansible inventory file. See the complete tree listing at the
+ beginning of this chapter for details.
+
+ The Ansible based Test Harness represents an example of how to
+ structure all the files needed for creating automated test cases using the
+ AF and provides a way to implement them. The
+ ansible.cfg file contains an example of the Ansible
+ default configuration. It offers the possibility to display the Ansible
+ console output in different ways, by setting the
+ stdout_callback option to selective
+ or debug . The default value for this option is set to
+ selective to print only certain tasks. It is
+ recommended to switch to debug when a test fails. By
+ setting the parameter any_errors_fatal to
+ True , task failures will be considered fatal errors
+ (the play execution will stop). and why would this stop of play
+ execution help in this debugging scenario
+
+ All Playbooks that execute AF python modules run on
+ localhost . New entries have to be created for direct
+ communication over SSH with the boards, as done in the
+ [fortigateFW] example.
+
+ The setup_env.sh script sets up the
+ testHarness test environment by creating
+ testHarness-venv python virtualenv , executing requests
+ needed by Automation Framework python modules and installing
+ Ansible.
+
+ The Ansible package version installed in the test environment is
+ 2.9.6. The playbooks are based on this version of Ansible.
+
+ The /playbooks directory contains all the
+ implemented Ansible Playbooks. For more details please refer to the Sample Test Cases Chapter in the
+ Manual.
+
+ The /uCPEM_config directory stores JSON
+ configuration files needed for the setup of the Enea Edge Management used by TH.
+ One configuration file is needed per Enea Edge Management installation, to be used
+ in the TH.
+
+ The /vnf_image directory stores the VNF Images
+ needed by the Ansible Playbooks (i.e. the sample test cases).
+
+ The /lab_config directory stores the JSON
+ configuration files related to a device (devices, NICs and bridges) as
+ well as sample custom scripts. Each subfolder should be named exactly like
+ the device name and should contain all the related configuration files
+ needed for the test cases to be run on it.
+
+ The /vnf_config directory stores the
+ configuration files related to a VNF Descriptor and VNF instances.
+ Typically these include a VNF Image JSON, VNF Instance JSON, VNF license
+ and any other files required by the type of the VNF. Each subfolder should
+ be named exactly like the name of the VNF Descriptor and should contain
+ all the related configuration files needed for test cases to be run using
+ this VNF.
+
+ The /log directory is created when the
+ setup_env.sh is run. When test cases are run, the
+ Ansible and the Python logs are stored in the
+ ansible.log and debug.log files,
+ respectively.
+
+
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/book.xml b/doc/book-enea-edge-auto-fw-th-user-guide/doc/book.xml
new file mode 100644
index 0000000..e0a5cdf
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-user-guide/doc/book.xml
@@ -0,0 +1,33 @@
+
+
+]>
+
+ Enea Enea Edge Automation Framework and Test Harness User Guide
+
+ Release Version
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/components.xml b/doc/book-enea-edge-auto-fw-th-user-guide/doc/components.xml
new file mode 100644
index 0000000..24a7a29
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-user-guide/doc/components.xml
@@ -0,0 +1,137 @@
+
+
+ Components
+
+ An overview of the Enea Edge Runtime and the Edge Management
+ in cooperation with the Automation Framework and Test Harness, will
+ be presented in detail.
+
+
+ Component Overview
+
+
+
+
+
+
+
+
+
+ Enea Edge
+
+ Enea Edge is comprised of the Enea Edge Management and the Enea
+ Edge Runtime.
+
+
+ Enea Edge Management
+
+ The Enea Edge Management application needs to be installed on a
+ supported platform. Upon installation, the system will be set up to
+ manage Enea Edge "devices", these are the virtualized CPE devices
+ used in testing.
+
+ For more on Enea Edge Management installation instructions, please
+ refer to the section on how to Installing the Enea Edge Management in the
+
+ Manual.
+
+
+
+ Enea Edge Runtime
+
+ One or more uCPE devices running the Enea Edge Runtime
+ are required as hosts to run the VNF(s). The uCPE device is
+ known to the Enea Edge Management as the "VcpeAgent" device module.
+
+
+ Before running any use case with the Automation Framework or the
+ Test Harness, make sure the uCPE device(s) have been added to the Edge Management.
+
+
+ Adding a VcpeAgent device can be done via two methods:
+
+
+
+ Through the Enea Edge Management GUI. Add the device using the
+ appropriate parameters by launching the UI under
+ Devices -> Manage in the
+ main screen.
+
+
+
+ REST API. Invoke the Enea Edge Management REST API to add a
+ device.
+
+
+
+ For more on Enea Edge installation instructions, please
+ refer to chapter Preparing the USB stick for installation of the
+ Enea Edge Runtime in the
+ Manual.
+
+
+
+
+ Automation Framework
+
+ Testing can be performed by running the available Python scripts
+ against the Enea Edge Management REST API (Python samples supplied). This can be
+ done by using the Python scripts individually or by using the Python
+ unit-test suite that is able to automatically run test-cases defined for
+ each available Python script.
+
+ In either case, it is desirable to use a different host (instead of
+ running the tests on the same system as the Enea Edge Management) in order to
+ ensure that the Enea Edge Management is setup and installed correctly in terms of
+ allowing external users to access it and use it effectively.
+
+
+
+ Test Harness
+
+ The Test Harness (TH) provides a way for driving configuration with
+ Ansible Playbooks, by running the python modules from the Automation
+ Framework (AF) and by direct connection over SSH to the boards that run
+ Enea Edge.
+
+ The Test Harness includes an automated test suite that
+ contains:
+
+
+
+ VNF, Device and Network Smoke Test Cases. A sample test suite
+ that acts as basic smoke tests for Enea Edge and also as a
+ sanity-check test suite for the AF and TH.
+
+
+
+ VNF Deployment and Lifecycle. A sample test suite that verifies
+ the instantiation, lifecycle control and destruction of a VNF for Enea
+ Edge.
+
+
+
+ Service Creation and Lifecycle. A sample test suite that
+ contains complex test cases showcasing service creation and lifecycle
+ management.
+
+
+
+ For details about the test suites or test cases please refer to
+ chapter Sample Test Cases in the
+ Manual.
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/getting_started.xml b/doc/book-enea-edge-auto-fw-th-user-guide/doc/getting_started.xml
new file mode 100644
index 0000000..97666cf
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-user-guide/doc/getting_started.xml
@@ -0,0 +1,239 @@
+
+
+ Getting Started with the Automation Framework and Test
+ Harness
+
+
+ Prerequisites
+
+ For installation of the Automation Framework and Test Harness a
+ CentOS 7 host machine is needed with support for:
+
+
+
+ Python 2.7.
+
+
+
+ EPEL Repository:sudo yum install epel-release
+
+
+
+ PIP package manager: sudo yum -y install python-pip
+
+
+
+ Virtualenv tool: sudo pip install virtualenv
+
+
+
+
+ The Automation Framework and Test Harness installation may be done
+ on the same machine used for Enea Edge Management installation, although this is
+ not encouraged. For more details see section Automation Framework in the .
+
+
+
+
+ Environment
+
+
+ Lab setup overview for Basic Setup
+
+
+
+
+
+
+ The following enviroment setup is needed for running all tests
+ defined in the
+ manual:
+
+ Lab Network
+ Requirements
+
+ DHCP enabled.
+
+
+
+ Internet Connectivity.
+
+
+
+ Enea Edge Management Host
+ Requirements
+
+
+
+ Running CentOS 7.
+
+
+
+ Connected to the Lab Network.
+
+
+
+ Enea Edge Management installed.
+
+
+ For details on how to install the Enea Edge Management, see Installing the Enea Edge Management in the
+
+ Manual.
+
+
+
+
+ uCPE device
+ Requirements
+
+ Minimum of 4 Physical Network Devices.
+
+
+
+ 4GB RAM and 4 cores (Intel C3000 or Xeon D).
+
+
+
+ 2 Physical connections to the Lab Network.
+
+
+
+ Enea Edge Runtime installed.
+
+
+ For information on how to install Enea Edge refer to
+ Preparing the USB stick for installation
+ of the Enea Edge Runtime in the
+ Manual.
+
+
+
+ Lab Setup Overview for ChainedVNFsService
+
+
+
+
+
+
+
+
+ uCPE device 1 and 2
+ Requirements
+
+ Minimum of 4 Physical Network Devices.
+
+
+
+ 16GB RAM and 8 cores (Intel C3000 or Xeon D).
+
+
+
+ 2 Physical connections to the Lab Network.
+
+
+
+ 1 Physical connection back to back between both uCPE
+ devices.
+
+
+
+ Enea Edge Runtime installed.
+
+
+
+
+
+ Installation and Initial Setup
+
+
+
+ Unzip the
+ Enea_NFV_Access_AF-TH_<version>-build<build_number>.zip
+ archive file, provided by Enea, on a supported host machine.
+
+ The directory in which the archive has been unpacked will be
+ denoted as <AF-TH-installdir> .
+
+
+
+ Enter the <AF-TH-install-dir> directory
+ and run the setup_env.sh script to do the initial
+ setup of the Test Harness environment: source setup_env.sh
+
+
+
+ Set up the Enea Edge Management which will be used by the TH:
+
+
+
+ Create the Enea Edge Management JSON config file in the
+ <AF-TH-install-dir>/uCPEM_config/
+ directory:{
+"ucpe_usr":"Enea Edge Management Username",
+"ucpe_pass":"Enea Edge Management Password",
+"ucpe_host":"Enea Edge Management IP/Hostname",
+"ftp_usr":"FTP Username",
+"ftp_pass":"FTP Password",
+"ftp_port":"FTP Port"
+} See the
+ <AF-TH-install-dir>/uCPEM_config/ucpem01.json
+ file as an example.
+
+
+
+ Run the setupuCPEManager.yml Ansible
+ Playbook with the JSON config path as a parameter:
+ ansible-playbook playbooks/setupuCPEManager.yml -e\
+"@uCPEM_config/<config_name>.json"
+
+ Example ansible-playbook playbooks/setupuCPEManager.yml -e\
+"@uCPEM_config/ucpem01.json"
+
+
+
+
+
+
+ The steps presented in this section are to be executed only once,
+ for the initial setup of the TH environment.
+
+
+ After the initial setup, each session ends by closing the Python
+ virtual environment through running deactivate from the
+ <AF-THinstall-dir> directory.
+
+ Subsequent use of the installation requires activating the Python
+ virtual enviroment before using the Automation Framework and Test Harness:
+ source
+ <AF-TH-install-dir>/testHarness-venv/bin/activate .
+
+ Furthermore, if a user wants to use a new Enea Edge Management instance for
+ a new session, the user also has to re-run the
+ setupuCPEManager.yml playbook with the corresponding
+ JSON config for the new Enea Edge Management instance.
+
+
+ Automation Framework and Test Harness History Information can be
+ found in the AF&TH CHANGELOG file available in:
+ <AF-TH-install-dir>/CHANGELOG
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png b/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png
new file mode 100755
index 0000000..0329450
Binary files /dev/null and b/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png differ
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png b/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png
new file mode 100755
index 0000000..a384877
Binary files /dev/null and b/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png differ
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/environment_basicsetup.png b/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/environment_basicsetup.png
new file mode 100755
index 0000000..c30dcfd
Binary files /dev/null and b/doc/book-enea-edge-auto-fw-th-user-guide/doc/images/environment_basicsetup.png differ
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/overview.xml b/doc/book-enea-edge-auto-fw-th-user-guide/doc/overview.xml
new file mode 100644
index 0000000..b2486a0
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-user-guide/doc/overview.xml
@@ -0,0 +1,188 @@
+
+
+ Overview
+
+ This document describes the Automation Framework and Test Harness for
+ Enea Edge, along with instructions regarding the necessary steps to
+ run these software tools.
+
+
+ Description
+
+ The Automation Framework provides a way for driving configuration
+ with Python scripting. It complements the Enea Edge Management GUI and uses
+ the northbound REST APIs, given to provide full usability of the Enea Management
+ features.
+
+ The Test Harness is based on running Ansible Playbooks to complete
+ different test cases, which make use of the Automation Framework Python
+ modules and/or direct commands on the uCPE devices running the Enea Edge Runtime.
+
+
+
+ Definitions and Acronyms
+
+
+ Definitions
+
+
+
+
+
+
+ Component
+
+ Description
+
+
+
+
+
+ Enea Edge
+
+ The Enea Edge (with ODM) Runtime and the
+ Enea Edge Management.
+
+
+
+
+
+
+ Acronyms
+
+
+
+
+
+
+ Component
+
+ Description
+
+
+
+
+
+ AF
+
+ Automation Framework for Enea Edge.
+
+
+
+ API
+
+ Application Programming Interface.
+
+
+
+ DHCP
+
+ Dynamic Host Configuration Protocol.
+
+
+
+ DPDK
+
+ Data Plane Development Kit.
+
+
+
+ FTP
+
+ File Transfer Protocol.
+
+
+
+ GUI
+
+ Graphical User Interface.
+
+
+
+ IP
+
+ Internet Protocol.
+
+
+
+ JSON
+
+ JavaScript Object Notation.
+
+
+
+ NIC
+
+ Network Interface Card.
+
+
+
+ NETCONF
+
+ Network Configuration Protocol.
+
+
+
+ NFV
+
+ Network Functions Virtualization.
+
+
+
+ ODM
+
+ Enea Element On Device Management.
+
+
+
+ OVS
+
+ Open vSwitch.
+
+
+
+ REST
+
+ Representational State Transfer.
+
+
+
+ SR-IOV
+
+ Single Root Input/Output Virtualization.
+
+
+
+ SSH
+
+ Secure Shell.
+
+
+
+ TH
+
+ Test Harness for Enea Edge.
+
+
+
+ Enea Edge Management
+
+ Enea Universal Customer Premises Equipment Manager.
+
+
+
+ VCPE
+
+ Virtual Customer Premises Equipment.
+
+
+
+ VNF
+
+ Virtualized Network Function.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/doc/troubleshooting_guide.xml b/doc/book-enea-edge-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
new file mode 100644
index 0000000..a5cd664
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
@@ -0,0 +1,43 @@
+
+
+ Troubleshooting Guide
+
+ The following are best practices and possible solutions to problems
+ that may occur during operation:
+
+
+
+ All the Playbooks have to be run from the root directory of the
+ Test Harness (TH) to avoid failures such as "File not found!", since the
+ paths to the required configuration files are hardcoded into the
+ Playbooks.
+
+
+
+ If the setup_env.sh fails, for debugging remove
+ &> /dev/null from the failed command. The
+ output of the command will be printed, and will not be redirected to
+ /dev/null anymore.
+
+
+
+ When setting up the Enea Edge Management to be used by the TH through the
+ setupuCPEManager.yml Playbook, if the uCPE
+ username/password/host are incorrect or are missing, all the Sample test
+ cases will fail. If the FTP username/password/port are wrong or are
+ missing, the tests that require file transfer to the Enea Edge Management will
+ fail.
+
+
+
+ Ansible logs are not written into the
+ log/ansible.log file when the
+ stdout_callback is set to
+ selective in the ansible.cfg file.
+ For debugging, check the python logs from the
+ log/debug.log file or change the
+ stdout_callback to debug and rerun
+ the test.
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-auto-fw-th-user-guide/swcomp.mk b/doc/book-enea-edge-auto-fw-th-user-guide/swcomp.mk
new file mode 100755
index 0000000..d17c2b3
--- /dev/null
+++ b/doc/book-enea-edge-auto-fw-th-user-guide/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-auto-fw-th-user-guide
+BOOKDESC_$(BOOKPACKAGES) := "Enea Enea Edge $(PROD_VER) Automation Framework and Test Harness User Guide"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-edge-example-usecases/doc/128t_vnf_router.xml b/doc/book-enea-edge-example-usecases/doc/128t_vnf_router.xml
new file mode 100644
index 0000000..89692b0
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/128t_vnf_router.xml
@@ -0,0 +1,715 @@
+
+
+ 128T VNF Router Example Use-case
+
+ The 128T Networking Platform (128T) natively provides network-based
+ security, control, and insight across data centers, wide-area networks
+ (WAN), and edge locations for enterprises, service providers, and cloud
+ companies alike.
+
+
+ Prerequisites
+
+ The following are needed for this example use case:
+
+
+
+ 1 in band management port for device management.
+
+
+
+ 1 in band management port for 128T VNF.
+
+
+
+ 1 WAN interface for 128T.
+
+
+
+ 1 LAN interface for 128T.
+
+
+
+ The following files are needed for this example use-case:
+
+
+
+ 128T router VNF image. Please contact 128 Technology to get a
+ VNF image and its license file.
+
+
+
+ cloud-init iso image.
+
+
+
+
+ For data path validation, it may be required to generate a new
+ cloud-init image to match your network configuration.
+
+
+
+
+ 128T VNF Router
+
+
+ 128T VNF Router Setup Overview
+
+
+
+
+
+
+
+
+
+ Use-case Setup
+
+ Configuring Network Interfaces on uCPE
+ devices:
+
+ Add the trgt uCPE device into Enea Edge Management:
+ Devices -> Manage -> Add .
+
+ Fill in the required fields with the following data:
+
+
+ Device Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ Type
+
+ Enea universal CPE
+
+
+
+ Release
+
+ 2.2.2
+
+
+
+ Name
+
+ trgt
+
+
+
+ IP/DNS Address
+
+ <unspecified>
+
+
+
+ Description
+
+ Target 1
+
+
+
+ SSH Port
+
+ 830
+
+
+
+ SSH User Name
+
+ root
+
+
+
+ Password
+
+ null
+
+
+
+ Device ID
+
+ Also configured during installation of the device
+ (E.g.: Target-15).
+
+
+
+ OK
+
+ Green status indicates connection with uCPE device
+ was established.
+
+
+
+
+
+
+
+ In order to add the device on the map: Right-Click on
+ Map -> Place Device -> trgt .
+
+
+
+ Configure the virtualization infrastructure for 128T VNF by
+ creating three OVS bridges and a host interface:
+
+ Add the Host Interface by selecting the trgt device, then
+ Configuration -> External Interfaces ->
+ Configuration -> Add , and fill in the required fields
+ with the following data:
+
+
+ Host Interface Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ Source
+
+ enp4s0f1 . The only interface
+ available for LAN connection.
+
+
+
+ networking-type
+
+ dpdk
+
+
+
+ dpdk-type
+
+ vfio-pci
+
+
+
+ Create
+
+ <interface enp4s0f1 ready to be used in a LAN
+ bridge.>
+
+
+
+
+
+ Select the trgt device then: Configuration ->
+ OpenVSwitch -> Bridges -> Add , and fill in the
+ required fields for each bridge with the following data from each
+ table:
+
+
+ ibm_br Bridge Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ id
+
+ <autogenerated - do not change>
+
+
+
+ Name
+
+ ibm_br
+
+
+
+ ovs-bridge-type
+
+ inbandMgmt
+
+
+
+ Create
+
+ The system will automatically select the
+ physical interface that has access to Enea Edge
+ Management.
+
+
+
+
+
+
+ vnf_mgmt_br Bridge Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ id
+
+ <autogenerated - do not change>
+
+
+
+ Name
+
+ vnf_mgmt_br
+
+
+
+ ovs-bridge-type
+
+ vnfMgmt
+
+
+
+ vnf-mgmt-address
+
+ 10.0.0.1
+
+
+
+ Create
+
+
+
+
+
+
+
+
+ lan_br Bridge Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ id
+
+ <autogenerated - do not change>
+
+
+
+ Name
+
+ lan_br
+
+
+
+ ovs-bridge-type
+
+ dataPlane
+
+
+
+ sub-type
+
+ communication
+
+
+
+ +
+
+ Name: enp4s0f1 OK
+
+
+
+ Create
+
+
+
+
+
+
+
+
+
+ Onboarding the VNFs:
+
+ Onboard the VM Image through VNF -> Descriptors ->
+ On-board , and fill in the required fields with the following
+ values:
+
+
+ VM Image Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ VM image file
+
+ centos_128t_with_ci.qcow2
+
+
+
+ Image format
+
+ QCOW2
+
+
+
+ VNF Type Name
+
+ 128T
+
+
+
+ Description
+
+ 128T Router
+
+
+
+ Version
+
+ 1.0
+
+
+
+ Memory in MB
+
+ 8192. More memory can be allocated if required
+ (<28672).
+
+
+
+ Num. of CPUs
+
+ 2. More CPUs can be reserved if required
+ (<15).
+
+
+
+ Interfaces -> +
+
+ Name: mgmt
+
+
+
+ Interfaces -> +
+
+ Name: wan
+
+
+
+ Interfaces -> +
+
+ Name: lan
+
+
+
+ Cloud Init -> Cloud-Init Datasource
+
+ ISO
+
+
+
+ Cloud Init -> Cloud-Init Disk Type
+
+ cdrom
+
+
+
+ Properties -> +
+
+ Name: vnfMgmtIpAddress. Value: 10.0.0.2
+
+
+
+ Properties -> +
+
+ Name: internalMgmtPort. Value: 443
+
+
+
+ Properties -> +
+
+ Name: externalMgmtPort. Value: 60001
+
+
+
+ Onboard
+
+ <Wait for message: VNF package onboarded
+ successfully>
+
+
+
+ Close
+
+
+
+
+
+
+
+
+
+
+ HTTPS access (443) can be changed with another type of
+ access. Please consult official 128T documentation and make sure
+ the 128T VNF is configured to accept another type of connection
+ before changing the port number.
+
+
+
+ externalMgmtPort (60001) represents the
+ external port on which the user can access the VNF management
+ interface via HTTPS. Another port can be selected if needed. There
+ are no other changes required or components affected by this
+ change.
+
+
+
+ vnfMgmtIpAddress (10.0.0.2) represents
+ the IP address of the management interface of the 128T VNF.
+ Changing this value requires an update to the 128T configuration
+ to match the new IP address.
+
+
+
+
+ Instantiating the VNFs:
+
+ Instantiate the 128T VNF by selecting the trgt device, then
+ VNF -> Instances -> Add .
+
+ Fill in the required fields with the following values:
+
+
+ 128T VNF Instantiation
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ Name
+
+ 128T_trgt_1
+
+
+
+ VNF Type
+
+ 128T
+
+
+
+ VNFD Version
+
+ 1.0
+
+
+
+ Flavour
+
+ Canonical
+
+
+
+ uCPE Device
+
+ trgt
+
+
+
+ Cloud Init File
+
+ centos_128t_internet_ci.iso
+
+
+
+ Domain Update Script
+
+
+
+
+
+ Interfaces
+
+
+
+
+
+ ID
+
+ IF Name
+
+
+
+ mgmt (dpdk)
+
+ Bridge: vnf_mgmt_br
+
+
+
+ wan (dpdk)
+
+ Bridge: ibm_br
+
+
+
+ lan (dpdk)
+
+ Bridge: lan_br
+
+
+
+ Create
+
+
+
+
+
+
+
+
+ To procure the VNF image files and their licenses, please
+ contact each respective VNF provider.
+
+
+
+
+ Testing the Use-case
+
+ In order to access the web interface of the 128T VNF, open a
+ browser from a machine connected on the same network with the WAN port
+ of the trgt uCPE device and browse to:
+ https://<public_trgt_WAN_IP>:60001 . Log in
+ using the following credentials:
+
+
+
+ Username: admin
+
+
+
+ Password: 128Tadmin
+
+
+
+ In order to validate the data path, connect a test machine to the
+ LAN physical port, assign the static IP and a route:> ifconfig eth3 192.168.64.3 netmask 255.255.255.0
+> ip route add default via 192.168.64.1 dev eth3
+> ping 8.8.8.8
+
+
+
+ Use-case Clean-up
+
+ In order to remove the setup created previously all components
+ need to be deleted in reverse order:
+
+
+
+ Select the trgt uCPE device -> VNF -> Instances ->
+ 128T -> Delete.
+
+
+
+ Select the trgt uCPE device -> Configuration ->
+ OpenVSwitch -> Bridges. Select all bridges -> Delete.
+
+
+
+ Select the trgt uCPE device -> Configuration -> External
+ Interfaces -> Configuration. Select all interfaces ->
+ Delete.
+
+
+
+ VNF -> Descriptors, select all bundles ->
+ Offboard.
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/appendix_1.xml b/doc/book-enea-edge-example-usecases/doc/appendix_1.xml
new file mode 100644
index 0000000..df262af
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/appendix_1.xml
@@ -0,0 +1,63 @@
+
+
+ How to create a 128T cloud-init iso image (day-0
+ configuration)
+
+ Prerequisites:
+
+ Development host with Linux shell.
+
+
+
+ genisoimage tool installed.
+
+
+
+ Unpack the 128T/128t-cloud-init-example.tar.gz
+ archive and check the README file for more details:
+
+ >tar -zxf 128t-cloud-init-example.tar.gz
+>cd 128T/cloud-init-example/
+>ls ./
+README
+user-data
+meta-data
+t128-running.xml
+
+ To generate the cloud-init iso image:
+
+ >genisoimage -output centos_128t_ci.iso -volid cidata -joliet \
+-rock user-data meta-data t128-running.xml
+
+ Notes:
+
+ user-data and meta-data
+ files must be kept unchanged.
+
+
+
+ To update the 128T configuration change the
+ t128-runing.xml file.
+
+
+
+ XML is the same file downloaded from 128T web access:
+ configuration -> Import and Export Configuration ->
+ Export Configuration -> Download Configuration . The
+ configuration can be updated from a web interface, downloaded onto the
+ development host and used in generating a new cloud-init iso
+ image.
+
+
+
+ By default, t128-running.xml is configured to pass
+ all traffic from the LAN to the WAN interface. There is only one change
+ required for the 128T VNF to work on the user's network:
+
+ <rt:next-hop>172.24.15.254</rt:next-hop>
+
+ Please change <172.24.15.254> with the IP address of your
+ Gateway in the t128-running.xml file and generate a new
+ iso image as described above. For more details about configuring the 128T
+ VNF please contact 128 Technologies.
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/appendix_2.xml b/doc/book-enea-edge-example-usecases/doc/appendix_2.xml
new file mode 100644
index 0000000..2458d99
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/appendix_2.xml
@@ -0,0 +1,326 @@
+
+
+ How to create the 128T image for NFV Access
+
+ The following steps were used by Enea to generate the 128T qcow2 image
+ used as the VNF image on NFV Access.
+
+
+ Keep in mind a Virtual Machine was used instead of a physical
+ host.
+
+
+ Prerequisites:
+
+ 128T-3.2.7-1.el7.centos.x86_64.iso provided
+ by 128 Technologies.
+
+
+
+ A Linux development host with internet access.
+
+
+
+ A least one of the TAP interfaces connected to a bridge with
+ Internet access.
+
+ How to create the 128T image for NFV
+ Access:
+
+ >qemu-img create -f qcow2 128t.qcow2 128G
+>qemu-system-x86_64 -enable-kvm -m 8G -cpu host -smp cores=3,sockets=1 \
+-M q35 -nographic bios /usr/share/qemu/bios.bin -boot order=d,menu=on \
+cdrom 128T-3.2.7-1.el7.centos.x86_64.iso \
+hdb 128t.qcow2 \
+device e1000,netdev=net1,mac=52:52:01:02:03:01 \
+netdev tap,id=net1,ifname=tap1,script=no,downscript=no
+
+
+
+ Press the <ENTER> key to begin the installation
+ process.
+
+
+
+ Wait for the distribution and the 128T to install:
+
+ ------------------------------
+128T Packages Installed
+
+Please Remove Install Media,
+
+then enter <Yes> to reboot and
+continue install process
+
+ <Yes> <No>
+------------------------------
+
+ Press Yes.
+
+
+
+ Wait to reboot and press CTR+ a+c to enter
+ the qemu monitor:
+
+ (qemu) quit
+
+
+
+ Start qemu only with the qcow2 image attached, no installer
+ image required:
+
+ >qemu-system-x86_64 -enable-kvm -m 8G -cpu host -smp cores=3,sockets=1 \
+-M q35 -nographic bios /usr/share/qemu/bios.bin \
+-boot order=c,menu=on \
+-hda 128t.qcow2 \
+-device e1000,netdev=net1,mac=52:52:01:02:03:01 \
+-netdev tap,id=net1,ifname=tap1,script=no,downscript=no
+
+------------------------------------------------------------------------------
+Booting from Hard Disk...
+.
+
+ * CentOS Linux (3.10.0-514.2.2.el7.x86_64) 7 (Core)
+ CentOS Linux (0-rescue-4e73a369e89e466a888c9c77655a1d65) 7 (Core)
+
+
+ Use the ^ and v keys to change the selection.
+ Press 'e' to edit the selected item, or 'c' for a command prompt.
+------------------------------------------------------------------------------
+
+ Select the first option.
+
+
+
+ |-------------------128T Installer-------------------|
+| |
+| Configure Linux Networking |
+| |
+| Before 128T SetUp? |
+| |
+| |
+| < Yes > < No > |
+|----------------------------------------------------|
+
+ Select NO.
+
+
+
+ |----------------------------------------------------|
+| Please select a role for this node: |
+| |----------------------------------------------| |
+| | (*) Router | |
+| | ( ) Conductor | |
+| |----------------------------------------------| |
+| |
+|----------------------------------------------------|
+| < OK > < Back > |
+|----------------------------------------------------| Select
+ Router and OK.
+
+
+
+ |-------------------Conductor Info-------------------|
+| |
+| |----------------------------------------------| |
+| |1st Conductor Address | |
+| |Conductor Address | |
+| |----------------------------------------------| |
+| |
+|----------------------------------------------------|
+| < OK > < Skip > < Back > < Help > |
+|----------------------------------------------------|
+
+ Select SKIP.
+
+
+
+ |----------------------HA Setup----------------------|
+| What kind of Router node is this? |
+| |----------------------------------------------| |
+| |(*) Standalone No HA peer | |
+| |( ) 1st HA Node HA peer is not set up | |
+| |( ) 2nd HA Node HA peer is already set up | |
+| |----------------------------------------------| |
+| |
+| |
+|----------------------------------------------------|
+| < OK > < Back > |
+|----------------------------------------------------| Select
+ Standalone and OK.
+
+
+
+ |---------------------Node Info----------------------|
+| |----------------------------------------------| |
+| | Node Role Router | |
+| | Node Name 128tNode | |
+| | Router Name 128tRouter | |
+| |----------------------------------------------| |
+| |
+|----------------------------------------------------|
+| < OK > < Advanced > < Back > < Help > |
+|----------------------------------------------------|
+
+ Enter a name for the router and node, press OK.
+
+
+
+ |-------------------Password Setup-------------------|
+| Enter the new password for the 128T 'admin' |
+| user: |
+| |----------------------------------------------| |
+| | 128Tadmin | |
+| |----------------------------------------------| |
+| | |
+|----------------------------------------------------|
+| < OK > < Back > |
+|----------------------------------------------------|
+
+ Enter the password for web access: 128Tadmin
+ and confirm the password.
+
+
+
+ |--------------------------Anonymous Data Collection--------------------------|
+| The 128T Networking Platform comes packaged with a software process |
+|("Roadrunner") that is used to proactively monitor the health and liveliness |
+|of the 128T Router and associated components. This watchdog process collects |
+|anonymous information from the router and sends it to 128 Technology for |
+|storage and analysis. This information helps inform 128 Technology about |
+|software usage, to aid in the support and improvement of the 128 Technology |
+|Networking Platform. |
+| |
+|Disabling this feature will prevent the sending of anonymous usage data to |
+|128 Technology. |
+| |
+| |
+| < Accept > < Back > < Disable > |
+|-----------------------------------------------------------------------------|
+
+ Select Accept.
+
+
+
+ |-----128T Statistics Table Creator-----|
+| Created table for metric 760/827 |
+| Created table for metric 770/827 |
+| Created table for metric 780/827 |
+| Created table for metric 790/827 |
+| Created table for metric 800/827 |
+| Created table for metric 810/827 |
+| Created table for metric 820/827 |
+| Finished pre-creating stats tables |
+| Creating tables for audit events |
+| Finished creating audit event tables |
+| Completed in 27.001386642456055 s |
+| Shutting down local Cassandra node |
+|---------------------------------------|
+| < OK > |
+|---------------------------------------|
+
+ Select OK.
+
+
+
+ |--------128T Installer Status----------|
+| |
+| Install SUCCESS |
+| |
+| Start 128T Router |
+| before proceeding to |
+| login prompt? |
+|---------------------------------------|
+| < Yes > < No > |
+|---------------------------------------|
+
+ Select: Yes
+
+
+
+ localhost login: root
+Password:
+
+ The following user accounts and passwords are created during the
+ ISO installation process:
+
+
+ Accounts Created
+
+
+
+
+
+
+ User
+
+ Password
+
+
+
+
+
+ root
+
+ 128tRoutes
+
+
+
+ t128
+
+ 128tRoutes
+
+
+
+
+
+
+
+ GUI login via HTTPS is enabled by default on port 443
+
+ [root@localhost ~]# dhclient enp0s2
+[root@localhost ~]# echo "nameserver 8.8.8.8" >>/etc/resolv.conf
+[root@localhost ~]# yum -y install cloud-init
+[root@localhost ~]# reboot
+
+
+
+ Wait to reboot and press CTR+ a+c to enter in qemu
+ monitor.
+
+ (qemu) quit
+> qemu-img info 128t.qcow2
+image: 128t.qcow2
+file format: qcow2
+virtual size: 128G (137438953472 bytes)
+disk size: 5.4G
+cluster_size: 65536
+Format specific information:
+ compat: 1.1
+ lazy refcounts: false
+ refcount bits: 16
+ corrupt: false
+
+
+
+ Compress the generated 128t.qcow2 image to
+ decrease the size of VNF image:
+
+ qemu-img convert -O qcow2 -c 128t.qcow2 centos_128t_compressed.qcow2
+
+> qemu-img info centos_128t_compressed.qcow2
+image: centos_128t_compressed.qcow2
+file format: qcow2
+virtual size: 128G (137438953472 bytes)
+disk size: 1.2G
+cluster_size: 65536
+Format specific information:
+ compat: 1.1
+ lazy refcounts: false
+ refcount bits: 16
+ corrupt: false
+
+centos_128t_compressed.qcow2 - Resulted image can be used in NFV Access.
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/appendix_3.xml b/doc/book-enea-edge-example-usecases/doc/appendix_3.xml
new file mode 100644
index 0000000..e8bd5ce
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/appendix_3.xml
@@ -0,0 +1,7 @@
+
+
+ How to configure Fortigate VNF (day-0 configuration)
+
+ Please check the README file from Fortigate folder for more
+ details.
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/appendix_4.xml b/doc/book-enea-edge-example-usecases/doc/appendix_4.xml
new file mode 100644
index 0000000..0e207ae
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/appendix_4.xml
@@ -0,0 +1,103 @@
+
+
+ Running Enea Automation Framework and Test Harness
+
+ For more detailed information regarding the Automation Framework and
+ Test Harness please see the .
+
+ The most relevant information from the Automation Framework and Test
+ Harness structure is presented below:
+
+ |---automation_framework
+| |---unittestSuite
+| | |---128tCleanup.json - Use case 1 - clean up - test.
+| | |---128tDeploy.json - Use case 1 - test.
+| | |---128t_FG_SFCCleanup.json - Use case 2 - clean up - test.
+| | |---128t_FG_SFCDeploy.json - Use case 2 - test.
+| | |---config
+| | | |---cust
+ - Folder containing the configuration files used by tests.
+| | |---unittestLoader.py
+| | |---unittestSuite.py
+|---lab_config
+| |---trgt-1
+| | |---ibm_br.json - In-band management definition.
+| | |---lan_br.json - Lan bridge definition.
+| | |---target.json
+ - Target definition - the "address", "deviceId", "name" and \
+ "version" must be updated.
+| | |---sfc_br.json - Service chain bridge definition.
+| | |---vnf_mgmt_br.json - VNF management bridge definition.
+| | |---lan_nic.json - NIC definition.
+|---vnf_config
+| |---128t
+| | |---128tInstance.json - 128T instantiation - used in use case 1.
+| | |---128t.json - 128T onboarding.
+| | |---128tSFCInstance.json - 128T instantiation - used in use case 2.
+| | |---centos_128t_internet_ci.iso - 128T cloud init (day-0) iso image.
+| |---fortigate
+| | |---fg_basic_fw.conf - Fortigate day-0 configuration.
+| | |---fortigateInstance.json - Fortigate instantiantion.
+| | |---fortigate.json - Fortigate onboarding.
+| | |---fortigateLicense.lic
+ - Fortigate license - contact Fortinet to get a VNF image and license file.
+|---vnf_image
+| |---centos_128t_with_ci.qcow2 - Contact 128 Technology to get a \
+ VNF image and its license file.
+| |---fortios.qcow2 - Contact Fortinet to get a VNF image \
+ and its license file.
+
+ Make sure to update the relevant configuration file for your setup.
+ The essential files to consider are the uCPE Device configuration
+ (target.json ), the license for the Fortigate VNF, and
+ the 128T cloud-init iso image matching your network.
+
+ For uCPE Device configuration (target.json )
+ please change the following information, if needed, in the JSON file:
+
+
+
+ address - The IP address of uCPE Device.
+
+
+
+ version - The NFVA version.
+
+
+
+ deviceId - The device ID of uCPE Device.
+
+
+
+ name - The name of uCPE Device.
+
+
+
+
+ Before starting the two usecases detailed in the following appendix,
+ the uCPE Device needs to be added into Enea Edge Management.
+
+
+ To properly set up the Automation Framework and Test Harness please
+ see Installation and Initial Setup in the
+ for more details.
+
+ To run a test:
+
+ > cd automation_framework/unittestSuite/
+> python unittestSuite.py -u admin -p admin -H <uCPEManager IP address> -n \
+<uCPE Device name> -s <Test suite> -d <description>
+
+ The Test suite must be one from any of the
+ following: 128tDeploy.json ,
+ 128tCleanup.json ,
+ 128t_FG_SFCDeploy.json , or
+ 128t_FG_SFCCleanup.json .
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/appendix_5.xml b/doc/book-enea-edge-example-usecases/doc/appendix_5.xml
new file mode 100644
index 0000000..67f38e5
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/appendix_5.xml
@@ -0,0 +1,243 @@
+
+
+ Example Tests Results using the Automation Framework and Test Harness
+
+ In order to run the following example usecases, certain configuration
+ file entries need to be modified according to the network setup that it will
+ be used, for more details see the previous appendix:
+
+
+
+ uCPE Device name: inteld1521-17
+
+
+
+ address: 172.24.8.62
+
+
+
+ version: 2.2.3
+
+
+
+ deviceId: inteld1521-17
+
+
+
+ > cat lab_config/trgt-1/target.json
+{
+ "name": "inteld1521-17",
+ "deviceGroupingTags": " ",
+ "description": "trgt",
+ "address": "172.24.8.62",
+ "port": "830",
+ "username": "root",
+ "password": "",
+ "certificate": null,
+ "passphrase": null,
+ "callHome": "false",
+ "maintMode": "false",
+ "version": "2.2.3",
+ "deviceId": "inteld1521-17"
+} The IP address of Enea Edge Management that will be used in
+ these examples is 172.24.3.92 .
+
+ The FortiGate and 128T VNF images need to be copied into the
+ vnf_image directory. The names should be the same as
+ those described in the previous appendix.
+
+ The FortiGate valid license file needs to be copied into the
+ vnf_config/fortigate/ directory. The name should be the
+ same as that described in the previous appendix.
+
+ The cloud init files that match the network, need to be copied into
+ the vnf_config/fortigate/ and the
+ vnf_config/128t/ directories respectively. The names
+ should be the same as those described in the previous appendix.
+
+
+ Use-case 1: 128T VNF Router Example Use-case
+
+ > cd automation_framework/unittestSuite/
+> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
+-s 128tDeploy.json -d "128T Deployment"
+
+Running 128T Deployment...
+
+test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ...
+2020-08-26 10:10:05,517 - INFO: Wait uCPE device
+2020-08-26 10:10:36,650 - INFO: Status: Connected
+2020-08-26 10:10:36,651 - INFO: Done
+ok
+test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ...
+2020-08-26 10:10:36,686 - INFO: Bind NIC
+2020-08-26 10:10:37,788 - INFO: Done
+ok
+test 003: Creating ibm bridge (__main__.UnittestSuite) ...
+2020-08-26 10:10:37,818 - INFO: New OVS network bridge
+2020-08-26 10:10:58,762 - INFO: Done
+ok
+test 004: Creating VNF Management bridge (__main__.UnittestSuite) ...
+2020-08-26 10:10:58,794 - INFO: New OVS network bridge
+2020-08-26 10:10:58,977 - INFO: Done
+ok
+test 005: Creating LAN bridge and attaching lan interface to the bridge \
+(__main__.UnittestSuite) ...
+2020-08-26 10:10:59,003 - INFO: New OVS network bridge
+2020-08-26 10:10:59,334 - INFO: Done
+ok
+test 006: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ...
+2020-08-26 10:10:59,370 - INFO: Onboard wizard
+2020-08-26 10:13:55,775 - INFO: Done
+ok
+test 007: Instantiate 128T VNF (__main__.UnittestSuite) ...
+2020-08-26 10:13:55,813 - INFO: Instantiate VNF
+2020-08-26 10:14:56,583 - INFO: Done
+ok
+
+----------------------------------------------------------------------
+Ran 7 tests in 291.103s
+
+OK
+
+> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
+-s 128tCleanup.json -d "128T Cleanup"
+
+Running 128T Cleanup...
+
+test 001: Destroying 128T VNF (__main__.UnittestSuite) ...
+2020-08-26 10:15:28,395 - INFO: Destroy VNF
+2020-08-26 10:15:29,452 - INFO: Done
+ok
+test 002: Deleting network bridge LAN (__main__.UnittestSuite) ...
+2020-08-26 10:15:29,493 - INFO: Delete OVS network bridge
+2020-08-26 10:15:29,734 - INFO: Done
+ok
+test 003: Deleting VNF management bridge (__main__.UnittestSuite) ...
+2020-08-26 10:15:29,765 - INFO: Delete OVS network bridge
+2020-08-26 10:15:30,080 - INFO: Done
+ok
+test 004: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ...
+2020-08-26 10:15:30,110 - INFO: Delete OVS network bridge
+2020-08-26 10:15:46,907 - INFO: Done
+ok
+test 005: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ...
+2020-08-26 10:15:46,967 - INFO: Unbind NIC
+2020-08-26 10:15:48,489 - INFO: Done
+ok
+test 006: Offboarding 128t VNF (__main__.UnittestSuite) ...
+2020-08-26 10:15:48,531 - INFO: Offboard VNF
+2020-08-26 10:15:49,171 - INFO: Done
+ok
+
+----------------------------------------------------------------------
+Ran 6 tests in 20.808s
+
+OK
+
+
+
+ Use-case 2: Service Chaining 128T - Fortigate Example
+ Use-case
+
+ > python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
+-s 128t_FG_SFCDeploy.json -d "128T - Fortigate SFC Deployment"
+
+Running 128T - Fortigate SFC Deployment...
+
+test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ...
+2020-08-26 10:17:29,361 - INFO: Wait uCPE device
+2020-08-26 10:18:00,473 - INFO: Status: Connected
+2020-08-26 10:18:00,474 - INFO: Done
+ok
+test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ...
+2020-08-26 10:18:00,634 - INFO: Bind NIC
+2020-08-26 10:18:01,805 - INFO: Done
+ok
+test 003: Creating ibm bridge (__main__.UnittestSuite) ...
+2020-08-26 10:18:01,863 - INFO: New OVS network bridge
+2020-08-26 10:18:30,640 - INFO: Done
+ok
+test 004: Creating VNF Management bridge (__main__.UnittestSuite) ...
+2020-08-26 10:18:30,670 - INFO: New OVS network bridge
+2020-08-26 10:18:30,876 - INFO: Done
+ok
+test 005: Creating LAN bridge and attaching lan interface to the bridge \
+(__main__.UnittestSuite) ...
+2020-08-26 10:18:30,908 - INFO: New OVS network bridge
+2020-08-26 10:18:31,243 - INFO: Done
+ok
+test 006: Creating SFC(service function chaining) bridge (__main__.UnittestSuite) ...
+2020-08-26 10:18:31,273 - INFO: New OVS network bridge
+2020-08-26 10:18:31,416 - INFO: Done
+ok
+test 007: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ...
+2020-08-26 10:18:31,448 - INFO: Onboard wizard
+2020-08-26 10:21:21,569 - INFO: Done
+ok
+test 008: Onboarding Fortigate VNF (wizard API) (__main__.UnittestSuite) ...
+2020-08-26 10:21:21,608 - INFO: Onboard wizard
+2020-08-26 10:21:27,199 - INFO: Done
+ok
+test 009: Instantiate 128T VNF (__main__.UnittestSuite) ...
+2020-08-26 10:21:27,226 - INFO: Instantiate VNF
+2020-08-26 10:22:27,067 - INFO: Done
+ok
+test 010: Instantiate Fortigate VNF (__main__.UnittestSuite) ...
+2020-08-26 10:22:27,121 - INFO: Instantiate VNF
+2020-08-26 10:22:31,310 - INFO: Done
+ok
+
+----------------------------------------------------------------------
+Ran 10 tests in 301.989s
+
+OK
+
+> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
+-s 128t_FG_SFCCleanup.json -d "128T - Fortigate SFC Cleanup"
+
+Running 128T - Fortigate SFC Cleanup...
+
+test 001: Destroying Fortigate VNF (__main__.UnittestSuite) ...
+2020-08-26 10:23:29,308 - INFO: Destroy VNF
+2020-08-26 10:23:30,026 - INFO: Done
+ok
+test 002: Destroying 128T VNF (__main__.UnittestSuite) ...
+2020-08-26 10:23:30,065 - INFO: Destroy VNF
+2020-08-26 10:23:30,917 - INFO: Done
+ok
+test 003: Deleting network bridge SFC (__main__.UnittestSuite) ...
+2020-08-26 10:23:30,960 - INFO: Delete OVS network bridge
+2020-08-26 10:23:31,123 - INFO: Done
+ok
+test 004: Deleting network bridge LAN (__main__.UnittestSuite) ...
+2020-08-26 10:23:31,156 - INFO: Delete OVS network bridge
+2020-08-26 10:23:31,381 - INFO: Done
+ok
+test 005: Deleting VNF management bridge (__main__.UnittestSuite) ...
+2020-08-26 10:23:31,412 - INFO: Delete OVS network bridge
+2020-08-26 10:23:31,596 - INFO: Done
+ok
+test 006: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ...
+2020-08-26 10:23:31,621 - INFO: Delete OVS network bridge
+2020-08-26 10:23:47,980 - INFO: Done
+ok
+test 007: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ...
+2020-08-26 10:23:48,019 - INFO: Unbind NIC
+2020-08-26 10:23:49,547 - INFO: Done
+ok
+test 008: Offboarding 128t VNF (__main__.UnittestSuite) ...
+2020-08-26 10:23:49,575 - INFO: Offboard VNF
+2020-08-26 10:23:50,252 - INFO: Done
+ok
+test 009: Offboarding Fortigate VNF (__main__.UnittestSuite) ...
+2020-08-26 10:23:50,295 - INFO: Offboard VNF
+2020-08-26 10:23:50,589 - INFO: Done
+ok
+
+----------------------------------------------------------------------
+Ran 9 tests in 21.326s
+
+OK
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/book.xml b/doc/book-enea-edge-example-usecases/doc/book.xml
new file mode 100644
index 0000000..2ffbefe
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/book.xml
@@ -0,0 +1,44 @@
+
+
+]>
+
+ Enea Edge Example Use-cases
+
+ Release Version
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/clav_vnf_examples.xml b/doc/book-enea-edge-example-usecases/doc/clav_vnf_examples.xml
new file mode 100644
index 0000000..8895c23
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/clav_vnf_examples.xml
@@ -0,0 +1,396 @@
+
+
+ Clavister VNF Example Use-cases
+
+ The Clavister VNF is a telco-ready, carrier-grade virtual next
+ generation firewall.
+
+
+ Clavister VNF using an Open vSwitch Bridge
+
+ In this use-case, uCPE device 1 runs the Clavister VNF, while uCPE
+ device 2 runs two Enea Test VNFs with iPerf client and server
+ applications. The uCPE devices are connected using OVS-DPDK
+ bridges.
+
+
+ Prerequisites
+
+ Two uCPE devices will be required for this setup. The system
+ requirements for each uCPE device are:
+
+
+
+ 1 Network Interface
+
+
+
+ 2 GB of RAM memory
+
+
+
+ The following files are needed for this example use-case:
+
+
+
+ Enea Test VNF image. Please contact Enea to get this image.
+
+
+
+ Clavister VNF image. Please contact Clavister to get this
+ image.
+
+
+ VNF Configuration files. These files are provided with your Enea
+ Edge release:
+
+
+ clavister-cloudinit.conf .
+ enea-vnf-iperf-client.conf .
+ enea-vnf-iperf-server.conf .
+
+
+
+
+
+
+ Use-case Setup
+
+ In this use-case, uCPE device 1 runs the Clavister VNF, while uCPE
+ device 2 runs two Enea Test VNFs with iPerf client and server
+ applications. The uCPE devices are connected using OVS-DPDK
+ bridges.
+
+
+ Clavister VNF using an Open vSwitch bridge
+
+
+
+
+
+
+
+
+
+ When connecting, the uCPE devices can use a back-to-back or a VPN connection.
+ An appropriate interface with the required capabilities needs to be chosen for
+ this purpose.
+
+
+ Network Configuration:
+
+
+
+ Select uCPE device 1, access Configuration ,
+ add the network interface that will be used and configure it for
+ DPDK.
+
+
+
+ Create an OVS bridge and attach the DPDK network
+ interface.
+
+
+
+ Repeat the steps above for uCPE device 2.
+
+
+
+ Onboarding the VNFs:
+
+
+
+ Onboard the Clavister VNF by filling the required fields with
+ the following values:
+
+
+
+ VM Image File : Provide
+ the path to the Clavister VNF qcow2 image
+
+
+
+ Memory in MB : 1024
+
+
+
+ Num of CPUs : 4
+
+
+
+ Storage in GB : 20
+
+
+
+ Interfaces : Add 2
+ interfaces
+
+
+
+ Cloud-init Datasource :
+ ConfigDrive
+
+
+
+ Cloud-init Disk Type :
+ disk
+
+
+
+
+
+ Onboard the Enea Test VNF by filling the required fields with
+ the following values:
+
+ VM Image File : Provide
+ the path to the Enea Test VNF qcow2 image
+
+
+
+ Memory in MB :
+ 2048
+
+
+
+ Num of CPUs : 2
+
+
+
+ Storage in GB :
+ 10
+
+
+
+ Interfaces : Add 1
+ interface
+
+
+
+ Cloud-init Datasource :
+ NoCloud
+
+
+
+ Cloud-init Disk Type :
+ disk
+
+
+
+
+
+ Instantiating the VNFs:
+
+
+
+ Instantiate the Clavister VNF on uCPE device 1 using the
+ required fields below:
+
+
+
+ Name : clavister
+
+
+
+ VNF Type : Select
+ Clavister VNF
+
+
+
+ uCPE Device : Select
+ uCPE device 1
+
+
+
+ Cloud Init File :
+ Provide the path to the Clavister cloud-init file.
+
+
+
+ Interfaces : Set the
+ interface type to DPDK and select the OVS
+ bridge created above, for both interfaces.
+
+
+
+
+
+ Instantiate the Enea iPerf server VNF on uCPE device 2 by
+ filling the required fields with the values below:
+
+
+
+ Name :
+ iperf_server
+
+
+
+ VNF Type : Select Enea
+ Test VNF
+
+
+
+ uCPE Device : Select
+ uCPE device 2
+
+
+
+ Cloud Init File :
+ Provide the path to the Enea VNF IPerf server cloud-init
+ file.
+
+
+
+ Interfaces : Set the
+ interface type to DPDK and select the OVS
+ bridge created above.
+
+
+
+
+
+ Instantiate the Enea iPerf client VNF on uCPE device 2 by
+ filling the required fields with the values below:
+
+
+
+ Name :
+ iperf_client
+
+
+
+ VNF Type : Select Enea
+ Test VNF
+
+
+
+ uCPE Device : Select
+ uCPE device 2
+
+
+
+ Cloud Init File :
+ Provide the path to the Enea VNF iPerf client cloud-init
+ file.
+
+
+
+ Interfaces : Set the
+ interface type to DPDK and select the OVS
+ bridge created above.
+
+
+
+
+
+
+
+ Testing the Use-case
+
+ SSH to uCPE device 2 (Username: root) and connect to the IPerf
+ client VNF console:
+
+ virsh list
+virsh console <id of iperf client>
+
+ In order to check that traffic is forwarded between the VNFs, run
+ the following:
+
+ # qemux86-64 login: root
+root@qemux86-64:~# iperf3 -c 192.168.10.10
+
+
+
+
+ Clavister VNF using SR-IOV
+
+
+ Prerequisites
+
+ Two uCPE devices will be required for this setup. The system
+ requirements for each uCPE device are:
+
+
+
+ 1 Network Interface
+
+
+
+ 2 GB of RAM memory
+
+
+
+ The following files are needed for this example use-case:
+
+
+
+ Enea Test VNF image. Please contact Enea to get this image.
+
+
+
+ Clavister VNF image. Please contact Clavister to get this
+ image.
+
+
+ VNF Configuration files. These files are provided with your Enea
+ Edge release:
+
+ clavister-cloudinit.conf .
+ enea-vnf-iperf-client.conf .
+ enea-vnf-iperf-server.conf .
+
+
+
+
+
+
+ Use-case Setup
+
+ The following use-case is essentially the same as the one detailed
+ above, in this scenario however, the uCPE devices are connected using
+ SR-IOV, with two virtual functions.
+
+
+ Clavister VNF using SR-IOV
+
+
+
+
+
+
+
+
+ Network Configuration:
+
+
+
+ Select uCPE device 1, access Configuration ,
+ add the network interface that will be used and configure it for
+ SR-IOV. For sriov-mode select adapter-pool and for
+ sriov-num-vfs select "2".
+
+
+
+ Repeat the step above for uCPE device 2.
+
+
+
+ Onboarding the VNFs:
+
+ See the onboarding parameters in the use-case above.
+
+ Instantiating the VNFs:
+
+ Use the same instantiation parameters as above, but select
+ interface type SrIovAdapterPool instead.
+
+
+
+ Testing the Use-case
+
+ Use the same test instructions as detailed in the use-case
+ above.
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/enea_test_vnf_examples.xml b/doc/book-enea-edge-example-usecases/doc/enea_test_vnf_examples.xml
new file mode 100644
index 0000000..bee5a63
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/enea_test_vnf_examples.xml
@@ -0,0 +1,308 @@
+
+
+ Enea Test VNF Example Use-cases
+
+ The Enea Test VNF is a simple Enea Linux based VM, which can be used
+ for various testing purposes, by using basic DPDK applications (e.g.
+ testpmd) as well as non-DPDK tools (e.g. iPerf3). For more information about
+ the Testpmd application please see the Testpmd Application User
+ Guide .
+
+
+ Prerequisites
+
+ Two uCPE devices will be required for this setup. The system
+ requirements for each uCPE device are:
+
+
+
+ 2 Network Interfaces. One for Enea Edge Management and one for data
+ traffic.
+
+
+
+ 2 GB of RAM memory
+
+
+
+ The following files are needed for this example use case:
+
+
+
+ VNF image: Enea Test VNF. Please contact Enea to get this
+ image.
+
+
+ VNF Configuration files. These files are provided with your Enea
+ Edge release:
+
+
+ enea-vnf-testpmd-fwd.conf .
+
+
+
+ enea-vnf-testpmd-term.conf .
+
+
+
+
+
+ TestPMD VNF
+
+ In this use-case, uCPE device 1 runs the pktgen DPDK application to
+ generate traffic and uCPE device 2 runs two Enea Test VNFs. One VNF runs
+ the TestPMD DPDK application forwarding traffic, and the other runs the
+ TestPMD in order to terminate traffic.
+
+
+ TestPMD VNF Overview
+
+
+
+
+
+
+
+
+
+ Use-case Setup
+
+ Network Configuration:
+
+
+
+ Select uCPE device 1, access Configuration ,
+ add the network interface that will be used and configure it for
+ DPDK. Note the PCI address of the interface, it will be used later
+ to run the pktgen application.
+
+
+
+ Select uCPE device 2, access Configuration ,
+ add the network interface that will be used and configure it for
+ DPDK.
+
+
+
+ Create an OVS bridge on uCPE device 2 and attach the DPDK
+ interface.
+
+
+
+ Onboarding the VNF:
+
+ Onboard the Enea Test VNF by filling the required fields with the
+ following values:
+
+
+
+ VM Image File : Provide the
+ path to the Enea Test VNF qcow2 image.
+
+
+
+ Memory in MB : 2048
+
+
+
+ Num of CPUs : 2
+
+
+
+ Storage in GB : 10
+
+
+
+ Interfaces : Add 1
+ interface.
+
+
+
+ Cloud-init Datasource :
+ NoCloud
+
+
+
+ Cloud-init Disk Type :
+ disk
+
+
+
+ Instantiating the VNFs:
+
+
+
+ Instantiate the Enea Edge TestPMD forwarding VNF on uCPE
+ Device 2 by filling the required fields with the following
+ values:
+
+
+
+ Name : testpmd_fwd
+
+
+
+ VNF Type : Select Enea
+ Test VNF.
+
+
+
+ uCPE Device : Select uCPE
+ device 2.
+
+
+
+ Cloud Init File : Provide
+ the path to the Enea VNF TestPMD forwarding cloud-init
+ file.
+
+
+
+ Interfaces : Set the
+ interface type to DPDK and select the OVS
+ bridge created above.
+
+
+
+
+
+ Instantiate the Enea Edge TestPMD termination VNF on
+ uCPE Device 2 by filling the required fields with the following
+ values:
+
+
+
+ Name : testpmd_term
+
+
+
+ VNF Type : Select Enea
+ Test VNF.
+
+
+
+ uCPE Device : Select uCPE
+ device 2.
+
+
+
+ Cloud Init File : Provide
+ the path to the Enea VNF TestPMD termination cloud-init
+ file.
+
+
+
+ Interfaces : Set the
+ interface type to DPDK and select the OVS
+ bridge created above.
+
+
+
+
+
+ Creating OVS flow rules:
+
+ Select uCPE device 2, access Configuration ,
+ open the OVS bridge and add two flow rules:
+
+
+
+ Source: DPDK interface, Target:
+ testpmd_fwd .
+
+
+
+ Source: testpmd_fwd , Target:
+ testpmd_term .
+
+
+ The flow rules can be described using either the Enea Edge
+ Management interface or the configuration files.
+
+
+
+
+
+
+ Testing the Use-case
+
+
+
+ SSH to uCPE device 1 (Username: root) and start the pktgen
+ application:
+
+ cd /usr/share/apps/pktgen/
+./pktgen -c 0x7 -n 4 --proc-type auto --socket-mem 256 -w 0000:01:00.0 -- \
+ -P -m "[1:2].0"
+
+Pktgen:/> start 0
+
+
+ Replace 0000:01:00.0 with the actual PCI address of the
+ network interface used on uCPE device 1.
+
+
+
+
+ SSH to uCPE device 2 and connect to the TestPMD forwarding VNF
+ console:
+
+ virsh list
+virsh console <id of testpmd fwd>
+
+
+
+ Check the TestPMD traffic forwarding statistics:
+
+ # qemux86-64 login: root
+tail -f /var/log/testpmd-out
+
+
+
+
+
+ TestPMD VNF using PCI passthrough
+
+ In this use case, uCPE device 1 will run the Pktgen and uCPE
+ device 2 will run the TestPMD VNF. Both will be using PCI
+ passthrough:
+
+
+
+ Make sure that neither uCPE device 1 nor uCPE device 2 have
+ any configured host interfaces by selcting uCPE device :
+ Configuration ->
+ OpenVSwitch -> Host
+ Interfaces .
+
+
+
+ On uCPE device 1 start the Pktgen VNF. Select
+ PciPassthrough as the Interface type.
+
+ From the drop-down list, select the PCI interface
+ corresponding to the NIC which is connected to uCPE device 2:
+
+
+
+ On uCPE device 2, start the TestPmdForwarder VNF. Select
+ "PciPassthrough" as the Interface type. From the drop-down list,
+ select the PCI interface corresponding to the NIC which is connected
+ to uCPE device 1:
+
+
+
+ To check that traffic is being forwarded from uCPE device 2,
+ SSH to the uCPE device and connect to the VNFs console:
+
+ Right click on uCPE device 2 and select SSH.
+Run: virsh list
+Run: virsh console [VM NAME]
+Run: tail -f /opt/testpmd-out
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/forti_vnf_examples.xml b/doc/book-enea-edge-example-usecases/doc/forti_vnf_examples.xml
new file mode 100644
index 0000000..bb38140
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/forti_vnf_examples.xml
@@ -0,0 +1,627 @@
+
+
+ FortiGate VNF Example Use-cases
+
+ FortiGate virtual appliances feature all of the security and
+ networking services common to traditional hardware-based FortiGate
+ appliances. The virtual appliances can be integrated in Firewall or SD-WAN
+ solution development.
+
+
+ FortiGate VNF as a Firewall
+
+ Enea provides an example of a simple basic firewall configuration
+ for the FortiGate VNF. FortiGate In-Band Management is a feature used for
+ running FortiGate Management traffic over WAN.
+
+ Instructions on how to alter the default configuration are provided
+ in section FortiGate VNF Web Management in the
+
+ Manual.
+
+
+ Prerequisites
+
+ System requirements for the uCPE device:
+
+
+
+ 4 x Network Interfaces
+
+
+
+ 4 cores
+
+
+
+ 4 GB of RAM memory
+
+
+
+ The following file(s) are needed for this example use-case:
+
+
+
+ FortiGate VNF image. Please contact Fortinet to get a VNF
+ image and its license file.
+
+
+
+ VNF Configuration file(s), provided with your Enea Edge
+ release: fortigate-basic-fw.conf .
+
+
+
+
+
+ Use-case Setup
+
+
+ Fortigate VNF as a Firewall
+
+
+
+
+
+
+
+
+ Network Configuration :
+
+ Since the firewall uses three External Network Interfaces, three
+ bridges need to be configured. Each bridge provides the ability to
+ connect a physical network interface to the virtual network interface of
+ a VM.
+
+ Setup of the uCPE device:
+
+
+
+ Connect WAN to the Lab Network.
+
+
+
+ Connect LAN1 to the Test Machine.
+
+
+
+ Leave LAN2 unconnected.
+
+
+
+ Connect ETH0 to the Lab Network (for Enea Edge Management
+ communications).
+
+
+
+ Select the uCPE device, access
+ Configuration and bind the three physical network
+ interfaces to DPDK.
+
+
+
+ Create three OVS bridges, one for each DPDK network interface
+ (WAN, LAN1 and LAN2).
+
+ Alternatively, the firewall can be setup to use bridges as
+ connection points for the FortiGate VNF, by replacing the OVS-DPDK
+ bridges with SR-IOV connection points.
+
+ Please note that while previously three physical interfaces
+ were presumed necessary for VNF connection, in the case of a
+ firewall setup only two physical interfaces are required for the
+ data path (one for WAN and one for LAN). Only two interfaces will be
+ configured as DPDK, with two bridges created, one for each type of
+ connection.
+
+
+ At VNF instantiation instead of assigning distinct bridges
+ for each LAN interface, only one will be used for both LAN1 and
+ LAN2, with no changes in WAN interface configuration.
+
+
+
+
+ Onboarding the VNF:
+
+ Onboard the FortiGate VNF by filling the required fields with the
+ following values:
+
+
+
+ VM Image File : Provide the
+ path to the FortiGate VNF qcow2 image.
+
+
+
+ Memory in MB : 1024
+
+
+
+ Num of CPUs : 1
+
+
+
+ Storage in GB : 20
+
+
+
+ Interfaces : Add 3 interfaces
+ (wan, lan1 and lan2).
+
+
+
+ Cloud-init Datasource :
+ ConfigDrive
+
+
+
+ Cloud-init Disk Type :
+ cdrom
+
+
+
+ Cloud-init content file : Add
+ a file entry where Path: license.
+
+
+
+ Instantiating the VNF:
+
+ Instantiate the FortiGate VNF by filling the required fields with
+ the following values:
+
+
+
+ Name : Name of the VM which
+ will be created on the uCPE device.
+
+
+
+ VNF Type : Name of the
+ onboarded VNF.
+
+
+
+ uCPE Device : Select the uCPE
+ device where the VNF will be instantiated.
+
+
+
+ License file : The FortiGate
+ license file provided by Fortinet.
+
+
+
+ Configuration file : The
+ Firewall example configuration file provided by Enea
+ (fortigate-basic-fw.conf ).
+
+
+
+ Port1 - WAN : Set the
+ External Interface type to
+ DPDK and connect it to the
+ wan_br ovs bridge.
+
+
+
+ Port2 - LAN1 : Set the
+ Incoming Interface type to
+ DPDK and connect it to the
+ lan1_br ovs bridge.
+
+
+
+ Port3 - LAN2 : Set the
+ Outgoing Interface type to
+ DPDK and connect it to the
+ lan2_br ovs bridge.
+
+
+ The names of the ports used during instantiation need to be
+ the same as the ones described above, as the same names will be
+ used in the configuration files provided for this example
+ use-case.
+
+
+
+
+
+
+ Testing the Use-case
+
+ Connect the Test Machine on the LAN interface and access the
+ internet from the Test Machine to use the firewall on the uCPE
+ device.
+
+
+ The connected Test Machine can be a laptop or a uCPE device. It
+ must have one interface configured to get a dynamic IP from a DHCP
+ server. The dhclient <interface> command can
+ be used to request an IP address. The received IP must be in the
+ 172.16.1.2 - 172.16.1.255 range.
+
+
+ The FortiGate VNF management interface is accessible through the
+ WAN interface. The WAN IP address can be used from a web browser on the
+ Lab Machine to access the FortiGate VNF Management Web UI. See section
+ FortiGate VNF web management in the
+
+ Manual for more information.
+
+
+
+
+ FortiGate VNF as an SD-WAN or a VPN
+
+ SD-WAN decouples the network from the management plane, detaching
+ traffic management and monitoring functions from hardware. Most forms of
+ SD-WAN technology create a virtual overlay that is transport-agnostic,
+ i.e. it abstracts underlying private or public WAN connections.
+
+ For deployment, the user plugs in WAN links into the device, which
+ automatically configures itself with the network.
+
+ Example SD-WAN configurations for the FortiGate VNF are provided by
+ Enea.
+
+
+ Prerequisites
+
+ Two uCPE devices will be needed for this setup. The system
+ requirements for each uCPE device are:
+
+
+
+ 4 x Network Interfaces
+
+
+
+ 4 cores
+
+
+
+ 4 GB of RAM memory
+
+
+
+ The following files are needed for this example use-case:
+
+
+
+ FortiGate VNF image. Please contact Fortinet to get a VNF
+ image and its license file.
+
+
+
+ VNF Configuration file(s), provided with your Enea Edge
+ release: fortigate-sdwan<x>.conf .
+
+
+
+
+
+ Use-case Setup
+
+
+ Fortigate VNF as an SD-WAN or a VPN
+
+
+
+
+
+
+
+
+
+ When connecting, the uCPE devices can use a back-to-back or a
+ VPN connection. An appropriate interface with the required
+ capabilities needs to be chosen for this purpose.
+
+
+ Network Configuration:
+
+ Since the SD-WAN VNF uses three External Network Interfaces, three
+ bridges need to be configured. Each bridge provides the ability to
+ connect a physical network interface to the VM's virtual network
+ interface.
+
+ Each VNF instance will have a virtual interface for VNF
+ management, for the WAN network and for LAN communication.
+
+ Setup of an Intel Whitebox uCPE
+ device :
+
+
+
+ Connect the VNF Management interfaces to
+ the Lab Network for VNF management access.
+
+
+
+ Connect the WAN interfaces back to back or
+ via VPN.
+
+
+
+ Connect the LAN interfaces to the Test
+ Machine.
+
+
+
+ Connect the ETH0 interfaces to the Lab
+ Network (for Enea Edge Management communications).
+
+
+
+ Select uCPE Device 1, access Configuration
+ and bind the three physical network interfaces to the DPDK.
+
+
+
+ Create three OVS bridges, one for each DPDK network interface
+ (VNF management, WAN and LAN).
+
+
+
+ Repeat the steps above for uCPE device 2.
+
+
+
+ Onboarding the VNF :
+
+ Onboard the FortiGate VNF by filling the required fields with the
+ following values:
+
+
+
+ VM Image File : Provide the
+ path to the FortiGate VNF qcow2 image.
+
+
+
+ Memory in MB : 1024
+
+
+
+ Num of CPUs : 1
+
+
+
+ Storage in GB : 20
+
+
+
+ Interfaces : Add 3 interfaces
+ in the same order as listed below:
+
+
+
+ vnfmgr : to connect it to
+ the vnfmgmt_br bridge.
+
+
+
+ wan: to connect it to the
+ wan_br bridge.
+
+
+
+ lan: to connect it to the
+ lan_br bridge.
+
+
+
+
+
+ Cloud-init Datasource :
+ ConfigDrive
+
+
+
+ Cloud-init Disk Type :
+ cdrom
+
+
+
+ Cloud-init content file : Add
+ a file entry where Path: license.
+
+
+
+
+ The order of the interfaces that need to be added must be
+ exactly as listed above or else onboarding and in turn instantiation
+ will fail.
+
+
+ Instantiating the FortiGate
+ VNF :
+
+ Instantiate the FortiGate VNF by filling the required fields with
+ the following values:
+
+
+
+ Name : Name of the VM which
+ will be created on the uCPE device.
+
+
+
+ VNF Type : Name of the
+ onboarded VNF.
+
+
+
+ uCPE Device : Select the uCPE
+ device where the VNF will be instantiated.
+
+
+
+ License file : The FortiGate
+ license file provided by Fortinet.
+
+
+
+ Configuration file : The
+ SD-WAN example configuration files provided by Enea:
+ fortigate-sdwan1.conf for the FortiGate VNF on
+ uCPE device 1 and fortigate-sdwan2.conf for the
+ FortiGate VNF on uCPE device 2.
+
+
+
+ Port1 - VNF Mgr : Set the type
+ to DPDK and connect it to the
+ vnfmgmt_br bridge.
+
+
+
+ Port2 - WAN : Set the type to
+ DPDK and connect it to the
+ wan_br bridge.
+
+
+
+ Port3 - LAN : Set the type to
+ DPDK and connect it to the
+ lan_br bridge.
+
+
+
+ Instantiate the FortiGate VNF on uCPE device 1 using the
+ sdwan1 example configuration file.
+
+ To complete the branch-to-branch setup, configure uCPE
+ device 2 in the same way as uCPE device
+ 1 .
+
+
+ The names of the ports used during instantiation need to be the
+ same as the ones described above, as the same names will be used in
+ the configuration files provided for this example use-case.
+
+
+
+
+ Testing the Use-case
+
+ Once the full SD-WAN setup is in place a VPN connection needs to
+ be established between the two uCPE devices. The Test Machines can be
+ connected to the LAN interface on each uCPE device.
+
+
+ The connected Test Machine can be a laptop or a uCPE device that
+ has one interface configured to get a dynamic IP from a DHCP server.
+ The dhclient <interface> command can be used
+ to request an IP address.The received IP must be in the 172.16.1.2 -
+ 172.16.1.255 range for Test Machine-1 and in the 172.16.2.2 -
+ 172.16.2.255 range for Test Machine-2.
+
+
+ The Test Machine connected to uCPE device 1
+ should be able to ping the Test Machine connected to uCPE
+ device 2 in this setup, over the WAN connection. The FortiGate
+ VNF management interface can be accessed from a web browser on the Lab
+ Machine. For more details please see FortiGate VNF Web Management, .
+
+
+ In this SD-WAN VPN setup example, bridges were used as
+ connection points for the FortiGate VNF. It is possible to replace
+ OVS-DPDK bridges with SR-IOV connection points.
+
+
+
+
+
+ FortiGate VNF Web Management
+
+ In order to check the IP address assigned to the FortiGate VNF you
+ need to connect to the FortiGate CLI.
+
+
+
+ SSH to the uCPE Device (Username: root) and connect to the
+ FortiGate VNF console:
+
+ virsh list
+virsh console <id of FortiGate VNF>
+
+
+
+ To access the FortiGate CLI, use admin as the
+ user, leaving the password blank/empty, and press enter.
+
+ Use the CLI command get system interface to
+ get the dynamic interfaces configuration.
+
+
+
+ Use the IP address assigned for the management interface in the
+ web browser (https://<IP> ), to access the
+ FortiGate VNF Web Management Interface. Use the same credentials as
+ before to login.
+
+
+
+ Browse through the configuration and perform changes according
+ to your setup:
+
+
+ The FortiGate VNF Web Management Interface
+
+
+
+
+
+
+
+
+
+
+ Optionally, alter the default FortiGate example configuration
+ provided by Enea, through the following steps:
+
+
+
+ Deploy the FortiGate Firewall in its default
+ settings.
+
+ Maybe more info about how to do it should be added
+ here.
+
+
+
+ Connect to the FortiGate VNF Web Management interface with a
+ web browser.
+
+
+
+ Modify the FortiGate configuration in the FortiGate VNF Web
+ Management as needed.
+
+
+
+ Store the updated configuration in a file, so it may be used
+ at the next FortiGate VNF instantiation.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/images/fortinet_interface.png b/doc/book-enea-edge-example-usecases/doc/images/fortinet_interface.png
new file mode 100755
index 0000000..9452264
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/fortinet_interface.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/trgt.png b/doc/book-enea-edge-example-usecases/doc/images/trgt.png
new file mode 100644
index 0000000..2977524
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/trgt.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/trgt.svg b/doc/book-enea-edge-example-usecases/doc/images/trgt.svg
new file mode 100755
index 0000000..86f4d12
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/images/trgt.svg
@@ -0,0 +1,1231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ image/svg+xml
+
+
+
+
+
+
+
+
+
+
+
+ Guest
+
+
+ OVS Bridge
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Legend: - Connection via cloud/internet: - Back to Back: BTB - Flow rules:
+
+
+
+
+
+
+ uCPE Device
+
+
+
+
+ Internet
+
+
+
+ Enea Edge Management
+
+
+
+ Web Interface (128T) https://<IP>:60001
+
+
+
+ ibm_br
+
+
+
+
+ lan_br
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Test Machine
+
+
+
+
+
+
+ vnf_mgmt_br
+
+
+
+
+
+
+ 128T
+
+
+
+ LAN
+ WAN
+ MGMT
+
+
+
+
+
+ .1
+ .2
+ .1
+ .2
+ 192.168.64.0/24
+ 10.0.0.0/24
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/images/trgt_servicechain.png b/doc/book-enea-edge-example-usecases/doc/images/trgt_servicechain.png
new file mode 100644
index 0000000..7cb5af0
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/trgt_servicechain.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/trgt_servicechain.svg b/doc/book-enea-edge-example-usecases/doc/images/trgt_servicechain.svg
new file mode 100755
index 0000000..4bd6d85
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/images/trgt_servicechain.svg
@@ -0,0 +1,1402 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ image/svg+xml
+
+
+
+
+
+
+
+
+
+
+
+ Guest
+
+
+ OVS Bridge
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Legend: - Connection via cloud/internet: - Back to Back: BTB - Flow rules:
+
+
+
+
+
+
+
+
+
+
+ uCPE Device
+
+
+
+ Internet
+
+
+ Enea Edge Management
+
+
+
+
+
+ ibm_br
+
+
+
+ lsfc_br
+
+
+
+ 128T
+
+ LAN
+ WAN
+ MGMT
+
+
+
+
+ .2
+ .1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Test Machine
+
+ .2
+
+ 192.168.64.0/24
+
+
+
+ vnf_mgmt_br
+
+ .1
+ 10.0.0.0/24
+
+
+
+ lan_br
+
+
+
+ Fortigate
+
+
+ LAN
+ WAN
+ MGMT
+
+ .3
+ .1
+ 172.16.1.0/24
+ .2
+
+
+
+
+
+
+
+ Web Interface (128T) https://<IP>:60001 (Fortigate) https://<IP>:60002
+
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_bridge.png b/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_bridge.png
new file mode 100644
index 0000000..97492ca
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_bridge.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_bridge.svg b/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_bridge.svg
new file mode 100755
index 0000000..2890881
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_bridge.svg
@@ -0,0 +1,966 @@
+
+
+
+
+
+ image/svg+xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Legend: - Connection via cloud/internet: - VPN/Back to Back (BTB): - Flow rules:
+
+
+
+
+
+
+
+
+
+
+
+
+ Enea Edge Management
+
+
+
+
+
+
+
+
+
+ Internet
+
+
+
+
+
+
+
+
+
+
+
+
+
+ uCPE Device 2
+
+
+ Iperf client
+
+
+ Iperf server
+
+
+
+
+ 192.168.20.20
+ 192.168.10.10
+
+
+
+ bridge
+
+ dpdk
+
+
+
+
+
+
+
+
+
+
+
+ uCPE Device 1
+
+
+
+
+
+
+
+ Clavister
+ 192.168.10.1
+ 192.168.20.1
+
+
+
+ bridge
+
+ dpdk
+
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_sriov.png b/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_sriov.png
new file mode 100644
index 0000000..2c9ae6b
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_sriov.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_sriov.svg b/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_sriov.svg
new file mode 100755
index 0000000..a33c619
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/images/uc_clavister_sriov.svg
@@ -0,0 +1,1152 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ image/svg+xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Legend: - Connection via cloud/internet: - VPN/Back to Back (BTB): - Flow rules:
+
+
+
+
+
+
+
+
+
+
+
+
+ Internet
+
+
+
+
+
+
+
+
+ Enea Edge Management
+
+
+
+
+
+
+
+
+
+
+
+
+ uCPE Device2
+
+
+
+
+
+
+
+
+
+
+ Iperf server
+ 192.168.10.10
+
+
+
+
+
+ SR-IOV
+
+ Iperf client
+ 192.168.20.20
+
+
+
+ uCPE Device1
+
+
+ SR-IOV
+
+
+
+
+
+
+
+
+
+
+ Clavister
+ 192.168.10.1
+ 192.168.20.1
+
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_enea_test_vnf.png b/doc/book-enea-edge-example-usecases/doc/images/uc_enea_test_vnf.png
new file mode 100644
index 0000000..be97bc0
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/uc_enea_test_vnf.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_enea_test_vnf.svg b/doc/book-enea-edge-example-usecases/doc/images/uc_enea_test_vnf.svg
new file mode 100755
index 0000000..fc71729
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/images/uc_enea_test_vnf.svg
@@ -0,0 +1,1002 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ image/svg+xml
+
+
+
+
+
+
+
+
+
+ Guest
+
+
+
+
+
+ Enea Edge Management
+
+
+
+
+
+
+
+
+
+
+
+
+ Internet
+
+
+ BTB
+
+
+
+ uCPE Device 1
+
+
+
+
+
+
+ pktgen_dpdk
+
+
+
+
+
+
+
+
+
+
+
+
+ uCPE Device 2
+
+
+ testpmd_fwd
+
+
+ testpmd_term
+
+
+
+
+
+
+
+
+
+ bridge
+ dpdk
+
+
+
+
+
+
+
+
+ Legend: - Connection via cloud/internet: - Back to Back: BTB - Flow rules:
+
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_fw.png b/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_fw.png
new file mode 100644
index 0000000..f8ae39a
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_fw.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_fw.svg b/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_fw.svg
new file mode 100755
index 0000000..160c8b0
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_fw.svg
@@ -0,0 +1,940 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ image/svg+xml
+
+
+
+
+
+
+
+
+
+
+
+ Test Machine
+
+
+
+
+
+
+
+
+ dpdk
+
+
+ wan_br
+
+
+
+
+ dpdk
+
+
+ lan1_br
+
+
+
+
+ dpdk
+
+
+ lan2_br
+
+
+
+ Fortigate
+
+
+ uCPE Device
+
+
+
+
+
+
+
+ Legend: - Connection via cloud/internet:
+
+
+
+
+
+
+
+
+
+ Test
+
+
+
+
+
+
+
+ Internet
+
+
+
+ Enea Edge Management
+
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_sdwan.png b/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_sdwan.png
new file mode 100644
index 0000000..b71b02e
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_sdwan.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_sdwan.svg b/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_sdwan.svg
new file mode 100755
index 0000000..3de54dd
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/images/uc_fortigate_sdwan.svg
@@ -0,0 +1,1449 @@
+
+
+
+
+
+ image/svg+xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Cloud
+
+
+
+ uCPE Device
+
+
+ uCPE Manager
+
+
+
+ Internet
+
+
+
+ VNF
+
+
+
+ Guest
+
+
+
+ OVS Bridge
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Internet
+
+
+
+ Enea Edge Management
+
+
+
+
+ uCPE Device 2
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ vnfmgmt_br
+
+ dpdk
+
+
+
+ Fortigate
+
+
+
+
+ wan_br
+ dpdk
+
+
+ dpdk
+
+
+ lan_br
+
+
+
+
+
+
+
+
+
+
+
+
+ Test Machine
+
+
+
+
+
+
+ Test Machine
+
+
+
+
+
+
+
+
+
+
+
+ uCPE Device 1
+
+
+
+
+
+
+
+
+
+ wan_br
+
+ dpdk
+
+
+
+
+ lan_br
+
+ dpdk
+
+
+
+
+
+ vnfmgmt_br
+
+ dpdk
+
+ Fortigate
+
+
+
+
+
+
+
+ Legend: - Connection via cloud/internet: - VPN/BTB:
+
+
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_vnf_chaining.png b/doc/book-enea-edge-example-usecases/doc/images/uc_vnf_chaining.png
new file mode 100644
index 0000000..6aaf4c0
Binary files /dev/null and b/doc/book-enea-edge-example-usecases/doc/images/uc_vnf_chaining.png differ
diff --git a/doc/book-enea-edge-example-usecases/doc/images/uc_vnf_chaining.svg b/doc/book-enea-edge-example-usecases/doc/images/uc_vnf_chaining.svg
new file mode 100755
index 0000000..2bb15af
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/images/uc_vnf_chaining.svg
@@ -0,0 +1,1186 @@
+
+
+
+
+
+ image/svg+xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Cloud
+
+
+
+ uCPE Device
+
+
+ uCPE Manager
+
+
+
+ Internet
+
+
+
+ VNF
+
+
+
+ Guest
+
+
+
+ OVS Bridge
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ sfc_br
+
+
+
+
+
+
+ Fortigate
+
+ lan
+ wan
+
+
+
+ LAN2
+
+ dpdk
+
+ lan_br
+
+ Juniper
+ lan
+ wan
+
+ dpdk
+
+
+ wan_br
+
+
+ uCPE Device 2
+
+
+
+
+
+
+
+
+
+
+ sfc_br
+
+
+
+ Juniper
+ wan
+ lan
+
+ dpdk
+
+ wan_br
+
+
+ Fortigate
+ wan
+ lan
+
+ dpdk
+
+
+ lan_br
+
+
+ uCPE Device 1
+
+
+ LAN1
+
+
+
+
+
+
+ Legend: - Connection via cloud/internet: - VPN/BTB:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Internet
+
+
+
+ Enea Edge Management
+
+
+
diff --git a/doc/book-enea-edge-example-usecases/doc/introduction.xml b/doc/book-enea-edge-example-usecases/doc/introduction.xml
new file mode 100644
index 0000000..b502e8b
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/introduction.xml
@@ -0,0 +1,27 @@
+
+
+ Introduction
+
+ This document describes several example use-cases concerning uCPE
+ configuration, onboarding and instantiation of certain VNFs, VNF chaining,
+ etc.
+
+ Before running any example use case make sure the uCPE device(s) have
+ been added to Enea Edge Management and placed on the map. For detailed
+ information on how to add a device to Enea Edge Management, how to configure the
+ network interfaces to use DPDK, PCI-passthrough or SR-IOV drivers, or VNF
+ configuration, please refer to the Manual.
+
+
+ Examples presented in this document use 3rd-party VNFs, which are
+ not provided by Enea. To procure and use these VNF image files and license
+ files, please contact the VNF provider.
+
+ Request the VNF prerequisites from the VNF vendors, or alternatively
+ obtain the prerequisites based on instructions from each VNF vendor
+ respectively.
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml b/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml
new file mode 100644
index 0000000..bb05905
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/service_chaining_128t_fortigate.xml
@@ -0,0 +1,1064 @@
+
+
+ Service Chaining 128T - Fortigate Example Use-case
+
+ The following is an example of how to setup and configure a service
+ chain on top of the Enea Edge Runtime, using the
+ following commercial VNFs: 128T router and FortiGate.
+
+
+ Prerequisites
+
+ The 128T router and the Fortinet firewall in a service chain require
+ the following prequisites for this example use case:
+
+
+
+ 1 in band management port for device management.
+
+
+
+ 1 in band management port for the 128T router.
+
+
+
+ 1 in band management port for Fortinet.
+
+
+
+ 1 WAN interface for Fortinet.
+
+
+
+ 1 LAN facing interface for Fortinet.
+
+
+
+ 1 WAN facing interface for the 128T router.
+
+
+
+ 1 service chain (SFC Bridged interface) to sit between the
+ Firewall and vRouter.
+
+
+
+ The following files are needed for this example use-case:
+
+
+
+ FortiGate VNF image. Please contact Fortinet to get a VNF image
+ and its license file.
+
+
+
+ 128T router VNF image. Please contact 128 Technology to get a
+ VNF image and its license file.
+
+
+
+ Cloud-init iso image.
+
+
+
+
+ To procure the VNF image files and their licenses, please contact
+ each respective VNF provider.
+
+
+
+
+ Service Chaining 128T - Fortigate
+
+
+ Service Chaining 128T - Fortigate Setup Overview
+
+
+
+
+
+
+
+
+
+ Use-case Setup
+
+ Configuring Network Interfaces on uCPE
+ devices:
+
+ Add the trgt uCPE device into Enea Edge Management:
+ Devices -> Manage -> Add , and fill in the
+ required fields with the following data:
+
+
+ Device Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ Type
+
+ Enea universal CPE
+
+
+
+ Release
+
+ 2.2.2
+
+
+
+ Name
+
+ trgt
+
+
+
+ IP/DNS Address
+
+ <unspecified>
+
+
+
+ Description
+
+ Target 1
+
+
+
+ SSH Port
+
+ 830
+
+
+
+ SSH User Name
+
+ root
+
+
+
+ Password
+
+ null
+
+
+
+ Device ID
+
+ Also configured during installation of the device
+ (E.g.: Target-15).
+
+
+
+ OK
+
+ Green status indicates connection with uCPE device
+ was established.
+
+
+
+
+
+
+
+ In order to add the device on the map: Right-Click on
+ Map -> Place Device -> trgt .
+
+
+
+ Configure the infrastructure for the 128T and Fortigate VNFs
+ in the service chain by creating four OVS bridges and a host
+ interface.
+
+ Add the Host Interface by selecting the trgt device, then
+ Configuration -> External Interfaces ->
+ Configuration -> Add , and fill in the required fields
+ with the following data:
+
+
+ Host Interface Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ Source
+
+ enp4s0f1 . The only interface
+ available for LAN connection.
+
+
+
+ networking-type
+
+ dpdk
+
+
+
+ dpdk-type
+
+ vfio-pci
+
+
+
+ Create
+
+ <interface enp4s0f1 ready to be used in a LAN
+ bridge.>
+
+
+
+
+
+ Add the OVS bridges by selecting the trgt device then:
+ Configuration -> OpenVSwitch -> Bridges ->
+ Add . Fill in the required fields for each bridge with
+ the following data from each table:
+
+
+ ibm_br Bridge Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ id
+
+ <autogenerated - do not change>
+
+
+
+ Name
+
+ ibm_br
+
+
+
+ ovs-bridge-type
+
+ inbandMgmt
+
+
+
+ Create
+
+
+
+
+
+
+
+
+
+
+ vnf_mgmt_br Bridge Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ id
+
+ <autogenerated - do not change>
+
+
+
+ Name
+
+ vnf_mgmt_br
+
+
+
+ ovs-bridge-type
+
+ vnfMgmt
+
+
+
+ vnf-mgmt-address
+
+ 10.0.0.1
+
+
+
+ Create
+
+
+
+
+
+
+
+
+ lan_br Bridge Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ id
+
+ <autogenerated - do not change>
+
+
+
+ Name
+
+ lan_br
+
+
+
+ ovs-bridge-type
+
+ dataPlane
+
+
+
+ sub-type
+
+ communication
+
+
+
+ +
+
+ Name: enp4s0f1 OK
+
+
+
+ Create
+
+
+
+
+
+
+
+
+ sfc_br Bridge Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ id
+
+ <autogenerated - do not change>
+
+
+
+ Name
+
+ sfc_br
+
+
+
+ ovs-bridge-type
+
+ dataPlane
+
+
+
+ sub-type
+
+ integration
+
+
+
+ Create
+
+
+
+
+
+
+
+
+
+ Onboarding the VNFs:
+
+ Onboard the 128T VNF VM Image through VNF ->
+ Descriptors -> On-board , and fill in the required fields
+ with the following values:
+
+
+ 128T VM Image Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ VM image file
+
+ centos_128t_with_ci.qcow2
+
+
+
+ Image format
+
+ QCOW2
+
+
+
+ VNF Type Name
+
+ 128T
+
+
+
+ Description
+
+ 128T Router
+
+
+
+ Version
+
+ 1.0
+
+
+
+ Memory in MB
+
+ 8192. More memory can be allocated if required
+ (<28672).
+
+
+
+ Num. of CPUs
+
+ 2. More CPUs can be reserved if required
+ (<15).
+
+
+
+ Interfaces -> +
+
+ Name: mgmt
+
+
+
+ Interfaces -> +
+
+ Name: wan
+
+
+
+ Interfaces -> +
+
+ Name: lan
+
+
+
+ Cloud Init -> Cloud-Init Datasource
+
+ ISO
+
+
+
+ Cloud Init -> Cloud-Init Disk Type
+
+ cdrom
+
+
+
+ Properties -> +
+
+ Name: vnfMgmtIpAddress. Value: 10.0.0.2
+
+
+
+ Properties -> +
+
+ Name: internalMgmtPort. Value: 443
+
+
+
+ Properties -> +
+
+ Name: externalMgmtPort. Value: 60001
+
+
+
+ Onboard
+
+ <Wait for message: VNF package onboarded
+ successfully>
+
+
+
+ Close
+
+
+
+
+
+
+
+
+
+
+ HTTPS access (443) can be changed to another type of access.
+ Please consult official 128T documentation and make sure the 128T
+ VNF is configured to accept another type of connection before
+ changing the port number.
+
+
+
+ externalMgmtPort(60001) represents the
+ external port on which the user can access the VNF management
+ interface from the web browser via HTTPS. The user can select
+ another port if needed. There are no other changes required or
+ components affected by this change.
+
+
+
+ vnfMgmtIpAddress (10.0.0.2) represents
+ the IP address of the management interface of the 128T VNF.
+ Changing this value requires an update to the 128T configuration
+ to match the new IP address.
+
+
+
+
+ Onboard the Fortigate VNF VM Image through VNF ->
+ Descriptors -> On-board , and fill in the required fields
+ with the following values:
+
+
+ Fortigate VM Image Details
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ VM image file
+
+ fortios.qcow2 . Please make sure to
+ contact Fortinet for an official FortiGate KVM image.
+
+
+
+ Image format
+
+ QCOW2
+
+
+
+ VNF Type Name
+
+ Fortigate
+
+
+
+ Description
+
+ Fortigate VNF
+
+
+
+ Version
+
+ 1.0
+
+
+
+ Memory in MB
+
+ 1024. More memory can be allocated if required
+ (<28672).
+
+
+
+ Num. of CPUs
+
+ 1. More CPUs can be reserved if required
+ (<15).
+
+
+
+ Interfaces -> +
+
+ Name: mgmt
+
+
+
+ Interfaces -> +
+
+ Name: wan
+
+
+
+ Interfaces -> +
+
+ Name: lan
+
+
+
+ Cloud Init -> Cloud-Init Datasource
+
+ ConfigDrive
+
+
+
+ Cloud Init -> Cloud-Init Disk Type
+
+ cdrom
+
+
+
+ Cloud Init -> +
+
+ Path: license
+
+
+
+ Properties -> +
+
+ Name: vnfMgmtIpAddress. Value: 10.0.0.3
+
+
+
+ Properties -> +
+
+ Name: internalMgmtPort. Value: 443
+
+
+
+ Properties -> +
+
+ Name: externalMgmtPort. Value: 60002
+
+
+
+ Onboard
+
+ <Wait for message: VNF package onboarded
+ successfully>
+
+
+
+ Close
+
+
+
+
+
+
+
+
+
+
+ HTTPS access (443) can be changed to another type of access.
+ Please consult official Fortigate documentation and make sure the
+ Fortigate VNF is configured to accept another type of connection
+ before changing the port number.
+
+
+
+ externalMgmtPort (60002) represents the
+ external port on which the user can access the VNF management
+ interface from the web browser via HTTPS. The user can select
+ another port if needed. There are no other changes required or
+ components affected by this change.
+
+
+
+ vnfMgmtIpAddress (10.0.0.3) represents
+ the IP address of the management interface of the Fortigate VNF.
+ Changing this value requires an update to the Fortigate
+ configuration to match with new IP address.
+
+
+
+
+ Instantiating the VNFs:
+
+ Instantiate the 128T VNF by selecting the trgt device, then
+ VNF -> Instances -> Add .
+
+ Fill in the required fields with the following values:
+
+
+ 128T VNF Instantiation
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ Name
+
+ 128T_trgt_1
+
+
+
+ VNF Type
+
+ 128T
+
+
+
+ VNFD Version
+
+ 1.0
+
+
+
+ Flavour
+
+ Canonical
+
+
+
+ uCPE Device
+
+ trgt
+
+
+
+ Cloud Init File
+
+ centos_128t_internet_ci.iso .
+
+
+
+ Domain Update Script
+
+
+
+
+
+ Interfaces
+
+
+
+
+
+ ID
+
+ IF Name
+
+
+
+ mgmt (dpdk)
+
+ Bridge: vnf_mgmt_br
+
+
+
+ wan (dpdk)
+
+ Bridge: ibm_br
+
+
+
+ lan (dpdk)
+
+ Bridge: sfc_br
+
+
+
+ Create
+
+
+
+
+
+
+
+
+ To procure the VNF image files and their licenses, please
+ contact each respective VNF provider.
+
+
+ Instantiate the Fortigate VNF by selecting the trgt device, then
+ VNF -> Instances -> Add .
+
+ Fill in the required fields with the following values:
+
+
+ Fortigate VNF Instantiation
+
+
+
+
+
+
+
+
+
+
+ Field
+
+ Value
+
+
+
+
+
+ Name
+
+ fg_trgt_1
+
+
+
+ VNF Type
+
+ Fortigate
+
+
+
+ VNFD Version
+
+ 1.0
+
+
+
+ Flavour
+
+ Canonical
+
+
+
+ uCPE Device
+
+ trgt
+
+
+
+ Cloud Init File
+
+ fg_cust_basic_fw.conf
+
+
+
+ License File
+
+ The FortiGate license file provided by Fortinet.
+
+
+
+ Domain Update Script
+
+
+
+
+
+ Interfaces
+
+
+
+
+
+ ID
+
+ IF Name
+
+
+
+ mgmt (dpdk)
+
+ Bridge: vnf_mgmt_br
+
+
+
+ wan (dpdk)
+
+ Bridge: sfc_br
+
+
+
+ lan (dpdk)
+
+ Bridge: lan_br
+
+
+
+ Create
+
+
+
+
+
+
+
+
+
+ Testing the Use-case
+
+ In order to access the web interfaces of the 128T VNF, open a
+ browser on a machine connected on the same network with the WAN port of
+ the target and connect to:
+ https://<publicIP>:60001 using the username:
+ admin and the password: 128Tadmin.
+
+ In order to access the web interfaces of the Fortigate VNF, open a
+ browser on a machine connected on the same network with the WAN port of
+ the target and connect to:
+ https://<publicIP>:60002 using the username:
+ admin, and leaving the password blank.
+
+
+ Make sure the WAN interface of the trgt device has access to the
+ internet. The Fortigate VNF requires internet access to validate the
+ license.
+
+
+ In order to validate the data path connect a test machine to the
+ LAN physical port and check for a dynamic IP (the Fortigate LAN
+ interface is configured with a DHCP server):> dhclient eth1
+> ping 8.8.8.8 For data path validation, a new cloud-init
+ image may need to be generated for the 128T VNF to match your network
+ configuration.
+
+
+
+ Use-case Clean-up
+
+ In order to remove the setup created in previously, all components
+ need to be deleted in reverse order:
+
+
+
+ Select the trgt uCPE device -> VNF -> Instances. Select
+ the 128T and Fortigate VNFs -> Delete.
+
+
+
+ Select the trgt uCPE device -> Configuration ->
+ OpenVSwitch -> Bridges. Select all bridges -> Delete.
+
+
+
+ Select the trgt uCPE device -> Configuration -> External
+ Interfaces -> Configuration. Select all interfaces ->
+ Delete.
+
+
+
+ VNF -> Descriptors. Select all bundles ->
+ Offboard.
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml
new file mode 100644
index 0000000..24442af
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/doc/vnf_chaining.xml
@@ -0,0 +1,407 @@
+
+
+ VNF Chaining Example Use-case
+
+ The term service chaining or service function chaining (SFC) is used
+ to describe the definition and instantiation of an ordered list of instances
+ of such service functions and the subsequent "steering" of traffic flows
+ through those service functions. The set of enabled service function chains
+ reflects operator service offerings and is designed in conjunction with
+ application delivery and service and network policy.
+
+ The following is an example of how to setup and configure a
+ branch-to-branch service comprised on two commercial VNFs (SD-WAN +
+ Firewall). This service will run in a service chain on top of the Enea
+ Edge Runtime, deployed through the Enea Edge
+ Management.
+
+ In the example setup the following commercial VNFs are used: Juniper
+ vSRX as the SD-WAN VNF and Fortigate as the Router/Firewall.
+
+
+ VNF Chaining with FortiGate
+
+
+ Prerequisites
+
+ Two uCPE devices will be needed for this setup. The system
+ requirements for each uCPE device are:
+
+
+
+ 4 x Network Interfaces
+
+
+
+ 4 GB of RAM memory
+
+
+
+
+ On each uCPE device, 3 interfaces need to be DPDK compliant and
+ one of these needs to be connected back-to-back to the other uCPE
+ device. This link simulates a WAN/uplink connection. Optionally, one
+ additional device (PC/laptop) can be connected on the LAN port of each
+ branch to run LAN-to-LAN connectivity tests.
+
+
+ The following files are needed for this example use-case:
+
+
+
+ Fortigate VNF image file.
+
+
+
+ Juniper vSRX VNF image file.
+
+
+
+ vSRX-Site<x>.iso Cloud-init files.
+
+
+
+ VNF Configuration files, provided with your Enea Edge
+ Release:
+
+
+
+ vSRX-domain-update-script .
+
+
+
+ FortiFW-Site<x>.conf .
+
+
+
+
+
+
+ To procure the VNF image files and their licenses, please
+ contact each respective VNF provider. To create the
+ vSRX-Site<x>.iso file, please follow the documentation provided
+ by Juniper.
+
+
+
+
+ Use-case Setup
+
+
+ VNF Chaining with Fortigate
+
+
+
+
+
+
+
+
+ No info about vnf_mgmt_br?
+
+ Network Configuration :
+
+ Both branches in the example have similar setups, therefore
+ necessary step details are presented for only one branch. The second
+ branch shall be configured in the same way, adapting as needed the
+ corresponding VNFs configuration files.
+
+
+
+ Assign three physical interfaces to the DPDK (one for
+ management, one WAN and one for LAN). In the example, one of these
+ interfaces gets an IP through DHCP and it will be used exclusively
+ for the management plane.
+
+
+
+ Create the following OVS-DPDK bridges:
+
+
+
+ vnf_mgmt_br . Used by VNF management
+ ports.
+
+
+
+ wan_br . Used by the service uplink
+ connection. In our case, Juniper vSRX will have its WAN virtual
+ interface in this bridge.
+
+
+
+ sfc_br . Used for creating the service
+ chain. Each VNF will have a virtual interface in this
+ bridge.
+
+
+
+ lan_br . Used for the LAN interface of
+ the Fortigate FW.
+
+
+
+
+
+ Add corresponding DPDK ports (see Step 1) to the management,
+ WAN and LAN bridges (sfc_br does not have a
+ physical port attached to it).
+
+
+ The networking setup (Steps 1-3) can be modeled using the
+ Offline Configuration entry, so that it is automatically
+ provisioned on the uCPE device, once it gets enrolled into the
+ management system (Enea Edge Management).
+
+
+
+
+ Onboarding the VNFs :
+
+
+
+ Onboard Juniper vSRX using the VNF by filling the required
+ fields with the following values:
+
+
+
+ The Flavor selected must have at least 2 vCPUs and 4 GB
+ RAM since vSRX is quite resource consuming.
+
+ Tested in-house with 4 vCPUs/ 6 GB RAM.
+
+
+
+ Add three virtual interfaces: management, WAN and
+ LAN.
+
+
+
+ Select ISO as the Cloud-Init Datasource
+ in the Cloud-Init tab.
+
+
+
+ Select cdrom as the Cloud-Init Disk
+ Type in the Cloud-Init tab.
+
+
+
+
+
+ Onboard Fortigate FW using the VNF Onboarding Wizard:
+
+
+
+ The Flavor selected can be quite light in resource
+ consumption, e.g. 1 CPU and 1 GB RAM.
+
+
+
+ Add three virtual interfaces: management, WAN and
+ LAN.
+
+
+
+ Select ConfigDrive as the Cloud-Init
+ Datasource in the Cloud-Init tab.
+
+
+
+ Select cdrom as the Cloud-Init Disk
+ Type in the Cloud-Init tab.
+
+
+
+ In the Cloud-init content files field add an entry where
+ Path: license .
+
+
+
+
+
+ Instantiating the VNFs:
+
+
+
+ Create the vSRX instance:
+
+
+
+ Use vSRX-Site1.iso as the Cloud-Init
+ file.
+
+
+
+ The Domain Update Script field can be
+ left empty for the Atom C3000 architecture, while for XeonD the
+ vSRX-domain-update-script file will be
+ used.
+
+
+
+ Add virtual interfaces:
+
+
+
+ Management interface added to
+ vnf_mgmt_br .
+
+
+
+ WAN interface added to
+ wan_br .
+
+
+
+ LAN interface added to
+ sfc_br .
+
+
+
+
+
+
+ The login/password values for the vSRX VNF are
+ root/vsrx1234 , respectively.
+
+
+
+
+ Create the Fortigate FW instance:
+
+
+
+ Use FortiFW-Site1.conf as the
+ Cloud-Init file.
+
+
+
+ Add .lic (not part of the folder) as
+ the license file.
+
+
+
+ Add virtual interfaces:
+
+
+
+ Management interface added to
+ vnf_mgmt_br .
+
+
+
+ WAN interface added to
+ sfc_br .
+
+
+
+ LAN interface added to
+ lan_br .
+
+
+
+
+
+
+ The login/password values for the Fortigate VNF are
+ admin/<empty password> ,
+ respectively.
+
+
+
+
+ At this point the service will be up and running on Site1. Repeat
+ the steps to instantiate a VNF for Site2, by changing the configuration
+ files accordingly.
+
+ After the service is deployed on both branches, the VPN tunnel is
+ established and LAN to LAN visibility can be verified by connecting one
+ device on each uCPE LAN port.
+
+
+
+ Testing the Use-case
+
+ Before testing LAN to LAN connectivity, preliminary tests of
+ service can be run to ensure everything was set up properly. For
+ instance, by connecting to vSRX CLI (any site), one can test IKE
+ security associations:
+
+ root@Atom-C3000:~ # cli
+root@Atom-C3000> show security ike security-associations
+Index State Initiator cookie Responder cookie Mode Remote Address
+1588673 UP 2f2047b144ebfce4 0000000000000000 Aggressive 10.1.1.2
+...
+root@Atom-C3000> show security ike security-associations index 1588673 detail
+...
+
+ Also, from the vSRX CLI, a user can check that the VPN tunnel was
+ established and get statistics of the packets passing the tunnel:
+
+ root@Atom-C3000> show security ipsec security-associations
+...
+root@Atom-C3000> show security ipsec statistics index <xxxxx>
+...
+
+ From the Fortigate Firewall CLI on Site 1, one can check
+ connectivity to the remote Fortigate FW (from Site 2):
+
+ FGVM080000136187 # execute ping 192.168.168.2
+PING 192.168.168.2 (192.168.168.2): 56 data bytes
+64 bytes from 192.168.168.2: icmp_seq=0 ttl=255 time=0.0 ms
+64 bytes from 192.168.168.2: icmp_seq=1 ttl=255 time=0.0 ms
+64 bytes from 192.168.168.2: icmp_seq=2 ttl=255 time=0.0 ms
+...
+
+ Since VNF management ports were configured to get IPs through
+ DHCP, the user can use a Web-based management UI to check and modify the
+ configuration settings of both vSRX and Fortigate.
+
+ For example, in the case of vSRX, from the VNF CLI you can list
+ the virtual interfaces as below:
+
+ root@Atom-C3000> show interfaces terse
+...
+fxp0.0 up up inet 172.24.15.92/22
+gre up up
+ipip up up
+...
+
+ When using provided configurations, the VNF management port for
+ Juniper vSRX is always fxp0.0 .
+
+ In the case of Fortigate, from the VNF CLI you can list the
+ virtual interfaces as such:
+
+ FGVM080000136187 # get system interface
+== [ port1 ]
+name: port1 mode: dhcp ip: 172.24.15.94 255.255.252.0 status: up netbios-forward:
+disable type: physical netflow-sampler: disable sflow-sampler: disable...
+...
+
+ When using provided configurations, the VNF management port for
+ Fortigate is always port1 .
+
+ If functionality is as intended, LAN-to-LAN connectivity can be
+ checked (through the VPN tunnel) by using two devices (PC/laptop)
+ connected to the LAN ports of each uCPE. Optionally, these devices can
+ be simulated by using Enea's sample VNF running on both uCPEs and
+ connected to the lan_br on each side. Please note
+ that instructions for onboarding and instantiating this VNF is not in
+ the scope of this document.
+
+ Since Fortigate VNF, which is acting as router and firewall, is
+ configured to be the DHCP server for the LAN network, the device
+ interface connected to the uCPE LAN port has to be configured to get
+ dinamically assigned IPs. These IPs are in the 172.0.0.0/24 network for
+ Site1 and the 172.10.10.0/24 network for Site2. Therefore, site-to-site
+ connectivity can be checked (from Site1) as such:
+
+ root@atom-c3000:~# ping 172.10.10.2
+PING 172.10.10.1 (172.10.10.2): 56 data bytes
+...
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-example-usecases/swcomp.mk b/doc/book-enea-edge-example-usecases/swcomp.mk
new file mode 100755
index 0000000..83f672c
--- /dev/null
+++ b/doc/book-enea-edge-example-usecases/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-example-usecases
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Example Use-cases"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
new file mode 100644
index 0000000..70a9978
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
@@ -0,0 +1,1042 @@
+
+
+
+ Advanced Configurations
+
+ This chapter describes possible configurations for advanced features
+ such as the Hugepage Reservation Service customization, UEFI Secure Boot and
+ Bare Metal Provisioning.
+
+
+
+
+ UEFI Secure Boot
+
+ Secure Boot was designed to enhance security in the pre-boot
+ environment. It prevents malicious software and applications from being
+ loaded during the system start-up process.
+
+ The basic principle of UEFI Secure Boot is that it requires all
+ artifacts involved in the boot process (bootloaders, kernel, initramfs) to
+ be signed using a set of private keys. On a Secure Boot enabled uCPE
+ device these artifacts are checked against a set of public certificates
+ which correspond to these keys. If there are any mismatches the boot
+ process will fail at the stage(s) they are detected.
+
+ For more information about Secure Boot please refer to Secure
+ Boot in Modern Computer Security Solutions .
+
+
+ Enabling UEFI Secure Boot
+
+ All Enea Edge image artifacts delivered with the release are
+ signed using the Enea UEFI Secure boot private keys. These artifacts can
+ be used on a uCPE device that doesn't have Secure Boot enabled. To use
+ the Secure Boot feature, however, the user must make the Enea UEFI
+ Secure Boot public certificates available on the uCPE device before
+ enabling the feature in BIOS. This process is called
+ "Provisioning".
+
+
+ Provisioning the Enea UEFI Secure Boot Certificates
+
+ The UEFI firmware is normally shipped with factory preloaded
+ certificates. If these do not already include Certificates from Enea,
+ they will need to be appended or replaced with the Enea
+ Certificates.
+
+ UEFI Secure Boot certificates provided
+ with your release:
+
+
+
+ Platform Key (PK) : this key protects the
+ next key from uncontrolled modification. Once this key is
+ enrolled, Secure Boot enters into User Mode .
+ The drivers and loaders signed with the Platform
+ Key can then be loaded by the firmware.
+
+
+
+ Key Exchange key (KEK) : this key allows
+ other certificates which have a connection to the private portion
+ of the Platform Key to be used.
+
+
+
+ Authorized Signature (DB) : contains the
+ trusted keys used for authenticating any
+ drivers or applications executed in the UEFI environment.
+
+
+
+ The Enea UEFI Secure Boot certificates are installed together
+ with the Enea Edge Runtime onto the hard drive. They can be found on
+ the EFI partition (usually the first partition of the drive) under
+ /uefi_sb_keys .
+
+ These certificates need to be manually enrolled in BIOS. The
+ exact details on how to proceed may vary depending the version of the
+ UEFI firmware.
+
+ The UEFI firmware is normally shipped with factory preloaded
+ certificates. If these do not already include Certificates from Enea,
+ they will need to be appended or replaced with the Enea
+ Certificates.
+
+
+
+ Enabling Secure Boot in BIOS
+
+ Once the certificates are enrolled, Secure Boot needs to be
+ enabled in BIOS and the device rebooted.
+
+
+
+
+
+ Hugepage Reservation Service
+
+ Huge page memory support is a mechanism that allows the Linux kernel
+ to support larger page sizes than the default page unit (4KB). Huge pages
+ are contiguous blocks of memory that come in 2MB or 1GB sizes. By using
+ huge page allocations, less memory is used for page tables and the
+ Translation Lookaside Buffer (TLB) miss rate is significantly reduced.
+ Enea Edge Runtime uses huge page backed memory in KVM guests in order to
+ improve performance.
+
+ Enea Edge Runtime implements an automatic hugepage allocation
+ service that is triggered at each startup. The service is skipped if
+ hugepages have been allocated in the kernel boot command line.
+
+ There are two strategies outlined for hugepage allocation:
+
+
+
+ If a system has an amount of memory up to 8GB, the allocation
+ algorithm will reserve up to 30% (no more than 2GB), for the OS and
+ the rest as 2MB hugepages.
+
+
+
+ If a system has an amount of memory that's higher than 8GB, the
+ allocation algorithm will reserve all but 2GB of memory as 1GB
+ hugepages, leaving the rest (2GB) to be used by the OS.
+
+
+
+
+ This is a best effort reservation after kernel boot, so the
+ results may vary accordingly.
+
+
+
+ Customizing Automatic Hugepage Reservation
+
+ Configuration of Hugepage reservation is done in
+ /etc/enea-nfv-access/hugepages.cfg .
+
+ Parameters used by the automatic algorithm:
+
+
+
+
+ hugepage_setup : Enables the automatic
+ configuration algorithm. It has only one value,
+ auto . For manual configuration comment or remove
+ this parameter. Use the other parameter descriptions as a
+ template/example.
+
+
+
+ threshold_to_use_1g : Decides the threshold
+ which instructs the algorithm to use 1GB hugepages. If a system's
+ memory is higher than threshold_to_use_1g , then
+ the algorithm will use 1GB hugepages, otherwise it will use 2MB
+ hugepages.
+
+
+
+ percent_os_alloc : Decides how much memory
+ to try to reserve for userspace applications. The algorithm will try
+ to reserve at least the value of percent_os_alloc
+ of the total system memory for userspace applications.
+
+
+
+ maximum_os_alloc_mb : Maximum amount of
+ memory to allocate for userspace applications. If
+ percent_os_alloc of the total system memory
+ exceeds maximum_os_alloc_mb then the maximum
+ allocated memory for userspace applications is
+ maximum_os_alloc_mb .
+
+
+
+ Example of automatic Hugepage
+ Configuration:
+
+ hugepage_setup = auto
+threshold_to_use_1g = 8192
+percent_os_alloc = 30
+maximum_os_alloc_mb = 2048
+
+ The following possible allocations can result (based on total
+ system memory available):
+
+
+
+ 2GB of memory: approximately 30% will be allocated for the OS
+ and the rest will be allocated as 2MB hugepages.
+
+
+
+ 4GB of memory: approximately 30% will be allocated for the OS
+ and the rest will be allocated as 2MB hugepages.
+
+
+
+ 16GB of memory: approximately 2GB will be allocated for the OS
+ and the rest as 1GB hugepages.
+
+
+
+
+ The memory allocated for the kernel and hugepages might vary
+ slightly depending on how much memory is available.
+
+
+
+
+ Customizing Manual Hugepage Reservation
+
+ The automatic algorithm can be disabled and hugepages in turn,
+ configured manually. To do this, comment the line which defines
+ hugepage_setup as auto and
+ configure memory for each CPU socket in the following manner:
+
+ <NUMA node>.<hugepage size> = <number of pages>
+
+ Where <NUMA node> refers to a node which
+ is part of the system's NUMA topology, <hugepage
+ size> decides what type of hugepages should be set and
+ <number of hugepages> is how many hugepages of
+ <hugepage size> should be allocated.
+
+ To list the available system nodes, run:
+
+ ls -d /sys/devices/system/node/node*
+
+ To list available hugepage sizes, per node, run:
+
+ ls -d /sys/devices/system/node/node*/hugepages/hugepages-*
+
+ Example of Manual Hugepage Configuration, configuring the system
+ to allocate three 1GB hugepages and 512 of 2MB hugepages on node:
+
+ node0.2048kB = 512
+node0.1048576kB = 3
+
+
+ Make sure there are no hugepages reserved in the kernel boot
+ command line, these will override any manual configuration done in the
+ service.
+
+
+
+
+
+ Installing the Enea Edge Management in High Availability
+ Mode
+
+ The following describes the setup needed for running the Enea Edge
+ Management in High Availabilty (HA) mode, with a MariaDB database cluster.
+ A setup example is illustrated in the diagram below.
+
+
+ The High Availability setup
+
+
+
+
+
+
+
+
+ The setup consists of two sub-clusters, placed in different
+ geographical locations, each consisting of three MariaDB servers. In this
+ example, two of the machines are running only MariaDB, while the rest are
+ hosting a MariaDB server and an Enea Edge Management instance. The entire
+ network is hidden behind a firewall that performs NAT. While in protection
+ (cluster) mode, the Enea Edge Management instances promote a Virtual IP
+ (VIP) that represents the IP address of the entire cluster. The firewall
+ in this case will allocate a public IP for the outside world that will be
+ translated into the VIP. Also in this example, the traffic towards the
+ cluster from outside the firewall is done through HTTPS, which will be
+ translated to HTTP inside the private network.
+
+
+ By default, communication to the Enea Edge Management is done with
+ HTTPS. To enable HTTP, go to System ,
+ Configuration , click on the Web Access tab and check the Enable HTTP checkbox.
+
+
+
+ Requirements for High Availability
+
+ The following hardware is needed for deploying the base
+ configuration:
+
+
+
+ Machines running the Enea Edge Management and MariaDB:
+
+
+
+ 4 CPU cores
+
+
+
+ 12 - 16 GB memory
+
+
+
+ 256 - 512 GB hard disk
+
+
+
+
+
+ Machines running only MariaDB:
+
+
+
+ 2 CPU cores
+
+
+
+ 8 GB memory
+
+
+
+ 256 - 512 GB hard disk
+
+
+
+
+
+
+
+ Firewall Rules
+
+ Please refer to Firewall Configuration in the
+ Manual. In addition, the following configuration is needed:
+
+
+
+ Disable SELINUX on all database servers by
+ editing /etc/sysconfig/selinux and changing the
+ following:
+
+ SELINUX=disabled
+SELINUXTYPE=targeted
+
+
+
+ Reboot the server:
+
+ [root@localhost ~]# sudo shutdown -r now
+
+
+
+ The following ports should be opened in the local firewall (not
+ the one doing NAT), for each Enea Edge Management machine:
+
+
+ Ports for Enea Edge Management Machines
+
+
+
+
+
+
+ Port (Protocol)
+
+ Usage
+
+
+
+
+
+ 80 (TCP)
+
+ HTTP
+
+
+
+ 443 (TCP)
+
+ HTTPS
+
+
+
+ 54327 (UDP)
+
+ Cluster multicasting (Hazelcast)
+
+
+
+ 5701 - 5708 (TCP)
+
+ Hazelcast communications
+
+
+
+ 4334 (TCP)
+
+ NETCONF call-home
+
+
+
+ 7000 - 7009 (TCP)
+
+ Reverse SSH connection pool
+
+
+
+
+
+ For MariaDB, the following ports must be opened (on each MariaDB
+ server, including the ones hosting the Enea Edge Management):
+
+
+ Ports for MariaDB Machines
+
+
+
+
+
+
+ Port (Protocol)
+
+ Usage
+
+
+
+
+
+ 3306 (TCP)
+
+ Client connections
+
+
+
+ 4567 (UDP/TCP)
+
+ Galera cluster replication with multicasting
+
+
+
+ 4568 (TCP)
+
+ Incremental state transfer
+
+
+
+ 4444 (TCP)
+
+ State snapshot transfer
+
+
+
+
+
+ The following ports should be accessible externally and translated
+ to the Virtual IP side as shown below:
+
+
+ Ports for Virtual IP
+
+
+
+
+
+
+ External Port (Protocol)
+
+ Usage
+
+ Local Port (Protocol)
+
+
+
+
+
+ 443 (TCP)
+
+ HTTPS to/back HTTP
+
+ 80 (TCP)
+
+
+
+ 4334 (TCP)
+
+ NETCONF call-home
+
+ 4334 (TCP)
+
+
+
+ 7000 - 7009 (TCP)
+
+ Reverse SSH connection pool
+
+ 7000 - 7009 (TCP)
+
+
+
+
+
+
+
+ Installing High Availability
+
+ The Enea Edge Management can be installed in High Availability
+ mode with a MariaDB database cluster by performing the following steps.
+ The mandatory Java configuration is also detailed.
+
+
+ Installing and configuring the MariaDB cluster
+
+ Install the latest MariaDB packages on all servers.
+
+
+ The setup was tested using MariaDB 10.5.8, built for CentOS
+ 7.
+
+
+ How to install MariaDB
+
+
+
+ Install the MariaDB official yum repository. Create a file
+ named mariadb.repo in
+ /etc/yum.repos.d/ with the following
+ content:# MariaDB 10.5 CentOS repository list - created 2021-02-16 08:46 UTC
+# http://downloads.mariadb.org/mariadb/repositories/
+[mariadb]
+name = MariaDB
+baseurl = http://yum.mariadb.org/10.5/centos7-amd64
+gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
+gpgcheck=1
+
+
+
+ For more information about setting the repository, consult
+ Downloads
+ - Setting up MariaDB Repositories .
+
+
+
+
+ Make sure the following packages are installed:
+
+ MariaDB-compat-10.5.8-1.el7.centos.x86_64
+MariaDB-common-10.5.8-1.el7.centos.x86_64
+MariaDB-server-10.5.8-1.el7.centos.x86_64
+MariaDB-client-10.5.8-1.el7.centos.x86_64
+galera-4-26.4.6-1.el7.centos.x86_64
+
+ These provide the MariaDB server, client and the Galera
+ wsrep provider library.
+
+
+
+ Copy the wsrep template:
+
+ [root@localhost ~]# cp /usr/share/mysql/wsrep.cnf /etc/my.cnf.d
+
+
+
+
+ Change the following configuration in
+ /etc/my.cnf.d/wsrep.cnf :
+
+ # Full path to wsrep provider library or 'none'
+wsrep_provider=/usr/lib64/galera-4/libgalera_smm.so
+
+# Provider specific configuration options
+#wsrep_provider_options=
+
+# Logical cluster name. Should be the same for all nodes.
+wsrep_cluster_name="ucpemanager"
+
+# Group communication system handle
+wsrep_cluster_address="gcomm://192.168.10.11,192.168.10.12,..,192.168.10.16"
+
+# Human-readable node name (non-unique). Hostname by default.
+wsrep_node_name=Node1 # current node's name. set node name for each server in \
+the cluster
+
+# Base replication <address|hostname>[:port] of the node.
+# The values supplied will be used as defaults for state transfer receiving,
+# listening ports and so on. Default: address of the first network interface.\
+wsrep_node_address=192.168.10.11
+#current node's interface IP . must be set for each node in the cluster
+
+
+ Steps 2, 3 and 4 must be performed for each MariaDB node
+ in the cluster.
+
+
+
+
+ Bootstrap the first node in the cluster (referred to as
+ Node1 in this example), by running:
+
+ [root@localhost ~]# galera_new_cluster
+
+ This script passes the
+ --wsrep-new-cluster to
+ mysqld which tells the node that there is no
+ pre-existing cluster to connect to. The node will create a new
+ UUID to identify the new cluster.
+
+
+ Do not execute this script when connecting to an existing
+ cluster. It will create a new UUID to identify the cluster
+ again, and the node won't reconnect to the old cluster.
+
+
+
+
+ Go to Node1 and start the service:
+
+ [root@localhost ~]# systemctl start mariadb
+
+ Subsequently, start the service on the other servers.
+
+
+
+ Verify that the nodes have entered the cluster:
+
+ [root@localhost ~]# mysql --host=localhost --user=root -p
+MariaDB [(none)]> show status like 'wsrep_cluster_conf_%';
++-----------------------+-------+
+| Variable_name | Value |
++-----------------------+-------+
+| wsrep_cluster_conf_id | 3 |
++-----------------------+-------+
+1 row in set (0.001 sec)
+
+
+
+ Run the initial configuration script (only once, on one of
+ the machines in the cluster):
+
+ [root@localhost ~]# mysql_secure_installation
+
+Switch to unix_socket authentication [Y/n] Y
+Enabled successfully!
+Reloading privilege tables..
+ ... Success!
+…
+Change the root password? [Y/n] Y
+New password:
+Re-enter new password:
+Password updated successfully!
+Reloading privilege tables..
+ ... Success!
+…
+Remove anonymous users? [Y/n] Y
+ ... Success!
+…
+Disallow root login remotely? [Y/n] Y
+ ... Success!
+…
+Remove test database and access to it? [Y/n] Y (optional)
+ - Dropping test database...
+ ... Success!
+ - Removing privileges on test database...
+ ... Success!
+Reload privilege tables now? [Y/n] Y
+ ... Success!
+
+Cleaning up...
+
+All done! If you've completed all of the above steps, your MariaDB
+installation should now be secure.
+
+Thanks for using MariaDB!
+
+
+
+ Create the initial database and grant access to it:
+
+ [root@localhost application]# mysql --host=localhost --user=root -p
+MariaDB [(none)]> CREATE DATABASE ucpemanager CHARACTER SET='utf8' \
+COLLATE='utf8_bin';
+Query OK, 1 row affected (0.004 sec)
+
+MariaDB [(none)]> GRANT ALL PRIVILEGES ON ucpemanager.* \
+TO 'enea'@'%' IDENTIFIED BY 'somepassword' WITH GRANT OPTION;
+
+
+
+
+
+ Installing the Java SDK
+
+ Please refer to Configuring OpenJDK and
+ PostgreSQL in the
+ Manual, for details on how to install and configure Java
+ OpenJDK.
+
+ Make sure the JAVA_HOME variable points to
+ the OpenJDK 11 installation:
+
+ [root@localhost ~]# echo $JAVA_HOME
+/usr/lib/jvm/java-11-openjdk-11.0.10.0.9-0.el7_9.x86_64
+
+
+
+
+ Installing the Enea Edge Management in High Availabilty
+ mode
+
+ These steps must be taken on each of the CentOS 7 machines that
+ will host the Enea Edge Management. The Enea Edge Management will be
+ installed and the setup for the external database cluster will be
+ prepared.
+
+ As the root user, go to the distribution folder of the Enea Edge
+ Management, and run:
+
+ [root@localhost distro]#./install.sh /opt/ \
+Enea_NFV_Access_uCPEManager_2.3.0-build23.tar.gz
+This will install uCPEManager into /opt/ucpemanager folder.
+Select the following options, while asked by the installation script:
+Are you using the embedded PostgreSQL database? [Y/N]: N
+External database selected, getting user information ...
+Press 1 for PostgreSQL, 2 for MariaDB, 3 for SQL Server, 4 for Oracle and 5 \
+for MySQL: 2
+Specify database server name(s) or IP Address(es): \
+192.168.10.11,192.168.10.12,…,192.168.10.16 *(see note)
+Specify database ID (or name) [ucpemanager]:
+Specify database server port [3306]:
+Specify database user name [root]: enea
+Specify database password [root]: somepassword
+Specify database startup thread pool size [1]:
+Creating database configuration file \
+/opt//ucpemanager/application/config/databaseConfig.xml ...
+Done .
+…
+Installing ucpemanager service ..
+Specify service username [ucpemanager]:
+Specify service password [ucpemanager]: somepassword
+…
+Specify the IP address of the local interface: 192.168.10.11
+Is this server part of a cluster? [Y/N]: Y
+Specify the name of the cluster [ucpemanager]:
+Specify the shared (virtual) cluster IP address: 192.168.10.10
+Specify the netmask for the cluster IP address [255.255.255.0]:
+HA Configuration files modified successfully.
+Configuration complete.
+
+
+ For each Enea Edge Management installation, place the local
+ interface IP first in the list of IPs. This will optimize database
+ communication, since the Enea Edge Management uses the list of IPs
+ sequentially, therefore using the internal loopback interface for
+ communicating with the database.
+
+
+ Once the servers are up and running, log into the Primary and go to System and select Cluster
+ View . The list of Enea Edge Management servers should be
+ displayed, with one listed as Primary and the rest as Backup.
+
+
+
+
+ Upgrading a High Availability Deployment
+
+ Upgrading a High Availabilty deployment is a highly complex,
+ multi-step process that requires care to ensure both consistency and
+ high-availability. Some steps need to be done manually.
+
+
+
+ We start with the assumption that ucpeManager-1
+ is the "PRIMARY" server.
+
+
+
+ Shut down database services on one side of the network, for
+ example: MariaDB-4, MariaDB-5 and MariaDB-6.
+
+
+
+ Disconnect the network interfaces towards the VPN for machines
+ MariaDB-4, MariaDB-5 and MariaDB-6. This will prevent any attempts
+ at failover/synchronization.
+
+
+
+ Run the upgrade process on ucpeManager-3
+ and ucpeManager-4 . This will upgrade the service
+ to the current release. Once the upgrade process completes, shutdown
+ the Enea Edge Management service on both machines.
+
+
+
+ Disconnect the ucpeManager-2 machine from
+ the network (which will take MariaDB-2 offline as well). At this
+ point, only the "PRIMARY" server is running, this is the start of
+ the interval when we are susceptible to single-server
+ failure.
+
+
+
+ Shutdown the MariaDB-2 process and run the Enea Edge
+ Management upgrade process on ucpeManager-2 . This
+ will upgrade the service to the current release. Once the upgrade
+ process completes, shutdown the Enea Edge Management service on the
+ machine.
+
+
+
+ Reconnect the network interfaces towards the VPN for MariaDB-4
+ (ucpeManager-3 ), MariaDB-5
+ (ucpeManager-4 ) and MariaDB-6
+ (ucpeManager-2 ). Restart database services on
+ MariaDB-2, MariaDB-4, MariaDB-5 and MariaDB-6. This will allow
+ database services on all machines to synchronize, any data that has
+ been modified during the upgrade process will be made
+ consistent.
+
+
+
+ Shutdown the "Primary" server
+ (ucpeManager-1 ). At this point, the service is no
+ longer available.
+
+
+
+ Start the Enea Edge Management services on
+ ucpeManager-2 . This machine will come up as the
+ new "PRIMARY" with the upgraded software. As part of the startup
+ process, it will upgrade the database and perform any other
+ upgrade-related functionality.
+
+
+
+ At this point (once startup completes), service is available.
+ However, we are still susceptible to single-server failure.
+
+
+
+ Start the Enea Edge Management services on
+ ucpeManager-3 and
+ ucpeManager-4 . At this point, we are in
+ highly-available mode.
+
+
+
+ Upgrade the Enea Edge Management on
+ ucpeManager-1 (the one that has been shut down).
+ Once that upgrade is complete and the service restarts, the entire
+ setup has been upgraded to the new version.
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/book.xml b/doc/book-enea-edge-getting-started/doc/book.xml
new file mode 100644
index 0000000..f02f770
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/book.xml
@@ -0,0 +1,44 @@
+
+
+]>
+
+ Enea Edge Getting Started
+
+ Release Version
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-getting-started/doc/grafana.xml b/doc/book-enea-edge-getting-started/doc/grafana.xml
new file mode 100644
index 0000000..05276ed
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/grafana.xml
@@ -0,0 +1,266 @@
+
+
+ Using Grafana and InfluxDB
+
+ InfluxDB is essentially a time series database process that runs on a
+ server, while Grafana is a visualization tool for time series data. Grafana
+ is a very lightweight server-side application, and most of the monitoring
+ runs in a browser.
+
+
+ Deploying Grafana and InfluxDB
+
+ Grafana and InfluxDB can be deployed using images for Docker on
+ linux. These images are provided by Enea along with a deploy script and
+ predefined dashboards.
+
+ The Grafana and InfluxDB images can be deployed on the same machine
+ or on separate machines.
+
+
+ Prerequisites for Deploying an Image
+
+ The following must be present in order to deploy an image:
+
+
+
+ CentOS 7 Linux.
+
+
+
+ Docker for CentOS 7 installed on the machine and set to
+ autostart as a service.
+
+
+
+ Superuser rights on the CentOS 7 machine.
+
+
+
+
+
+ Deploying Grafana and InfluxDB
+
+ On the CentOS 7 server open a terminal, log into a bash shell with
+ the root account and perform the following:
+
+
+
+ Extract
+ Enea_Edge_Telemetry_Deploy_<version>-build<build_number>.tar.gz .
+
+ The directory in which the archive will be unpacked will be
+ denoted as: <Telemetry-installdir> .
+
+
+
+ Enter <Telemetry-installdir> .
+
+
+
+ Run the provided telemetry_deploy.sh
+ script.
+
+
+
+ When prompted, select what images you want to deploy.
+
+ If an image is already deployed, you will be prompted to
+ replace it.
+
+
+
+ During the InfluxDB deployment, you will be prompted to
+ provide a username and password. These must match the ones
+ configured in the Enea Edge Management for Telemetry.
+
+
+ Changing the InfluxDB username and password requires
+ redeploying the InfluxDB image.
+
+
+
+
+ Verify the installation by running the command docker
+ ps -a . The Grafana and InfluxDB containers should be
+ present and have the status Up .
+
+
+
+
+
+
+ Setting Grafana and InfluxDB parameters
+
+ Customizing InfluxDB and Grafana parameters can be done by selecting
+ System , then the Configuration menu, accessing the Properties tab, and clicking on the Telemetry tab. The settings that can be changed are
+ listed in the table below:
+
+
+ Telemetry settings
+
+
+
+
+
+
+
+
+
+
+ Field name
+
+ Description
+
+ Default value
+
+
+
+ Grafana Hostname or IP Address
+
+ The hostname or IP address where the Grafana instance is
+ installed.
+
+ no default
+
+
+
+ Grafana Port
+
+ The port Grafana uses.
+
+ 3000
+
+
+
+ Grafana Dashboard
+
+ The dashboard that should be used when opening Grafana
+ using the Enea Edge Management.
+
+ host
+
+
+
+ InfluxDB Hostname or IP Address
+
+ The hostname or IP address where the InfluxDB database is
+ installed.
+
+ no default
+
+
+
+ InfluxDB Port
+
+ The port used for communication between InfluxDB and the
+ Telemetry server.
+
+ 25826
+
+
+
+ InfluxDB Username
+
+ The username used for encrypting communication between
+ InfluxDB and the Telemetry server.
+
+ admin0
+
+
+
+ InfluxDB Password
+
+ The password used for encrypting communication between
+ InfluxDB and the Telemetry server.
+
+ admin
+
+
+
+
+
+ When changing any of the settings in the Telemetry tab, the Enea Edge Management will inform
+ all uCPE devices of the change if they have telemetry running.
+
+
+ Telemetry Properties
+
+
+
+
+
+
+
+
+
+
+ Starting and stopping Telemetry
+
+ When a uCPE Device is selected, in the Operations menu, the Start
+ Telemetry and Stop Telemetry
+ options are available.
+
+ When starting Telemetry for a uCPE device, the Enea Edge Management
+ sends the following information about the InfluxDB:
+
+
+
+ The IP address and hostname where InfluxDB is installed.
+
+
+
+ The port used for communication between InfluxDB and the
+ Telemetry server.
+
+
+
+ The credentials used for encrypting communication between
+ InfluxDB and the Telemetry server.
+
+
+
+ These fields are read-only and are populated with the values already
+ set in the System Configuration . If one
+ of the fields is not set or if it does not have the desired value, modify
+ it in the System Configuration . The
+ password is sent encrypted using the Base64 scheme.
+
+
+ Telemetry Start Dialog
+
+
+
+
+
+
+
+
+ When the Telemetry status is changed on a uCPE device, a
+ notification is sent to the Enea Edge Management. These notifications can
+ be inspected under Fault found in the
+ Event menu.
+
+
+
+ Launching Grafana
+
+ When a uCPE Device is selected, the Telemetry button is available. Pressing this button
+ will open a new window pointing to Grafana. The current uCPE device will
+ be selected in Grafana.
+
+ The hostname or IP Address and the port of the Grafana installation
+ can be customized by selecting System ,
+ then the Configuration menu, accessing
+ the Properties tab, and clicking on the
+ Telemetry tab. The default dashboard
+ available when launching Grafana can be customized as well.
+
+
diff --git a/doc/book-enea-edge-getting-started/doc/images/archive_list.png b/doc/book-enea-edge-getting-started/doc/images/archive_list.png
new file mode 100755
index 0000000..302f32d
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/archive_list.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/collect_debug_logs.png b/doc/book-enea-edge-getting-started/doc/images/collect_debug_logs.png
new file mode 100755
index 0000000..6582737
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/collect_debug_logs.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/debug_settings.png b/doc/book-enea-edge-getting-started/doc/images/debug_settings.png
new file mode 100755
index 0000000..2c97b2c
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/debug_settings.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/dev_file_mg.png b/doc/book-enea-edge-getting-started/doc/images/dev_file_mg.png
new file mode 100755
index 0000000..a4a4f5c
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/dev_file_mg.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/download_files.png b/doc/book-enea-edge-getting-started/doc/images/download_files.png
new file mode 100755
index 0000000..cb686e4
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/download_files.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/edit_inter.png b/doc/book-enea-edge-getting-started/doc/images/edit_inter.png
new file mode 100755
index 0000000..fddde37
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/edit_inter.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/edit_inter_config.png b/doc/book-enea-edge-getting-started/doc/images/edit_inter_config.png
new file mode 100755
index 0000000..f9ab8aa
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/edit_inter_config.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/fault_events.png b/doc/book-enea-edge-getting-started/doc/images/fault_events.png
new file mode 100755
index 0000000..aeec955
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/fault_events.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/high_av_setup.png b/doc/book-enea-edge-getting-started/doc/images/high_av_setup.png
new file mode 100644
index 0000000..d119ecb
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/high_av_setup.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/onboard_a_vnf_image.png b/doc/book-enea-edge-getting-started/doc/images/onboard_a_vnf_image.png
new file mode 100755
index 0000000..da52202
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/onboard_a_vnf_image.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/ovs_bridges_tab.png b/doc/book-enea-edge-getting-started/doc/images/ovs_bridges_tab.png
new file mode 100755
index 0000000..0b3ec54
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/ovs_bridges_tab.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/prep_deploy.png b/doc/book-enea-edge-getting-started/doc/images/prep_deploy.png
new file mode 100755
index 0000000..2db2487
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/prep_deploy.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/prep_execution.png b/doc/book-enea-edge-getting-started/doc/images/prep_execution.png
new file mode 100755
index 0000000..404760b
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/prep_execution.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/telemetry_settings.png b/doc/book-enea-edge-getting-started/doc/images/telemetry_settings.png
new file mode 100644
index 0000000..276b716
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/telemetry_settings.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/telemetry_start.png b/doc/book-enea-edge-getting-started/doc/images/telemetry_start.png
new file mode 100644
index 0000000..81510b5
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/telemetry_start.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/vnf_space.png b/doc/book-enea-edge-getting-started/doc/images/vnf_space.png
new file mode 100755
index 0000000..57ed581
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/vnf_space.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/wap_external_interface.png b/doc/book-enea-edge-getting-started/doc/images/wap_external_interface.png
new file mode 100644
index 0000000..ee49fc1
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/wap_external_interface.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/images/wap_wireless_ap.png b/doc/book-enea-edge-getting-started/doc/images/wap_wireless_ap.png
new file mode 100644
index 0000000..b7c77bf
Binary files /dev/null and b/doc/book-enea-edge-getting-started/doc/images/wap_wireless_ap.png differ
diff --git a/doc/book-enea-edge-getting-started/doc/installation_guide.xml b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
new file mode 100644
index 0000000..d9784a0
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
@@ -0,0 +1,1193 @@
+
+
+ Setting up and Installing the Enea Edge Base Configuration
+
+ The setup and installation steps detailed below will deploy a base
+ configuration which will be used as a reference for more complex deployment
+ scenarios.
+
+
+ Hardware Requirements
+
+ The following hardware is needed for deploying the base
+ configuration:
+
+
+
+ One server running the CentOS 7 distribution
+
+
+ The CentOS 7 server must be updated to the latest revision
+ before installing Enea Edge.
+
+
+ The following will detail CPU, RAM and storage requirements for
+ the Enea Edge Management.
+
+
+
+ For small-sized deployments (tens of devices):
+
+
+
+ 4 cores
+
+
+
+ 16 GB RAM
+
+
+
+ 300 GB single disk storage
+
+
+
+
+
+ For mid-sized deployments (hundreds of devices):
+
+
+
+ 8 cores
+
+
+
+ 32 GB RAM
+
+
+
+ 300 GB single disk storage
+
+
+
+
+
+ For large deployments (thousands of devices):
+
+
+
+ 16 cores
+
+
+
+ 64-256 GB RAM
+
+
+
+ 1-2 TB single disk storage
+
+
+
+
+
+ The purpose of the CentOS 7 server is to host the Enea Edge
+ Management. Network access between the CentOS 7 server and the uCPE
+ devices is required. The Enea Edge Management and the uCPE devices
+ will be connected on separate subnets to avoid inconsistencies.
+
+
+
+ One or more uCPE devices.
+
+ Whitebox devices where the Enea Edge Runtime will be installed,
+ containing a minimum of 2 cores and 4 GB RAM and at least two ethernet
+ ports that will be configured as WAN and LAN during deployment.
+
+ When hosting an entire solution including one or several network
+ services, the hardware must also have the resources to host one or
+ more VNFs. During a typical evaluation, a dual VNF service on the Enea
+ Edge Runtime needs a CPU with 4-8 cores and at least 8 GB RAM. The
+ supported Intel CPUs of Enea Edge are documented in the
+ manual.
+
+ Enea Edge Runtime needs EFI support in BIOS to boot. When
+ configuring the uCPE device BIOS a serial connection is
+ required.
+
+
+
+ A laptop.
+
+ The laptop is used for 2 scenarios:
+
+
+
+ Installing the Enea Edge Runtime on uCPE Devices.
+
+
+
+ Connecting to the GUI of the Enea Edge Management for
+ management and configuration. Network access between the CentOS 7
+ server and the laptop is required. Please see the manual
+ available with your release, for recommended browsers.
+
+
+
+
+
+ A 16 GB USB stick used for the uCPE Device Installation.
+
+
+
+
+
+ Software Configuration
+
+ The CentOS 7 server requires a specific configuration for the setup
+ to work.
+
+
+ Firewall Configuration
+
+ Any firewall running on the CentOS 7 server may block the
+ management protocols required to communicate between the uCPE device and
+ the Enea Edge Management as well as between the Enea Edge Management and
+ its northbound clients. Quick handling of a blocking firewall would be
+ to disable it, typical for a lab environment, through:
+
+ sudo systemctl stop firewalld
+sudo systemctl disable firewalld
+sudo systemctl mask now firewalld
+
+ For an advanced firewall configuration, the following ports need
+ to be opened:
+
+
+ Ports to be Activated
+
+
+
+
+
+
+ 80
+
+ TCP
+
+ Required for GUI Access.
+
+
+
+ 443
+
+ TCP
+
+ Required for GUI Access and Device Connectivity.
+
+
+
+ 54327
+
+ UDP
+
+ Required for the Enea Edge Management High Availability
+ Configuration.
+
+
+
+ 5701:5708
+
+ TCP
+
+ Required for the Enea Edge Management High Availability
+ Configuration.
+
+
+
+ 4334
+
+ TCP
+
+ Required for Call Home.
+
+
+
+ 2021:2040
+
+ TCP
+
+ Required for Call Home when connecting uCPE Devices using
+ Enea NFV Access 2.3.0 or older.
+
+
+
+
+
+ Use the following command sequence to enable the required ports
+ for deployment of the Enea Edge Management:
+
+ sudo firewall-cmd --permanent --add-port=80/tcp
+sudo firewall-cmd --permanent --add-port=443/tcp
+sudo firewall-cmd --permanent --add-port=54327/udp
+sudo firewall-cmd --permanent --add-port=5701-5708/tcp
+sudo firewall-cmd --permanent --add-port=4334/tcp
+sudo firewall-cmd --permanent --add-port=2021-2040/tcp
+sudo firewall-cmd --reload
+
+
+ If the Enea Edge Management host resides behind a corporate
+ port-filtering firewall, then all the aforementioned ports need to
+ also be enabled on the respective firewall. As an additional
+ requirement, port 22/TCP also needs to be enabled for reverse SSH to
+ the Enea Edge Management.
+
+ No enabling and no forwarding rules are necessary for ports
+ 2021-2040 if using Enea Edge 2.4.0 or newer.
+
+
+
+
+ Configuring OpenJDK and PostgreSQL
+
+ The Enea Edge Management requires a specific Java version (OpenJDK
+ 11) and a PostgreSQL version to operate correctly.
+
+ Installing OpenJDK
+
+
+
+ Install OpenJDK 11 using the root account:
+
+ yum install java-11-openjdk-devel
+
+
+
+ Verify the installation:
+
+ java -version
+openjdk version "11.0.3" 2019-04-16 LTS
+OpenJDK Run Time Environment 18.9 (build 11.0.3+7-LTS)
+OpenJDK 64-Bit Server VM 18.9 (build 11.0.3+7-LTS, mixed mode, sharing)
+
+
+ If there are multiple java versions installed, switch
+ between them using the following command:
+
+ alternatives --config java
+
+ Optionally, the user can switch between the
+ javac versions using:
+
+ alternatives --config javac
+
+
+
+
+ The following system variables need to point to the OpenJDK 11
+ installation:
+
+ export JAVA_HOME=$(dirname $(dirname $(readlink $(readlink $(which java)))))
+export PATH=$PATH:$JAVA_HOME/bin
+export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
+
+
+ In order to make these system variables persistent, the
+ commands given above should be added to a script in the
+ /etc/profile.d/ folder. Sudo access is needed for this
+ operation.
+
+
+
+
+ The Enea Edge Management requires a specific PostgreeSQL version.
+ This is embedded in the Enea Edge Management installation. In order to
+ avoid conflicts, any existing PostgreeSQL installation needs to be
+ uninstalled.
+
+ Uninstalling PostgreSQL
+
+
+
+ Open a terminal with administrative rights, i.e. log into a
+ bash shell with root privileges.
+
+
+
+ Execute the following command to check if you have a currently
+ running PostgreSQL database server:
+
+ ps -ef | grep post
+
+
+
+ Remove the installed PostgreSQL server (including the existing
+ postgres user):
+
+
+ This step is not necessary if the Enea Edge Management will
+ be using an external database (like MariaDB).
+
+
+ yum remove postgres\*
+rm -rf /var/lib/pgsql
+rm -f /etc/postgres-reg.ini
+userdel postgres
+
+
+
+ If you have multiple spindles, it is recommended to let the
+ application run off one and the database off the other. This will result
+ in optimum performance. It is also recommended that the swap disk be the
+ same as the one used for the application.
+
+ Assuming another spindle is used (/drive2 ) do
+ the following:
+
+
+
+ Create a folder which will host the database (e.g.
+ emsDatabase ).
+
+
+
+ Create a soft-link that will point to this folder:
+
+ ln -s /opt/ems/elementcenter/database /drive2/emsDatabase
+
+
+
+ Follow the installation steps for the Enea Edge Management
+ available in Installing the Enea Edge Management in
+ the
+ Manual.
+
+
+
+
+
+
+ uCPE Device Configuration
+
+
+ Determining the WAN and LAN ports
+
+ A typical whitebox comes with multiple physical network ports,
+ ready to be used. The user must determine the purpose and allocation of
+ each port. The allocation is later aligned with the software
+ configuration within the Web-installer.
+
+ A common way is to allocate the left ports to WANs and the right
+ ports to LANs. At least one port must be allocated to WAN and one to
+ LAN.
+
+
+
+ Determining the Device ID
+
+ Each uCPE device needs a unique identifier. This identifier is
+ used to match the registration in the Enea Edge Management and the
+ offline configuration of the uCPE device during ZTP (Zero Touch
+ Provisioning).
+
+ Select a text string to represent the uCPE device, e.g.
+ uCPE-1 or fwa-t1012vc_boston_1234 .
+ It can have any length and any type of characters with the exception of
+ quotation characters (' or ") or line terminators (\n or \r) which can
+ interfere with the JSON format of the
+ install_data.json file.
+
+
+
+ Configuring the BIOS
+
+ The factory configuration of the BIOS may not match the
+ requirements of Enea Edge Runtime. The BIOS configuration needs to be
+ reviewed and potentially reconfigured to prepare for a successful
+ installation.
+
+ Access the BIOS using a serial cable between the uCPE device and
+ the laptop, to review and configure the BIOS correctly. The whitebox
+ vendor is expected to provide the right serial cable for the box. A
+ terminal emulator (such as putty) is needed on the laptop.
+
+ Enable the following BIOS features/configurations:
+
+
+
+ EFI
+
+
+
+ Intel Virtualization Technology (VT-x)
+
+
+
+ Intel Virtualization Technology for Directed I/O (VT-d)
+
+
+
+ SR-IOV
+
+
+
+ The boot order may also need to be modified to support
+ installation and execution of the Enea Edge Runtime on the uCPE
+ device.
+
+ The following boot order is recommended for a base
+ configuration:
+
+
+
+ Boot from USB
+
+
+
+ Boot from Disk
+
+
+
+ By arranging the above boot order there is no need for a further
+ configuration of the BIOS during installation and deployment.
+
+
+
+
+ Preparing the Deployment
+
+
+ Installing the Enea Edge Management
+
+ The Enea Edge Management can be installed using a fresh
+ (first-time) configuration or using a backup file of a previous
+ installation, created within the Enea Edge Management GUI.
+
+
+ Fresh Installation of the Enea Edge Management
+
+ On the CentOS 7 server open a terminal, log into a bash shell
+ with the root account and perform the following:
+
+
+
+ Extract
+ Enea_Edge_Management_<version>-build<build_number>.tar.gz
+
+ The directory in which the archive has been unpacked will be
+ denoted as: <uCPEM-installdir> .
+
+
+
+ Enter <uCPEM-installdir>/dist .
+
+
+
+ Choose the target installation folder, e.g.
+ /opt/ems . Everything will be installed under a
+ folder called /ucpemanager within the target
+ installation folder.
+
+ The application files will be installed in
+ /opt/ems/ucpemanager/application . The database
+ will be installed in
+ /opt/ems/ucpemanager/database .
+
+
+
+ Run the following interactive command:
+
+ ./install.sh /opt/ems \
+Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
+
+ The default configuration values are specified in brackets.
+ If no other value is preferred and typed in, pressing
+ ENTER will keep the default values. When there
+ is an option within parentheses (i.e.Y/N), a value must be
+ specified.
+
+
+ The same configuration values set now will need to be
+ provided when upgrading or uninstalling the Enea Edge
+ Management.
+
+
+
+
+ Database Configurations:
+
+
+
+ Are you using the embedded PostgreSQL database?
+ [Y/N]: Y .
+
+
+
+ Specify the database process password
+ [postgres]:
+
+
+
+ Specify the database ID (or name)
+ [ucpemanager]:
+
+
+
+ Specify the database server port
+ [5432]:
+
+
+
+ Specify a database user name
+ [postgres]:
+
+
+
+ Specify a database password
+ [postgres]:
+
+
+
+ Specify the database startup thread pool size
+ [1]:
+
+
+
+
+
+ Service Configurations:
+
+
+
+ Specify a service username
+ [ucpemanager ]:
+
+
+
+ Specify a service password
+ [ucpemanager ]:
+
+
+
+
+
+ High Availability Configurations:
+
+
+
+ Specify the IP address of the local interface: The
+ CentOS 7 Server loopback address:
+ 127.0.0.1 .
+
+
+
+ Is this server part of a cluster? [Y/N]:
+ N .
+
+
+
+
+
+ Heap Configuration: Please enter the new
+ Maximum Heap Size [4g] :
+
+
+
+ Create the self-signed certificate: Specify IP
+ or domain name:
+
+
+ The certificate can be generated again by running the
+ createCertificate script from the
+ distribution folder.
+
+
+
+
+ This command will:
+
+
+
+ Extract the application files from the compressed
+ installation kit.
+
+
+
+ Install the bundled database.
+
+
+
+ Install the Enea Edge Management as a service with the
+ name ucpemanager .
+
+
+
+ Start the ucpemanager service
+
+
+
+
+
+ Using the IPv4 address of the CentOS 7 Server in a web
+ browser, running on the laptop, log into the Enea Edge Management
+ GUI using the default username and password:
+ admin/admin .
+
+
+
+
+ The IPv4 address of the CentOS 7 Server, connected to the same
+ network as the uCPE Devices, will be used as a configuration
+ parameter when setting up the uCPE devices.
+
+ If the CentOS 7 Server is installed behind NAT, the IPv4
+ address used will be the public IP of the NAT device and port
+ forwarding rules must be created to ensure the uCPE device can
+ access the Enea Edge Management. For more details, please see Firewall Configuration.
+
+
+
+
+ Installation of the Enea Edge Management using a System
+ Back-up
+
+ The Enea Edge Management can be restored if a backup file has
+ been previously created.
+
+ A backup file can be created by accessing the System menu, and clicking System Backup , from the Enea Edge Management
+ GUI. The resulting zip archive will be located in the
+ /opt/ems/ucpemanager/application/backup folder
+ and will be named
+ SystemBackup_MMMDD_YYYY_HHMM_SS.zip (e.g
+ System-Backup_Feb19_2013_2257_42.zip). Save the archive to another
+ location outside the Enea Edge Management installation folder for
+ future use.
+
+
+ The System Back-up file obtained from the Enea Edge Management
+ GUI (SystemBackup_MMMDD_YYYY_HHMM_SS.zip ) is
+ different from the snapshot obtained during a Enea Edge Management
+ Upgrade or Uninstall operation
+ (ucpemanager-Backup-YYYYddMMHHmm.tar.gz ) needed
+ for recovery of the Enea Edge Management. For more details, see
+ Restoring a previous Enea Edge
+ Management installation in the
+ Manual.
+
+
+ To install the Enea Edge Management with the restore option
+ provide an additional argument as shown below during
+ installation:
+
+ ./install.sh \
+/opt/ems Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz \
+SystemBackup_MMMDD_YYYY_HHMM_SS.zip
+
+
+
+
+ Preparing the USB stick for installation of the Enea Edge
+ Runtime
+
+ To install the Enea Edge Runtime, create a bootable USB stick with
+ the image you intend to install.
+
+ In the example below, step by step instructions are provided for
+ the CentOS 7 distribution. It's possible with the appropriate tools to
+ also use Windows OS or MacOS.
+
+
+ The .hddimg image is available in the
+ Enea_Edge_Runtime_Platform_
+ <processor>_<version>-build<build_number>.tar.gz
+ file you downloaded with your release.
+
+
+ Create a bootable USB stick
+ image
+
+
+
+ Copy the .hddimg image file provided by
+ Enea, into the CentOS 7 server.
+
+
+
+ Connect the USB stick to the CentOS 7 Server and identify the
+ USB device name given by the system with
+ lsblk :
+
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+sda 8:0 1 28.7G 0 disk
+sdb 8:0 0 111.8G 0 disk
+|-sdb1 8:1 0 111.8G 0 part
+
+
+
+ Copy the .hddimg image onto the USB
+ stick, e.g:
+
+ sudo dd if=./enea-nfv-access-<machine>.hddimg \
+of=/dev/sdb bs=4M conv=fsync
+
+ Where
+ enea-nfv-access-<machine>.hddimg is the
+ .hddimg file and sdb is the
+ assigned USB device name.
+
+
+
+
+
+ Preparing Physical Deployment for Installation
+
+
+ Preparing for Hardware Installation
+
+
+
+
+
+
+
+
+ While the uCPE device is powered off, in order to install and
+ configure the Enea Edge Runtime (using the prepared USB stick), connect
+ the laptop to a uCPE device LAN port. For this purpose, a Layer 2 switch
+ or direct cable connection can be used.
+
+
+
+ Installing Enea Edge - uCPE Device Installation
+
+ To initiate the installation of the Enea Edge Runtime do the
+ following:
+
+
+
+ Plug the USB stick into the uCPE device.
+
+
+
+ Power up the uCPE device and boot the USB stick.
+
+
+
+ The Web-installer application will start automatically and can
+ be accessed in a web browser on the laptop at
+ http://172.16.1.1 (port 80).
+
+
+
+ On the Requirements page of
+ the Web-installer, the user must confirm the current state of
+ installation prerequisites is inline with the desired state:
+
+
+
+ Requirements table. Minimum values apply to the
+ installation process only. For runtime operations, additional
+ resources should be available depending on the specific
+ workload. Requirements are color coded (green when met, red when
+ mandatory and not met, orange when optional and not met). The
+ Requirements table has the following fields:
+
+
+
+ Disk size (mandatory). 2GB or more are required for
+ the installation.
+
+
+
+ CPU cores (mandatory). 2 cores or more are required
+ for the installation.
+
+
+
+ RAM (mandatory). 2GB or more are required for the
+ installation.
+
+
+
+ VT-x (mandatory). Intel Virtualization Technology must
+ be enabled.
+
+
+
+ VT-d (optional, recommended). Intel Virtualization
+ Technology for Directed I/O should be enabled.
+
+
+
+ IOMMU Group separation (optional). If the hardware
+ does not support IOMMU Group separation, there are certain
+ limitations regarding how the vfio-pci
+ driver can be used. For more details, see the Known Issues and Limitations in
+ this Release in the
+ Manual.
+
+
+
+
+
+ Force installation checkbox. When enabled, the
+ installation can be performed even if some of the mandatory
+ requirements are not met or if non-fatal problems are detected
+ during the process.
+
+
+
+
+
+ On the Enea Edge Management
+ settings page of the Web-installer, the user must fill
+ in:
+
+
+
+ The static Enea Edge Management IP Address or FQDN. This can be
+ either:
+
+
+
+ The IP address of the Enea Edge Management host
+ machine, if the device can directly access it.
+
+
+
+ The IP address of the NAT device, if the Enea Edge
+ Management host is located behind a NAT. For more details,
+ please see Firewall
+ Configuration.
+
+
+
+ The Fully Qualified Domain Name (FQDN) of the Enea
+ uCPE Manager host machine.
+
+
+
+
+
+ The unique identifier of the uCPE device (called
+ "DeviceId" in this guide).
+
+
+
+ Customer Tags. They are used for Zero Touch Provisioning
+ (ZTP) and can be left empty for a base configuration. What can
+ be entered here (if needed), are the tag(s) specified when
+ creating an offline configuration in the Enea Edge Management. A
+ later addition of customer tags can only be done by reinstalling
+ the uCPE devices.
+
+
+
+
+
+ Connect the WAN cable to the uCPE device (see Figure 2). This
+ will be used as the uCPE management network interface, as described
+ below.
+
+
+
+ On the Network Setup page of
+ the Web-installer, the user must do the following:
+
+
+
+ Select a WAN interface to use as the management network
+ interface. This interface is used by the Enea Edge Management to
+ communicate with the uCPE device.
+
+
+
+ Plug-in additional WAN interfaces (if applicable) and
+ provide their Layer 3 configuration.
+
+
+
+
+
+ When the user has completed the configuration steps in the
+ Web-installer, Enea Edge Runtime is installed on the hard drive. At this
+ stage, the user should remove the USB stick and the LAN cable, and
+ shutdown the uCPE device. It will be started after necessary
+ configurations are done in the Enea Edge Management, as described
+ below.
+
+
+ If errors are detected during installation, full logs will be
+ available on the last page of the Web-installer. Please contact Enea
+ for log analysis. The system is not expected to be usable if errors are
+ reported during installation.
+
+ If the USB stick was booted in UEFI mode, a UEFI boot entry is
+ automatically created and the system will start booting from the hard
+ drive without further user configuration.
+
+
+
+
+ Preparing Physical Deployment for Execution
+
+
+ Preparing for Deployment Execution
+
+
+
+
+
+
+
+
+ The following network configuration is needed for managing the
+ uCPE device and service deployment:
+
+
+
+ Network connection between the server running the Enea Edge
+ Management and the laptop.
+
+
+
+ Network connection between the server running the Enea Edge
+ Management and the uCPE device.
+
+
+
+
+
+
+ Management of uCPE Devices
+
+ When the installation is complete the uCPE device can be managed in
+ the Enea Edge Management.
+
+
+ Add a default Offline Configuration
+
+ Zero Touch Provisioning is always turned on when a uCPE device
+ connects to the Enea Edge Management. To enable it in the Enea Edge
+ Management, an offline configuration needs to be registered for Day-0
+ configuration.
+
+
+ Day-0 configuration is a software lifecycle term referring to
+ early configurations used to put the uCPE device in an active state.
+ Day-1 Configurations are applied after Day-0 and set the uCPE device
+ and its service in an active state. Day-2 Configurations are live
+ configurations on the uCPE device and its service, applied after they
+ have been activated.
+
+
+ The offline configuration consists of data and parameters that are
+ meant to be automatically set when a uCPE device connects to the Enea
+ Edge Management for the first time. The configuration is typically
+ focused on setting up the network management of the uCPE device, e.g.
+ configuring network interfaces, WAN and LAN networking and service
+ chains.
+
+ For this base configuration, the offline configuration will be
+ left blank. The blank offline configuration can be filled with
+ user-specific values and data once the service is created, which is done
+ after the installation is complete.
+
+
+ If the offline configuration is not configured, an alarm will be
+ raised: Day-0 Config:ZTP:Major when the uCPE device
+ tries to connect to the Enea Edge Management, informing the user that
+ the ZTP setup failed for the uCPE device.
+
+
+ To create an offline
+ configuration
+
+ In a browser access the Enea Edge Management, open Applications and select Offline Config .
+
+
+
+ Create a new offline configuration in the GUI by selecting
+ the Add button and filling in the
+ mandatory fields: name ,
+ deviceVersion and
+ deviceId .
+
+ The name is user defined and can be set to any unique text
+ string identifying the configuration. The
+ deviceVersion must match the Enea Edge Runtime
+ version of the uCPE device and the deviceId
+ must be the previously set identifier of the uCPE device
+ (DeviceId).
+
+
+
+
+
+ Add a uCPE device to the Management System
+
+ In order to enroll a uCPE device in the management system and
+ establish a management connection, the user will add uCPE device
+ information in the Enea Edge Management. This is accomplished by going
+ to Devices , selecting Manage and then clicking the Add button.
+
+ The relevant parameters are:
+
+
+
+ Type. The type of device to
+ be added, i.e Enea universal CPE.
+
+
+
+ Name. The name by which the
+ uCPE device is referred to in the Enea Edge Management.
+ (Mandatory).
+
+
+
+ SSH Port. The NETCONF Port
+ used for communications. Default is set to 830.
+
+
+
+ SSH User Name. The user name
+ for SSH connectivity. Default user is root.
+
+
+
+ SSH Password. Leave this
+ blank.
+
+
+
+ Device Calls Home. This
+ checkbox indicates the direction of uCPE device communications. For
+ a base configuration, leave this flag unchecked.
+
+
+
+ Device ID. The unique
+ identifier of the uCPE device. (Mandatory).
+
+
+
+ For more details concerning Device Calls Home, please see Device Call Home Connection for
+ Deployment behind NAT in the
+ Manual.
+
+
+
+ Booting the uCPE device and adding it to the Map
+
+ When connectivity is established with the Enea Edge Management and
+ a uCPE device is already registered with a matching Device
+ ID , the installation is complete, and the connection is
+ established.
+
+ When a uCPE device is registered it can be manually added to the
+ map for overview. Right-click on the
+ map and select Place Device to put the
+ uCPE device on the map.
+
+ In case of management connection failure (e.g. due to a
+ misconfiguration), the uCPE device status will be seen as RED
+ (disconnected) in the Enea Edge Management. The uCPE device
+ configuration can be corrected by removing the WAN cable(s),
+ reconnecting the laptop to the LAN interface of the uCPE device and
+ rebooting it. At this point, the Web-installer can be accessed from the
+ laptop as described in Installing Enea Edge - uCPE Device
+ installation in the
+ Manual.
+
+
+
+
+ uCPE Device Monitorization and Control
+
+ Once the uCPE device is connected to the Enea Edge Management, it is
+ ready for central management. Two important functions available in the
+ Enea Edge Management GUI are alarm checking and resource
+ allocation.
+
+
+ Checking Alarms
+
+ The Enea Edge Management dashboard presents alarms in a specific
+ window on the front page.
+
+ An alarm can be easily triggered by disconnecting and reconnecting
+ the WAN ethernet cable from the uCPE device. The management system will
+ detect the broken link and raise an alarm: Device
+ Disconnected::Critical .
+
+ A separate Alarm Management window can be accessed from the Enea
+ Edge Management menu for in-depth access and programming of Alarms and
+ Events.
+
+
+
+ Checking uCPE device Resource Allocation
+
+ When the uCPE device is connected to the Enea Edge Management it
+ is of interest to check the amount of hardware resources in use.
+
+ To check CPU, RAM and disk utilization simply select the uCPE
+ device and go to the Virtual Machines
+ tab in the map view. The same view will show active VNFs running on the
+ uCPE device once instantiated.
+
+
+
+ Accessing the uCPE device CLI
+
+ As a final check to make sure the uCPE device was installed and
+ configured correctly, access the uCPE device Linux CLI by selecting the
+ uCPE device on the map and using the SSH
+ button from the panel. A new window will appear for CLI
+ access. The default user and password are root and
+ blank, respectively.
+
+ This is a pure Linux CLI providing access to standard Linux CLI
+ commands. The CLI is a central feature for running custom
+ scripting.
+
+
+ In case the uCPE device was installed behind a NAT device, the
+ reverse SSH connection will be used. For more details, please see
+ Device Call Home Connection for
+ deployment behind NAT in the
+ Manual.
+
+
+
+
diff --git a/doc/book-enea-edge-getting-started/doc/introduction.xml b/doc/book-enea-edge-getting-started/doc/introduction.xml
new file mode 100644
index 0000000..4dec1e1
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/introduction.xml
@@ -0,0 +1,264 @@
+
+
+
+ Overview
+
+ This document describes the Enea Edge and provides installation
+ steps for deploying a base configuration in order to create:
+
+
+
+ A functional Enea Edge Management installation ready to manage uCPE
+ devices.
+
+
+
+ One or several managed uCPE devices, ready to host network
+ services, using one wired WAN and one wired LAN connection.
+
+
+
+ Extended deployment and configuration options are also detailed in the
+ following chapters.
+
+
+ Enea Edge
+
+ Enea Edge for universal Customer Premise Equipment (uCPE) is a
+ virtualization and management platform, which allows end-users to onboard,
+ instantiate, and run third-party VNFs onto their systems. It is comprised
+ of two major components working in close cooperation:
+
+
+
+ The Enea Edge Runtime, which acts as the host
+ for Virtualized Network Functions (VNFs) and provides management over
+ NETCONF.
+
+
+
+ The Enea Edge Management, a solution that runs on an external
+ server, used for VNF Management and managing large numbers of uCPE
+ devices.
+
+
+
+ In addition, Enea Edge includes a framework for
+ automation and testing. More information can be found in
+ .
+
+ Details concerning release content, including documentation
+ structure, are provided in the manual included
+ with your release.
+
+
+ Enea Edge Runtime
+
+ Enea Edge Runtime is a lightweight,
+ multi-architecture virtualization platform built on de-facto standards
+ in an SDN/NFV ecosystem. It is designed for a high networking
+ performance with minimal hardware footprint, by only providing relevant
+ functionalties and technologies.
+
+ Virtualization methods include Virtual Machines (KVM / QEMU) and
+ container(s) (Docker). High networking throughput and low latency are
+ ensured by accelerated data plane relying on technologies like DPDK,
+ OVS-DPDK and SR-IOV/PCI-Passthrough. Key functionalities, such as
+ platform software management, virtualized networking, VNFs life-cycle
+ management and FCAPS are provided through the YANG-modelled NETCONF
+ protocol.
+
+
+ VNF Space
+
+
+
+
+
+
+
+
+
+
+ Enea Edge Management
+
+ The Enea Edge Management is centralized control system providing
+ uCPEs domain management capabilities through a GUI and REST API. It can
+ be deployed on a host or a virtual machine running 64-bit CentOS 7 on an
+ x86 platform. The Enea Edge Management uses a southbound NETCONF protocol
+ to connect and manage uCPE devices.
+
+ The Enea Edge Management provides the following key features:
+
+
+
+ Enea Edge Runtime Software Management
+
+
+
+ VNF Onboarding
+
+
+
+ VNF Management
+
+
+
+ FCAPS
+
+
+
+ Zero Touch Provisioning
+
+
+
+ Alarms / Events management and monitoring
+
+
+
+
+
+
+ Definitions and Acronyms
+
+
+ Definitions
+
+
+ Definitions
+
+
+
+
+
+
+
+
+ Enea Edge
+
+ The Enea Edge Runtime and the Enea Edge
+ Management.
+
+
+
+ Enea Edge Runtime
+
+ A lightweight, multi-architecture virtualization
+ platform, supporting Virtual Machines.
+
+
+
+ Enea Edge Management
+
+ Enea Universal Customer Premises Equipment
+ Manager.
+
+
+
+ uCPE device
+
+ A whitebox running the Enea Edge
+ Runtime.
+
+
+
+
+
+
+
+ Acronyms
+
+
+ Acronyms
+
+
+
+
+
+
+
+
+ API
+
+ Application Programming Interface.
+
+
+
+ DPDK
+
+ Data Plane Development Kit.
+
+
+
+ EFI
+
+ Extensible Firmware Interface.
+
+
+
+ FCAPS
+
+ Fault-management, Configuration, Accounting, Performance
+ and Security.
+
+
+
+ NETCONF
+
+ Network Configuration Protocol.
+
+
+
+ NFV
+
+ Network Functions Virtualization.
+
+
+
+ OVS
+
+ Open vSwitch.
+
+
+
+ UEFI
+
+ Unified Extensible Firmware Interface.
+
+
+
+ SR-IOV
+
+ Single Root Input/Output Virtualization.
+
+
+
+ PCI
+
+ Peripheral Component Interconnect.
+
+
+
+ REST
+
+ Representational State Transfer.
+
+
+
+ VNF
+
+ Virtual Network Function.
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/log_collector.xml b/doc/book-enea-edge-getting-started/doc/log_collector.xml
new file mode 100644
index 0000000..baa1340
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/log_collector.xml
@@ -0,0 +1,401 @@
+
+
+ Using the Log Collector
+
+ Troubleshooting problems on the uCPE device require an analysis of a
+ set of information i.e. logs collected from the uCPE device and/or the Enea
+ Edge Management. The following information describes how the log collection
+ mechanism works.
+
+
+ Log collecting using the Enea Edge Management
+
+ The Enea Edge Management allows for collecting a set of logs and state
+ information from a uCPE device.
+
+
+ Collecting the Logs
+
+ Collect the necessary log files and system details, then create an
+ archive (a tar file) on the uCPE device in the
+ /var/odm/log/archives folder:
+
+
+
+ Access Operations and then
+ select Collect Debug Logs .
+
+
+
+ Provide a file name in the new window.
+
+
+
+ Press the Execute button.
+
+ A success message is shown in the same window as shown below.
+ At this moment, the process of collecting logs on the uCPE device
+ starts.
+
+
+
+ Collecting Debug Logs
+
+
+
+
+
+
+
+
+
+
+ It might take some time for the archive to be created. When the
+ operation completes, a "CollectLogsComplete" notification is sent from
+ the uCPE device to the Enea Edge Management. This can be viewed in the
+ GUI in the Faults menu, after selecting
+Events .
+
+
+ Collecting Debug Logs
+
+
+
+
+
+
+
+
+
+
+
+ View collected Logs
+
+ A list with the archives containing already collected logs will be
+ shown in the Device File Listing table:
+
+
+
+ Access Files and then the
+Download button.
+
+
+
+ Press the List button.
+
+
+ Device File Listing Table
+
+
+
+
+
+
+
+
+
+
+
+ If the filename you specified does not appear, it might still be
+ in the process of creation. Click on the Refresh
+ icon at the bottom of the table until you can see the desired file
+ listing.
+
+
+
+
+ Downloading Logs from the uCPE Device
+
+ This option transfers a debug file archive from the uCPE device to
+ Enea Edge Management.
+
+
+
+ Access Files and choose the
+ Download button.
+
+
+
+ Press the List button.
+
+
+
+ In the Device File Listing table, select
+ the archive you want to download from the uCPE device to Enea Edge
+ Management.
+
+
+
+ Press the Download from Device
+ button.
+
+ The archive will be downloaded from the uCPE device and stored
+ on the Enea Edge Management.
+
+
+
+
+ The archive will not be deleted from the uCPE device after
+ download.
+
+
+
+
+ Downloading collected Logs locally
+
+ This option downloads a logs archive from the Enea Edge Management to
+ a local (user) machine for analysis. The archive must first be available
+ in the Enea Edge Management in order to be downloaded.
+
+
+
+ Access the Devices menu and select
+Files .
+
+
+
+ Select the Downloaded Files tab.
+
+
+
+ Select an archive from the Downloaded Files
+ table.
+
+
+
+ Click the Download button.
+
+ The file will be downloaded in browser's download
+ folder.
+
+
+ Downloaded Files Table
+
+
+
+
+
+
+
+
+
+
+
+
+ Deleting a Logs Archive from a uCPE device
+
+ Use this option when you want to delete unnecessary collected logs
+ on the uCPE device.
+
+
+
+ Access Files and then click the
+ Download button.
+
+
+
+ Press the List button.
+
+
+
+ In the Device File Listing table, select
+ the archive you want to delete from the uCPE device.
+
+
+
+ Press the Delete button.
+
+ The archive will be deleted from the uCPE device and the table
+ will be updated.
+
+
+
+ The same can be achieved using these alternative options:
+
+
+
+ Access the Operations menu and
+select Delete Debug Log Archive .
+
+
+
+ Provide a file name in the new window.
+
+
+
+ Press the Execute button.
+
+ A success message is displayed if the file is deleted from the
+ uCPE device correctly.
+
+
+
+
+
+ Deleting a Logs Archive from the Enea Edge Management
+
+ This option deletes a logs archive from the Enea Edge
+ Management.
+
+
+
+ Access the Devices menu, then select
+ Files .
+
+
+
+ Select the Downloaded Files tab.
+
+
+
+ Select an archive from the Downloaded Files
+table.
+
+
+
+ Click the Delete button.
+
+ The file will be deleted from the Enea Edge Management and the
+ table will be updated.
+
+
+
+
+ Deleting the logs file from the Enea Edge Management does not
+ affect the file located on the uCPE device.
+
+
+
+
+ Enabling/Disabling of the Log Collector via Permissions
+
+ To disable the ability to access/download the uCPE device's
+ debug-log files from the Enea Edge Management, the appropriate permissions
+ must be changed:
+
+
+
+ Access the Security menu,
+then select Configuration .
+
+
+
+ Click the Security Groups tab.
+
+
+
+ Click the desired group.
+
+
+
+ Click the Permissions tab on the right
+ side.
+
+
+
+ Click the Devices tab like in the image
+ below.
+
+
+
+ Change the Device File Management option to
+ none to disable the feature.
+
+
+
+
+ Device File Management
+
+
+
+
+
+
+
+
+
+
+ Downloading Enea Edge Management Logs
+
+ Often, sending the Enea Edge Management logs together with collected
+ uCPE device logs to the support team provides important information for
+ troubleshooting (especially in cases of connectivity issues with the
+ uCPE device and error popups).
+
+ Enea Edge Management log files are located in
+ application/logs/ in the Enea Edge Management's
+ installation folder
+ (e.g./opt/ems/ucpemanager/application/logs ). They
+ can be copied from that location, or they can be downloaded using the
+ Enea Edge Management GUI by performing the following:
+
+
+
+ Access Test , then Debug
+ Settings and select the Log Files tab.
+
+
+
+ Select the desired log file
+ (ucpemanager.log or
+ watchdog.log ) and press the
+ Download button.
+
+
+
+ A new (blank) popup window opens and the file is downloaded
+ locally. This popup can be closed after the download.
+
+
+
+ Repeat steps 2. And 3. Until all the desired log files have
+ been downloaded
+
+
+
+
+ Debug Settings
+
+
+
+
+
+
+
+
+
+
+
+ Log collecting without using the Enea Edge Management
+
+ Log collection from uCPE Devices can also be done when there is no
+ Enea Edge Management connection. A SSH connection to uCPE Device is needed
+ for use of the log collector script, which can be found in the uCPE Device
+ file system in /usr/local/enea/ .
+
+ The Log collector script takes relevant information about the system
+ and collects it in an archive:
+
+ ./log-collector.sh -p <LOG_PATHh> -n <ARCHIVE_NAME>
+
+ Where -p is the path where the log archive will
+ be saved, -n is the archive name.
+
+
+ If -p is not provided, the default path will be
+ used: /var/logcollector . If -n is
+ not provided, the default name will be used:
+ log_archive_<timestamp>.tar.gz .
+
+
+ To access the help menu of the script:
+
+ ./log-collector.sh -h
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/net_config_options.xml b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
new file mode 100644
index 0000000..dae5b36
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
@@ -0,0 +1,886 @@
+
+
+ Network Configuration Options
+
+ Various Advanced Network Configuration options can be done from Enea
+ Edge Management GUI.
+
+
+ Device Call Home Connection for Deployment behind NAT
+
+ The Device Call Home option enables the initiation of the connection
+ between the uCPE Device and the Enea Edge Management, from the uCPE
+ device. The Device Call Home option is required when deploying a uCPE
+ device behind NAT since the IP address of the uCPE device is hidden for
+ the Enea Edge Management.
+
+ Enable Device Call Home by marking the Device Call Home checkbox
+ when registering the uCPE device in Enea Edge Management. When using this
+ mechanism, the device will initiate a connection to the Enea Edge
+ Management for NETCONF traffic (over SSH), while the Enea Edge Management
+ waits for a device connection.
+
+
+
+ uCPE Device Network Configuration
+
+ The following describes the steps required for setting up the
+ virtualization infrastructure, ensuring that a uCPE device has networking
+ setup for virtualized service deployment. Networking is enabled by
+ selecting physical interfaces to be used by virtualized networking and
+ creating different types of bridges to enable VNF communication.
+
+ The Zero Touch Provisioning mechanism is also touched upon, as
+ alternative to manual configuration of the virtualization
+ infrastructure.
+
+
+ Configure DPDK
+
+ DPDK is an important functionality for accelerating networking
+ performance. The DPDK is enabled by default and should be utilized in
+ most configurations.
+
+ In use cases where CPU capacity is very limited, disabling DPDK
+ can free up CPU capacity and overall performance can improve. Navigate
+ to Configuration , then DPDK and deselect Enable
+ DPDK to disable the DPDK.
+
+
+ Disabling the DPDK cannot be done after other network
+ configurations have been made.
+
+
+ In Configuration , select
+ DPDK where DPDK resources can also be
+ configured such as:
+
+
+
+ LCore Mask . Allocated cores
+ for non-datapath OVS-DPDK threads (CPU core bitmask). Default:
+ 0x2.
+
+
+
+ PMD CPU Mask . Allocated cores
+ for datapath processing (CPU core bitmask). Default: 0x4.
+
+
+
+ Socket Memory . Hugepage
+ memory allocated for DPDK. Default: 1494.
+
+
+
+
+
+ Configure External Interfaces
+
+ Once a management connection with the uCPE device has been
+ established by using any of the supported methods, the virtualization
+ networking infrastructure can be configured either manually or by using
+ Zero Touch Provisioning.
+
+ Available network interfaces can be added to the management
+ system, for use by the networking virtualization infrastructure.
+
+ In order to make physical network interfaces available to the
+ virtualization infrastructure and VNFs, they must be configured into the
+ management system.
+
+ To add an interface into the Enea Edge Management, select the uCPE
+ device, then from the top toolbar select Configuration , then External Interfaces , Configuration , and click the Add button. The available Interface types are
+ detailed below.
+
+
+ DPDK Interface Type
+
+ Configuring a physical interface in DPDK mode will require a
+ DPDK-based application (e.g. OVS-DPDK) in order to access and use the
+ interface. An interface set as DPDK can be attached to an OVS-DPDK
+ bridge.
+
+
+ Make sure the Enable DPDK
+ checkbox is selected by accessing Device , Configuration and choosing DPDK , otherwise no interface can be assigned
+ as DPDK.
+
+
+ To add a DPDK interface under the management system, set
+ appropriate values for the following fields:
+
+
+
+ Source: name of the physical interface.
+
+
+
+ Networking-type: dpdk
+
+
+
+ Dpdk-type: the kernel module that allows user space access
+ to the physical interface. Either the vfio-pci
+ (most commonly used type) or the igb_uio driver
+ can be used.
+
+
+
+
+
+ SR-IOV Interface Type
+
+ SR-IOV technology allows for the creation of a number of virtual
+ functions on the host interface, which can be used by VNFs running on
+ the uCPE device.
+
+ For SR-IOV mode configuration, the user must set values for the
+ following fields:
+
+
+
+ Source: name of the physical interface.
+
+
+
+ Networking-type: srIov
+
+
+
+ sriov-mode: adapter-pool
+
+
+
+ sriov-num-vfs: the number of virtual functions to
+ create.
+
+
+
+
+
+ Standard Interface Type
+
+ Some of the physical network interfaces available on a uCPE
+ device, including Ethernet interfaces, do not have DPDK or SR-IOV
+ support. Instead, the Linux kernel driver has to be used.
+
+ To add Standard Interfaces under the management system, the user
+ must set values for the following fields:
+
+
+
+ Source: the name of physical interface.
+
+
+
+ Networking-type: standard.
+
+
+
+
+
+ Wan Interface Type
+
+ WAN interfaces configured during the installation of the uCPE
+ device are automatically added in the Enea Edge Management as type
+ wan . The WAN interface used for management of the
+ uCPE device is marked with the Management property
+ set to True .
+
+ If a WAN interface is to be assigned for use by a VNF, it must
+ be changed into another interface type depending on the type of
+ connection that will be used. The management WAN interface cannot be
+ changed to a different type. It is automatically used when an In-band
+ management bridge is created.
+
+ How to Edit the Configuration of a Wan
+ Interface
+
+
+
+ To edit an interface configuration type from the Enea Edge
+ Management, select the uCPE device, then from the top toolbar
+ select the Configuration menu,
+ then External Interfaces and
+ Configuration . The already
+ configured interfaces are displayed here, as seen in the figure
+ above.
+
+
+
+ In order to edit an already configured interface, (as in the
+ example popup shown below, a WAN interface) double click on the
+ desired one and a popup will appear. A different popup appears for
+ each type of interface. From the Host
+ Interface window, a user can change the networking type
+ and the IP address assignment:
+
+
+ Editing an Interface
+
+
+
+
+
+
+
+
+
+
+
+ When changing the address-assignment from
+ static to DHCP, if any of the ip-address ,
+ netmask or gateway fields have
+ invalid values a validation error will be triggered. These fields
+ must be empty or have the valid values for their respective address
+ assignment.
+
+
+
+
+ Wap Interface Type
+
+ Wireless Access Point (Wap) interfaces are used to create
+ Wireless Access Points. Only interfaces with
+ wap-capable capabilities can be added as WAP
+ interfaces.
+
+ How to edit the Configuration of a Wap
+ Interface
+
+
+
+ To edit an interface configuration from the Enea Edge
+ Management, select the uCPE device, then from the top toolbar
+ select the Configuration menu
+ then External Interfaces and
+ select Configuration . The already
+ configured interfaces will be displayed here.
+
+
+
+ In order to edit an already configured interface, (as in the
+ example popup shown below, a WAP interface) double click on the
+ desired one and a pop-up will appear. A different pop-up appears
+ for each type of interface. From the Host
+ Interface window, the following parameters are
+ configurable:
+
+
+
+ Country Code: the country code, a 2 letter
+ ISO3166-alpha2 identifier.
+
+
+
+ Wireless Band: 2.4 GHz or 5 GHz. Depending on the band
+ selection, the correct Wireless Mode and
+ Radio Channel must be provided.
+
+
+
+
+ Editing an Interface
+
+
+
+
+
+
+
+
+
+
+
+ Correct Country Code
+ selection is mandatory. All configuration options are available in
+ the Enea Edge Management GUI but only the Radio Settings that
+ conform with the selected country's official regulatory laws will be
+ applied when the Wireless AP is started on the uCPE Device.
+
+
+
+
+ Manual Configuration
+
+ For Manual Configuration of uCPE networking, select the uCPE
+ device first, then access the Configuration menu, and choose External Interfaces , where a list of available
+ network interfaces and their capabilities can be found.
+
+ After networking interfaces have been added to the Enea Edge
+ Management, the user can change the interface type (DPDK, SR-IOV,
+ Standard, WAN, WAP).
+
+
+ Configuration of External Interfaces
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Zero Touch Provisioning - Creating an Offline Configuration
+
+ Zero-Touch Provisioning (ZTP) refers to the process of when a device
+ starts up for the first time and its initial configuration is pushed down
+ by an external management system, so that it is setup for proper operation
+ without additional manual intervention by an operator. ZTP is an
+ alternative to Manual configuration.
+
+ A variety of operations can occur as part of ZTP such as initial
+ device setup, configuration of managed objects, etc. The goal is to set up
+ a device to the maximum possible extent without forcing an operator to be
+ physically present (initially) to manage the device.
+
+ An offline configuration is usually prepared in advance for the Enea
+ Edge Management to setup the virtualization infrastructure on the uCPE
+ device, as soon as a device enrolls into the management system.
+
+
+ Offline Configuration
+
+ The Offline Configuration subsystem is used to pre-populate a
+ configuration for a device that will be brought under management at a
+ future point in time. When creating an offline configuration store a
+ Device ID can be specified. This ID uniquely
+ identifies the device to be initialized.
+
+ Alternatively, a wildcard can be used in the Device
+ ID field, which results in a configuration being pushed on all
+ uCPE devices upon their initial connection towards the Enea Edge
+ Management.
+
+ If the offline configuration is not configured for a uCPE device,
+ an alarm will be raised: Day-0 Config:ZTP:Major ,
+ which occurs when the uCPE device connects to the Enea Edge Management
+ informing that the ZTP setup failed for the specific uCPE device.
+
+ To create an offline configuration, select from the top toolbar
+ the Applications menu, then Offline Config and choose Add . The following fields should be
+ filled:
+
+
+
+ Name: name of the device.
+
+
+
+ Device type: Enea universal CPE.
+
+
+
+ DeviceVersion:
+
+
+
+ Config Set: uCPE Config
+
+
+
+ Device ID: device ID or a wildcard(*).
+
+
+
+ Device Grouping Tags: a tag to group devices. These tags match
+ the customer tags provided during the installation of the
+ device.
+
+
+
+ The Name is user defined and can be set to any unique text string
+ identifying the configuration. The Device Version will match the Enea
+ Edge version of the uCPE device and the Device ID will be set to the
+ previously set identifier of the uCPE device.
+
+ When a device connects to the Enea Edge Management for the first
+ time, it checks the device to see if it has been Zero Touch Provisioned
+ (ZTP). If not, it looks for an offline configuration that matches these
+ values, in the following order:
+
+
+
+ The Device ID.
+
+
+
+ The set of tags.
+
+
+
+ A "*" for Device ID (wildcard).
+
+
+
+ If a match is found, the offline configuration is sent to the
+ device as part of Zero-Touch-Provisioning.
+
+ After creating the Offline Config Store, access the device by
+ selecting Applications , then offline config and clicking Config App , to provision it with the required
+ initial configuration. This operation mirrors what happens during manual
+ configuration described previously.
+
+
+ The ZTP will only be triggered the first time a uCPE device
+ connects to the Enea Edge Management. Just changing an offline
+ configuration will not push the new changes to the device. If an
+ offline configuration is changed after uCPE device registration, a
+ factory reset can be executed to force a new ZTP to execute. Select
+ the device, then access the Operations menu and select factory reset .
+
+
+
+
+
+ Custom Scripts for Custom Networking Configurations
+
+ The custom scripts feature allows users to execute user-defined
+ scripts on the uCPE device at various times.This allows for more flexible
+ and advanced configurations such as a LTE modem configuration, advanced
+ network configurations or OVS flow rule programming at any time.
+
+
+ Uploading Scripts
+
+ The scripts need to be uploaded to the Enea Edge Management prior
+ to use. When uploading scripts to the Enea Edge Management make sure to
+ select the right script type.
+
+ The following script types are supported:
+
+
+
+ Once-before-startup . This script will only
+ execute once after the system has rebooted, prior to processing any
+ device configuration.
+
+
+
+ Always-before-startup . This script will
+ always execute after the system has rebooted, prior to processing
+ any device configuration.
+
+
+
+ Once-after-startup . The script will always
+ execute after the system has rebooted, after all device
+ configuration processes have completed.
+
+
+
+ Always-after-startup . This script will
+ always execute after all device configuration processes have
+ completed after the system has rebooted.
+
+
+
+
+ After a factory reset, any of the
+ Once-before-* or Once-after-*
+ scripts will be re-run as described above.
+
+
+ Follow the instruction below to upload scripts:
+
+
+
+ Access the Devices menu, then
+ Custom Scripts and choose Configure .
+
+
+
+ Select Upload to EMS .
+
+
+
+ In the Script Type menu,
+ select the type the uploaded script should have.
+
+
+
+ Press Choose File to select
+ the scripts needed, and then click Send .
+
+
+
+
+
+ Removing Scripts
+
+ Follow the instruction below to remove scripts:
+
+
+
+ Access the Devices menu, then
+ Custom Scripts and select Configure .
+
+
+
+ Select the script you want to delete from the Uploaded Scripts tab and then click Delete , which will remove the script
+ immediately from the Enea Edge Management.
+
+
+
+
+
+
+
+ Running the Scripts
+
+ How to run Custom Scripts
+
+
+
+ Access the Devices menu,
+ choose Custom Scripts and select
+ Apply Scripts .
+
+
+
+ In the Script Config Screen
+ pop up, select the devices from the device(s) chooser list on which
+ to run the scripts. Press the >
+ button to move the devices to the right side of the chooser, which
+ is the list of devices that will execute the selected
+ scripts.
+
+
+
+ Select the scripts from the list under the device(s) chooser
+ by pressing the + button.
+
+
+
+ In the pop-up window, select the scripts from the list. If
+ there are no scripts to select, then there is no script uploaded
+ with that particular type. Upload the script(s) needed and try
+ again.
+
+
+
+ Check the Reboot devices
+ checkbox if you want to reboot and execute the scripts at once and
+ then select ok .
+
+
+ The status of execution for the scripts can be seen by
+ accessing Fault , opening the
+ Events screen and filtering by
+ device and/or the event name
+ CustomScriptExecuted .
+
+
+
+
+
+
+
+ Wireless Access Point
+
+ The Wireless AP Screen from the Enea Edge Management Configuration
+ menu allows users to configure a Wireless Access Point .
+ A wap-capable interface and a LAN bridge must be added
+ before doing the Wireless AP configuration. For more details see sections
+ Wap interface Type and Data-plane bridge.
+
+ The following parameters are configurable:
+
+
+
+ SSID: the Wireless network name - any string with a max. length
+ of 32 octets.
+
+
+
+ Interface Name: the wap-capable external
+ interface.
+
+
+
+ Lan Bridge: the LAN bridge where wireless clients will be
+ hosted.
+
+
+
+ WAP Security Mode: open or
+ wpa2Psk . When choosing wpa2Psk ,
+ a password and an encryption
+ must be provided. The password can be any string
+ with a minimum length of 8 and a maximum length of 63
+ characters.
+
+
+
+ DHCP Server: disabled or
+ enabled . When enabled is
+ selected, the range of IPs (IP Address Start -
+ IP Address End ), Netmask and
+ Gateway values must be provided.
+
+
+
+
+ Wireless AP
+
+
+
+
+
+
+
+
+
+ Only a single Wireless AP is allowed on a physical interface. The
+ validation of the wap-capable interface is done when
+ adding the Wireless AP, so, in case of an error, the parameters of the
+ wap-capable interface must be rechecked. This can be
+ done by accessing the Configuration
+ menu and selecting External
+ Interfaces .
+
+
+
diff --git a/doc/book-enea-edge-getting-started/doc/troubleshooting.xml b/doc/book-enea-edge-getting-started/doc/troubleshooting.xml
new file mode 100644
index 0000000..4984a35
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/troubleshooting.xml
@@ -0,0 +1,226 @@
+
+
+ Troubleshooting and Recovery
+
+ In all scenarios where possible, collect the logs for debugging. More
+ information on log collecting can be found in Using the Log Collector in the
+ Manual.
+
+ The following is a small list of possible Enea Edge problems, and
+ their solutions. If you encounter other issues or can't get Enea Edge to
+ work successfully after consulting the information below, please use the
+ Enea Support Team Form, available in the
+ Manual
+ downloaded with your release.
+
+
+ Troubleshooting and Recovery
+
+
+
+
+
+
+ Enea Edge Problem
+
+ Solution
+
+
+
+
+
+ A uCPE device fails to connect to the Enea Edge Management
+ after installation.
+
+ If the uCPE device is not able to connect to the Enea Edge
+ Management after an installation, the Web-installer application is
+ started automatically on the uCPE device to change the configuration
+ via a web browser. Please see Booting the uCPE device and adding
+ it to the Map in the
+ Manual.
+
+
+
+ The uCPE Device cannot boot after an upgrade.
+
+
+
+ Perform a hardware reboot of the uCPE Device and select
+ the previous Enea Edge Runtime image from the GRUB menu. This
+ action assumes physical access to the uCPE device.
+
+
+
+ Reinitiate the Upgrade procedure according to the steps
+ in section uCPE device upgrades in the
+
+ Manual.
+
+
+
+
+
+ After a failed uCPE device upgrade the previous Enea Edge
+ image (from the GRUB menu) does not boot.
+
+ Reinstall Enea Edge on the uCPE device and redeploy the
+ initial configuration and virtualized services, by following the
+ steps in Installing Enea Edge - uCPE Device
+ installation in the
+ Manual.
+
+
+
+ The Enea Edge Management upgrade fails and a working snapshot
+ is available.
+
+ If a working snapshot obtained during a previous Upgrade or
+ Uninstall is available
+ (ucpemanager-Backup-YYYYddMMHHmm.tar.gz ):
+
+
+ Cleanup the current upgrade attempt with:
+
+ ./cleanup.sh /opt/ems
+
+
+
+ Restore the previous installation as described in Restoring a previous
+ Enea Edge Management installation in the
+ Manual.
+
+
+
+
+
+ The Enea Edge Management upgrade fails and no working
+ snapshot is available, but a System Back-up file exists.
+
+
+
+ Cleanup the current upgrade attempt with:
+
+ ./cleanup.sh /opt/ems
+
+
+
+ Perform an installation with the restore option of a
+ previous Enea Edge Management configuration as described in
+ Installation of the
+ Enea Edge Management using a System Back-up in the
+ Manual.
+
+
+
+
+
+ The uCPE device is booted, the ssh connection is available
+ but the device is not connected to the Enea Edge Management.
+
+
+
+ Perform a hardware reboot on the uCPE device to
+ reinitiate the connection mechanism.
+
+
+
+ Use the Reconnect
+ button from the Enea Edge Management's GUI.
+
+
+
+ Connect to uCPE Device console and run the factory reset
+ script:
+
+ /usr/local/odm/bin/factory_reset.sh
+
+
+
+ If the above actions do not work, reinstall and
+ reconfigure the device using the steps provided in Installing Enea Edge - uCPE
+ Device installation in the
+ Manual.
+
+
+
+
+
+ The SSH connection to the device cannot be
+ established.
+
+ Perform a hardware reboot on the uCPE device. If the problem
+ is not fixed, reinstall and reconfigure the device using the steps
+ provided in Installing Enea Edge - uCPE Device
+ installation in the
+ Manual.
+
+
+
+ The VNF Service is not working as expected after
+ reconfiguration (e.g. a VNF chain is malfunctioning).
+
+
+
+ Undo all flows and/or configuration changes in order to
+ move the system to a previously working configuration.
+
+
+
+ Reboot the device by accessing Operations and then selecting Reboot from within the Enea Edge
+ Management.
+
+
+
+ If the above actions do not work, redeploy all services.
+ This is done by cleaning up the existing configuration by
+ accessing Operations , then
+ selecting Factory Reset for a
+ specific device and redeploying the VNF services.
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml b/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
new file mode 100644
index 0000000..641775d
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
@@ -0,0 +1,588 @@
+
+
+ Upgrading Enea Edge
+
+ Enea provides regular releases that will require the upgrading of Enea
+ Edge components. The Enea Edge Management must be upgraded first, followed
+ by upgrading the Enea Edge Runtime on the uCPE devices.
+
+
+ Upgrading the Enea Edge Management
+
+
+ It is recommended to create a system backup by accessing System and selecting System
+ Backup from the Enea Edge Management GUI, for recovery in
+ case of an upgrade failure.
+
+
+
+
+ Extract the
+ Enea_Edge_Management_<version>-build<build_number>.tar.gz
+ folder.
+
+ The directory in which the archive has been unpacked will be
+ denoted as <uCPEM-installdir> .
+
+
+
+ Enter <uCPEM-installdir>/dist .
+
+
+
+ Run the following command with the root account and change
+ /opt/ems to the correct location of the Enea Edge
+ Management installation:
+
+ ./upgrade.sh /opt/ems \
+Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
+
+
+
+ Running this command will:
+
+
+
+ Stop the currently running ucpemanager
+ service.
+
+
+
+ Create a compressed file of the ucpemanager
+ application folder
+ (ucpemanager-Back-up-YYYYddMMHHmm.tar.gz ), which
+ contains a snapshot of the existing installation in the
+ <uCPEM-installdir>/dist directory.
+
+
+ The snapshot file created during the upgrade can be used for
+ restoring the Enea Edge Management.
+
+
+
+
+ Extract the application files from the specified compressed
+ install kit.
+
+
+
+ Start the ucpemanager service.
+
+
+
+ Fresh Installation of the Enea Edge Management
+ in the
+ Manual contains information about the input required to be entered during
+ the execution of the upgrade script.
+
+ For an example on how to upgrade an Enea Edge Management installation
+ in a High Availability setup, consult Upgrading a High Availability Deployment in the
+
+ Manual.
+
+
+ Restoring a previous Enea Edge Management Installation
+
+ How to restore a previous Enea Edge
+ Management installation
+
+
+
+ Extract
+ Enea_Edge_Management_<version>-build<build_number>.tar.gz
+
+
+
+ The directory in which the archive has been unpacked will be
+ denoted as <uCPEM-installdir> .
+
+
+
+ Copy the snapshot file
+ (ucpemanager-Backup-YYYYddMMHHmm.tar.gz )
+ created during a previous Enea Edge Management Upgrade or Enea Edge
+ Management Uninstall Operation into the
+ <uCPEM-installdir> directory.
+
+
+
+ Enter <uCPEM-installdir>/dist .
+
+
+
+ Run the following command with the root user and change
+ /opt/ems to the correct location of the Enea Edge
+ Management installation:
+
+ ./restore.sh /opt/ems ucpemanager-Backup-YYYYddMMHHmm.tar.gz
+
+
+
+ Running this command will:
+
+
+
+ Remove any vestiges of the existing
+ ucpemanager service, if they exist.
+
+
+
+ Reinstall the Enea Edge Management application on the
+ specified target location, restoring the data in the database and
+ files in the process.
+
+
+
+ The ucpemanager service will then start with
+ the older version now running on the system.
+
+
+
+ Uninstalling an existing Enea Edge Management
+ Installation
+
+ How to uninstall an existing Enea Edge
+ Management installation
+
+
+
+ Navigate to the folder where the Enea Edge Management is
+ installed: <uCPEM-installdir> .
+
+
+
+ Run the following command with the root user and change
+ /opt/ems to the correct location of the Enea Edge
+ Management installation:
+
+ ./uninstall.sh /opt/ems
+
+
+
+ Running this command will:
+
+
+
+ Stop the currently running ucpemanager
+ service.
+
+
+
+ Create a compressed file of the ucpemanager
+ application folder:
+ ucpemanager-Back-up-YYYYddMMHHmm.tar.gz , which
+ contains a snapshot of the existing installation and functions as a
+ restore point.
+
+
+ The snapshot file created during the uninstall can be used
+ for restoring Enea Edge Management.
+
+
+
+
+ Uninstall the ucpemanager service, so that
+ it will not start up on reboot.
+
+
+
+ Uninstall the database service.
+
+
+
+ Completely remove the contents of the application and database
+ folders.
+
+
+
+ After these steps, the Enea Edge Management is completely removed
+ from the system.
+
+
+
+
+ uCPE device Upgrades
+
+ A uCPE device can be upgraded using the Enea Edge Management
+ GUI.
+
+
+ The uCPE device Upgrade Process
+
+ The Device Upgrade/Install option performs the following
+ operations to the uCPE device:
+
+
+
+ Prepare for upgrade. This
+ stage prepares the files needed for an upgrade.
+
+
+
+ Install file on device. This
+ stage copies the file to the uCPE device.
+
+
+
+ Upgrade Device. This stage
+ upgrades the uCPE device to a newer version.
+
+
+
+
+ Upgrading from Enea NFV Access 2.3.0 is not possible when using
+ the Enea uCPE Manager in HTTPS mode. Either switch to HTTP by accessing
+ System , Configuration , Web
+ Access and checking the Enable
+ HTTP box, or installing it manually.
+
+
+
+
+ Managing the uCPE device Upgrade
+
+ Before an installation or upgrade can be completed, certain
+ configuration data must be set. Files also need to be uploaded to the
+ Device Upgrade image repository in order to be uploaded to the
+ device.
+
+ Launch the Device Upgrade management console by selecting
+ Devices and then the Upgrade button from the top tool-bar. The console
+ will contain the following tabs:
+
+
+
+ Image Library . To add/delete
+ an image.
+
+
+
+ Upgrade Operations . See
+ upgrades that are currently running, cancel any upgrades in
+ progress, or start a uCPE device upgrade.
+
+
+
+ Configuration . Upgrade
+ configuration parameters.
+
+
+
+
+ The uCPE Device upgrade is done with image files of the type
+ rootfs.ostree.tar.bz2 , which are available in the
+ Enea_Edge_Runtime_<processor>_<version>-build<build_number>.tar.gz
+ file you downloaded with your release.
+
+
+
+ Image Library
+
+ Adding an image to the image
+ repository/library
+
+ Select Devices and then
+ the Upgrade button.
+
+
+
+ Select Add from the
+ Image Library tab to add a new
+ image file.
+
+
+
+ Select Choose File to
+ provide the path to the image file (must be of type
+ rootfs.os-tree.tar.bz2 ).
+
+
+
+ Select the target hardware platform corresponding to the
+ image being uploaded (xeon-d or
+ atom-c3000 ).
+
+
+
+ Click Send to upload the
+ image to the image repository.
+
+
+
+ Deleting an image from the image
+ repository
+
+
+
+ Select Devices and then the
+ Upgrade button.
+
+
+
+ Select the image you want to delete from the Image Library tab and then click Delete .
+
+
+
+
+
+ Upgrade Operations
+
+ The Upgrade Operations tab
+ allows a user to manage uCPE device upgrades in the system. It allows
+ the user to see all the upgrades that are currently in progress, as
+ well as listing the completed ones. If an upgrade succeeds or fails,
+ then a row will be added to the completed upgrades table. If one
+ fails, the failure message will be visible in the table.
+
+
+ The list of completed upgrade tasks resides in the cache
+ memory and will not persist across reboots of the server.
+
+
+ How to Install/Upgrade a device
+ immediately or schedule the process for later
+
+ Select Devices and then
+ the Upgrade button.
+
+
+
+ Select Upgrade Devices
+ from the Upgrade Operations
+ tab. This will launch a Multi Device Install
+ Image screen that will allow the user to install and
+ upgrade more than one uCPE device at a time or upgrade
+ later.
+
+
+
+ The configurable parameters are:
+
+
+
+ Scheduling . Click this checkbox if the
+ upgrade will be done later. Schedule the day, hour and minute for
+ when to run the upgrade.
+
+
+ The hour represents the local Enea Edge Management server
+ hour.
+
+
+
+
+ Description . An optional description of
+ the operation. It is recommended to add a description so that
+ different upgrades happening simultaneously can be
+ distinguished.
+
+
+
+ Image File . Click on Choose Image File to select the image
+ file.
+
+
+
+ Devices . The list of uCPE Devices that
+ can accept an image file is populated when the image file is
+ chosen.
+
+ Mark the uCPE devices that you wish to upgrade and press the
+ > button to move the uCPE
+ devices to the right side of the selector. Those chosen form the
+ list of uCPE devices that will be upgraded.
+
+
+
+ Upgrade Operation . The available options
+ are:
+
+
+
+ Install and Activate . This will do an
+ image installation as well as an upgrade.
+
+
+
+ Install Only . This will do an image
+ installation only. The image is copied to the uCPE device, and
+ an upgrade will be done later either at a scheduled time or
+ when the option Activate Only is
+ selected.
+
+
+
+ Activate Only . This will activate an
+ already installed image on the uCPE device.
+
+
+
+
+
+ To start the upgrade, click ok .
+
+
+
+
+ When the uCPE device activates the upgrade, it will be
+ rebooted automatically.
+
+
+
+
+ Releases installed on a uCPE device
+
+ The installed releases on a uCPE device can be viewed by
+ selecting the uCPE device first, then from the top toolbar selecting
+ Configuration and then the Upgrade button.
+
+ The installed releases on the uCPE device, the release status,
+ release state, commit-id and release version will
+ be listed in a table.
+
+
+
+ uCPE device Upgrade Status
+
+ The status of the installation and upgrade can be viewed in the
+ Upgrade Operations tab. Ongoing or
+ scheduled upgrade operations can be viewed or cancelled.
+
+ To view the status of an installation or
+ upgrade operations
+
+
+
+ Select Devices and then the
+ Upgrade button.
+
+
+
+ Select Upgrade Operations .
+ The ongoing operations are listed at the top and a history of
+ failed or successful operations are listed at the bottom.
+
+
+
+ Select an Active or
+ Completed Upgrade Operation and
+ then the Device Status button to
+ see detailed information regarding the upgrade operation,
+ including the uCPE devices involved and information per uCPE
+ device.
+
+
+
+ To cancel an upgrade
+ operation
+
+
+
+ Select Devices , then the
+ Upgrade button and choose
+ Upgrade Operations .
+
+
+
+ Select an operation from the list and choose Cancel Upgrade and Confirm . The operation will then be deleted
+ from the list.
+
+
+
+
+
+ Configuration
+
+
+ The default values present in the configuration of each uCPE
+ device are recommended for use. Modifying them is for an Advanced User only.
+
+
+ How to Configure the uCPE device
+ Upgrade
+
+ Select Devices and then
+ the Upgrade button.
+
+
+
+ Select Configuration .
+
+
+
+ The configurable parameters are:
+
+
+
+ deviceImageDir . This is the disk
+ location of the device image repository.
+
+
+ If no absolute path name is given it is assumed to
+ be relative to the installation directory.
+
+
+
+
+ maxThreads . This number dictates
+ how many upgrades the system can manage at one time, either
+ individually launched or launched from the multi-device
+ screens. This value defaults to 20, which means that 20 uCPE
+ devices may be updated at one time.
+
+
+
+ KeepAlive . This number represents
+ the number of seconds that a thread will be kept alive
+ before it is collected. If multiple installations are
+ occurring, this will keep the thread alive for X seconds
+ before it is released. If not released, it can be used by
+ the internal scheduling system as soon as it has completed
+ an upgrade.
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-getting-started/doc/vnf_mg.xml b/doc/book-enea-edge-getting-started/doc/vnf_mg.xml
new file mode 100644
index 0000000..bd2fb0b
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/doc/vnf_mg.xml
@@ -0,0 +1,477 @@
+
+
+ VNF Management
+
+ The Enea Edge Management is responsible for onboarding, configuring
+ (e.g. CloudInit) and ensuring life cycle management of VNFs that are
+ instantiated and run on the various uCPE devices.
+
+
+ Onboarding a VNF
+
+ The onboarding of a VNF means adding it to the Enea Edge Management
+ VNF Catalogue and preparing it for instantiation (deployment on connected
+ uCPE devices). This is accomplished using the Enea Edge Management
+ Onboarding graphical user interface.
+
+ Typically, the Getting Started Guide of a VNF, provided by the VNF
+ vendor, contains all necessary information needed to onboard a VNF.
+
+
+ Retrieving Artifacts
+
+ The user must first retrieve the necessary artifacts from the VNF
+ vendor:
+
+
+
+ Download the VNF from the commercial vendor.
+
+
+
+ Procure any VNF-specific files from the VNF vendor, e.g.
+ license file.
+
+
+ There are no standard ways of managing VNF licenses,
+ therefore no general guidelines can be provided. One example of
+ license handling that can be employed in the Enea Edge Management
+ is the adding of a license during the Cloud-Init setup.
+
+
+
+
+ Optionally, get access to the VNF specific VNF Manager for day
+ 1 and 2 configuration (in cloud or for local deployment).
+
+
+
+ Procure the Getting Started Guide from the VNF vendor,
+ preferably for KVM deployment for VNF specific configuration
+ information.
+
+
+
+
+
+ Preparation
+
+ Once all needed downloadables, documentation and more have been
+ attained, preparation for onboarding must be completed:
+
+
+
+ Determine the use-case and performance requirements of the VNF
+ you wish to deploy:
+
+
+
+ This decides what resources the VNF is configured for,
+ along with networking and day zero configurations.
+
+
+ Generally, the Getting Started Guide for the VNF
+ provides guidelines for resource allocation, but since
+ performance is dependent on hardware capacity, the right
+ resource allocation for deployment is determined through
+ benchmarking.
+
+
+
+
+ Determine the amount of hardware resources needed for the
+ VNF (RAM, number of CPUs and storage size).
+
+
+
+ Determine how many Virtual Network Interfaces the VNF will
+ use.
+
+
+
+
+
+ Determine the Day-0 configuration method from the VNF Getting
+ Started guidelines.
+
+
+ For many VNFs, day zero configuration can be skipped in
+ early onboarding efforts when automation is not of
+ importance.
+
+
+
+
+ Determine any requirements needed by the Cloud-Init file
+ structure and the content needed when this structure is used.
+
+
+
+
+
+ Onboarding into the Enea Edge Management
+
+ How to onboard a VNF into the Enea Edge
+ Management
+
+
+
+ Select from the top toolbar VNF and then Descriptors .
+
+
+
+ Click the On-board
+ button.
+
+
+
+ This window contains data fields where both necessary and optional
+ information about the VNF can be supplied. After doing so, press the
+ Onboard button, the Enea Edge Management will create the VNF descriptor
+ and add it to its VNF Catalog.
+
+
+ Onboard a VNF
+
+
+
+
+
+
+
+
+ Main fields
+
+
+
+ VM Image File . This is the
+ Virtual Machine image file for the VNF. Typically, it is a QCOW
+ image. Press Choose File and select
+ the image you wish to upload.
+
+
+
+ Image Format . Select the
+ format which matches the image file format.
+
+
+
+ VNF Type Name . This is the
+ name that will be used to identify this VNF. It will be shown in the
+ VNFs list.
+
+
+
+ Description . This field
+ contains any description provided and is only displayed in the GUI
+ tables in the Enea Edge Management.
+
+
+
+ Version . This is the version
+ of the current VNF that you are hosting. It's used to distinguish
+ this VNF from other versions of the same type.
+
+
+
+ Memory in MB . This is the
+ amount of memory (in megabytes) that will be provided to this type
+ of VNF when it is instantiated. To determine the value for this
+ field, consult the VNF vendor.
+
+
+
+ Num of CPUs . The number of
+ CPUs that will be dedicated to an instance of this VNF when created.
+ To determine the value for this field, consult the VNF
+ vendor.
+
+
+
+ Storage in GB . How much disk
+ space to provide an instance of this VNF. To determine the value for
+ this field, consult the VNF vendor.
+
+
+
+ Interfaces Tab
+
+ Click on the Interfaces tab to
+ show the Interfaces table.
+
+ This table will contain the interfaces required by this VNF to be
+ configured, when creating an instance. Consult the VNF vendor to
+ determine which and how many are required. Each interface requires a
+ name, and optionally a description, used only by the Enea Edge
+ Management.
+
+
+ CAUTION: The user MUST conserve the same order for the virtual
+ interfaces during both onboarding and instantiation phases.
+
+
+ Cloud Init Tab
+
+ Click the Cloud Init tab to
+ provide the Cloud-Init configuration. There are three fields that need
+ to be populated:
+
+
+
+ Cloud-Init Datasource
+
+ To onboard a VNF you must specify the Cloud-Init
+ Datasource that the VNF uses. This information is procured
+ from the VNF Vendor. Choose one of the following methods to specify
+ the datasource:
+
+
+
+ None . If there is no
+ datasource.
+
+
+
+ ConfigDrive . This method
+ allows you to provide any number of content-data files
+ containing Cloud-Init data.
+
+
+
+ NoCloud . This is a
+ simpler method that uses only one cloud init file
+ (User-Data).
+
+
+
+ ISO . Pre-cooked
+ cloud-init image. This image must be created by the user
+ according to VNF requirements.
+
+
+
+
+
+ Cloud-Init Disk Type
+
+ The Cloud-Init Disk Type field must be set
+ to either Disk , or CD-ROM ,
+ depending on what the VNF requires. You can get this information
+ from the VNF Vendor.
+
+
+
+ Content Files Table
+
+ The Content Files Table is ONLY used if
+ ConfigDrive is chosen as the Cloud-Init
+ Datasource. For each content file added, a Path
+ must be provided. When the Enea Edge Management is used to create an
+ instance for multiple VNFs, the user will be prompted to provide a
+ data file for each entry in this table. Each type of VNF will
+ require different cloud-init files, e.g.: a license file. The data
+ files will be added to the cloud-init image that the user provides
+ at the instantiation of the VNF. If the cloud-init image is not
+ provided, no Cloud-Init Data Source will be created for that VNF and
+ there will be no warning.
+
+
+
+ Consult with the VNF vendor to determine what is required for the
+ VNF you are onboarding.
+
+ Properties Tab
+
+ In this table, you can enter values for properties that will be
+ used during instantiation of the VNF. The values will augment the
+ default values in the domain.xml file used by
+ libvirt/virsh (running in Enea Edge) when creating an
+ instance of the VNF. Consult with the VNF Vendor or ENEA support for
+ values needed by specific VNFs.
+
+ Property Values
+
+
+
+ numHugePages defines the number of huge
+ memory pages the VNF uses (for DPDK).
+
+
+
+ vnfMgmtIpAddress : the IP address of the
+ VNF's management interface, connected to a
+ vnfMgmt bridge (e.g. 10.0.0.2).
+
+
+
+ internalMgmtPort : the VNF's TCP/UDP port
+ used for management (e.g. 443).
+
+
+
+ externalMgmtPort : the Management port used
+ for external access (e.g. 60001).
+
+
+
+
+ The last three properties are useful in conjuction with the
+ vnfMgmt bridge type. They allow the user to map the
+ internal VNF management port to an external port, useful for VNF
+ configuration from WAN.
+
+ In the previous example, the internal TCP port 443 (HTTPS) was
+ mapped to the external port 60001, which allows the user to access the
+ VNF management port from a web browser e.g.
+ https://<WAN_IP>:60001 .
+
+
+
+
+
+ Instantiating a VNF
+
+ When a VNF is onboarded and available in the VNF catalog, it can be
+ instantiated on connected uCPE devices. The configurations provided when
+ the VNF is onboarded, serve as a template for instantiation. Before
+ instantiating any VNF, please make sure the available storage space on the
+ uCPE device is big enough to accommodate the VNF you need to
+ instantiate.
+
+ Follow the instructions below to instantiate a VNF:
+
+
+
+ Select from the top toolbar VNF
+ and choose Instances .
+
+
+
+ Click the Add button.
+
+
+
+ Fill out the following mandatory fields:
+
+
+
+ Name: a descriptive name.
+
+
+
+ VNF Type: a list of onboarded VNFs.
+
+
+
+ uCPE Device: the uCPE device to instantiate the VNF
+ on.
+
+
+
+ Networking Configuration:
+
+
+
+ Connect each configured NIC with a bridge, SR-IOV or PCI
+ Passthrough.
+
+
+
+ Set up each NIC with a driver method.
+
+
+
+
+ All configured NICs must be set up before instantiating a
+ VNF. Failure to do so will end in a failed instantiation.
+
+
+
+
+
+
+ Add VNF-specific configuration data by uploading a Cloud-Init
+ file (when the Cloud-Init is used).
+
+
+
+ Add any VNF-specific files (e.g license files).
+
+
+
+ Hit the Create button to deploy
+ the VNF and run it on the specified uCPE device.
+
+
+
+ Selecting the VNF menu then
+ choosing Events will show that the VNF
+ was created and a connection was established.
+
+
+
+ Accessing the VNF console
+
+ Once the VNF is deployed, the VNF console can be entered using SSH
+ and virsh commands. The VNF Console is a typical starting point for
+ determining a successful deployment and configuring a VNF beyond Day
+ Zero.
+
+
+
+ SSH to the uCPE device from the Enea Edge Management (Access the
+ Device menu and select SSH ) using:
+
+
+
+ For normal connections: the Username
+ (default: root), the Password (default: no
+ password), the Port (default: 22) and the
+ Reverse ssh checkbox: unchecked.
+
+
+
+ For reverse ssh connections (ssh to a uCPE device behind
+ NAT): the Username (default: root) and the
+ Reverse ssh checkbox checked. The port will be
+ automatically chosen by the Enea Edge Management in the range
+ defined in the SSH configuration
+ panel, available when accessing System , then Configuration and choosing Reverse SSH . By default, the start port
+ will be 7000 and the maximum number of ports
+ allocated to all devices is 10. Only one port per device is
+ allowed.
+
+ When the SSH window is closed, the tunnel configuration is
+ deleted on the uCPE device and the tunnel is destroyed, so that
+ the port can be reused to establish a new tunnel when
+ needed.
+
+
+
+
+
+ In SSH:
+
+
+
+ Use the virsh list command to list all
+ running VNFs and to determine the VNF's instance number.
+
+
+
+ Use the virsh console <instance
+ number> command to enter the VNF-specific
+ console.
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-getting-started/swcomp.mk b/doc/book-enea-edge-getting-started/swcomp.mk
new file mode 100755
index 0000000..41e4416
--- /dev/null
+++ b/doc/book-enea-edge-getting-started/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-getting-started
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Getting Started"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-edge-management-open-source/doc/README b/doc/book-enea-edge-management-open-source/doc/README
new file mode 100644
index 0000000..1077acb
--- /dev/null
+++ b/doc/book-enea-edge-management-open-source/doc/README
@@ -0,0 +1,4 @@
+The licenses.xml in the git repository of Enea NFV Access Open Source Report
+is the frozen version belonging to the last official release of Enea NFV Access.
+The contents must be generated from the release script to obtain the latest
+lists of packages and licenses.
diff --git a/doc/book-enea-edge-management-open-source/doc/about.xml b/doc/book-enea-edge-management-open-source/doc/about.xml
new file mode 100644
index 0000000..05cea19
--- /dev/null
+++ b/doc/book-enea-edge-management-open-source/doc/about.xml
@@ -0,0 +1,12 @@
+
+
+
+ About this Report
+
+ This document contains the open source and license information
+ pertaining to packages provided with Enea Edge .
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-management-open-source/doc/book.xml b/doc/book-enea-edge-management-open-source/doc/book.xml
new file mode 100644
index 0000000..715fbe6
--- /dev/null
+++ b/doc/book-enea-edge-management-open-source/doc/book.xml
@@ -0,0 +1,15 @@
+
+
+]>
+
+ Enea Edge Management Open Source Report
+ Release Version
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-management-open-source/doc/licenses.xml b/doc/book-enea-edge-management-open-source/doc/licenses.xml
new file mode 100644
index 0000000..92b4729
--- /dev/null
+++ b/doc/book-enea-edge-management-open-source/doc/licenses.xml
@@ -0,0 +1,5872 @@
+
+
+
+ Packages and Licenses
+
+
+ Packages
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Package Name
+ Version
+ Description
+ License
+
+
+
+
+
+
+
+ 7-zip
+
+ Windows Zip/Unzip utility
+ GNU LGPL + unRAR restriction + BSD 3-clause License
+
+
+
+ ANTLR Runtime
+ 4.5.2
+ Java-based Parser-Generator
+ BSD
+
+
+
+ ASM
+ 3.1
+ Java bytecode manipulation library
+ 3-Clause BSD License
+
+
+
+ Apache FtpServer
+ 1.0.3
+ FTP server implementation
+ Apache 2.0
+
+
+
+ Apache SSHD
+ 0.3.0
+ SSH server implementation
+ Apache 2.0
+
+
+
+ Apache Tomcat
+ 9.0.14
+ Servlet Container
+ Apache 2.0
+
+
+
+
+ Apache HTTP Components
+ 4.5.1
+ HTTP client libraries
+ Apache 2.0
+
+
+
+ Apache HTTP Client
+ 3.1
+ HTTP commons libraries
+ Apache 2.0
+
+
+
+ Apache Log4j
+ 2.0
+ Logging libraries
+ Apache 2.0
+
+
+
+ Apache Commons Codec
+ 1.9
+ MD5 libraries
+ Apache 2.0
+
+
+
+ Application Icons
+
+ Graphical Icon Images
+ Freeware
+
+
+
+ Atomikos TransactionsEssentials
+ 4.0.6
+ Transaction management
+ Apache 2.0
+
+
+
+ BeanShell
+ 2.0
+ http://www.beanshell.org
+ Apache 2.0
+
+
+
+ Browser-based SSH terminal
+
+ shell_in_a_box.js,vt100.js
+ Commercially licensed to ENEA
+
+
+
+ Byte Buddy
+
+ Byte Buddy is a code generation and manipulation library for creating and modifying Java classes.
+ Apache 2.0
+
+
+
+ ClassMate
+
+ Library for introspecting types with full generic information including resolving of field and method types.
+ Apache 2.0
+
+
+
+ CGLib Nodep
+
+ CGLib Nodep.
+ Apache 2.0
+
+
+
+ Commons Compress
+ 1.5
+ Compression libraries
+ Apache 2.0
+
+
+
+ Commons Lang
+ 3.8.1
+ Java Language utilities libraries
+ Apache 2.0
+
+
+
+ EasyMock
+ 3.4
+ Java framework that allows to create mocks in unit tests.
+ Apache 2.0
+
+
+
+ flot
+ 0.8.3
+ JS Graphing lib
+ Flot license
+
+
+
+ flot.tooltip
+
+ tool tip plugin for flot
+ MIT
+
+
+
+ flot.axis.labels
+
+ label plugin for flot
+ MIT
+
+
+
+ GNU Crypto
+ 2.0.1
+ Included with JRadius, this is used for Radius login and authentication.
+ GPL with the "library exception"
+ (GNU GPL V3 License)
+
+
+
+
+ guava
+ 18.0
+ Java utilities
+ Apache 2.0
+
+
+
+ Google Web Toolkit
+ 2.8.2
+ RIA Web GUI Creation
+ Apache 2.0
+
+
+
+ GWT Maps
+ 3.8.0-pre1
+ GWT Library to Google Maps API
+ Apache 2.0
+
+
+
+ GWT Beans Binding
+ 0.3
+ Bean utilities for GWT
+ GNU Lesser GPL
+
+
+
+ gwt-dispatch
+ 1.1.0
+ gwt RPC enhancement
+ BSD 3-Clause
+
+
+
+ GWT GIN
+ 1.0
+ Google Injection - GIN and GUICE
+ Apache 2.0
+
+
+
+ GWT Graphics
+ 0.9.7 (modified)
+ Vector Graphics for GWT [MODIFIED BY ENEA]
+ Apache 2.0
+
+
+
+ GWT Incubator
+ 2.1.0
+ GWT Incubator Jar
+ Apache 2.0
+
+
+
+ GWT-Log
+ 3.3.2
+ Library for GWT Logging
+ Apache 2.0
+
+
+
+ GWT Voices
+ 3.3.2
+ GWT Support for playing MP3 files in the browser
+ Apache 2.0
+
+
+
+ GWT Upload
+ 1.0.3
+ GWT GUI support for File Uploading
+ Apache 2.0
+
+
+
+ Hazelcast
+ 3.6.2
+ In-Memory Data Grid
+ Apache 2.0
+
+
+
+ Hibernate
+ 5.4.1
+ Relational Persistence for Java
+ GNU LesserGPL 2.1
+
+
+
+ Javassist
+ 3.24
+ Java byte-code manipulation library
+ Mozilla Public License Version 1.1 , GNU Lesser General Public License, version 2.1 , APACHE LICENSES (included in zip, free to distribute)
+
+
+
+ Jackson
+ 2.9.8
+ JSON processor
+ Apache 2.0
+
+
+
+ JavaMail API
+ 1.5.1
+ Mail API used for sending mail
+ Dual license consisting of the CDDL v1.1 and GPL v2 with
+ CPE
+
+
+
+ Jersey
+ 2.30
+ JAX-RS Reference implementation
+ Eclipse Public License - v 2.0 , The GNU General Public License (GPL) Version 2, June
+ 1991
+
+
+
+ Jersey Filtering
+ 2.30
+ Jersey extension module providing support for Entity Data Filtering.
+ Apache 2.0 ,BSD 2-clause ,EDL 1.0 ,EPL 2.0 ,MIT ,Public ,W3C
+
+
+
+ Jersey Media JSON Jackson
+ 2.30
+ JJersey JSON Jackson (2.x) entity providers support module.
+ Apache 2.0 ,EPL 2.0 ,GNU
+
+
+
+ Jersey Media Moxy
+ 2.30
+ Jersey JSON entity providers support module based on EclipseLink MOXy.
+ Apache 2.0 ,BSD 2-clause ,EDL 1.0 ,EPL 2.0 ,MIT ,Public ,W3C
+
+
+
+ Jersey Media Multipart
+ 2.30
+ Jersey Multipart entity providers support module.
+ Apache 2.0 ,BSD 2-clause ,EDL 1.0 ,EPL 2.0 ,MIT ,Public ,W3C
+
+
+
+ JAX-WS
+ 2.3.1
+ Java Web Service Reference implementation
+ Dual license consisting of the CDDL v1.1 and GPL v2
+ with CPE
+
+
+
+ Jakarta Commons Net
+ 3.3
+ Network Protocol client libraries
+ Apache 2.0
+
+
+
+ JAXB API
+
+ JAXB API
+ CDDL 1.1
+
+
+
+ JTDS
+ 1.2.5
+ SQLServer Driver
+ GNU Lesser GPL
+
+
+
+ JSch
+ 0.1.54
+ Java SSH2 Implementation
+ BSD-style
+
+
+
+ Jython
+ 2.7.1
+ Python interpreter for Java
+ Python Software Foundation
+
+
+
+ JBoss Cache
+ 3.2.5
+ Tree-based memory cache
+ GNU LesserGPL 2.1
+
+
+
+ JDOM
+ 1.1.1
+ XML Document Parser
+ Apache-style open source
+
+
+
+ JRadius
+ 1.1.4 (From Coova)
+ A Radius client used to perform Radius authentication and accounting.
+ GNU Lesser GPL
+
+
+
+ JSOCKS
+
+ Pure-Java implementation of SOCKS protocol
+ GNU Lesser GPL v3
+
+
+
+ jQuery
+
+ JS lib
+ MIT license
+
+
+
+ MariaDB Java client
+ 2.7.2
+ Java client for MariaDB database and MySQL
+ GNU LesserGPL 2.1
+
+
+
+ Open CSV
+ 2.2
+ Used for CSV output utilities
+ Apache 2.0
+
+
+
+ OpenStack4j
+ 3.0.3
+ Java OpenStack client libraries
+ Apache 2.0
+
+
+
+ Objenesis
+ 2.4
+ Objenesis is a library dedicated to bypass the constructor when creating an object.
+ Apache 2.0
+
+
+
+ OSHI
+ 3.13
+ Native Operating System and Hardware Information libraries
+ MIT License
+
+
+
+ PostgreSQL Database
+ 9.0.4-1
+ Relational Database
+ PostgreSQL license (similar to BSD or MIT)
+
+
+
+ PostgreSQL JDBC Driver
+ 9.0-801
+ Java driver for PostgreSQL Relational Database
+ PostgreSQL license (similar
+ to BSD or MIT)
+
+
+
+ PowerMock
+ 1.7.1
+ Java framework that allows to create mocks in unit tests for cases that are not possible with EasyMock.
+ Apache 2.0
+
+
+
+ Quartz
+ 2.2.1
+ Scheduling system
+ Apache 2.0
+
+
+
+ Rox
+ 1.2
+ XML RPC
+ BSD-style
+
+
+
+ SLF4J
+ 1.7.25
+ Logging framework
+ SLF4J MIT License
+
+
+
+ SNMP4J
+ 2.1
+ SNMP Client Library
+ Apache 2.0
+
+
+
+ SNMP4J-Agent
+ 2.0.7
+ SNMP Agent Library
+ Apache 2.0
+
+
+
+ Spring Framework
+ 5.1.4
+ Micro Container, Utilities
+ Apache 2.0
+
+
+
+ Syslog4j
+ 0.9.46
+ Syslog implementation in Java
+ GNU Lesser GPL 2.1
+
+
+
+ True License
+ 1.29
+ Licensing framework
+ Apache 2.0
+
+
+
+ UUID
+ 3.1
+ High-performance UUID generator
+ MIT
+
+
+
+ XMLBeans
+ 2.5.0
+ XML binding to Java types
+ Apache 2.0
+
+
+
+ YAJSW
+ 12.14
+ Service wrapper for Java applications
+ Apache 2.0
+
+
+
+
+
+
+
+
+ Open Source Licenses
+
+
+ 7-Zip
+
+
+
+ ~~~~~
+ License for use and distribution
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+ 7-Zip Copyright (C) 1999-2012 Igor Pavlov.
+
+ Licenses for files are:
+
+ 1) 7z.dll: GNU LGPL + unRAR restriction
+ 2) All other files: GNU LGPL
+
+ The GNU LGPL + unRAR restriction means that you must follow both
+ GNU LGPL rules and unRAR restriction rules.
+
+
+ Note:
+ You can use 7-Zip on any computer, including a computer in a commercial
+ organization. You don't need to register or pay for 7-Zip.
+
+
+ GNU LGPL information
+ --------------------
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You can receive a copy of the GNU Lesser General Public License from
+ http://www.gnu.org/
+
+
+ unRAR restriction
+ -----------------
+
+ The decompression engine for RAR archives was developed using source
+ code of unRAR program.
+ All copyrights to original unRAR code are owned by Alexander Roshal.
+
+ The license for original unRAR code has the following restriction:
+
+ The unRAR sources cannot be used to re-create the RAR compression algorithm,
+ which is proprietary. Distribution of modified unRAR sources in separate form
+ or as a part of other software is permitted, provided that it is clearly
+ stated in the documentation and source comments that the code may
+ not be used to develop a RAR (WinRAR) compatible archiver.
+
+
+ --
+ Igor Pavlov
+
+
+
+
+ ANTLR 4 License
+
+[The BSD License] Copyright (c) 2012 Terence Parr and Sam Harwell All rights
+reserved. Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+Redistributions of source code must retain the above copyright notice, this
+list of conditions and the following disclaimer. Redistributions in binary form
+must reproduce the above copyright notice, this list of conditions and the
+following disclaimer in the documentation and/or other materials provided with
+the distribution. Neither the name of the author nor the names of its
+contributors may be used to endorse or promote products derived from this
+software without specific prior written permission. THIS SOFTWARE IS PROVIDED
+BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
+EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+ FLOT LICENSE
+
+
+
+
+Copyright (c) 2007-2014 IOLA and Ole Laursen
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.
+
+
+
+
+ France Télécom
+
+
+Copyright (c) 2012 France Télécom
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. Neither the name of the copyright holders nor the names of its
+ contributors may be used to endorse or promote products derived from
+ this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+ Apache License
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+
+ 6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run time a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.
+
+ c) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ d) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ e) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+
+ How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. 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 the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the library's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
+
+
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+
+
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+ This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+ 0. Additional Definitions.
+
+ As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+ "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+ An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+ A "Combined Work" is a work produced by combining or linking an
+Application with the Library. The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+ The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+ The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+ 1. Exception to Section 3 of the GNU GPL.
+
+ You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+ 2. Conveying Modified Versions.
+
+ If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+ a) under this License, provided that you make a good faith effort to
+ ensure that, in the event an Application does not supply the
+ function or data, the facility still operates, and performs
+ whatever part of its purpose remains meaningful, or
+
+ b) under the GNU GPL, with none of the additional permissions of
+ this License applicable to that copy.
+
+ 3. Object Code Incorporating Material from Library Header Files.
+
+ The object code form of an Application may incorporate material from
+a header file that is part of the Library. You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+ a) Give prominent notice with each copy of the object code that the
+ Library is used in it and that the Library and its use are
+ covered by this License.
+
+ b) Accompany the object code with a copy of the GNU GPL and this license
+ document.
+
+ 4. Combined Works.
+
+ You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+ a) Give prominent notice with each copy of the Combined Work that
+ the Library is used in it and that the Library and its use are
+ covered by this License.
+
+ b) Accompany the Combined Work with a copy of the GNU GPL and this license
+ document.
+
+ c) For a Combined Work that displays copyright notices during
+ execution, include the copyright notice for the Library among
+ these notices, as well as a reference directing the user to the
+ copies of the GNU GPL and this license document.
+
+ d) Do one of the following:
+
+ 0) Convey the Minimal Corresponding Source under the terms of this
+ License, and the Corresponding Application Code in a form
+ suitable for, and under terms that permit, the user to
+ recombine or relink the Application with a modified version of
+ the Linked Version to produce a modified Combined Work, in the
+ manner specified by section 6 of the GNU GPL for conveying
+ Corresponding Source.
+
+ 1) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (a) uses at run time
+ a copy of the Library already present on the user's computer
+ system, and (b) will operate properly with a modified version
+ of the Library that is interface-compatible with the Linked
+ Version.
+
+ e) Provide Installation Information, but only if you would otherwise
+ be required to provide such information under section 6 of the
+ GNU GPL, and only to the extent that such information is
+ necessary to install and execute a modified version of the
+ Combined Work produced by recombining or relinking the
+ Application with a modified version of the Linked Version. (If
+ you use option 4d0, the Installation Information must accompany
+ the Minimal Corresponding Source and Corresponding Application
+ Code. If you use option 4d1, you must provide the Installation
+ Information in the manner specified by section 6 of the GNU GPL
+ for conveying Corresponding Source.)
+
+ 5. Combined Libraries.
+
+ You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+ a) Accompany the combined library with a copy of the same work based
+ on the Library, uncombined with any other library facilities,
+ conveyed under the terms of this License.
+
+ b) Give prominent notice with the combined library that part of it
+ is a work based on the Library, and explaining where to find the
+ accompanying uncombined form of the same work.
+
+ 6. Revised Versions of the GNU Lesser General Public License.
+
+ The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+ If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
+
+
+
+ jTDS
+
+
+License
+jTDS is Free Software. jTDS is made available under the terms of the
+GNU Lesser General Public License. The LGPL is sufficiently flexible to allow
+the use of jTDS in both open source and commercial projects. Using jTDS is
+considered to be dynamic linking; hence our interpretation of the LGPL is that
+the use of the unmodified jTDS source or binary does not affect the license of
+your application code.
+
+If you modify jTDS and redistribute your modifications, the LGPL applies,
+basically meaning that you'll have to make the modified version publicly
+available under the LGPL license too. This ensures that all users of the
+software have access to all future improvements.
+
+jTDS was initially based on software released under a BSD license by CDS
+Networks, Inc. and/or Craig Spannring, the author of the original FreeTDS JDBC
+driver from which jTDS is derived. Between releases 0.8.1 and 0.9 jTDS was
+completely rewritten so the original BSD license no longer applies.
+
+
+
+ JSch
+
+JSch 0.0.* was released under the GNU LGPL license. Later, we have switched
+over to a BSD-style license.
+
+------------------------------------------------------------------------------
+Copyright (c) 2002-2015 Atsuhiko Yamanaka, JCraft,Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+ 1. Redistributions of source code must retain the above copyright notice,
+ this list of conditions and the following disclaimer.
+
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the distribution.
+
+ 3. The names of the authors may not be used to endorse or promote products
+ derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JCRAFT,
+INC. OR ANY CONTRIBUTORS TO THIS SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
+OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+ Jython
+
+
+The Jython License
+
+A. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING JYTHON
+
+PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
+
+1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"),
+and the Individual or Organization ("Licensee") accessing and otherwise using
+this software ("Jython") in source or binary form and its associated
+documentation.
+
+2. Subject to the terms and conditions of this License Agreement, PSF hereby
+grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
+analyze, test, perform and/or display publicly, prepare derivative works,
+distribute, and otherwise use Jython alone or in any derivative version,
+provided, however, that PSF's License Agreement and PSF's notice of copyright,
+i.e., "Copyright (c) 2007 Python Software Foundation; All Rights Reserved" are
+retained in Jython alone or in any derivative version prepared by Licensee.
+
+3. In the event Licensee prepares a derivative work that is based on or
+incorporates Jython or any part thereof, and wants to make the derivative work
+available to others as provided herein, then Licensee hereby agrees to include
+in any such work a brief summary of the changes made to Jython.
+
+4. PSF is making Jython available to Licensee on an "AS IS" basis. PSF MAKES NO
+REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT
+LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF
+MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF JYTHON
+WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.
+
+5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF JYTHON FOR ANY
+INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING,
+DISTRIBUTING, OR OTHERWISE USING JYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF
+ADVISED OF THE POSSIBILITY THEREOF.
+
+6. This License Agreement will automatically terminate upon a material breach
+of its terms and conditions.
+
+7. Nothing in this License Agreement shall be deemed to create any relationship
+of agency, partnership, or joint venture between PSF and Licensee. This License
+Agreement does not grant permission to use PSF trademarks or trade name in a
+trademark sense to endorse or promote products or services of Licensee, or any
+third party.
+
+8. By copying, installing or otherwise using Jython, Licensee agrees to be
+bound by the terms and conditions of this License Agreement.
+
+Jython 2.0, 2.1 License
+
+Copyright (c) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Jython Developers
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this
+list of conditions and the following disclaimer. Redistributions in binary form
+must reproduce the above copyright notice, this list of conditions and the
+following disclaimer in the documentation and/or other materials provided with
+the distribution. Neither the name of the Jython Developers nor the names of
+its contributors may be used to endorse or promote products derived from this
+software without specific prior written permission. THIS SOFTWARE IS PROVIDED
+BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS'' AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
+EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
+PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+ Open Source Initiative OSI - The BSD 3-Clause License
+
+
+<b> Open Source Initiative OSI - The BSD 3-Clause License </b>
+
+Copyright (c) <YEAR>, <OWNER> All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+- Redistributions of source code must retain the above copyright notice, this
+list of conditions and the following disclaimer. - Redistributions in binary
+form must reproduce the above copyright notice, this list of conditions and the
+following disclaimer in the documentation and/or other materials provided with
+the distribution. - Neither the name of the <ORGANIZATION> nor the names
+of its contributors may be used to endorse or promote products derived from
+this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+ MOZILLA PUBLIC LICENSE
+
+
+MOZILLA PUBLIC LICENSE Version 1.1 1. Definitions.
+
+1.0.1. "Commercial Use" means distribution or otherwise making the Covered Code
+available to a third party. 1.1. ''Contributor'' means each entity that creates
+or contributes to the creation of Modifications.
+
+1.2. ''Contributor Version'' means the combination of the Original Code, prior
+Modifications used by a Contributor, and the Modifications made by that
+particular Contributor.
+
+1.3. ''Covered Code'' means the Original Code or Modifications or the
+combination of the Original Code and Modifications, in each case including
+portions thereof.
+
+1.4. ''Electronic Distribution Mechanism'' means a mechanism generally accepted
+in the software development community for the electronic transfer of data.
+
+1.5. ''Executable'' means Covered Code in any form other than Source Code.
+
+1.6. ''Initial Developer'' means the individual or entity identified as the
+Initial Developer in the Source Code notice required by Exhibit A.
+
+1.7. ''Larger Work'' means a work which combines Covered Code or portions
+thereof with code not governed by the terms of this License.
+
+1.8. ''License'' means this document.
+
+1.8.1. "Licensable" means having the right to grant, to the maximum extent
+possible, whether at the time of the initial grant or subsequently acquired,
+any and all of the rights conveyed herein.
+
+1.9. ''Modifications'' means any addition to or deletion from the substance or
+structure of either the Original Code or any previous Modifications. When
+Covered Code is released as a series of files, a Modification is:
+
+A. Any addition to or deletion from the contents of a file containing Original
+Code or previous Modifications. B. Any new file that contains any part of the
+Original Code or previous Modifications.
+
+
+
+1.10. ''Original Code'' means Source Code of computer software code which is
+described in the Source Code notice required by Exhibit A as Original Code, and
+which, at the time of its release under this License is not already Covered
+Code governed by this License. 1.10.1. "Patent Claims" means any patent claim(
+s), now owned or hereafter acquired, including without limitation, method,
+process, and apparatus claims, in any patent Licensable by grantor.
+
+1.11. ''Source Code'' means the preferred form of the Covered Code for making
+modifications to it, including all modules it contains, plus any associated
+interface definition files, scripts used to control compilation and
+installation of an Executable, or source code differential comparisons against
+either the Original Code or another well known, available Covered Code of the
+Contributor's choice. The Source Code can be in a compressed or archival form,
+provided the appropriate decompression or de-archiving software is widely
+available for no charge.
+
+1.12. "You'' (or "Your") means an individual or a legal entity exercising
+rights under, and complying with all of the terms of, this License or a future
+version of this License issued under Section 6.1. For legal entities, "You''
+includes any entity which controls, is controlled by, or is under common
+control with You. For purposes of this definition, "control'' means (a) the
+power, direct or indirect, to cause the direction or management of such entity,
+whether by contract or otherwise, or (b) ownership of more than fifty percent (
+50%) of the outstanding shares or beneficial ownership of such entity.
+
+2. Source Code License. 2.1. The Initial Developer Grant. The Initial Developer
+hereby grants You a world-wide, royalty-free, non-exclusive license, subject to
+third party intellectual property claims: (a) under intellectual property
+rights (other than patent or trademark) Licensable by Initial Developer to use,
+reproduce, modify, display, perform, sublicense and distribute the Original
+Code (or portions thereof) with or without Modifications, and/or as part of a
+Larger Work; and (b) under Patents Claims infringed by the making, using or
+selling of Original Code, to make, have made, use, practice, sell, and offer
+for sale, and/or otherwise dispose of the Original Code (or portions thereof). (
+c) the licenses granted in this Section 2.1(a) and (b) are effective on the
+date Initial Developer first distributes Original Code under the terms of this
+License. (d) Notwithstanding Section 2.1(b) above, no patent license is
+granted: 1) for code that You delete from the Original Code; 2) separate from
+the Original Code; or 3) for infringements caused by: i) the modification of
+the Original Code or ii) the combination of the Original Code with other
+software or devices.
+
+
+
+2.2. Contributor Grant. Subject to third party intellectual property claims,
+each Contributor hereby grants You a world-wide, royalty-free, non-exclusive
+license
+
+(a) under intellectual property rights (other than patent or trademark)
+Licensable by Contributor, to use, reproduce, modify, display, perform,
+sublicense and distribute the Modifications created by such Contributor (or
+portions thereof) either on an unmodified basis, with other Modifications, as
+Covered Code and/or as part of a Larger Work; and (b) under Patent Claims
+infringed by the making, using, or selling of Modifications made by that
+Contributor either alone and/or in combination with its Contributor Version (or
+portions of such combination), to make, use, sell, offer for sale, have made,
+and/or otherwise dispose of: 1) Modifications made by that Contributor (or
+portions thereof); and 2) the combination of Modifications made by that
+Contributor with its Contributor Version (or portions of such combination). (c)
+the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
+Contributor first makes Commercial Use of the Covered Code. (d) Notwithstanding
+Section 2.2(b) above, no patent license is granted: 1) for any code that
+Contributor has deleted from the Contributor Version; 2) separate from the
+Contributor Version; 3) for infringements caused by: i) third party
+modifications of Contributor Version or ii) the combination of Modifications
+made by that Contributor with other software (except as part of the
+Contributor Version) or other devices; or 4) under Patent Claims infringed by
+Covered Code in the absence of Modifications made by that Contributor.
+
+
+
+3. Distribution Obligations.
+
+3.1. Application of License. The Modifications which You create or to which You
+contribute are governed by the terms of this License, including without
+limitation Section 2.2. The Source Code version of Covered Code may be
+distributed only under the terms of this License or a future version of this
+License released under Section 6.1, and You must include a copy of this License
+with every copy of the Source Code You distribute. You may not offer or impose
+any terms on any Source Code version that alters or restricts the applicable
+version of this License or the recipients' rights hereunder. However, You may
+include an additional document offering the additional rights described in
+Section 3.5. 3.2. Availability of Source Code. Any Modification which You
+create or to which You contribute must be made available in Source Code form
+under the terms of this License either on the same media as an Executable
+version or via an accepted Electronic Distribution Mechanism to anyone to whom
+you made an Executable version available; and if made available via Electronic
+Distribution Mechanism, must remain available for at least twelve (12) months
+after the date it initially became available, or at least six (6) months after
+a subsequent version of that particular Modification has been made available to
+such recipients. You are responsible for ensuring that the Source Code version
+remains available even if the Electronic Distribution Mechanism is maintained
+by a third party.
+
+3.3. Description of Modifications. You must cause all Covered Code to which You
+contribute to contain a file documenting the changes You made to create that
+Covered Code and the date of any change. You must include a prominent statement
+that the Modification is derived, directly or indirectly, from Original Code
+provided by the Initial Developer and including the name of the Initial
+Developer in (a) the Source Code, and (b) in any notice in an Executable
+version or related documentation in which You describe the origin or ownership
+of the Covered Code.
+
+3.4. Intellectual Property Matters
+
+(a) Third Party Claims. If Contributor has knowledge that a license under a
+third party's intellectual property rights is required to exercise the rights
+granted by such Contributor under Sections 2.1 or 2.2, Contributor must include
+a text file with the Source Code distribution titled "LEGAL'' which describes
+the claim and the party making the claim in sufficient detail that a recipient
+will know whom to contact. If Contributor obtains such knowledge after the
+Modification is made available as described in Section 3.2, Contributor shall
+promptly modify the LEGAL file in all copies Contributor makes available
+thereafter and shall take other steps (such as notifying appropriate mailing
+lists or newsgroups) reasonably calculated to inform those who received the
+Covered Code that new knowledge has been obtained. (b) Contributor APIs. If
+Contributor's Modifications include an application programming interface and
+Contributor has knowledge of patent licenses which are reasonably necessary to
+implement that API, Contributor must also include this information in the LEGAL
+file.
+
+(c) Representations. Contributor represents that, except as disclosed pursuant
+to Section 3.4(a) above, Contributor believes that Contributor's Modifications
+are Contributor's original creation(s) and/or Contributor has sufficient rights
+to grant the rights conveyed by this License.
+
+3.5. Required Notices. You must duplicate the notice in Exhibit A in each file
+of the Source Code. If it is not possible to put such notice in a particular
+Source Code file due to its structure, then You must include such notice in a
+location (such as a relevant directory) where a user would be likely to look
+for such a notice. If You created one or more Modification(s) You may add your
+name as a Contributor to the notice described in Exhibit A. You must also
+duplicate this License in any documentation for the Source Code where You
+describe recipients' rights or ownership rights relating to Covered Code. You
+may choose to offer, and to charge a fee for, warranty, support, indemnity or
+liability obligations to one or more recipients of Covered Code. However, You
+may do so only on Your own behalf, and not on behalf of the Initial Developer
+or any Contributor. You must make it absolutely clear than any such warranty,
+support, indemnity or liability obligation is offered by You alone, and You
+hereby agree to indemnify the Initial Developer and every Contributor for any
+liability incurred by the Initial Developer or such Contributor as a result of
+warranty, support, indemnity or liability terms You offer.
+
+3.6. Distribution of Executable Versions. You may distribute Covered Code in
+Executable form only if the requirements of Section 3.1-3.5 have been met for
+that Covered Code, and if You include a notice stating that the Source Code
+version of the Covered Code is available under the terms of this License,
+including a description of how and where You have fulfilled the obligations of
+Section 3.2. The notice must be conspicuously included in any notice in an
+Executable version, related documentation or collateral in which You describe
+recipients' rights relating to the Covered Code. You may distribute the
+Executable version of Covered Code or ownership rights under a license of Your
+choice, which may contain terms different from this License, provided that You
+are in compliance with the terms of this License and that the license for the
+Executable version does not attempt to limit or alter the recipient's rights in
+the Source Code version from the rights set forth in this License. If You
+distribute the Executable version under a different license You must make it
+absolutely clear that any terms which differ from this License are offered by
+You alone, not by the Initial Developer or any Contributor. You hereby agree to
+indemnify the Initial Developer and every Contributor for any liability
+incurred by the Initial Developer or such Contributor as a result of any such
+terms You offer.
+
+3.7. Larger Works. You may create a Larger Work by combining Covered Code with
+other code not governed by the terms of this License and distribute the Larger
+Work as a single product. In such a case, You must make sure the requirements
+of this License are fulfilled for the Covered Code.
+
+4. Inability to Comply Due to Statute or Regulation. If it is impossible for
+You to comply with any of the terms of this License with respect to some or all
+of the Covered Code due to statute, judicial order, or regulation then You
+must: (a) comply with the terms of this License to the maximum extent possible;
+and (b) describe the limitations and the code they affect. Such description
+must be included in the LEGAL file described in Section 3.4 and must be
+included with all distributions of the Source Code. Except to the extent
+prohibited by statute or regulation, such description must be sufficiently
+detailed for a recipient of ordinary skill to be able to understand it. 5.
+Application of this License. This License applies to code to which the Initial
+Developer has attached the notice in Exhibit A and to related Covered Code. 6.
+Versions of the License. 6.1. New Versions. Netscape Communications
+Corporation (''Netscape'') may publish revised and/or new versions of the
+License from time to time. Each version will be given a distinguishing version
+number. 6.2. Effect of New Versions. Once Covered Code has been published under
+a particular version of the License, You may always continue to use it under
+the terms of that version. You may also choose to use such Covered Code under
+the terms of any subsequent version of the License published by Netscape. No
+one other than Netscape has the right to modify the terms applicable to Covered
+Code created under this License.
+
+6.3. Derivative Works. If You create or use a modified version of this License (
+which you may only do in order to apply it to code which is not already Covered
+Code governed by this License), You must (a) rename Your license so that the
+phrases ''Mozilla'', ''MOZILLAPL'', ''MOZPL'', ''Netscape'', "MPL", ''NPL'' or
+any confusingly similar phrase do not appear in your license (except to note
+that your license differs from this License) and (b) otherwise make it clear
+that Your version of the license contains terms which differ from the Mozilla
+Public License and Netscape Public License. (Filling in the name of the Initial
+Developer, Original Code or Contributor in the notice described in Exhibit A
+shall not of themselves be deemed to be modifications of this License.)
+
+7. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN
+"AS IS'' BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
+INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
+DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE
+ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU.
+SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL
+DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING,
+REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART
+OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT
+UNDER THIS DISCLAIMER. 8. TERMINATION. 8.1. This License and the rights
+granted hereunder will terminate automatically if You fail to comply with terms
+herein and fail to cure such breach within 30 days of becoming aware of the
+breach. All sublicenses to the Covered Code which are properly granted shall
+survive any termination of this License. Provisions which, by their nature,
+must remain in effect beyond the termination of this License shall survive.
+8.2. If You initiate litigation by asserting a patent infringement claim (
+excluding declatory judgment actions) against Initial Developer or a
+Contributor (the Initial Developer or Contributor against whom You file such
+action is referred to as "Participant") alleging that:
+
+(a) such Participant's Contributor Version directly or indirectly infringes
+any patent, then any and all rights granted by such Participant to You under
+Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from
+Participant terminate prospectively, unless if within 60 days after receipt of
+notice You either: (i) agree in writing to pay Participant a mutually
+agreeable reasonable royalty for Your past and future use of Modifications made
+by such Participant, or (ii) withdraw Your litigation claim with respect to the
+Contributor Version against such Participant. If within 60 days of notice, a
+reasonable royalty and payment arrangement are not mutually agreed upon in
+writing by the parties or the litigation claim is not withdrawn, the rights
+granted by Participant to You under Sections 2.1 and/or 2.2 automatically
+terminate at the expiration of the 60 day notice period specified above.
+
+(b) any software, hardware, or device, other than such Participant's
+Contributor Version, directly or indirectly infringes any patent, then any
+rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are
+revoked effective as of the date You first made, used, sold, distributed, or
+had made, Modifications made by that Participant.
+
+8.3. If You assert a patent infringement claim against Participant alleging
+that such Participant's Contributor Version directly or indirectly infringes
+any patent where such claim is resolved (such as by license or settlement)
+prior to the initiation of patent infringement litigation, then the reasonable
+value of the licenses granted by such Participant under Sections 2.1 or 2.2
+shall be taken into account in determining the amount or value of any payment
+or license.
+
+8.4. In the event of termination under Sections 8.1 or 8.2 above, all end
+user license agreements (excluding distributors and resellers) which have been
+validly granted by You or any distributor hereunder prior to termination shall
+survive termination.
+
+9. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY,
+WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU THE
+INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
+OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY
+INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER
+INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE,
+COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
+LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH
+DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
+PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE
+LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
+LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
+LIMITATION MAY NOT APPLY TO YOU. 10. U.S. GOVERNMENT END USERS. The Covered
+Code is a ''commercial item,'' as that term is defined in 48 C.F.R. 2.101 (Oct.
+1995), consisting of ''commercial computer software'' and ''commercial computer
+software documentation,'' as such terms are used in 48 C.F.R. 12.212 (Sept.
+1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through
+227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with
+only those rights set forth herein. 11. MISCELLANEOUS. This License represents
+the complete agreement concerning subject matter hereof. If any provision of
+this License is held to be unenforceable, such provision shall be reformed only
+to the extent necessary to make it enforceable. This License shall be governed
+by California law provisions (except to the extent applicable law, if any,
+provides otherwise), excluding its conflict-of-law provisions. With respect to
+disputes in which at least one party is a citizen of, or an entity chartered or
+registered to do business in the United States of America, any litigation
+relating to this License shall be subject to the jurisdiction of the Federal
+Courts of the Northern District of California, with venue lying in Santa Clara
+County, California, with the losing party responsible for costs, including
+without limitation, court costs and reasonable attorneys' fees and expenses.
+The application of the United Nations Convention on Contracts for the
+International Sale of Goods is expressly excluded. Any law or regulation which
+provides that the language of a contract shall be construed against the drafter
+shall not apply to this License. 12. RESPONSIBILITY FOR CLAIMS. As between
+Initial Developer and the Contributors, each party is responsible for claims
+and damages arising, directly or indirectly, out of its utilization of rights
+under this License and You agree to work with Initial Developer and
+Contributors to distribute such responsibility on an equitable basis. Nothing
+herein is intended or shall be deemed to constitute any admission of liability.
+13. MULTIPLE-LICENSED CODE. Initial Developer may designate portions of the
+Covered Code as �Multiple-Licensed?. �Multiple-Licensed? means that the
+Initial Developer permits you to utilize portions of the Covered Code under
+Your choice of the MPL or the alternative licenses, if any, specified by the
+Initial Developer in the file described in Exhibit A.
+
+EXHIBIT A -Mozilla Public License.
+
+The contents of this file are subject to the Mozilla Public License Version
+1.1 (the "License"); you may not use this file except in compliance with the
+License. You may obtain a copy of the License at http://www.mozilla.org/MPL/
+Software distributed under the License is distributed on an "AS IS" basis,
+WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for
+the specific language governing rights and limitations under the License.
+
+The Original Code is Javassist.
+
+The Initial Developer of the Original Code is Shigeru Chiba. Portions created
+by the Initial Developer are Copyright (C) 1999-2010 Shigeru Chiba. All Rights
+Reserved.
+
+Contributor(s): ______________________________________.
+
+Alternatively, the contents of this file may be used under the terms of the GNU
+Lesser General Public License Version 2.1 or later (the "LGPL"), in which case
+the provisions of the LGPL are applicable instead of those above. If you wish
+to allow use of your version of this file only under the terms of the LGPL, and
+not to allow others to use your version of this file under the terms of the
+MPL, indicate your decision by deleting the provisions above and replace them
+with the notice and other provisions required by the LGPL. If you do not delete
+the provisions above, a recipient may use your version of this file under the
+terms of either the MPL or the LGPL.
+
+
+
+ Sun Microsystems, Inc. ("Sun") ENTITLEMENT for SOFTWARE
+
+<b>Sun Microsystems, Inc. ("Sun") ENTITLEMENT for SOFTWARE
+</b>
+Licensee/Company: Entity receiving Software.
+
+Effective Date: Date of delivery of the Software to You.
+
+Software: JavaMail 1.4.3
+
+License Term: Perpetual (subject to termination under the SLA).
+
+Licensed Unit: Software Copy.
+
+Licensed unit Count: Unlimited.
+
+Permitted Uses:
+
+1. You may reproduce and use the Software for Your own Individual,
+Commercial and Research and Instructional Use only for the purposes of
+designing, developing, testing, and running Your applets and
+applications ("Programs").
+
+2. Subject to the terms and conditions of this Agreement and
+restrictions and exceptions set forth in the Software's documentation,
+You may reproduce and distribute portions of Software identified as a
+redistributable in the documentation (each a "Redistributable"),
+provided that You comply with the following (note that You may be
+entitled to reproduce and distribute other portions of the Software not
+defined in the documentation as a Redistributable under certain other
+licenses as described in the THIRDPARTYLICENSEREADME, if applicable):
+
+(a) You distribute Redistributable complete and unmodified and only
+bundled as part of Your Programs,
+
+(b) Your Programs add significant and primary functionality to the
+Redistributable,
+
+(c) You distribute Redistributable for the sole purpose of running Your
+Programs,
+
+(d) You do not distribute additional software intended to replace any
+component(s) of the Redistributable,
+
+(e) You do not remove or alter any proprietary legends or notices
+contained in or on the Redistributable.
+
+(f) You only distribute the Redistributable subject to a license
+agreement that protects Sun's interests consistent with the terms
+contained in this Agreement, and
+
+(g) You agree to defend and indemnify Sun and its licensors from and
+against any damages, costs, liabilities, settlement amounts and/or
+expenses (including attorneys' fees) incurred in connection with any
+claim, lawsuit or action by any third party that arises or results from
+the use or distribution of any and all Programs and/or
+Redistributable.
+
+3. Java Technology Restrictions. You may not create, modify, or change
+the behavior of, or authorize Your licensees to create, modify, or
+change the behavior of, classes, interfaces, or subpackages that are in
+any way identified as "java", "javax", "sun" or similar convention as
+specified by Sun in any naming convention designation.
+
+4. No Diagnostic, Maintenance, Repair or Technical Support Services.
+The scope of Your license does not include any right, express or
+implied, (i) to access, copy, distribute, display or use the Software
+to provide diagnostic, maintenance, repair or technical support
+services for Sun softwa re or Sun hardware on behalf of any third party
+for Your direct or indirect commercial gain or advantage, without Sun's
+prior written authorization, or (ii) for any third party to access,
+copy, distribute, display or use the Software to provide diagnostic,
+maintenance, repair or technical support services for Sun software or
+Sun hardware on Your behalf for such party's direct or indirect
+commercial gain or advantage, without Sun's prior written
+authorization. The limitations set forth in this paragraph apply to any
+and all error corrections, patches, updates, and upgrades to the
+Software You may receive, access, download or otherwise obtain from
+Sun.
+
+5. Records and Documentation. During the term of the SLA and
+Entitlement, and for a period of three (3) years thereafter, You agree
+to keep proper records and documentation of Your compliance with the
+SLA and Entitlement. Upon Sun's reasonable request, You will provide
+copies of such records and documentation to Sun for the purpose of
+confirming Your compliance with the terms and conditions of the SLA and
+Entitlement. This section will survive any termination of the SLA and
+Entitlement. You may terminate this SLA and Entitlement at any time by
+destroying all copies of the Software in which case the obligations set
+forth in Section 7 of the SLA shall apply.
+
+
+Sun Microsystems, Inc. ("Sun")
+SOFTWARE LICENSE AGREEMENT
+
+READ THE TERMS OF THIS AGREEMENT ("AGREEMENT") CAREFULLY BEFORE OPENING
+SOFTWARE MEDIA PACKAGE. BY OPENING SOFTWARE MEDIA PACKAGE, YOU AGREE TO
+THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCESSING SOFTWARE
+ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING
+THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE
+TO ALL OF THE TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE
+OF PURCHASE FOR A REFUND OR, IF SOFTWARE IS ACCESSED ELECTRONICALLY,
+SELECT THE "DECLINE" (OR "EXIT") BUTTON AT THE END OF THIS AGREEMENT.
+IF YOU HAVE SEPARATELY AGREED TO LICENSE TERMS ("MASTER TERMS") FOR
+YOUR LICENSE TO THIS SOFTWARE, THEN SECTIONS 1-6 OF THIS AGREEMENT
+("SUPPLEMENTAL LICENSE TERMS") SHALL SUPPLEMENT AND SUPERSEDE THE
+MASTER TERMS IN RELATION TO THIS SOFTWARE.
+
+1. Definitions.
+
+(a) "Entitlement" means the collective set of applicable documents
+authorized by Sun evidencing your obligation to pay associated fees (if
+any) for the license, associated Services, and the authorized scope of
+use of Software under this Agreement.
+
+(b) "Licensed Unit" means the unit of measure by which your use of
+Software and/or Service is licensed, as described in your Entitlement.
+
+(c) "Permitted Use" means the licensed Software use(s) authorized
+in this Agreement as specified in your Entitlement. The Permitted Use
+for any bundled Sun software not specified in your Entitlement will be
+evaluation use as provided in Section 3.
+
+(d) "Service" means the service(s) that Sun or its delegate will
+provide, if any, as selected in your Entitlement and as further
+described in the applicable service listings at
+www.sun.com/service/servicelist.
+
+(e) "Software" means the Sun software described in your
+Entitlement. Also, certain software may be included for evaluation use
+under Section 3.
+
+(f) "You" and "Your" means the individual or legal entity specified
+in the Entitlement, or for evaluation purposes, the entity performing
+the evaluation.
+
+2. License Grant and Entitlement.
+
+Subject to the terms of your Entitlement, Sun grants you a
+nonexclusive, nontransferable limited license to use Software for its
+Permitted Use for the license term. Your Entitlement will specify (a)
+Software licensed, (b) the Permitted Use, (c) the license term, and (d)
+the Licensed Units.
+
+Additionally, if your Entitlement includes Services, then it will also
+specify the (e) Service and (f) service term.
+
+If your rights to Software or Services are limited in duration and the
+date such rights begin is other than the purchase date, your
+Entitlement will provide that beginning date(s).
+
+The Entitlement may be delivered to you in various ways depending on
+the manner in which you obtain Software and Services, for example, the
+Entitlement may be provided in your receipt, invoice or your contract
+with Sun or authorized Sun reseller. It may also be in electronic
+format if you download Software.
+
+3. Permitted Use.
+
+As selected in your Entitlement, one or more of the following Permitted
+Uses will apply to your use of Software. Unless you have an Entitlement
+that expressly permits it, you may not use Software for any of the
+other Permitted Uses. If you don't have an Entitlement, or if your
+Entitlement doesn't cover additional software delivered to you, then
+such software is for your Evaluation Use.
+
+(a) Evaluation Use. You may evaluate Software internally for a period
+of 90 days from your first use.
+
+(b) Research and Instructional Use. You may use Software internally to
+design, develop and test, and also to provide instruction on such
+uses.
+
+(c) Individual Use. You may use Software internally for personal,
+individual use.
+
+(d) Commercial Use. You may use Software internally for your own
+commercial purposes.
+
+(e) Service Provider Use. You may make Software functionality
+accessible (but not by providing Software itself or through outsourcing
+services) to your end users in an extranet deployment, but not to your
+affiliated companies or to government agencies.
+
+4. Licensed Units.
+
+Your Permitted Use is limited to the number of Licensed Units stated in
+your Entitlement. If you require additional Licensed Units, you will
+need additional Entitlement(s).
+
+5. Restrictions.
+
+(a) The copies of Software provided to you under this Agreement are
+licensed, not sold, to you by Sun. Sun reserves all rights not
+expressly granted. (b) You may make a single archival copy of Software,
+but otherwise may not copy, modify, or distribute Software. However if
+the Sun documentation accompanying Software lists specific portions of
+Software, such as header files, class libraries, reference source code,
+and/or redistributable files, that may be handled differently, you may
+do so only as provided in the Sun documentation. (c) You may not rent,
+lease, lend or encumber Software. (d) Unless enforcement is prohibited
+by applicable law, you may not decompile, or reverse engineer Software.
+(e) The terms and conditions of this Agreement will apply to any
+Software updates, provided to you at Sun's discretion, that replace
+and/or supplement the original Software, unless such update contains a
+separate license. (f) You may not publish or provide the results of any
+benchmark or comparison tests run on Software to any third party
+without the prior written consent of Sun. (g) Software is confidential
+and copyrighted. (h) Unless otherwise specified, if Software is
+delivered with embedded or bundled software that enables functionality
+of Software, you may not use such software on a stand-alone basis or
+use any portion of such software to interoperate with any program(s)
+other than Software. (i) Software may contain programs that perform
+automated collection of system data and/or automated software updating
+services. System data collected through such programs may be used by
+Sun, its subcontractors, and its service delivery partners for the
+purpose of providing you with remote system services and/or improving
+Sun's software and systems. (j) Software is not designed, licensed or
+intended for use in the design, construction, operation or maintenance
+of any nuclear facility and Sun and its licensors disclaim any express
+or implied warranty of fitness for such uses. (k) No right, title or
+interest in or to any trademark, service mark, logo or trade name of
+Sun or its licensors is granted under this Agreement.
+
+6. Java Compatibility and Open Source.
+
+Software may contain Java technology. You may not create additional
+classes to, or modifications of, the Java technology, except under
+compatibility requirements available under a separate agreement
+available at www.java.net.
+
+Sun supports and benefits from the global community of open source
+developers, and thanks the community for its important contributions
+and open standards-based technology, which Sun has adopted into many of
+its products.
+
+Please note that portions of Software may be provided with notices and
+open source licenses from such communities and third parties that
+govern the use of those portions, and any licenses granted hereunder do
+not alter any rights and obligations you may have under such open
+source licenses, however, the disclaimer of warranty and limitation of
+liability provisions in this Agreement will apply to all Software in
+this distribution.
+
+7. Term and Termination.
+
+The license and service term are set forth in your Entitlement(s). Your
+rights under this Agreement will terminate immediately without notice
+from Sun if you materially breach it or take any action in derogation
+of Sun's and/or its licensors' rights to Software. Sun may terminate
+this Agreement should any Software become, or in Sun's reasonable
+opinion likely to become, the subject of a claim of intellectual
+property infringement or trade secret misappropriation. Upon
+termination, you will cease use of, and destroy, Software and confirm
+compliance in writing to Sun. Sections 1, 5, 6, 7, and 9-15 will
+survive termination of the Agreement.
+
+8. Limited Warranty.
+
+Sun warrants to you that for a period of 90 days from the date of
+purchase, as evidenced by a copy of the receipt, the media on which
+Software is furnished (if any) will be free of defects in materials and
+workmanship under normal use. Except for the foregoing, Software is
+provided "AS IS". Your exclusive remedy and Sun's entire liability
+under this limited warranty will be at Sun's option to replace Software
+media or refund the fee paid for Software. Some states do not allow
+limitations on certain implied warranties, so the above may not apply
+to you. This limited warranty gives you specific legal rights. You may
+have others, which vary from state to state.
+
+9. Disclaimer of Warranty.
+
+UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS,
+REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT
+ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO
+BE LEGALLY INVALID.
+
+10. Limitation of Liability.
+
+TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS
+LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR
+SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
+HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR
+RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS
+BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's
+liability to you, whether in contract, tort (including negligence), or
+otherwise, exceed the amount paid by you for Software under this
+Agreement. The foregoing limitations will apply even if the above
+stated warranty fails of its essential purpose. Some states do not
+allow the exclusion of incidental or consequential damages, so some of
+the terms above may not be applicable to you.
+
+11. Export Regulations.
+
+All Software, documents, technical data, and any other materials
+delivered under this Agreement are subject to U.S. export control laws
+and may be subject to export or import regulations in other countries.
+You agree to comply strictly with these laws and regulations and
+acknowledge that you have the responsibility to obtain any licenses to
+export, re-export, or import as may be required after delivery to you.
+
+12. U.S. Government Restricted Rights.
+
+If Software is being acquired by or on behalf of the U.S. Government or
+by a U.S. Government prime contractor or subcontractor (at any tier),
+then the Government's rights in Software and accompanying documentation
+will be only as set forth in this Agreement; this is in accordance with
+48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD)
+acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD
+acquisitions).
+
+13. Governing Law.
+
+Any action related to this Agreement will be governed by California law
+and controlling U.S. federal law. No choice of law rules of any
+jurisdiction will apply.
+
+14. Severability.
+
+If any provision of this Agreement is held to be unenforceable, this
+Agreement will remain in effect with the provision omitted, unless
+omission would frustrate the intent of the parties, in which case this
+Agreement will immediately terminate.
+
+15. Integration.
+
+This Agreement, including any terms contained in your Entitlement, is
+the entire agreement between you and Sun relating to its subject
+matter. It supersedes all prior or contemporaneous oral or written
+communications, proposals, representations and warranties and prevails
+over any conflicting or additional terms of any quote, order,
+acknowledgment, or other communication between the parties relating to
+its subject matter during the term of this Agreement. No modification
+of this Agreement will be binding, unless in writing and signed by an
+authorized representative of each party.
+
+Please contact Sun Microsystems, Inc. 4150 Network Circle, Santa Clara,
+California 95054 if you have questions.
+
+
+
+ COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.1
+
+<b>COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.1
+</b>
+
+ 1. Definitions.
+1.1. "Contributor" means each individual or entity that creates or contributes to the
+creation of Modifications.
+1.2. "Contributor Version" means the combination of the Original Software, prior
+Modifications used by a Contributor (if any), and the Modifications
+made by that particular Contributor.
+1.3. "Covered Software" means (a) the Original Software, or (b) Modifications, or (c)
+the combination of files containing Original Software with files
+containing Modifications, in each case including portions thereof.
+1.4. "Executable" means the Covered Software in any form other than Source Code.
+1.5. "Initial Developer" means the individual or entity that first makes Original
+Software available under this License.
+1.6. "Larger Work" means a work which combines Covered Software or portions thereof
+with code not governed by the terms of this License.
+1.7. "License" means this document.
+1.8. "Licensable" means having the right to grant, to the maximum extent possible,
+whether at the time of the initial grant or subsequently acquired,
+any and all of the rights conveyed herein.
+1.9. "Modifications" means the Source Code and Executable form of any of the following:
+A. Any file that results from an addition to, deletion from or modification of the
+contents of a file containing Original Software or previous
+Modifications;
+B. Any new file that contains any part of the Original Software or previous
+Modification; or
+C. Any new file that is contributed or otherwise made available under the terms
+of this License.
+1.10. "Original Software" means the Source Code and Executable form of computer
+software code that is originally released under this License.
+1.11. "Patent Claims" means any patent claim(s), now owned or hereafter acquired,
+including without limitation, method, process, and apparatus claims,
+in any patent Licensable by grantor.
+1.12. "Source Code" means (a) the common form of computer software code in which
+modifications are made and (b) associated documentation included
+in or with such code.
+1.13. "You" (or "Your") means an individual or a legal entity exercising rights under,
+and complying with all of the terms of, this License. For legal
+entities, "You" includes any entity which controls, is controlled by,
+or is under common control with You. For purposes of this definition,
+"control" means (a) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or otherwise,
+or (b) ownership of more than fifty percent (50%) of the outstanding
+shares or beneficial ownership of such entity.
+2. License Grants.
+2.1. The Initial Developer Grant.
+Conditioned upon Your compliance with Section 3.1 below and subject to third party
+intellectual property claims, the Initial Developer hereby grants
+You a world-wide, royalty-free, non-exclusive license:
+(a) under intellectual property rights (other than patent or trademark) Licensable
+by Initial Developer, to use, reproduce, modify, display, perform,
+sublicense and distribute the Original Software (or portions thereof),
+with or without Modifications, and/or as part of a Larger Work; and
+(b) under Patent Claims infringed by the making, using or selling of Original Software,
+to make, have made, use, practice, sell, and offer for sale, and/or
+otherwise dispose of the Original Software (or portions thereof).
+(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date
+Initial Developer first distributes or otherwise makes the
+Original Software available to a third party under the terms
+of this License.
+(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code
+that You delete from the Original Software, or (2) for infringements
+caused by: (i) the modification of the Original Software, or (ii)
+the combination of the Original Software with other software or devices.
+2.2. Contributor Grant.
+Conditioned upon Your compliance with Section 3.1 below and subject to third
+party intellectual property claims, each Contributor hereby grants
+You a world-wide, royalty-free, non-exclusive license:
+(a) under intellectual property rights (other than patent or trademark)
+Licensable by Contributor to use, reproduce, modify, display, perform,
+sublicense and distribute the Modifications created by such Contributor
+(or portions thereof), either on an unmodified basis, with other
+Modifications, as Covered Software and/or as part of a Larger Work; and
+(b) under Patent Claims infringed by the making, using, or selling of Modifications
+made by that Contributor either alone and/or in combination with its
+Contributor Version (or portions of such combination), to make, use, sell,
+offer for sale, have made, and/or otherwise dispose of: (1) Modifications
+made by that Contributor (or portions thereof); and (2) the combination
+of Modifications made by that Contributor with its Contributor Version
+(or portions of such combination).
+(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
+Contributor first distributes or otherwise makes the Modifications
+available to a third party.
+(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for
+any code that Contributor has deleted from the Contributor Version; (2) for
+infringements caused by: (i) third party modifications of
+Contributor Version, or (ii) the combination of Modifications made by that
+Contributor with other software (except as part of the Contributor Version)
+or other devices; or (3) under Patent Claims infringed by Covered Software
+in the absence of Modifications made by that Contributor.
+3. Distribution Obligations.
+3.1. Availability of Source Code.
+Any Covered Software that You distribute or otherwise make available in Executable
+form must also be made available in Source Code form and that Source Code form
+must be distributed only under the terms of this License. You must include
+a copy of this License with every copy of the Source Code form of the
+Covered Software You distribute or otherwise make available. You must inform
+recipients of any such Covered Software in Executable form as to how they
+can obtain such Covered Software in Source Code form in a reasonable manner
+on or through a medium customarily used for software exchange.
+3.2. Modifications.
+The Modifications that You create or to which You contribute are governed by the
+terms of this License. You represent that You believe Your Modifications are Your
+original creation(s) and/or You have sufficient rights to grant the rights
+conveyed by this License.
+3.3. Required Notices.
+You must include a notice in each of Your Modifications that identifies You as the
+Contributor of the Modification. You may not remove or alter any copyright,
+patent or trademark notices contained within the Covered Software, or any
+notices of licensing or any descriptive text giving attribution to any
+Contributor or the Initial Developer.
+3.4. Application of Additional Terms.
+You may not offer or impose any terms on any Covered Software in Source Code form that
+alters or restricts the applicable version of this License or the recipients' rights
+hereunder. You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered Software.
+However, you may do so only on Your own behalf, and not on behalf of the
+Initial Developer or any Contributor. You must make it absolutely clear
+that any such warranty, support, indemnity or liability obligation is
+offered by You alone, and You hereby agree to indemnify the Initial Developer
+and every Contributor for any liability incurred by the Initial Developer or
+such Contributor as a result of warranty, support, indemnity or liability
+terms You offer.
+3.5. Distribution of Executable Versions.
+You may distribute the Executable form of the Covered Software under the terms of this
+License or under the terms of a license of Your choice, which may contain terms
+different from this License, provided that You are in compliance with the
+terms of this License and that the license for the Executable form does
+not attempt to limit or alter the recipient's rights in the Source Code
+form from the rights set forth in this License. If You distribute the
+Covered Software in Executable form under a different license, You must make
+it absolutely clear that any terms which differ from this License are offered
+by You alone, not by the Initial Developer or Contributor. You hereby agree to
+indemnify the Initial Developer and every Contributor for any liability
+incurred by the Initial Developer or such Contributor as a result of any
+such terms You offer.
+3.6. Larger Works.
+You may create a Larger Work by combining Covered Software with other code not
+governed by the terms of this License and distribute the Larger Work as a single
+product. In such a case, You must make sure the requirements of this License
+are fulfilled for the Covered Software.
+4. Versions of the License.
+4.1. New Versions.
+Oracle is the initial license steward and may publish revised and/or new versions of
+this License from time to time. Each version will be given a distinguishing
+version number. Except as provided in Section 4.3, no one other than
+the license steward has the right to modify this License.
+4.2. Effect of New Versions.
+You may always continue to use, distribute or otherwise make the Covered Software
+available under the terms of the version of the License under which You originally
+received the Covered Software. If the Initial Developer includes a notice
+in the Original Software prohibiting it from being distributed or otherwise
+made available under any subsequent version of the License, You must
+distribute and make the Covered Software available under the terms of the
+version of the License under which You originally received the Covered Software.
+Otherwise, You may also choose to use, distribute or otherwise make the
+Covered Software available under the terms of any subsequent version of the
+License published by the license steward.
+4.3. Modified Versions.
+When You are an Initial Developer and You want to create a new license for Your
+Original Software, You may create and use a modified version of this License if You:
+(a) rename the license and remove any references to the name of the license steward
+(except to note that the license differs from this License); and (b) otherwise
+make it clear that the license contains terms which differ from this License.
+5. DISCLAIMER OF WARRANTY.
+COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
+WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE,
+FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY
+AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE
+PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR
+ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING,
+REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART
+OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT
+UNDER THIS DISCLAIMER.
+
+6. TERMINATION.
+6.1. This License and the rights granted hereunder will terminate automatically if
+You fail to comply with terms herein and fail to cure such breach within 30 days
+of becoming aware of the breach. Provisions which, by their nature, must remain in
+effect beyond the termination of this License shall survive.
+6.2. If You assert a patent infringement claim (excluding declaratory judgment actions)
+against Initial Developer or a Contributor (the Initial Developer or Contributor
+against whom You assert such claim is referred to as "Participant") alleging that the
+Participant Software (meaning the Contributor Version where the Participant
+is a Contributor or the Original Software where the Participant is the Initial
+Developer) directly or indirectly infringes any patent, then any and all rights
+granted directly or indirectly to You by such Participant, the Initial Developer
+(if the Initial Developer is not the Participant) and all Contributors under
+Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant
+terminate prospectively and automatically at the expiration of such 60 day notice
+period, unless if within such 60 day period You withdraw Your claim with respect
+to the Participant Software against such Participant either unilaterally
+or pursuant to a written agreement with Participant.
+6.3. If You assert a patent infringement claim against Participant alleging that the
+Participant Software directly or indirectly infringes any patent where
+such claim is resolved (such as by license or settlement) prior to the
+initiation of patent infringement litigation, then the reasonable value
+of the licenses granted by such Participant under Sections 2.1 or 2.2
+shall be taken into account in determining the amount or value of any
+payment or license.
+6.4. In the event of termination under Sections 6.1 or 6.2 above, all end user licenses
+that have been validly granted by You or any distributor hereunder prior
+to termination (excluding licenses granted to You by any distributor)
+shall survive termination.
+7. LIMITATION OF LIABILITY.
+UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
+CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER
+CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER
+OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT,
+SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING,
+WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER
+FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES,
+EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
+THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
+PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE
+LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
+LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
+LIMITATION MAY NOT APPLY TO YOU.
+
+8. U.S. GOVERNMENT END USERS.
+The Covered Software is a "commercial item," as that term is defined in 48 C.F.R. 2.101
+(Oct. 1995), consisting of "commercial computer software" (as that term
+is defined at 48 C.F.R. § 252.227-7014(a)(1)) and "commercial computer
+software documentation" as such terms are used in 48 C.F.R. 12.212
+(Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1
+through 227.7202-4 (June 1995), all U.S. Government End Users acquire
+Covered Software with only those rights set forth herein. This U.S. Government
+Rights clause is in lieu of, and supersedes, any other FAR, DFAR, or other
+clause or provision that addresses Government rights in computer software
+under this License.
+
+9. MISCELLANEOUS.
+This License represents the complete agreement concerning subject matter hereof. If any
+provision of this License is held to be unenforceable, such provision
+shall be reformed only to the extent necessary to make it enforceable.
+This License shall be governed by the law of the jurisdiction specified
+in a notice contained within the Original Software (except to the extent
+applicable law, if any, provides otherwise), excluding such jurisdiction's
+conflict-of-law provisions. Any litigation relating to this License
+shall be subject to the jurisdiction of the courts located in the
+jurisdiction and venue specified in a notice contained within the
+Original Software, with the losing party responsible for costs,
+including, without limitation, court costs and reasonable attorneys'
+fees and expenses. The application of the United Nations Convention on
+Contracts for the International Sale of Goods is expressly excluded.
+Any law or regulation which provides that the language of a contract
+shall be construed against the drafter shall not apply to this License.
+You agree that You alone are responsible for compliance with the
+United States export administration regulations (and the export control
+laws and regulation of any other countries) when You use, distribute
+or otherwise make available any Covered Software.
+
+10. RESPONSIBILITY FOR CLAIMS.
+As between Initial Developer and the Contributors, each party is responsible for
+claims and damages arising, directly or indirectly, out of its
+utilization of rights under this License and You agree to work with
+Initial Developer and Contributors to distribute such responsibility
+on an equitable basis. Nothing herein is intended or shall be
+deemed to constitute any admission of liability.
+
+NOTICE PURSUANT TO SECTION 9 OF THE COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
+The code released under the CDDL shall be governed by the laws of the State of
+California (excluding conflict-of-law provisions). Any litigation relating to this
+License shall be subject to the jurisdiction of the Federal Courts of
+the Northern District of California and the state courts of the State
+of California, with venue lying in Santa Clara County, California.
+
+
+
+
+
+
+
+GNU GENERAL PUBLIC LICENSE
+
+
+ <b> GNU GENERAL PUBLIC LICENSE</b>
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software
+ interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Program does not specify a
+version number of this License, you may choose any version ever
+published by the Free Software Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ 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
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
+
+
+
+"CLASSPATH" EXCEPTION TO THE GPL VERSION 2
+
+Certain source files distributed by Sun Microsystems, Inc. are subject
+to the following clarification and special exception to the GPL Version
+2, but only where Sun has expressly included in the particular source
+file's header the words
+
+"Sun designates this particular file as subject to the "Classpath"
+exception as provided by Sun in the License file that accompanied this
+code."
+
+Linking this library statically or dynamically with other modules is
+making a combined work based on this library. Thus, the terms and
+conditions of the GNU General Public License Version 2 cover the whole
+combination.
+
+As a special exception, the copyright holders of this library give you
+permission to link this library with independent modules to produce an
+executable, regardless of the license terms of these independent modules,
+and to copy and distribute the resulting executable under terms of your
+choice, provided that you also meet, for each linked independent module,
+the terms and conditions of the license of that module.? An independent
+module is a module which is not derived from or based on this library.?
+If you modify this library, you may extend this exception to your
+version of the library, but you are not obligated to do so.? If you do
+not wish to do so, delete this exception statement from your version.
+
+
+
+PostgreSQL Database Management System
+
+PostgreSQL Database Management System
+(formerly known as Postgres, then as Postgres95)
+
+Portions Copyright (c) 1996-2012, The PostgreSQL Global Development Group
+
+Portions Copyright (c) 1994, The Regents of the University of California
+
+Permission to use, copy, modify, and distribute this software and its documentation
+ for any purpose, without fee,
+and without a written agreement is hereby granted, provided that the above copyright
+ notice and this paragraph and
+the following two paragraphs appear in all copies.
+
+IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT,
+ INDIRECT, SPECIAL, INCIDENTAL, OR
+CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE
+ AND ITS DOCUMENTATION, EVEN
+IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING,
+ BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED
+ HEREUNDER IS ON AN "AS IS" BASIS, AND THE
+UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT,
+ UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
+
+
+
+PostgreSQL JDBC driver license
+
+ PostgreSQL JDBC driver license
+
+Copyright (c) 1997-2011, PostgreSQL Global Development Group
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice,
+ this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+3. Neither the name of the PostgreSQL Global Development Group nor the names
+ of its contributors may be used to endorse or promote products derived
+ from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+
+
+JDOM license
+
+ JDOM license
+
+ Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin.
+ All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ 1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions, and the following disclaimer.
+
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions, and the disclaimer that follows
+ these conditions in the documentation and/or other materials
+ provided with the distribution.
+
+ 3. The name "JDOM" must not be used to endorse or promote products
+ derived from this software without prior written permission. For
+ written permission, please contact <request_AT_jdom_DOT_org>.
+
+ 4. Products derived from this software may not be called "JDOM", nor
+ may "JDOM" appear in their name, without prior written permission
+ from the JDOM Project Management <request_AT_jdom_DOT_org>.
+
+ In addition, we request (but do not require) that you include in the
+ end-user documentation provided with the redistribution and/or in the
+ software itself an acknowledgement equivalent to the following:
+ "This product includes software developed by the
+ JDOM Project (http://www.jdom.org/)."
+ Alternatively, the acknowledgment may be graphical using the logos
+ available at http://www.jdom.org/images/logos.
+
+ THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+ WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT
+ CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+ USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+ OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ SUCH DAMAGE.
+
+ This software consists of voluntary contributions made by many
+ individuals on behalf of the JDOM Project and was originally
+ created by Jason Hunter <jhunter_AT_jdom_DOT_org> and
+ Brett McLaughlin <brett_AT_jdom_DOT_org>. For more information
+ on the JDOM Project, please see <http://www.jdom.org/>.
+
+
+
+RoX
+
+ RoX is licensed under the BSD license. This is the simplest way I know how to say
+ "do as you please".
+
+Copyright (c) 2006, James Greenfield
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+ * Neither the name of the nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+UUID
+
+eaio: UUID - an implementation of the UUID specification
+Copyright (c) 2003-2007 Johann Burkard (jb@eaio.com) http://eaio.com.
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the "Software"),
+to deal in the Software without restriction, including without limitation
+the rights to use, copy, modify, merge, publish, distribute, sublicense,
+and/or sell copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
+NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
+DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
+OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
+USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+
+24x24 Free Application Icons
+
+<b>24x24 Free Application Icons
+</b>
+This icon set is free for use in personal and commercial projects.
+
+License Agreement
+
+By purchasing icons from Aha-Soft, You (the purchaser)
+agree to the terms of this agreement, as detailed below.
+
+You may use the icons from Aha-Soft in commercial and
+personal design projects, software or Internet products.
+Icons can be displayed in documentation, help files, and
+advertising materials. You are free to sell and distribute
+products and projects using purchased icons without further
+royalty fees.
+
+All icon files are provided 'as is'. Aha-Soft cannot be
+held liable for any negative issues that may occur as a
+result of using the icons.
+
+You agree that all ownership and copyright of the icons
+remains the property of Aha-Soft. You may not resell,
+distribute, lease, license or sub-license the icons or
+modified icons (or a subset of the icons), to any third
+party unless they are incorporated into your software or
+design products.
+
+If you have any questions regarding copyright or licensing,
+including whether another license is required for icon use
+within products, please contact us here: www.aha-soft.com/support.htm
+
+Product page: http://www.small-icons.com/stock-icons/24x24-free-application-icons.htm
+
+Icon Design Service
+
+We can design custom icons for you. Please find the basic information
+about ordering icons, pricing and the portfolio here:
+www.aha-soft.com/customdev/design.htm
+
+
+Notice
+Web-site small-icons.com belongs to Aha-Soft.
+
+Support page: http://www.aha-soft.com/support.htm
+
+Copyright � 2009 Aha-Soft. All rights reserved.
+
+
+
+SLF4J License
+
+ SLF4J License
+
+Copyright (c) 2004-2008 QOS.ch
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+
+Flot License
+
+ Flot License
+
+Copyright (c) 2007-2014 IOLA and Ole Laursen
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.
+
+
+
+Coova JRadius License
+
+
+==========================================================================
+
+Coova JRadius License:
+
+The Coova extensions to JRadius library are licensed under the The GNU
+Library or "Lesser" General Public License (LGPL), while stand-alone
+applications within in the JRadius project, listed below, are released under
+the standard The GNU General Public License (GPL). For details, visit
+http://jradius.net/. See source files for details regarding stand-alone
+applications contained herein which are released under the GPL.
+
+Copyright 2006-2008 David Bird <david@coova.com>
+
+See doc/GPL-LICENSE, doc/LGPL-LICENSE, and source files for details.
+
+==========================================================================
+
+Original JRadius License:
+
+The JRadius core library is licensed under the The GNU Library or "Lesser"
+General Public License (LGPL), while stand-alone applications within in the
+JRadius project, listed below, are released under the standard The GNU
+General Public License (GPL). For details, visit http://jradius.net/
+
+This software is OSI Certified Open Source Software. OSI Certified is a
+certification mark of the Open Source Initiative.
+
+Stand-alone JRadius Applications:
+
+ * JRadiusSimulator
+ * JRadiusWiFiClient
+ * RadClient
+ * RadBench
+ * RadiusDictionary
+
+Copyright 2004-2006 PicoPoint, B.V.
+Copyright 2006-2008 David Bird <david@coova.com>
+
+See doc/GPL-LICENSE, doc/LGPL-LICENSE, and source files for details.
+
+==========================================================================
+
+
+
+GNU Crypto
+
+==========================================================================
+
+GNU Crypto
+From the gnu-crypto WebSite:
+
+GNU Crypto, part of the GNU project, released under the aegis of GNU, aims at
+providing free, versatile, high-quality, and provably correct implementations
+of cryptographic primitives and tools in the Java programming language for use
+by programmers and end-users.
+
+GNU Crypto is licensed under the terms of the GNU General Public License, with
+the "library exception" which permits its use as a library in conjunction with
+non-Free software:
+
+"As a special exception, the copyright holders of this library give you
+permission to link this library with independent modules to produce an
+executable, regardless of the license terms of these independent modules, and
+to copy and distribute the resulting executable under terms of your choice,
+provided that you also meet, for each linked independent module, the terms and
+conditions of the license of that module. An independent module is a module
+which is not derived from or based on this library. If you modify this library,
+you may extend this exception to your version of the library, but you are not
+obligated to do so. If you do not wish to do so, delete this exception
+statement from your version."
+
+The effect of that license is similar to using the LGPL, except that static
+linking is permitted. GPL with that exception is sometimes called the Guile
+License, because the Guile implementation of Scheme (for embedding) uses this
+license.
+
+
+
+
+EasyMock
+
+==========================================================================
+
+EasyMock
+From the GitHub CONTRIBUTING.md:
+
+Project License: Apache License Version 2.0
+
+By contributing code you automatically agree with the following points regarding
+ licensing:
+
+ You will only Submit Contributions where You have authored 100% of the content.
+ You will only Submit Contributions to which You have the necessary rights.
+ This means that if You are employed You have received the necessary permissions
+ from Your employer to make the Contributions.
+ Whatever content You Contribute will be provided under the Project License.
+
+
+
+
+
+PowerMock
+
+==========================================================================
+
+PowerMock
+From the GitHub LICENSE.txt:
+
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright 2007-2017 PowerMock Contributors
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+limitations under the License.
+
+
+
+
+Objenesis
+
+==========================================================================
+
+Objenesis
+From the GitHub LICENSE.txt:
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+limitations under the License.
+
+
+
+ASM
+
+License
+ASM is released under the following 3-Clause BSD License:
+
+ASM: a very small and fast Java bytecode manipulation framework
+Copyright (c) 2000-2011 INRIA, France Telecom
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. Neither the name of the copyright holders nor the names of its
+ contributors may be used to endorse or promote products derived from
+ this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+ JavaScript third-party licenses
+
+
+ bootstrap@3.3.7 MIT
+The MIT License (MIT)
+
+Copyright (c) 2011-2016 Twitter, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+font-awesome@4.7.0 (OFL-1.1 AND MIT)
+
+babel-polyfill@6.23.0 MIT
+
+core-js@2.4.1 MIT
+Copyright (c) 2014-2016 Denis Pushkarev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+regenerator-runtime@0.10.3 MIT
+
+process@0.11.9 MIT
+(The MIT License)
+
+Copyright (c) 2013 Roman Shtylman <shtylman@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+raf.js@0.0.4 MIT
+
+axios@0.13.1 MIT
+Copyright (c) 2014 Matt Zabriskie
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+react@15.4.2 BSD-3-Clause
+BSD License
+
+For React software
+
+Copyright (c) 2013-present, Facebook, Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ * Neither the name Facebook nor the names of its contributors may be used to
+ endorse or promote products derived from this software without specific
+ prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+object-assign@4.1.1 MIT
+The MIT License (MIT)
+
+Copyright (c) Sindre Sorhus <sindresorhus@gmail.com> (sindresorhus.com)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+fbjs@0.8.12 BSD-3-Clause
+BSD License
+
+For fbjs software
+
+Copyright (c) 2013-present, Facebook, Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ * Neither the name Facebook nor the names of its contributors may be used to
+ endorse or promote products derived from this software without specific
+ prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+react-dom@15.4.2 BSD-3-Clause
+BSD License
+
+For React software
+
+Copyright (c) 2013-present, Facebook, Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ * Neither the name Facebook nor the names of its contributors may be used to
+ endorse or promote products derived from this software without specific
+ prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+clone@1.0.2 MIT
+Copyright © 2011-2015 Paul Vorbach <paul@vorba.ch>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the “Software”), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+buffer@4.9.1 MIT
+The MIT License (MIT)
+
+Copyright (c) Feross Aboukhadijeh, and other contributors.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+base64-js@1.2.0 MIT
+The MIT License (MIT)
+
+Copyright (c) 2014
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+ieee754@1.1.8 BSD-3-Clause
+Copyright (c) 2008, Fair Oaks Labs, Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice,
+ this list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ * Neither the name of Fair Oaks Labs, Inc. nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+
+isarray@1.0.0 MIT
+
+react-modal@1.7.3 MIT
+Copyright (c) 2014 Ryan Florence
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+exenv@1.2.0 BSD
+BSD License
+
+For React software
+
+Copyright (c) 2013-2015, Facebook, Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ * Neither the name Facebook nor the names of its contributors may be used to
+ endorse or promote products derived from this software without specific
+ prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+lodash.assign@4.2.0 MIT
+Copyright jQuery Foundation and other contributors <https://jquery.org/>
+
+Based on Underscore.js, copyright Jeremy Ashkenas,
+DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
+
+This software consists of voluntary contributions made by many
+individuals. For exact contribution history, see the revision history
+available at https://github.com/lodash/lodash
+
+The following license applies to all parts of this software except as
+documented below:
+
+====
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+====
+
+Copyright and related rights for sample code are waived via CC0. Sample
+code is defined as all source code displayed within the prose of the
+documentation.
+
+CC0: http://creativecommons.org/publicdomain/zero/1.0/
+
+====
+
+Files located in the node_modules and vendor directories are externally
+maintained libraries used by this software which have their own
+licenses; we recommend you read them, as their terms may differ from the
+terms above.
+
+
+element-class@0.2.2 ISC
+
+string-format@0.5.0 undefined
+
+json3@3.3.2 undefined
+Copyright (c) 2012-2014 Kit Cambridge.
+http://kitcambridge.be/
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+webpack@1.14.0 MIT
+(The MIT License)
+
+Copyright (c) 2012 - 2015 Tobias Koppers
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+rc-tooltip@3.4.2 undefined
+The MIT License (MIT)
+Copyright (c) 2015-present Alipay.com, https://www.alipay.com/
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+rc-trigger@1.9.1 undefined
+The MIT License (MIT)
+Copyright (c) 2015-present Alipay.com, https://www.alipay.com/
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+babel-runtime@6.23.0 MIT
+
+rc-util@4.0.2 undefined
+The MIT License (MIT)
+Copyright (c) 2015-present Alipay.com, https://www.alipay.com/
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+add-dom-event-listener@1.0.2 undefined
+The MIT License (MIT)
+
+Copyright (c) 2014-present yiminghe
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this
+ software and associated documentation files (the "Software"), to deal in the
+ Software without restriction, including without limitation the rights to use
+ , copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+ of the Software, and to permit persons to whom the Software is furnished to
+ do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies
+ or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+ INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
+ A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+ COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+ IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
+ IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+rc-align@2.3.3 undefined
+
+dom-align@1.5.3 undefined
+The MIT License (MIT)
+
+Copyright (c) 2014-present yiminghe
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this
+ software and associated documentation files (the "Software"), to deal in the
+ Software without restriction, including without limitation the rights to use,
+ copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+ the Software, and to permit persons to whom the Software is furnished to do
+ so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies
+ or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+ INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
+ A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+ COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+ IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+ CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+rc-animate@2.3.3 undefined
+The MIT License (MIT)
+
+Copyright (c) 2014-present yiminghe
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this
+ software and associated documentation files (the "Software"), to deal in the
+ Software without restriction, including without limitation the rights to use,
+ copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+ the Software, and to permit persons to whom the Software is furnished to do
+ so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies
+ or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+ INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
+ A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+ COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+ IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+ CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+css-animation@1.3.2 undefined
+The MIT License (MIT)
+
+Copyright (c) 2014-present yiminghe
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this
+ software and associated documentation files (the "Software"), to deal in the
+ Software without restriction, including without limitation the rights to use,
+ copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+ the Software, and to permit persons to whom the Software is furnished to do so,
+ subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies
+ or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+ INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
+ A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+ COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+ IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
+ IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+component-classes@1.2.6 MIT
+
+component-indexof@0.0.3 undefined
+
+react-redux@4.4.7 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Dan Abramov
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+redux@3.6.0 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015-present Dan Abramov
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+lodash@4.17.4 MIT
+Copyright JS Foundation and other contributors <https://js.foundation/>
+
+Based on Underscore.js, copyright Jeremy Ashkenas,
+DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
+
+This software consists of voluntary contributions made by many
+individuals. For exact contribution history, see the revision history
+available at https://github.com/lodash/lodash
+
+The following license applies to all parts of this software except as
+documented below:
+
+====
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+====
+
+Copyright and related rights for sample code are waived via CC0. Sample
+code is defined as all source code displayed within the prose of the
+documentation.
+
+CC0: http://creativecommons.org/publicdomain/zero/1.0/
+
+====
+
+Files located in the node_modules and vendor directories are externally
+maintained libraries used by this software which have their own
+licenses; we recommend you read them, as their terms may differ from the
+terms above.
+
+
+symbol-observable@1.0.4 MIT
+The MIT License (MIT)
+
+Copyright (c) Sindre Sorhus <sindresorhus@gmail.com> (sindresorhus.com)
+Copyright (c) Ben Lesh <ben@benlesh.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+hoist-non-react-statics@1.2.0 undefined
+Software License Agreement (BSD License)
+========================================
+
+Copyright (c) 2015, Yahoo! Inc. All rights reserved.
+----------------------------------------------------
+
+Redistribution and use of this software in source and binary forms, with or
+without modification, are permitted provided that the following conditions are
+met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+ * Neither the name of Yahoo! Inc. nor the names of YUI's contributors may be
+ used to endorse or promote products derived from this software without
+ specific prior written permission of Yahoo! Inc.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+invariant@2.2.2 BSD-3-Clause
+Copyright (c) 2016, Andres Suarez
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of invariant nor the names of its
+ contributors may be used to endorse or promote products derived from
+ this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+moment@2.18.1 MIT
+Copyright (c) JS Foundation and other contributors
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.
+
+
+react-virtualized-select@3.0.1 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Brian Vaughn
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+
+prop-types@15.5.9 BSD-3-Clause
+BSD License
+
+For React software
+
+Copyright (c) 2013-present, Facebook, Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ * Neither the name Facebook nor the names of its contributors may be used to
+ endorse or promote products derived from this software without specific
+ prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+react-select@1.0.0-rc.3 MIT
+The MIT License (MIT)
+
+Copyright (c) 2016 Jed Watson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+react-input-autosize@1.1.3 MIT
+The MIT License (MIT)
+
+Copyright (c) 2017 Jed Watson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+create-react-class@15.5.3 BSD-3-Clause
+BSD License
+
+For React software
+
+Copyright (c) 2013-present, Facebook, Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ * Neither the name Facebook nor the names of its contributors may be used to
+ endorse or promote products derived from this software without specific
+ prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+classnames@2.2.5 MIT
+The MIT License (MIT)
+
+Copyright (c) 2016 Jed Watson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+react-virtualized@9.7.5 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Brian Vaughn
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+
+dom-helpers@3.2.1 MIT
+
+react-tagsinput@3.15.1 MIT
+The MIT License
+
+Copyright (c) 2015 Ola Holmström <olaholmstrom+github@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+recharts@0.20.8 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 recharts
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+
+d3-scale@1.0.4 BSD-3-Clause
+Copyright 2010-2015 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-array@1.1.1 BSD-3-Clause
+Copyright 2010-2016 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-collection@1.0.3 BSD-3-Clause
+Copyright 2010-2016, Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-interpolate@1.1.4 BSD-3-Clause
+Copyright 2010-2016 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-color@1.0.3 BSD-3-Clause
+Copyright 2010-2016 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-format@1.1.1 BSD-3-Clause
+Copyright 2010-2015 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-time@1.0.6 BSD-3-Clause
+Copyright 2010-2016 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-time-format@2.0.5 BSD-3-Clause
+Copyright 2010-2016 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-shape@1.0.4 BSD-3-Clause
+Copyright 2010-2015 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+d3-path@1.0.5 BSD-3-Clause
+Copyright 2015-2016 Mike Bostock
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of the author nor the names of contributors may be used to
+ endorse or promote products derived from this software without specific prior
+ written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+react-smooth@0.1.20 MIT
+The MIT License (MIT)
+
+Copyright (c) 2016 recharts
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+raf@3.3.0 MIT
+
+performance-now@0.2.0 MIT
+Copyright (c) 2013 Meryn Stol
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+ this software and associated documentation files (the "Software"), to deal
+ in the Software without restriction, including without limitation the rights
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+ copies of the Software, and to permit persons to whom the Software is
+ furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+ copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+ INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
+ A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+ COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
+ OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+react-addons-transition-group@15.4.2 BSD-3-Clause
+BSD License
+
+For React software
+
+Copyright (c) 2013-present, Facebook, Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ * Neither the name Facebook nor the names of its contributors may be used to
+ endorse or promote products derived from this software without specific
+ prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+react-resize-detector@0.3.3 MIT
+
+reduce-css-calc@1.3.0 MIT
+The MIT License (MIT)
+
+Copyright (c) 2014 Maxime Thirouin & Joakim Bengtson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+balanced-match@0.4.2 MIT
+(MIT)
+
+Copyright (c) 2013 Julian Gruber <julian@juliangruber.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+reduce-function-call@1.0.2 MIT
+The MIT License (MIT)
+
+Copyright (c) 2014 "MoOx" Maxime Thirouin
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+math-expression-evaluator@1.2.16 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Ankit G.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+
+recharts-scale@0.2.1 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Sen Yang
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+
+events@1.1.1 MIT
+MIT
+
+Copyright Joyent, Inc. and other Node contributors.
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to permit
+persons to whom the Software is furnished to do so, subject to the
+following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
+NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
+DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
+OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
+USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+rc-collapse@1.6.12 MIT
+The MIT License (MIT)
+
+Copyright (c) 2014-present yiminghe
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+ of this software and associated documentation files (the "Software"),
+ to deal in the Software without restriction, including without limitation
+ the rights to use, copy, modify, merge, publish, distribute, sublicense,
+ and/or sell copies of the Software, and to permit persons to whom the
+ Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+ all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+ INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+ FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
+ OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+ WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
+ OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+react-sizeme@2.3.1 MIT
+The MIT License (MIT)
+
+Copyright (c) 2016 Sean Matheson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+element-resize-detector@1.1.11 MIT
+The MIT License (MIT)
+
+Copyright (c) 2016 Lucas Wiener
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+batch-processor@1.0.0 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Lucas Wiener
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+
+react-color@2.11.4 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Case Sandberg
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+reactcss@1.2.2 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Case Sandberg
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+material-colors@1.2.5 ISC
+
+redux-replaceable-middleware@1.1.0 ISC
+
+redux-thunk@2.2.0 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Dan Abramov
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+redux-promise-middleware@3.3.2 MIT
+Copyright 2015-current Patrick Burtchaell <patrick@pburtchaell.com>
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+
+redux-saga@0.12.1 MIT
+The MIT License (MIT)
+
+Copyright (c) 2015 Yassine Elouafi
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+
+
diff --git a/doc/book-enea-edge-management-open-source/swcomp.mk b/doc/book-enea-edge-management-open-source/swcomp.mk
new file mode 100644
index 0000000..4a18540
--- /dev/null
+++ b/doc/book-enea-edge-management-open-source/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-management-open-source
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Management Open Source Report"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-edge-release-info/doc/about_release.xml b/doc/book-enea-edge-release-info/doc/about_release.xml
new file mode 100644
index 0000000..960f136
--- /dev/null
+++ b/doc/book-enea-edge-release-info/doc/about_release.xml
@@ -0,0 +1,184 @@
+
+
+
+ About This Release
+
+ Enea Edge is a complete NFVI software platform designed for
+ deployment on any white box uCPE device, and optimized for common use cases.
+ Enea Edge includes both the Enea Edge Runtime deployed on a white box,
+ and a management component with automation tools deployed in a private or
+ public cloud.
+
+ The Enea Edge Release includes a new version of
+ the major components as well as other features and optimizations, and
+ documentation updates. A list of new features and improvements can be found
+ in Section 2.1 New Features and
+ Improvements .
+
+
+ Enea Edge Release Content
+
+ The release content is detailed below:
+
+
+
+ Enea_Edge_Runtime_C3000_<version>-build<build_number>.tar.gz
+
+
+
+ Enea_Edge_Runtime_XeonD_<version>-build<build_number>.tar.gz
+
+
+
+ Enea_Edge_Automation_<version>-build<build_number>.zip
+
+
+
+ Enea_Edge_Management_<version>-build<build_number>.tar.gz
+
+
+
+ Enea_Edge_Telemetry_Deploy_<version>-build<build_number>.tar.gz
+
+
+
+ VNF_example_configurations.tar.gz
+
+
+
+ Enea_Edge_AF-TH_<version>-build<build_number>.zip
+ (deprecated, see Section 2.1 New Features and
+ Improvements .)
+
+
+
+ -- documentation/
+ /* Enea Edge documentation */
+-- README
+-- aarch64 /* architecture */
+ -- cn8304/
+ /* artifacts for the host side */
+ -- deb/
+ /* deb packages */
+ -- images/
+ -- enea-nfv-access
+ /* precompiled artifacts for the platform release image */
+ -- various artifacts (rootfs, kernel, config etc.)
+ -- enea-nfv-access-dev
+ /* precompiled artifacts for the development process. The image
+ contains userspace tools and kernel configurations necessary
+ for developing, debugging and profiling applications and
+ kernel modules */
+ -- various artifacts
+ -- qemuarm64
+ /* artifacts for the guest side */
+ -- deb/
+ /* deb packages */
+ -- images/
+ -- enea-nfv-access-guest
+ /* precompiled artifacts for the QEMU/Docker release image */
+ -- various artifacts
+ -- enea-nfv-access-guest-dev
+ /* precompiled artifacts for the development process. The image
+ contains userspace tools and kernel configurations necessary
+ for developing, debugging and profiling applications and
+ kernel modules */
+ -- various artifacts
+
+
+ INFO Below is a complete section with ID
+ "eltf-target-tables-section" included from elft_params_updated.xml. It
+ contains a variable number of target tables and the section title should be
+ "Supported Targets with Parameters". It has have a short sentence about what
+ it is in the beginning. The subtitles shall have the directory name of the
+ target in the manifest.
+
+
+
+
+ User Documentation
+
+ This release of Enea Edge contains the following set of
+ documents:
+
+
+
+ Enea Edge Release Information. Describes the Enea Edge
+ release content, main changes, the list of known issues and
+ limitations.
+
+
+
+ .
+ Describes how to deploy and upgrade an Enea Edge base
+ configuration, advanced configurations of the system and
+ troubleshooting information.
+
+
+
+ .
+ Describes examples of onboarding, instantiating and configuring
+ various VNFs.
+
+
+
+ .
+ Describes the Automation Framework for Enea Edge.
+
+
+
+ . Describes the
+ Automation Framework and Test Harness for Enea Edge and
+ provides instructions regarding the necessary steps to run these
+ software tools (deprecated, see
+ Section 2.1 New Features
+ and Improvements ).
+
+
+
+ .
+ Describes a sample Test Suite for System Testing of Enea Edge.
+ (deprecated, see Section 2.1
+ New Features and Improvements ).
+
+
+
+
+
+ Supported Web Browsers
+
+ These need to be updated
+
+ The current release supports using the following web browsers:
+
+
+
+ Google Chrome (tested with version 86).
+
+
+
+ Mozilla Firefox (tested with version 82).
+
+
+
+ Microsoft Edge (tested with version 84).
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-release-info/doc/book.xml b/doc/book-enea-edge-release-info/doc/book.xml
new file mode 100644
index 0000000..b886ee1
--- /dev/null
+++ b/doc/book-enea-edge-release-info/doc/book.xml
@@ -0,0 +1,30 @@
+
+
+]>
+
+ Enea Edge Release
+ Information
+
+ Release Version
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-release-info/doc/getting_enea_nfv_access.xml b/doc/book-enea-edge-release-info/doc/getting_enea_nfv_access.xml
new file mode 100644
index 0000000..9eecd3c
--- /dev/null
+++ b/doc/book-enea-edge-release-info/doc/getting_enea_nfv_access.xml
@@ -0,0 +1,54 @@
+
+
+
+ Getting Enea NFV Access
+
+ Enea NFV Access releases and updates are available as binaries ready
+ for download.
+
+ Downloading Enea NFV Access
+Does the content below need to be revised to no longer make reference or mention to Enea Portal?
+
+
+ Log in to the link above using the credentials provided by
+ Enea.
+
+
+
+ From the right corner of the top main menu, choose the
+ Access section.
+
+
+
+ The Files section on the left will display each
+ official release of Enea NFV Access, with the latest at the top.
+
+ Each release listing displays the dates for release and updates
+ available, along with a Download button that allows
+ you to directly save the version you wish to use.
+
+
+
+ By clicking on the link at the top of any listing of Enea NFV
+ Access, you'll access the changelog page for that version. At the bottom
+ of the page are clearly labeled region-specific zip files containing the
+ binary sources.
+
+ Documentation is also available at the bottom of the page.
+
+
+
+ On the right side of the main Access page is
+ the Online Documentation section, listing pdfs for
+ the latest versions of documentation. They can all be accessed for
+ indiviudual downloading without the need to download the binaries
+ first.
+
+
+
+ For details about the books delivered and their purpose, refer to
+ . For information concerning the
+ contents of the release package, please see .
+
diff --git a/doc/book-enea-edge-release-info/doc/jiraissues_override.xml b/doc/book-enea-edge-release-info/doc/jiraissues_override.xml
new file mode 100644
index 0000000..7282d0f
--- /dev/null
+++ b/doc/book-enea-edge-release-info/doc/jiraissues_override.xml
@@ -0,0 +1,36 @@
+
+
+
diff --git a/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
new file mode 100644
index 0000000..1f5fb0c
--- /dev/null
+++ b/doc/book-enea-edge-release-info/doc/known_bugs_and_limitations.xml
@@ -0,0 +1,217 @@
+
+
+
+ Known Issues and Limitations in this Release
+
+ This chapter lists the known general issues and limitations that
+ affect the current release.
+
+
+
+ LXCR-9904 Enea Edge Runtime cannot be installed on
+ USB storage devices.
+
+
+
+ LXCR-9799 Proper boot order is not ensured if a
+ uCPE device has more than one HDD attached.
+
+
+
+ ELCCR-527 Cancelling a file upload in the Enea
+ Edge Management will require the user to close and reopen the upload window
+ for the next upload to work.
+
+
+
+ ELCCR-577 If Enea Edge Management is restored from a backup
+ made on a release version older than Enea NFV Access 2.2.3, VNFs cannot be instantiated
+ from the GUI.
+
+
+
+ ELCCR-474 Deleting VNF instances with flows
+ configured on the OVS bridges can be done only after removing the
+ flows.
+
+
+
+ ELCCR-572 Sometimes when selecting and deleting
+ more than one VNF instance simultaneously, an error message might be
+ triggered, even if the delete operation succeeds.
+
+
+
+ ELCCR-847 The Juniper vSRX VNF cannot be
+ instantiated on the Xeon-D architectures due to missing CPU features in
+ the VNF's domain XML. This impacts all example use cases where the Juniper VNF is used.
+
+
+
+ USERDOCAP-648 The storage size
+ parameter on the VNF onboarding page is ignored. The default storage
+ size specified when creating the VM image is used when instantiating the
+ VM and when presenting VM information.
+
+
+
+ LXCR-9853 The WAN interface of a uCPE device needs
+ to be connected to a network with at least a router/gateway installed
+ for next-hop communication.
+
+
+
+ LXCR-9992 Depending on hardware capabilities,
+ there are certain limitations regarding the vfio-pci
+ and igb_uio drivers. While the Enea Edge
+ Runtime uses the vfio-pci driver by default,
+ for certain hardware configurations, igb_uio should
+ be used instead, by providing custom scripting. Please contact Enea for
+ further details.
+
+
+
+ STCR-6224 The Enea Edge Automation
+ and the Enea Edge Automation Framework and Test Harness do not
+ support multiple custom scripts uploaded to a uCPE device at the same
+ time.
+
+
+
+ STCR-6292 Management of WAN Interfaces is not
+ implemented in the Enea Edge Automation Framework and Test Harness.
+
+
+
+ USERDOCAP-628 Enea Edge Automation Framework
+ and Test Harness does not have support for product features implemented
+ in Enea Edge 2.4.0 or newer.
+
+
+
+ ELCCR-912 When the Enea Edge Management is installed
+ on CentOS 7, prior to C7.1804 (kernel version 3.10.0-862), adding an
+ upgrade image fails. As a workaround, please update
+ glib2 to version 2.54.2 or later, using #yum
+ update glib2 .
+
+
+
+ ELCCR-854 Changing the management interface IP
+ address will result in a temporary loss of connection with the uCPE
+ device. If the device is behind a NAT, while using the Call Home
+ connection, reestablishing the connection automatically could take up to
+ 20 minutes. Restarting the vCPE Overlay will immediately reestablish the
+ connection, but that implies the existence of an alternate way to
+ trigger the vCPE restart operation on the device.
+
+
+
+ USERDOCAP-641 Enea Edge does not have
+ support for IPv6 addresses on both uCPE devices and the Enea Edge
+ Management installation.
+
+
+
+ ELCCR-1428 Wireless AP creation through the REST
+ API does not validate that the wireless interface and LAN bridge are
+ configured. Using these parameters may result in undefined
+ behavior.
+
+
+
+ USERDOCAP-651 Wireless AP configuration is
+ optimized for wireless modules that use the ath10k
+ driver. Using other wireless modules may result in undefined
+ behavior.
+
+
+
+ ELCCR-1351 The updated
+ .Keystore and server.xml files
+ from the
+ /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/
+ folder are overwritten during a product upgrade. As a workaround for
+ this issue, after an upgrade, copy the updated
+ .Keystore and server.xml files
+ into the
+ /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/
+ folder and restart the ucpemanager service.
+
+
+
+ ELCCR-1371 The current self-signed certificate for
+ the Enea Edge Management is generated at build time, with a hard-coded
+ common-name causing the uCPE device upgrade to fail in HTTPS mode. As a
+ workaround, another certificate (containing an IP based common-name)
+ must be generated.
+
+ Perform the following the steps to generate the
+ certificate:
+
+
+
+ Stop the Edge Management service.
+
+
+
+ Create the certificate using the
+ createCertificate.sh script from distribution
+ folder. This will create a new .Keystore file
+ and copy it into the
+ /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates
+ folder.
+
+
+
+ Start the Enea Edge Management, the new certificate should now
+ take effect.
+
+
+
+
+
+ ELCCR-1378 Modifying the type of the external
+ interfaces can lead to errors. Instead of modifying, it is recommended
+ to delete the old interfaces and recreate them with the desired
+ type.
+
+
+
+ ELCCR-907 At times the VIP address is not acquired
+ by any of the backup nodes if a power failure happens on primary node in
+ a High Availability setup. To recover, follow the official documentation
+ available at Galera Cluster
+ Recovery .
+
+
+
+ LXCR-3283 PDF
+ navigation : When using links to open other PDFs, or jump to
+ another place in the same PDF, jumping back sometimes fails. This has
+ been observed when opening a PDF in Adobe Reader, inside a browser with
+ PDF add-on, as well as when the browser is configured to open PDF files
+ in an external PDF reader. As a workaround, open the HTML version of the
+ document.
+
+
+
+ ELCCR-1468 When using the Enea Edge Management in
+ HTTPS mode, upgrading a device from NFV Access 2.3.0 is not possible.
+ Either switch to HTTP mode (for more details see The uCPE device Upgrade Process in the
+
+ Manual) or install it manually.
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-release-info/doc/main_changes.xml b/doc/book-enea-edge-release-info/doc/main_changes.xml
new file mode 100644
index 0000000..c01a149
--- /dev/null
+++ b/doc/book-enea-edge-release-info/doc/main_changes.xml
@@ -0,0 +1,162 @@
+
+
+
+ Main Changes
+
+ Below you'll find information about the new features and updates made
+ in this release, as well as details on the provided packages and the
+ backwards compatibility with previous versions.
+
+
+ New Features and Improvements
+
+ New Features:
+
+
+
+ CPDX-3496 Embedded WiFi support for all-in-one
+ store/home office deployment.
+
+
+
+ CPDX-3499 Expanded hardware, OS and network
+ monitoring capability with Grafana integration.
+
+
+
+ CPDX-3498 High Availability support with redundant
+ Enea Edge Management in active standby configuration.
+
+
+
+ CPDX-3407 HTTPS based downloads of VNFs for
+ simplified deployment of the Enea Edge Management in cloud
+ environments.
+
+
+
+ CPDX-3500 The Enea Edge Automation,
+ a tool for automatic system configuration based on Python
+ scripting that will replace the existing Enea Edge Automation
+ Framework and Test Harness in the next major release.
+
+ The Enea Edge Automation Framework and Test Harness, and
+ its related documentation the
+ and the
+ are deprecated starting with Enea Edge 2.4.0.
+
+
+
+ Improvements:
+
+
+
+ A new Requirements page has
+ been added to the Web-installer, displaying device characteristics and
+ checking minimal hardware requirements.
+
+
+
+ A Web-installer's log is displayed on the last page in case the
+ installation process has failed.
+
+
+
+ Extended Web-installer support for NVME disks.
+
+
+
+ Early Access Features:
+
+ The following Early Access features are included in this release
+ (made originally available with Enea NFV Access 2.3.0):
+
+
+
+ Platform and VNF Snapshots:
+
+
+
+ Platform Snapshots allow users to store, manage and restore
+ snapshots of the Enea Edge Runtime configuration,
+ with the purpose of recovering after a failed reconfiguration.
+ This feature is disabled by default.
+
+
+
+ VNF Snapshots allow users to store, manage and restore
+ snapshots of VNFs deployed on the Enea Edge
+ Runtime, with the purpose of restoring the VNF after a persistent
+ VNF failure. This feature is disabled by default.
+
+
+
+
+ Users that would like to try out the Snapshot features should
+ contact Enea Support for additional documentation and
+ assistance.
+
+
+
+
+ Early Access features are provided for evaluation and early
+ feedback. They are not allowed to be used for business-critical
+ deployment, unless previously approved by Enea. Support cases reported on
+ Early Access features may only be set to a Minor Priority, with the intent
+ of addressing them in upcoming GA releases.
+
+
+
+ Open Source
+
+ For more information about the Open Source packages included, please
+ refer to the Enea Edge Open Source Reports listed below. Each report
+ contains open source and license information pertaining to packages
+ provided with this release, for their respective component.
+
+
+
+ .
+
+
+
+ .
+
+
+
+ .
+
+
+
+ .
+
+
+
+ .
+
+
+
+
+
+ Compatibility
+
+ This release does not contain any change impacting
+ compatibility.
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-release-info/doc/system_requirements_prerequisites.xml b/doc/book-enea-edge-release-info/doc/system_requirements_prerequisites.xml
new file mode 100644
index 0000000..b0317b3
--- /dev/null
+++ b/doc/book-enea-edge-release-info/doc/system_requirements_prerequisites.xml
@@ -0,0 +1,62 @@
+
+
+
+ Host Requirements
+
+ Using Enea NFV Access or compiling applications requires certain
+ packages to be installed on your build host. The requirements listed below
+ are extensive to allow getting Enea NFV Access to be booted on target
+ machines and for building applications.
+
+
+
+
+
+
+
+
+
+
+
+ Build Host
+ Requirements
+ host requirements
+
+
+
+
+ Linux distribution
+
+ The downloaded product can installed on the target machine
+ using a Linux host. For information about supported hosts and
+ targets, see .
+
+
+
+ Packages
+
+ Depending on the Linux distribution and version of the host,
+ certain packages may be required. See details on what packages are
+ needed and how to install them in the following sections.
+
+
+
+ Disk space
+
+ Your build host should have at least 50 GB of free disk space
+ for installing the SDK, eSDK or cross-compiling
+ applications.
+
+
+
+ Recommended RAM
+
+ Your build host must have at least 4 GB available
+ RAM.
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-release-info/swcomp.mk b/doc/book-enea-edge-release-info/swcomp.mk
new file mode 100644
index 0000000..892f097
--- /dev/null
+++ b/doc/book-enea-edge-release-info/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-release-info
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Release Information"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-edge-runtime-open-source/doc/README b/doc/book-enea-edge-runtime-open-source/doc/README
new file mode 100644
index 0000000..607ce67
--- /dev/null
+++ b/doc/book-enea-edge-runtime-open-source/doc/README
@@ -0,0 +1,4 @@
+The licenses.xml in the git repository of Enea NFV Access Runtime Platform Open Source Report
+is the frozen version belonging to the last official release of Enea NFV Access.
+The contents must be generated from the release script to obtain the latest
+lists of packages and licenses.
diff --git a/doc/book-enea-edge-runtime-open-source/doc/about.xml b/doc/book-enea-edge-runtime-open-source/doc/about.xml
new file mode 100644
index 0000000..2a8bf01
--- /dev/null
+++ b/doc/book-enea-edge-runtime-open-source/doc/about.xml
@@ -0,0 +1,8 @@
+
+
+
+ About this Report
+
+ This document contains the open source and license information pertaining to packages provided with this release of the Enea Edge Runtime and the Installer.
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-runtime-open-source/doc/book.xml b/doc/book-enea-edge-runtime-open-source/doc/book.xml
new file mode 100644
index 0000000..a575375
--- /dev/null
+++ b/doc/book-enea-edge-runtime-open-source/doc/book.xml
@@ -0,0 +1,15 @@
+
+
+]>
+
+ Enea Edge Runtime Open Source Report
+ Release Version
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-runtime-open-source/doc/licenses.xml b/doc/book-enea-edge-runtime-open-source/doc/licenses.xml
new file mode 100644
index 0000000..6f9aa06
--- /dev/null
+++ b/doc/book-enea-edge-runtime-open-source/doc/licenses.xml
@@ -0,0 +1,9936 @@
+
+
+
+ Packages and Licenses
+
+
+ Packages
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Package Name
+ Version
+ Description
+ License
+
+
+
+
+
+
+ 4g-sierra
+ 1.0
+ Scripts to setup 4G modems from Sierra
+ Enea
+
+
+ acl
+ 2.2.52
+ Utilities for managing POSIX Access Control Lists.
+ LGPL-2.1, GPL-2.0
+
+
+ acpid
+ 2.0.28
+ A daemon for delivering ACPI events.
+ GPL-2.0
+
+
+ alsa-lib
+ 1.1.4.1
+ ALSA sound library.
+ LGPL-2.1, GPL-2.0
+
+
+ ant
+ 1.8.1
+ Another Neat Tool - build system for Java
+ Apache-2.0
+
+
+ antlr
+ 2.7.7
+ Framework for constructing recognizers interpreters compilers and translators
+ PD
+
+
+ apache2
+ 2.4.27
+ The Apache HTTP Server is a powerful efficient and extensible web server.
+ Apache-2.0
+
+
+ apr-util
+ 1.6.0
+ Apache Portable Runtime (APR) companion library.
+ Apache-2.0
+
+
+ apr
+ 1.6.2
+ Apache Portable Runtime (APR) library.
+ Apache-2.0
+
+
+ apt
+ 1.2.24
+ Advanced front-end for dpkg.
+ GPL-2.0
+
+
+ attr
+ 2.4.47
+ Utilities for manipulating filesystem extended attributes.
+ LGPL-2.1, GPL-2.0
+
+
+ aufs-util
+ 4.4
+ Tools for managing AUFS mounts.
+ GPL-2.0
+
+
+ augeas
+ 1.5.0
+ Augeas configuration API.
+ LGPL-2.1
+
+
+ autoconf-archive
+ 2016.09.16
+ a collection of freely re-usable Autoconf macros.
+ GPL-3.0-with-autoconf-exception
+
+
+ autoconf
+ 2.69
+ Autoconf is an extensible package of M4 macros that produce shell scripts to automatically configure software source code packages. Autoconf creates a configuration script for a package from a template file that lists the operating system features that the package can use in the form of M4 macro calls.
+ GPL-2.0, GPL-3.0
+
+
+ automake
+ 1.15.1
+ Automake is a tool for automatically generating `Makefile.in' files compliant with the GNU Coding Standards. Automake requires the use of Autoconf.
+ GPL-2.0
+
+
+ avahi
+ 0.6.32
+ "Avahi is a fully LGPL framework for Multicast DNS Service Discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. This tool implements IPv4LL ""Dynamic Configuration of IPv4 Link-Local Addresses"" (IETF RFC3927) a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server."
+ GPL-2.0, LGPL-2.1
+
+
+ avalon-framework-api
+ 4.3
+ Common way for components to be created initialized configured started. (API-only)
+ Apache-2.0
+
+
+ base-files
+ 3.0.14
+ The base-files package creates the basic system directory structure and provides a small set of key configuration files for the system.
+ GPL-2.0
+
+
+ base-passwd
+ 3.5.29
+ The master copies of the user database files (/etc/passwd and /etc/group). The update-passwd tool is also provided to keep the system databases synchronized with these master files.
+ GPL-2.0
+
+
+ bash-completion
+ 2.7
+ Programmable Completion for Bash 4.
+ GPL-2.0
+
+
+ bash
+ 4.4
+ An sh-compatible command language interpreter.
+ GPL-3.0
+
+
+ bc
+ 1.06
+ Arbitrary precision calculator language.
+ GPL-2.0, LGPL-2.1
+
+
+ bcel
+ 5.2
+ Java Bytecode manipulation library
+ Apache-2.0
+
+
+ bind
+ 9.10.5-P3
+ ISC Internet Domain Name Server.
+ ISC, BSD
+
+
+ binutils-cross-x86_64
+ 2.29.1
+ The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
+ GPL-3.0
+
+
+ binutils
+ 2.29.1
+ The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
+ GPL-3.0
+
+
+ bison
+ 3.0.4
+ Bison is a general-purpose parser generator that converts an annotated context-free grammar into an LALR(1) or GLR parser for that grammar. Bison is upward compatible with Yacc: all properly-written Yacc grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with little trouble.
+ GPL-3.0
+
+
+ bjam
+ 1.64.0
+ Portable Boost.Jam build tool for boost.
+ BSL-1.0, MIT, Python-2.0
+
+
+ bmap-tools
+ 3.4
+ "Bmap-tools - tools to generate block map (AKA bmap) and flash images using bmap. Bmaptool is a generic tool for creating the block map (bmap) for a file and copying files using the block map. The idea is that large file containing unused blocks like raw system image files can be copied or flashed a lot faster with bmaptool than with traditional tools like ""dd"" or ""cp""."
+ GPL-2.0
+
+
+ boost
+ 1.64.0
+ Free peer-reviewed portable C++ source libraries.
+ BSL-1.0, MIT, Python-2.0
+
+
+ bridge-utils
+ 1.5
+ Tools for ethernet bridging.
+ GPL-2.0
+
+
+ bsf
+ 2.4.0
+ Bean Scripting Framework package
+ Apache-2.0
+
+
+ btrfs-tools
+ 4.12
+ Btrfs is a new copy on write filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance repair and easy administration. This package contains utilities (mkfs fsck btrfsctl) used to work with btrfs and an utility (btrfs-convert) to make a btrfs filesystem from an ext3.
+ GPL-2.0
+
+
+ busybox
+ 1.24.1
+ BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for most of the utilities you usually find in GNU fileutils shellutils etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete POSIX environment for any small or embedded system.
+ GPL-2.0, BSD-4-Clause
+
+
+ bzip2
+ 1.0.6
+ bzip2 compresses files using the Burrows-Wheeler block-sorting text compression algorithm and Huffman coding. Compression is generally considerably better than that achieved by more conventional LZ77/LZ78-based compressors and approaches the performance of the PPM family of statistical compressors.
+ BSD-4-Clause
+
+
+ ca-certificates
+ 20170717
+ This package includes PEM files of CA certificates to allow SSL-based applications to check for the authenticity of SSL connections. This derived from Debian's CA Certificates.
+ GPL-2.0, MPL-2.0
+
+
+ cacao-initial
+ 0.98
+ CacaoVM for use as OpenEmbedded's Java VM
+ GPL-2.0
+
+
+ cairo
+ 1.14.10
+ Cairo is a multi-platform library providing anti-aliased vector-based rendering for multiple target backends. Paths consist of line segments and cubic splines and can be rendered at any width with various join and cap styles. All colors may be specified with optional translucence (opacity/alpha) and combined using the extended Porter/Duff compositing algebra as found in the X Render Extension.
+ MPL-1.0, LGPL-2.1, GPL-3.0
+
+
+ cantarell-fonts
+ 0.0.24
+ The Cantarell font typeface is designed as a contemporary Humanist sans serif and was developed for on-screen reading; in particular reading web pages on an HTC Dream mobile phone.
+ OFL-1.1
+
+
+ cdrkit
+ 1.1.11
+ CD/DVD command line tools.
+ GPL-2.0
+
+
+ cdrtools
+ 3.01a31
+ A set of tools for CD recording including cdrecord.
+ GPL-2.0, CDDL-1.0, LGPL-2.1
+
+
+ classpath-initial
+ 0.93
+ Java1.4-compatible GNU Classpath variant that is used as bootclasspath for jikes-native.
+ GPL-2.0, SAX-PD
+
+
+ classpath
+ 0.99
+ GNU Classpath standard Java libraries - For native Java-dependent programs
+ GPL-2.0, SAX-PD
+
+
+ cloud-init
+ 0.7.6
+ Init scripts for use on cloud images
+ GPL-3.0
+
+
+ cmake
+ 3.8.2
+ Cross-platform open-source make system.
+ BSD
+
+
+ collectd
+ 5.12.0
+ collectd is a daemon which collects system performance statistics periodically and provides mechanisms to store the values in a variety of ways for example in RRD files.
+ GPL-2.0, MIT
+
+
+ commons-logging
+ 1.1.1
+ Java Internet protocol suite library
+ Apache-2.0
+
+
+ commons-net
+ 1.4.1
+ Java Internet protocol suite library
+ Apache-2.0
+
+
+ compose-file
+ 3.0
+ Parser for the Compose file format (version 3)
+ Apache-2.0
+
+
+ containerd-docker
+ v0.2.x
+ containerd is a daemon to control runC built for performance and density. containerd leverages runC's advanced features such as seccomp and user namespace support as well as checkpoint and restore for cloning and live migration of containers.
+ Apache-2.0
+
+
+ core-image-minimal-initramfs
+ 1.0
+ Small image capable of booting a device. The kernel includes the Minimal RAM-based Initial Root Filesystem (initramfs) which finds the first 'init' program more efficiently.
+ MIT
+
+
+ coreutils
+ 8.27
+ The GNU Core Utilities provide the basic file shell and text manipulation utilities. These are the core utilities which are expected to exist on every system.
+ GPL-3.0
+
+
+ crda
+ 3.18
+ Wireless Central Regulatory Domain Agent.
+ copyleft-next-0.3.0
+
+
+ cross-localedef
+ 2.26
+ Cross locale generation tool for glibc.
+ LGPL-2.1
+
+
+ cryptodev-linux
+ 1.9
+ A /dev/crypto device driver header file.
+ GPL-2.0
+
+
+ cup
+ 0.10k
+ Lexical analyzer generator for Java
+ CUP
+
+
+ curl
+ 7.58.0
+ Command line tool and library for client-side URL transfers.
+ MIT
+
+
+ cwautomacros
+ 20110201
+ Collection of autoconf m4 macros.
+ GPL-2.0
+
+
+ db
+ 5.3.28
+ Berkeley Database v5.
+ Sleepycat
+
+
+ dbus-glib
+ 0.108
+ GLib bindings for the D-Bus message bus that integrate the D-Bus library with the GLib thread abstraction and main loop.
+ AFL-2.0, GPL-2.0
+
+
+ dbus-test
+ 1.10.20
+ D-Bus test package (for D-bus functionality testing only).
+ AFL-2.0, GPL-2.0
+
+
+ dbus
+ 1.10.20
+ "D-Bus is a message bus system a simple way for applications to talk to one another. In addition to interprocess communication D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a \""single instance\"" application or daemon and to launch applications and daemons on demand when their services are needed."
+ AFL-2.0, GPL-2.0
+
+
+ debianutils
+ 4.8.1.1
+ Miscellaneous utilities specific to Debian.
+ GPL-2.0, SMAIL_GPL
+
+
+ depmodwrapper
+ 1.0
+ Wrapper script for the Linux kernel module dependency indexer.
+ MIT
+
+
+ dhcp
+ 4.3.6
+ DHCP (Dynamic Host Configuration Protocol) is a protocol which allows individual devices on an IP network to get their own network configuration information from a server. DHCP helps make it easier to administer devices.
+ ISC
+
+
+ diffutils
+ 3.6
+ Diffutils contains the GNU diff diff3 sdiff and cmp utilities. These programs are usually used for creating patch files.
+ GPL-3.0
+
+
+ dmidecode
+ 3.1
+ DMI (Desktop Management Interface) table related utilities.
+ GPL-2.0
+
+
+ dnsmasq
+ 2.78
+ Lightweight easy to configure DNS forwarder and DHCP server.
+ GPL-2.0, GPL-3.0
+
+
+ docker
+ 17.06.0
+ Linux container runtime Docker complements kernel namespacing with a high-level API which operates at the process level. It runs unix processes with strong guarantees of isolation and repeatability across servers. . Docker is a great building block for automating distributed systems: large-scale web deployments database clusters continuous deployment systems private PaaS service-oriented architectures etc. . This package contains the daemon and client. Using docker.io is officially supported on x86_64 and arm (32-bit) hosts. Other architectures are considered experimental. . Also note that kernel version 3.10 or above is required for proper operation of the daemon process and that any lower versions may have subtle and/or glaring issues.
+ Apache-2.0
+
+
+ dosfstools
+ 4.1
+ DOS FAT Filesystem Utilities.
+ GPL-3.0
+
+
+ dpdk-dev-libibverbs
+ 1.2.1-3.4-2.0.0.0
+ libibverbs library to support Mellanox config
+ GPL-2.0
+
+
+ dpdk
+ 18.02
+ Intel(r) Data Plane Development Kit
+ BSD, LGPL-2.0, GPL-2.0
+
+
+ dpkg
+ 1.18.24
+ Package maintenance system from Debian.
+ GPL-2.0
+
+
+ dtc
+ 1.4.4
+ The Device Tree Compiler is a tool used to manipulate the Open-Firmware-like device tree used by PowerPC kernels.
+ GPL-2.0, BSD
+
+
+ e2fsprogs
+ 1.43.5
+ The Ext2 Filesystem Utilities (e2fsprogs) contain all of the standard utilities for creating fixing configuring and debugging ext2 filesystems.
+ GPL-2.0, LGPL-2.0, BSD, MIT
+
+
+ ebtables
+ 2.0.10-4
+ Utility for basic Ethernet frame filtering on a Linux bridge advanced logging MAC DNAT/SNAT and brouting.
+ GPL-2.0
+
+
+ ecj-bootstrap
+ 1.0
+ JDT Core Batch Compiler - Bootstrap variant
+ MIT
+
+
+ ecj-initial
+ 1.0
+ JDT Core Batch Compiler - Bootstrap variant
+ MIT
+
+
+ efibootmgr
+ 0.15
+ Linux user-space application to modify the EFI Boot Manager.
+ GPL-2.0
+
+
+ efitools
+ 1.7.0
+ From the EFI Tools package in the Linux user-space it's now possible to read and manipulate the UEFI signatures database via the new efi-readvar and efi-updatevar commands. Aside from needing efitools 1.4 the EFIVARFS file-system is also needed which was only introduced in the Linux 3.8 kernel.
+ GPL-2.0
+
+
+ efivar
+ 0.31
+ efivar provides a simple command line interface to the UEFI variable facility
+ LGPL-2.1
+
+
+ element-vcpe
+ 4.1.3
+ vCPE(based on Element-ODM)
+ Enea, BSD, BSD-2-Clause, GPL-3.0, ISC, LGPL-2.1
+
+
+ elfutils
+ 0.170
+ Utilities and libraries for handling compiled object files.
+ GPL-3.0, Elfutils-Exception
+
+
+ enea-nfv-access-vnf
+ 1.0
+ VNF image of the Enea Edge Runtime includes kernel rootfs and boot parameters
+ MIT
+
+
+ enea-nfv-access
+ 1.0
+ Image for the host side of the Enea Edge Runtime with ODM and NETCONF Edgelink customizations
+ MIT
+
+
+ ethtool
+ 4.11
+ A small utility for examining and tuning the settings of your ethernet-based network interfaces.
+ GPL-2.0
+
+
+ expat
+ 2.2.3
+ Expat is an XML parser library written in C. It is a stream-oriented parser in which an application registers handlers for things the parser might find in the XML document (like start tags)
+ MIT
+
+
+ fastjar
+ 0.98
+ jar replacement written in C.
+ GPL-2.0
+
+
+ file
+ 5.31
+ File attempts to classify files depending on their contents and prints a description if a match is found.
+ BSD
+
+
+ findutils
+ 4.6.0
+ The GNU Find Utilities are the basic directory searching utilities of the GNU operating system. These programs are typically used in conjunction with other programs to provide modular and powerful directory search and file locating capabilities to other commands.
+ GPL-3.0
+
+
+ flex
+ 2.6.0
+ Flex is a fast lexical analyser generator. Flex is a tool for generating programs that recognize lexical patterns in text.
+ BSD
+
+
+ fontconfig
+ 2.12.4
+ Fontconfig is a font configuration and customization library which does not depend on the X Window System. It is designed to locate fonts within the system and select them according to requirements specified by applications. Fontconfig is not a rasterization library nor does it impose a particular rasterization library on the application. The X-specific library 'Xft' uses fontconfig along with freetype to specify and rasterize fonts.
+ MIT, PD
+
+
+ freetype
+ 2.8
+ FreeType is a software font engine that is designed to be small efficient highly customizable and portable while capable of producing high-quality output (glyph images). It can be used in graphics libraries display servers font conversion tools text image generation tools and many other products as well.
+ FreeType, GPL-2.0
+
+
+ fuse
+ 2.9.7
+ FUSE (Filesystem in Userspace) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. FUSE also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations.
+ GPL-2.0, LGPL-2.0
+
+
+ gawk
+ 4.1.4
+ The GNU version of awk a text processing utility. Awk interprets a special-purpose programming language to do quick and easy text pattern matching and reformatting jobs.
+ GPL-3.0
+
+
+ gcc-cross-initial-x86_64
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc-cross-x86_64
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc-runtime
+ 7.3.0
+ Runtime libraries from GCC.
+ GPL-3.0-with-GCC-exception
+
+
+ gcc-source-7.3.0
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gcc
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ gdbm
+ 1.13
+ Key/value database library with extensible hashing.
+ GPL-3.0
+
+
+ gettext-minimal
+ 0.19.8.1
+ Contains the m4 macros sufficient to support building autoconf/automake. This provides a significant build time speedup by the removal of gettext-native from most dependency chains (now only needed for gettext for the target).
+ FSF-Unlimited
+
+
+ gettext
+ 0.19.8.1
+ GNU gettext is a set of tools that provides a framework to help other programs produce multi-lingual messages. These tools include a set of conventions about how programs should be written to support message catalogs a directory and file naming organization for the message catalogs themselves a runtime library supporting the retrieval of translated messages and a few stand-alone programs to massage in various ways the sets of translatable and already translated strings.
+ GPL-3.0, LGPL-2.1
+
+
+ giflib
+ 5.1.4
+ shared library for GIF images.
+ MIT
+
+
+ git
+ 2.13.3
+ Distributed version control system.
+ GPL-2.0
+
+
+ glib-2.0
+ 2.52.3
+ GLib is a general-purpose utility library which provides many useful data types macros type conversions string utilities file utilities a main loop abstraction and so on.
+ LGPL-2.0, BSD, PD
+
+
+ glibc-locale
+ 2.26
+ Locale data from glibc.
+ GPL-2.0, LGPL-2.1
+
+
+ glibc
+ 2.26
+ The GNU C Library is used as the system C library in most systems with the Linux kernel.
+ GPL-2.0, LGPL-2.1
+
+
+ gmp
+ 6.1.2
+ GMP is a free library for arbitrary precision arithmetic operating on signed integers rational numbers and floating point numbers
+ GPL-2.0, LGPL-3.0
+
+
+ gnome-desktop-testing
+ 2014.1
+ Test runner for GNOME-style installed tests.
+ LGPL-2.0
+
+
+ gnu-config
+ 20150728
+ Tool that installs the GNU config.guess / config.sub into a directory tree
+ GPL-3.0-with-autoconf-exception
+
+
+ gnu-efi
+ 3.0.6
+ Libraries for producing EFI binaries.
+ GPL-2.0, BSD-2-Clause
+
+
+ gnujaf
+ 1.1.1
+ Provides a mean to type data and locate components suitable for performing various kinds of action on it.
+ GPL-2.0-with-GCC-exception
+
+
+ gnulib
+ 2017-08-20.18
+ A collection of software subroutines which are designed to be usable on many operating systems. The goal of the project is to make it easy for free software authors to make their software run on many operating systems. Since source is designed to be copied from gnulib it is not a library per-se as much as a collection of portable idioms to be used in other projects.
+ LGPL-2.0
+
+
+ gnumail
+ 1.1.2
+ GNU's free implementation of the JavaMail API specification
+ GPL-2.0-with-GCC-exception
+
+
+ gnutls
+ 3.5.13
+ GNU Transport Layer Security Library.
+ GPL-3.0, LGPL-2.1
+
+
+ go-capability
+ 0.0
+ Utilities for manipulating POSIX capabilities in Go.
+ BSD-2-Clause
+
+
+ go-cli
+ 1.1.0
+ A small package for building command line apps in Go
+ MIT
+
+
+ go-connections
+ 0.2.1
+ Utility package to work with network connections
+ Apache-2.0
+
+
+ go-context
+ git
+ A golang registry for global request variables.
+ BSD-3-Clause
+
+
+ go-cross-x86_64
+ 1.9.4
+ The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
+ BSD-3-Clause
+
+
+ go-dbus
+ 4.0.0
+ Native Go bindings for D-Bus
+ BSD-2-Clause
+
+
+ go-distribution
+ 2.6.0
+ The Docker toolset to pack ship store and deliver content
+ Apache-2.0
+
+
+ go-fsnotify
+ 1.2.11
+ A golang registry for global request variables.
+ BSD-3-Clause
+
+
+ go-libtrust
+ 0.0
+ Primitives for identity and authorization
+ Apache-2.0
+
+
+ go-logrus
+ 0.11.0
+ A golang registry for global request variables.
+ MIT
+
+
+ go-mux
+ git
+ A powerful URL router and dispatcher for golang.
+ BSD-3-Clause
+
+
+ go-patricia
+ 2.2.6
+ A generic patricia trie (also called radix tree) implemented in Go (Golang)
+ MIT
+
+
+ go-pty
+ git
+ PTY interface for Go
+ MIT
+
+
+ go-systemd
+ 4
+ Go bindings to systemd socket activation journal D-Bus and unit files
+ Apache-2.0
+
+
+ go
+ 1.9.4
+ The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
+ BSD-3-Clause
+
+
+ gobject-introspection
+ 1.52.1
+ Middleware layer between GObject-using C libraries and language bindings.
+ LGPL-2.0, GPL-2.0
+
+
+ gotty
+ 1.0
+ Run a terminal application as a web service
+ MIT
+
+
+ gperf
+ 3.1
+ GNU gperf is a perfect hash function generator
+ GPL-3.0
+
+
+ gpgme
+ 1.9.0
+ GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a High-Level Crypto API for encryption decryption signing signature verification and key management
+ GPL-2.0, LGPL-2.1
+
+
+ gptfdisk
+ 1.0.3
+ GPT fdisk is a disk partitioning tool loosely modeled on Linux fdisk but used for modifying GUID Partition Table (GPT) disks. The related FixParts utility fixes some common problems on Master Boot Record (MBR) disks.
+ GPL-2.0
+
+
+ grep
+ 3.1
+ GNU grep utility.
+ GPL-3.0
+
+
+ groff
+ 1.22.3
+ The groff (GNU troff) software is a typesetting package which reads plain text mixed with formatting commands and produces formatted output.
+ GPL-3.0
+
+
+ grpc-go
+ 1.4.0
+ The Go language implementation of gRPC. HTTP/2 based RPC
+ BSD
+
+
+ grub-disable-fallback
+ 1.0
+ Enea service to disable grub fallback when boot is successful
+ Enea
+
+
+ grub-efi
+ 2.02
+ GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
+ GPL-3.0
+
+
+ grub
+ 2.02
+ GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
+ GPL-3.0
+
+
+ gtk-doc
+ 1.25
+ Gtk-doc is a set of scripts that extract specially formatted comments from glib-based software and produce a set of html documentation files from them
+ GPL-2.0
+
+
+ gzip
+ 1.8
+ GNU Gzip is a popular data compression program originally written by Jean-loup Gailly for the GNU project. Mark Adler wrote the decompression part
+ GPL-3.0
+
+
+ harfbuzz
+ 1.4.8
+ HarfBuzz is an OpenType text shaping engine.
+ MIT
+
+
+ haveged
+ 1.9.1
+ The haveged project is an attempt to provide an easy-to-use unpredictable random number generator based upon an adaptation of the HAVEGE algorithm. Haveged was created to remedy low-entropy conditions in the Linux random device that can occur under some workloads especially on headless servers.
+ GPL-3.0
+
+
+ help2man
+ 1.47.4
+ Program for creating simple man pages.
+ GPL-3.0
+
+
+ hostapd
+ 2.9
+ User space daemon for extended IEEE 802.11 management.
+ BSD-3-Clause
+
+
+ htop
+ 1.0.3
+ htop process monitor.
+ GPL-2.0
+
+
+ hugepage-reservation
+ 1.0
+ Reserve hugepages on system startup.
+ Enea
+
+
+ icedtea7
+ 2.1.3
+ Harness to build the source code from OpenJDK using Free Software build tools
+ GPL-2.0-with-classpath-exception
+
+
+ icu
+ 59.1
+ The International Component for Unicode (ICU) is a mature portable set of C/C++ and Java libraries for Unicode support software internationalization (I18N) and globalization (G11N) giving applications the same results on all platforms.
+ ICU
+
+
+ inetlib
+ 1.1.1
+ GNU Classpath inetlib is an extension library to provide extra network protocol support for GNU Classpath and ClasspathX project but it can also used standalone to add http imap pop3 and smtp client support applications.
+ GPL-2.0-with-GCC-exception
+
+
+ initramfs-framework
+ 1.0
+ Modular initramfs system.
+ MIT
+
+
+ initramfs-module-install-efi
+ 1.0
+ initramfs-framework module for EFI installation option.
+ MIT
+
+
+ initramfs-module-install
+ 1.0
+ initramfs-framework module for installation option.
+ MIT
+
+
+ initramfs-module-setup-live
+ 1.0
+ initramfs-framework module for live booting.
+ MIT
+
+
+ initramfs-ostree-image
+ 1.0
+ OSTree initramfs image
+ MIT
+
+
+ inputproto
+ 2.3.2
+ This package provides the wire protocol for the X Input extension. The extension supports input devices other then the core X keyboard and pointer.
+ MIT
+
+
+ intltool
+ 0.51.0
+ Utility scripts for internationalizing XML.
+ GPL-2.0
+
+
+ iperf3
+ 3.2
+ iperf is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing protocols and buffers. For each test it reports the bandwidth loss and other parameters.
+ BSD
+
+
+ iproute2
+ 4.11.0
+ Iproute2 is a collection of utilities for controlling TCP / IP networking and traffic control in Linux. Of the utilities ip and tc are the most important. ip controls IPv4 and IPv6 configuration and tc stands for traffic control.
+ GPL-2.0
+
+
+ iptables
+ 1.6.1
+ iptables is the userspace command line program used to configure and control network packet filtering code in Linux.
+ GPL-2.0
+
+
+ iw
+ 4.9
+ iw is a new nl80211 based CLI configuration utility for wireless devices. It supports almost all new drivers that have been added to the kernel recently.
+ BSD
+
+
+ ixgbe
+ 5.10.2
+ The ixgbe driver supports 82598- and 82599-based PCI Express* 10 Gigabit Network Connections.
+ GPL-2.0
+
+
+ ixgbevf
+ 4.10.2
+ This virtual function driver supports kernel versions 2.6.x and newer This driver supports 82599 X540 X550 and X552-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support. The guest OS loading this driver must support MSI-X interrupts.
+ GPL-2.0
+
+
+ jacl
+ 1.4.1
+ Tcl interpreter for Java
+ UCB, SUN, AMD, CDS
+
+
+ jamvm
+ 2.0.0-devel
+ A compact Java Virtual Machine which conforms to the JVM specification version 2.
+ GPL-2.0
+
+
+ jansson
+ 2.9
+ Jansson is a C library for encoding decoding and manipulating JSON data.
+ MIT
+
+
+ jaxp1.3
+ 1.4.01
+ Java XML parser and transformer APIs (DOM SAX JAXP TrAX)
+ Apache-2.0, W3C, PD
+
+
+ jdepend
+ 2.9.1
+ Design quality metrics generator for each Java
+ BSD
+
+
+ jikes-initial
+ 1.0
+ Initial Java 1.4-compatible (and not higher) compiler.
+ MIT
+
+
+ jikes
+ 1.22
+ Java compiler adhering to language and VM specifications
+ IPL-1.0
+
+
+ jlex
+ 1.2.6
+ Lexical analyzer generator for Java
+ JLEX
+
+
+ jq
+ 1.5
+ jq is like sed for JSON data you can use it to slice and filter and map and transform structured data with the same ease that sed awk grep and friends let you play with text.
+ MIT
+
+
+ jsch
+ 0.1.40
+ SSH implementation in Java
+ BSD
+
+
+ junit
+ 3.8.2
+ JUnit is a testing framework for Java
+ CPL-1.0
+
+
+ jzlib
+ 1.0.7
+ zlib implementation in Java
+ BSD
+
+
+ kbd
+ 2.0.4
+ Keytable files and keyboard utilities.
+ GPL-2.0
+
+
+ kbproto
+ 1.0.7
+ This package provides the wire protocol for the X Keyboard extension. This extension is used to control options related to keyboard handling and layout.
+ MIT
+
+
+ kern-tools
+ 0.2
+ Tools for managing Yocto Project style branched kernels.
+ GPL-2.0
+
+
+ keymaps
+ 1.0
+ Keymaps and initscript to set the keymap on bootup.
+ GPL-2.0
+
+
+ keyutils
+ 1.5.10
+ Utilities to control the kernel key management facility and to provide a mechanism by which the kernel call back to userspace to get a key instantiated.
+ LGPL-2.1, GPL-2.0
+
+
+ kmod
+ 24
+ kmod is a set of tools to handle common tasks with Linux kernel modules like insert remove list check properties resolve dependencies and aliases.
+ GPL-2.0, LGPL-2.1
+
+
+ krb5
+ 1.15.1
+ "Kerberos is a system for authenticating users and services on a network. Kerberos is a trusted third-party service. That means that there is a third party (the Kerberos server) that is trusted by all the entities on the network (users and services usually called ""principals""). . This is the MIT reference implementation of Kerberos V5. . This package contains the Kerberos key server (KDC). The KDC manages all authentication credentials for a Kerberos realm holds the master keys for the realm and responds to authentication requests. This package should be installed on both master and slave KDCs."
+ MIT
+
+
+ ldconfig
+ 2.12.1
+ A standalone native ldconfig build.
+ GPL-2.0
+
+
+ less
+ 487
+ Less is a program similar to more i.e. a terminal based program for viewing text files and the output from other programs. Less offers many features beyond those that more does.
+ GPL-3.0, BSD-2-Clause
+
+
+ libaio
+ 0.3.110
+ Asynchronous input/output library that uses the kernels native interface
+ LGPL-2.1
+
+
+ libarchive
+ 3.3.2
+ C library and command-line tools for reading and writing tar cpio zip ISO and other archive formats
+ BSD
+
+
+ libassuan
+ 2.4.3
+ IPC library used by GnuPG and GPGME.
+ GPL-3.0, LGPL-2.1
+
+
+ libbsd
+ 0.8.6
+ This library provides useful functions commonly found on BSD systems and lacking on others like GNU systems thus making it easier to port projects with strong BSD origins without needing to embed the same code over and over again on each project.
+ BSD-4-Clause, ISC, PD
+
+
+ libcap
+ 2.25
+ Library for getting/setting POSIX.1e capabilities.
+ BSD, GPL-2.0
+
+
+ libcgroup
+ 0.41
+ libcgroup is a library that abstracts the control group file system in Linux. Control groups allow you to limit account and isolate resource usage (CPU memory disk I/O etc.) of groups of processes.
+ LGPL-2.1
+
+
+ libcheck
+ 0.10.0
+ Check - unit testing framework for C code.
+ LGPL-2.1
+
+
+ libdaemon
+ 0.14
+ Lightweight C library which eases the writing of UNIX daemons.
+ LGPL-2.1
+
+
+ libdevmapper
+ 2.02.171
+ LVM2 is a set of utilities to manage logical volumes in Linux.
+ GPL-2.0, LGPL-2.0
+
+
+ libecj-bootstrap
+ 3.6.2
+ JDT Core Batch Compiler - Jar only
+ EPL-1.0
+
+
+ liberation-fonts
+ 2.00.1
+ The Liberation(tm) Fonts is a font family originally created by Ascender(c) which aims at metric compatibility with Arial Times New Roman Courier New.
+ OFL-1.1
+
+
+ libffi
+ 3.2.1
+ The `libffi' library provides a portable high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. FFI stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The `libffi' library really only provides the lowest machine dependent layer of a fully featured foreign function interface. A layer must exist above `libffi' that handles type conversions for values passed between the two languages.
+ MIT
+
+
+ libfile-slurp-perl
+ 9999.19
+ This module provides subroutines to read or write entire files with a simple call. It also has a subroutine for reading the list of filenames in a directory.
+ Artistic-1.0, GPL-1.0
+
+
+ libgcc-initial
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception
+
+
+ libgcc
+ 7.3.0
+ GNU cc and gcc C compilers.
+ GPL-3.0-with-GCC-exception, GPL-3.0
+
+
+ libgcrypt
+ 1.8.0
+ General purpose cryptographic library based on the code from GnuPG.
+ GPL-2.0, LGPL-2.1, GPL-3.0
+
+
+ libgpg-error
+ 1.27
+ Small library that defines common error values for all GnuPG components.
+ GPL-2.0, LGPL-2.1
+
+
+ libgudev
+ 231
+ GObject wrapper for libudev.
+ LGPL-2.1
+
+
+ libice
+ 1.0.9
+ The Inter-Client Exchange (ICE) protocol provides a generic framework for building protocols on top of reliable byte-stream transport connections. It provides basic mechanisms for setting up and shutting down connections for performing authentication for negotiating versions and for reporting errors.
+ MIT
+
+
+ libidn
+ 1.33
+ Implementation of the Stringprep Punycode and IDNA specifications defined by the IETF Internationalized Domain Names (IDN) working group.
+ LGPL-2.1, LGPL-3.0, GPL-3.0
+
+
+ libjpeg-turbo
+ 1.5.2
+ libjpeg-turbo is a derivative of libjpeg that uses SIMD instructions (MMX SSE2 NEON) to accelerate baseline JPEG compression and decompression
+ BSD-3-Clause
+
+
+ libmbim
+ 1.16.0
+ libmbim is a glib-based library for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol
+ GPL-2.0, LGPL-2.1
+
+
+ libmnl
+ 1.0.4
+ Minimalistic user-space library oriented to Netlink developers providing functions for common tasks in parsing validating and constructing both the Netlink header and TLVs.
+ LGPL-2.1
+
+
+ libmpc
+ 1.0.3
+ Mpc is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result. It is built upon and follows the same principles as Mpfr
+ LGPL-3.0
+
+
+ libndp
+ 1.6
+ Library for IPv6 Neighbor Discovery Protocol.
+ LGPL-2.1
+
+
+ libnewt
+ 0.52.20
+ Newt is a programming library for color text mode widget based user interfaces. Newt can be used to add stacked windows entry widgets checkboxes radio buttons labels plain text fields scrollbars etc. to text mode user interfaces. This package also contains the shared library needed by programs built with newt as well as a /usr/bin/dialog replacement called whiptail. Newt is based on the slang library.
+ LGPL-2.0
+
+
+ libnl
+ 3.4.0
+ A library for applications dealing with netlink sockets.
+ LGPL-2.1
+
+
+ libnss-mdns
+ 0.10
+ Name Service Switch module for Multicast DNS (zeroconf) name resolution.
+ LGPL-2.1
+
+
+ libpcap
+ 1.8.1
+ Libpcap provides a portable framework for low-level network monitoring. Libpcap can provide network statistics collection security monitoring and network debugging.
+ BSD
+
+
+ libpciaccess
+ 0.13.5
+ libpciaccess provides functionality for X to access the PCI bus and devices in a platform-independent way.
+ MIT
+
+
+ libpcre
+ 8.41
+ The PCRE library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. PCRE has its own native API as well as a set of wrapper functions that correspond to the POSIX regular expression API.
+ BSD
+
+
+ libpng
+ 1.6.31
+ PNG image format decoding library.
+ Libpng
+
+
+ libpthread-stubs
+ 0.4
+ This library provides weak aliases for pthread functions not provided in libc or otherwise available by default.
+ MIT
+
+
+ libqmi
+ 1.20.2
+ libqmi is a glib-based library for talking to WWAN modems and devices which speak the Qualcomm MSM Interface (QMI) protocol
+ GPL-2.0, LGPL-2.1
+
+
+ libsdl
+ 1.2.15
+ Simple DirectMedia Layer is a cross-platform multimedia library designed to provide low level access to audio keyboard mouse joystick 3D hardware via OpenGL and 2D video framebuffer.
+ LGPL-2.1
+
+
+ libsign
+ 0.3.2
+ This project targets to provide a generic signing framework. This framework separates the signing request and signing process and correspondingly forms the so-called signlet and signaturelet. Each signaturelet only concerns about the details about how to construct the layout of a signature format and signlet only cares how to construct the signing request.
+ BSD-3-Clause
+
+
+ libsm
+ 1.2.2
+ "The Session Management Library (SMlib) is a low-level \""C\"" language interface to XSMP. The purpose of the X Session Management Protocol (XSMP) is to provide a uniform mechanism for users to save and restore their sessions. A session is a group of clients each of which has a particular state."
+ MIT
+
+
+ libtasn1
+ 4.12
+ Library for ASN.1 and DER manipulation.
+ GPL-3.0, LGPL-2.1
+
+
+ libtool
+ 2.4.6
+ This is GNU libtool a generic library support script. Libtool hides the complexity of generating special library types (such as shared libraries) behind a consistent interface.
+ GPL-2.0, LGPL-2.1
+
+
+ libunistring
+ 0.9.7
+ Text files are nowadays usually encoded in Unicode and may consist of very different scripts from Latin letters to Chinese Hanzi with many kinds of special characters accents right-to-left writing marks hyphens Roman numbers and much more. But the POSIX platform APIs for text do not contain adequate functions for dealing with particular properties of many Unicode characters. In fact the POSIX APIs for text have several assumptions at their base which don't hold for Unicode text. This library provides functions for manipulating Unicode strings and for manipulating C strings according to the Unicode standard. This package contains documentation.
+ LGPL-3.0, GPL-2.0
+
+
+ libusb1
+ 1.0.21
+ Userspace library to access USB (version 1.0).
+ LGPL-2.1
+
+
+ libvirt
+ 4.2.0
+ A toolkit to interact with the virtualization capabilities of recent versions of Linux.
+ LGPL-2.1, GPL-2.0
+
+
+ libx11
+ 1.6.5
+ This package provides a client interface to the X Window System otherwise known as 'Xlib'. It provides a complete API for the basic functions of the window system.
+ MIT, BSD
+
+
+ libxau
+ 1.0.8
+ libxau provides the main interfaces to the X11 authorisation handling which controls authorisation for X connections both client-side and server-side.
+ MIT
+
+
+ libxcb
+ 1.12
+ The X protocol C-language Binding (XCB) is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
+ MIT
+
+
+ libxdmcp
+ 1.1.2
+ The purpose of the X Display Manager Control Protocol (XDMCP) is to provide a uniform mechanism for an autonomous display to request login service from a remote host. An X terminal (screen keyboard mouse processor network interface) is a prime example of an autonomous display.
+ MIT
+
+
+ libxext
+ 1.3.3
+ libXext provides an X Window System client interface to several extensions to the X protocol. The supported protocol extensions are DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. libXext also provides a small set of utility functions to aid authors of client APIs for X protocol extensions.
+ MIT
+
+
+ libxft
+ 2.3.2
+ Xft was designed to provide good support for scalable fonts and to do so efficiently. Unlike the core fonts system it supports features such as anti-aliasing and sub-pixel rasterisation. Perhaps more importantly it gives applications full control over the way glyphs are rendered making fine typesetting and WYSIWIG display possible. Finally it allows applications to use fonts that are not installed system-wide for displaying documents with embedded fonts. Xft is not compatible with the core fonts system: usage of Xft requires fairly extensive changes to toolkits (user-interface libraries).
+ MIT
+
+
+ libxkbcommon
+ 0.7.1
+ libxkbcommon is a keymap compiler and support library which processes a reduced subset of keymaps as defined by the XKB specification.
+ MIT
+
+
+ libxml-parser-perl
+ 2.44
+ XML::Parser - A perl module for parsing XML documents.
+ Artistic-1.0, GPL-1.0
+
+
+ libxml2
+ 2.9.5
+ The XML Parser Library allows for manipulation of XML files. Libxml2 exports Push and Pull type parser interfaces for both XML and HTML. It can do DTD validation at parse time on a parsed document instance or with an arbitrary DTD. Libxml2 includes complete XPath XPointer and Xinclude implementations. It also has a SAX like interface which is designed to be compatible with Expat.
+ MIT
+
+
+ libxrandr
+ 1.5.1
+ The X Resize Rotate and Reflect Extension called RandR for short brings the ability to resize rotate and reflect the root window of a screen. It is based on the X Resize and Rotate Extension as specified in the Proceedings of the 2001 Usenix Technical Conference [RANDR].
+ MIT
+
+
+ libxrender
+ 0.9.10
+ The X Rendering Extension (Render) introduces digital image composition as the foundation of a new rendering model within the X Window System. Rendering geometric figures is accomplished by client-side tessellation into either triangles or trapezoids. Text is drawn by loading glyphs into the server and rendering sets of them.
+ MIT
+
+
+ libxslt
+ 1.1.29
+ GNOME XSLT library.
+ MIT
+
+
+ libyaml
+ 0.1.7
+ LibYAML is a C library for parsing and emitting data in YAML 1.1 a human-readable data serialization format.
+ MIT
+
+
+ lighttpd
+ 1.4.45
+ Lightweight high-performance web server.
+ BSD
+
+
+ linux-firmware
+ 0.0
+ Firmware files for use with Linux kernel.
+ Redistributable binaries
+
+
+ linux-intel-guest
+ 4.14.123
+ Linux kernel.
+ GPL-2.0
+
+
+ linux-intel-host
+ 4.14.123
+ Linux kernel.
+ GPL-2.0
+
+
+ linux-libc-headers
+ 4.12
+ Sanitized set of kernel headers for the C library's use.
+ GPL-2.0
+
+
+ lmsensors-config
+ 1.0
+ Hardware health monitoring configuration files
+ MIT
+
+
+ lmsensors
+ 3.6.0
+ Hardware health monitoring applications.
+ GPL-2.0, LGPL-2.1
+
+
+ log-collector
+ 1.0
+ Service that collects platform logs
+ Enea
+
+
+ log4j1.2
+ 1.2.17
+ Java library to help the programmer output log statements to a variety of output targets
+ Apache-2.0
+
+
+ logkit
+ 1.2.2
+ Logging toolkit designed for secure performance orientated logging in Java applications
+ Apache-2.0
+
+
+ logrotate
+ 3.12.3
+ Rotates compresses removes and mails system log files.
+ GPL-2.0
+
+
+ lsb
+ 4.1
+ LSB support for OpenEmbedded.
+ GPL-2.0
+
+
+ lsbinitscripts
+ 9.72
+ SysV init scripts which are only used in an LSB image.
+ GPL-2.0
+
+
+ lshw
+ 02.17
+ A small tool to provide detailed information on the hardware configuration of the machine. It can report exact memory configuration firmware version mainboard configuration CPU version and speed cache configuration bus speed etc. on DMI-capable or EFI systems.
+ GPL-2.0
+
+
+ lsof
+ 4.89
+ Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open Files and it does just that.
+ BSD
+
+
+ lvm2
+ 2.02.171
+ LVM2 is a set of utilities to manage logical volumes in Linux.
+ GPL-2.0, LGPL-2.0
+
+
+ lxc
+ 2.0.8
+ lxc aims to use these new functionnalities to provide an userspace container object
+ GPL-2.0
+
+
+ lxd
+ git
+ "LXD is a container ""hypervisor"" and a new user experience for LXC Specifically it's made of three components: - A system-wide daemon (lxd) - A command line client (lxc) - An OpenStack Nova plugin (nova-compute-lxd)"
+ Apache-2.0
+
+
+ lz4
+ 1.7.4
+ LZ4 is a very fast lossless compression algorithm providing compression speed at 400 MB/s per core scalable with multi-cores CPU. It also features an extremely fast decoder with speed in multiple GB/s per core typically reaching RAM speed limits on multi-core systems.
+ BSD, BSD-2-Clause, GPL-2.0
+
+
+ lzo
+ 2.10
+ Lossless data compression library.
+ GPL-2.0
+
+
+ lzop
+ 1.03
+ lzop is a compression utility which is designed to be a companion to gzip. \nIt is based on the LZO data compression library and its main advantages over \ngzip are much higher compression and decompression speed at the cost of some \ncompression ratio. The lzop compression utility was designed with the goals \nof reliability speed portability and with reasonable drop-in compatibility \nto gzip.
+ GPL-2.0
+
+
+ m4
+ 1.4.18
+ GNU m4 is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible although it has some extensions (for example handling more than 9 positional parameters to macros). GNU M4 also has built-in functions for including files running shell commands doing arithmetic etc.
+ GPL-3.0
+
+
+ make
+ 4.2.1
+ Make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. Make gets its knowledge of how to build your program from a file called the makefile which lists each of the non-source files and how to compute it from other files.
+ GPL-3.0, LGPL-2.0
+
+
+ makedepend
+ 1.0.5
+ The makedepend program reads each sourcefile in sequence and parses it like a C-preprocessor processing all #include #define #undef #ifdef #ifndef #endif #if #elif and #else directives so that it can correctly tell which #include directives would be used in a compilation. Any #include directives can reference files having other #include directives and parsing will occur in these files as well.
+ MIT
+
+
+ makedevs
+ 1.0.1
+ Tool for creating device nodes.
+ GPL-2.0
+
+
+ mklibs
+ 0.1.43
+ mklibs produces cut-down shared libraries that contain only the routines required by a particular set of executables.
+ GPL-2.0
+
+
+ modemmanager
+ 1.7.991
+ ModemManager is a DBus-activated daemon which controls mobile broadband (2G/3G/4G) devices and connections
+ GPL-2.0, LGPL-2.1
+
+
+ mokutil
+ 0.3.0
+ The utility to manipulate machines owner keys which managed in shim.
+ GPL-3.0
+
+
+ mozjs
+ 17.0.0
+ SpiderMonkey is Mozilla's JavaScript engine written in C/C++.
+ MPL-2.0
+
+
+ mpfr
+ 3.1.5
+ C library for multiple-precision floating-point computations with exact rounding.
+ GPL-3.0, LGPL-3.0
+
+
+ mtools
+ 4.0.18
+ Mtools is a collection of utilities to access MS-DOS disks from GNU and Unix without mounting them.
+ GPL-3.0
+
+
+ nasm
+ 2.13.01
+ General-purpose x86 assembler.
+ BSD-2-Clause
+
+
+ ncurses
+ 6.0
+ SVr4 and XSI-Curses compatible curses library and terminfo tools including tic infocmp captoinfo. Supports color multiple highlights forms-drawing characters and automatic recognition of keypad and function-key sequences. Extensions include resizable windows and mouse support on both xterm and Linux console using the gpm library.
+ MIT
+
+
+ net-snmp
+ 5.7.3
+ Various tools relating to the Simple Network Management Protocol.
+ BSD
+
+
+ net-tools
+ 1.60-26
+ A collection of programs that form the base set of the NET-3 networking distribution for the Linux operating system
+ GPL-2.0
+
+
+ netbase
+ 5.4
+ This package provides the necessary infrastructure for basic TCP/IP based networking
+ GPL-2.0
+
+
+ netcat-openbsd
+ 1.105
+ A simple Unix utility which reads and writes data across network connections using TCP or UDP protocol. It is designed to be a reliable 'back-end' tool that can be used directly or easily driven by other programs and scripts. At the same time it is a feature-rich network debugging and exploration tool since it can create almost any kind of connection you would need and has several interesting built-in capabilities.
+ BSD-3-Clause
+
+
+ netcf
+ 0.2.8
+ netcf is a cross-platform network configuration library.
+ LGPL-2.1
+
+
+ nettle
+ 3.3
+ A low level cryptographic library.
+ LGPL-3.0, GPL-2.0
+
+
+ networkmanager
+ 1.10.10
+ NetworkManager.
+ GPL-2.0
+
+
+ nfv-init
+ 1.0
+ Enea service expected to be run after cloud-init
+ Enea
+
+
+ nfv-installer
+ 1.0
+ Enea Edge installer
+ Enea
+
+
+ nfva-cfgtool
+ 1.0
+ Command line tool to for accessing the Enea Edge install configuration json file
+ Enea
+
+
+ nfva-hotfixes
+ 1.0
+ Different hotfixes
+ Enea
+
+
+ nfva-startup
+ 1.0
+ Service that configures the network according to installer settings
+ Enea
+
+
+ nodejs
+ 8.4.0
+ nodeJS Evented I/O for V8 JavaScript
+ MIT, BSD, Artistic-2.0
+
+
+ notary
+ 0.4.2
+ Notary is a Docker project that allows anyone to have trust over arbitrary collections of data
+ Apache-2.0
+
+
+ nspr
+ 4.16
+ Netscape Portable Runtime Library.
+ GPL-2.0, MPL-2.0, LGPL-2.1
+
+
+ nss
+ 3.31.1
+ Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3 TLS PKCS 5 PKCS 7 PKCS 11 PKCS 12 S/MIME X.509 v3 certificates and other security standards.
+ MPL-2.0, GPL-2.0, MPL-2.0, LGPL-2.1
+
+
+ ntp-user-stub
+ 1.0
+ The NTP user/group were added in previous NFVA releases and are needed for OSTree upgrades to ensure backwards compatibility.
+ Enea
+
+
+ numactl
+ 2.0.11
+ Simple NUMA policy support. It consists of a numactl program to run other programs with a specific NUMA policy and a libnuma to do allocations with NUMA policy in applications.
+ GPL-2.0, LGPL-2.1
+
+
+ onig
+ 5.9.6
+ Regular expressions library. The characteristics of this library is that different character encoding for every regular expression object can be specified.
+ BSD
+
+
+ openipmi
+ 2.0.24
+ OpenIPMI is an effort to create a full-function IPMI system to allow full access to all IPMI information on a server and to abstract it to a level that will make it easy to use
+ GPL-2.0, LGPL-2.1, BSD
+
+
+ openjdk-8
+ 102b14
+ Java runtime based upon the OpenJDK Project
+ GPL-2.0-with-classpath-exception
+
+
+ openssh
+ 7.5p1
+ Secure rlogin/rsh/rcp/telnet replacement (OpenSSH) Ssh (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine.
+ BSD
+
+
+ openssl
+ 1.0.2o
+ Secure Socket Layer (SSL) binary and related cryptographic tools.
+ OpenSSL
+
+
+ openvswitch
+ 2.9
+ Open vSwitch is a production quality multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension while still supporting standard management interfaces and protocols (e.g. NetFlow sFlow SPAN RSPAN CLI LACP 802.1ag)
+ Apache-2.0
+
+
+ opkg-utils
+ 0.3.5
+ Additional utilities for the opkg package manager.
+ GPL-2.0
+
+
+ oro
+ 2.0.8
+ Perl5-compatible regular expressions library for Java
+ Apache-2.0
+
+
+ os-release
+ 1.0
+ The /etc/os-release file contains operating system identification data.
+ MIT
+
+
+ ostree-initrd
+ 3
+ Extremely basic live image init script.
+ MIT
+
+
+ ostree-rw
+ 1.0
+ Enea bash script to make current ostree hash writable
+ Enea
+
+
+ ostree
+ v2018.7
+ Tool for managing bootable immutable versioned filesystem trees.
+ LGPL-2.0
+
+
+ packagegroup-core-boot
+ 1.0
+ The minimal set of packages required to boot the system
+ MIT
+
+
+ packagegroup-core-ssh-openssh
+ 1.0
+ OpenSSH SSH client/server.
+ MIT
+
+
+ packagegroup-efi-secure-boot
+ 1.0
+ EFI Secure Boot packages for secure-environment.
+ MIT
+
+
+ packagegroup-enea-telemetry
+ 1.0
+ Packages for Telemetry.
+ MIT
+
+
+ packagegroup-enea-virtualization-4gusb-modems
+ 1.0
+ Packagegroup for 4G usb modems.
+ MIT
+
+
+ packagegroup-enea-virtualization-docker
+ 1.0
+ Packagegroup for Docker.
+ MIT
+
+
+ packagegroup-enea-virtualization-dpdk
+ 1.0
+ Packagegroup for DPDK.
+ MIT
+
+
+ packagegroup-enea-virtualization-guest
+ 1.0
+ This package group includes packages and packagegroups specific to the guest side of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-virtualization-host
+ 1.0
+ This package group includes packages and packagegroups specific to the host side of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-virtualization-libvirt
+ 1.0
+ Package group for libvirt.
+ MIT
+
+
+ packagegroup-enea-virtualization-lxc
+ 1.0
+ Packagegroup for LXC.
+ MIT
+
+
+ packagegroup-enea-virtualization-lxd
+ 1.0
+ Packagegroup for LXD.
+ MIT
+
+
+ packagegroup-enea-virtualization-ovs
+ 1.0
+ Packagegroup for Open vSwitch.
+ MIT
+
+
+ packagegroup-enea-virtualization-qemu
+ 1.0
+ Packagegroup for QEMU.
+ MIT
+
+
+ packagegroup-enea-virtualization
+ 1.0
+ This packagegroup includes packages and packagegroups required for both host and guest images of the Enea Linux Virtualization Profile.
+ MIT
+
+
+ packagegroup-enea-wifi
+ 1.0
+ This package group includes packages and packagegroups that enable WiFi connectivity in the Enea Edge Runtime
+ MIT
+
+
+ pango
+ 1.40.6
+ Pango is a library for laying out and rendering of text with an emphasis on internationalization. Pango can be used anywhere that text layout is needed though most of the work on Pango so far has been done in the context of the GTK+ widget toolkit. Pango forms the core of text and font handling for GTK+-2.x.
+ LGPL-2.0
+
+
+ parted
+ 3.2
+ Disk partition editing/resizing utility.
+ GPL-3.0
+
+
+ partrt
+ 1.1
+ partrt is a tool for dividing a SMP Linux system into a real time domain and a non-real time domain.
+ BSD
+
+
+ pciutils
+ 3.5.5
+ The PCI Utilities package contains a library for portable access to PCI bus configuration space and several utilities based on this library.
+ GPL-2.0
+
+
+ perl
+ 5.24.1
+ Perl scripting language.
+ Artistic-1.0, GPL-1.0
+
+
+ pigz
+ 2.3.4
+ pigz which stands for parallel implementation of gzip is a fully functional replacement for gzip that exploits multiple processors and multiple cores to the hilt when compressing data. pigz was written by Mark Adler and uses the zlib and pthread libraries.
+ Zlib, Apache-2.0
+
+
+ pixman
+ 0.34.0
+ Pixman provides a library for manipulating pixel regions -- a set of Y-X banded rectangles image compositing using the Porter/Duff model and implicit mask generation for geometric primitives including trapezoids triangles and rectangles.
+ MIT, PD
+
+
+ pkgconfig
+ 0.29.2
+ pkg-config is a helper tool used when compiling applications and libraries. It helps determined the correct compiler/link options. It is also language-agnostic.
+ GPL-2.0
+
+
+ pm-utils
+ 1.4.1
+ Simple shell command line tools to suspend and hibernate.
+ GPL-2.0
+
+
+ polkit
+ 0.113
+ The polkit package is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes.
+ LGPL-2.0
+
+
+ popt
+ 1.16
+ Library for parsing command line options.
+ MIT
+
+
+ prelink
+ 1.0
+ The prelink package contains a utility which modifies ELF shared libraries and executables so that far fewer relocations need to be resolved at runtime and thus programs come up faster.
+ GPL-2.0
+
+
+ procps
+ 3.3.12
+ Procps contains a set of system utilities that provide system information about processes using the /proc filesystem. The package includes the programs ps top vmstat w kill and skill.
+ GPL-2.0, LGPL-2.0
+
+
+ pseudo
+ 1.8.2
+ Pseudo gives fake root capabilities to a normal user.
+ LGPL-2.1
+
+
+ ptest-runner
+ 2.1
+ The ptest-runner2 package installs a ptest-runner program which loops through all installed ptest test suites and runs them in sequence.
+ GPL-2.0
+
+
+ python-asn1crypto
+ 0.23.0
+ Python binding to the Networking and Cryptography (NaCl) library
+ Apache-2.0
+
+
+ python-certifi
+ 2017.7.27.1
+ This installable Python package contains a CA Bundle that you can reference in your Python code. This is useful for verifying HTTP requests for example. This is the same CA Bundle which ships with the Requests codebase and is derived from Mozilla Firefox's canonical set.
+ ISC
+
+
+ python-cffi
+ 1.11.2
+ Foreign Function Interface for Python calling C code.
+ MIT
+
+
+ python-chardet
+ 3.0.4
+ Universal encoding detector for Python 2 and 3.
+ LGPL-2.1
+
+
+ python-cryptography-vectors
+ 2.0.3
+ Test vectors for the cryptography package..
+ Apache-2.0, BSD
+
+
+ python-cryptography
+ 2.0.3
+ Provides cryptographic recipes and primitives to python developers.
+ Apache-2.0, BSD
+
+
+ python-cython
+ 0.27.1
+ Cython is a language specially designed for writing Python extension modules. It's designed to bridge the gap between the nice high-level easy-to-use world of Python and the messy low-level world of C.
+ Apache-2.0
+
+
+ python-enum34
+ 1.1.6
+ backport of Python 3.4's enum package.
+ BSD-3-Clause
+
+
+ python-functools32
+ 3.2.3-2
+ Backport of the functools module from Python 3.2.3 for use on 2.7 and PyPy..
+ Python-2.0
+
+
+ python-futures
+ 3.0.5
+ The concurrent.futures module provides a high-level interface for asynchronously executing callables.
+ BSD
+
+
+ python-idna
+ 2.6
+ Internationalised Domain Names in Applications.
+ BSD-3-Clause, Python-2.0, Unicode
+
+
+ python-ipaddress
+ 1.0.18
+ Python 3.3+'s ipaddress for Python 2.6 2.7 3.2..
+ Python-2.0
+
+
+ python-iso8601
+ 0.1.12
+ Simple module to parse ISO 8601 dates.
+ MIT
+
+
+ python-jsonpatch
+ 1.16
+ Appling JSON patches in Python 2.6+ and 3.x.
+ BSD
+
+
+ python-jsonpointer
+ 1.12
+ Resolve JSON Pointers in Python.
+ BSD
+
+
+ python-jsonschema
+ 2.6.0
+ An implementation of JSON Schema validation for Python.
+ MIT
+
+
+ python-m2crypto
+ 0.26.4
+ A Python crypto and SSL toolkit.
+ BSD
+
+
+ python-ndg-httpsclient
+ 0.4.3
+ Provides enhanced HTTPS support for httplib and urllib2 using PyOpenSSL
+ BSD
+
+
+ python-netaddr
+ 0.7.19
+ A network address manipulation library for Python..
+ BSD
+
+
+ python-netifaces
+ 0.10.6
+ Portable network interface information.
+ MIT
+
+
+ python-pip
+ 9.0.1
+ PIP is a tool for installing and managing Python packages.
+ MIT, LGPL-2.1
+
+
+ python-pretend
+ 1.0.8
+ A library for stubbing in Python.
+ BSD
+
+
+ python-prettytable
+ 0.7.2
+ Python library for displaying tabular data in a ASCII table format.
+ BSD
+
+
+ python-psutil
+ 5.3.1
+ A cross-platform process and system utilities module for Python.
+ BSD
+
+
+ python-py
+ 1.4.34
+ Library with cross-python path ini-parsing io code log facilities.
+ MIT
+
+
+ python-pyasn1
+ 0.3.6
+ Python library implementing ASN.1 types..
+ BSD-2-Clause
+
+
+ python-pycparser
+ 2.18
+ Parser of the C language written in pure Python.
+ BSD-3-Clause
+
+
+ python-pyopenssl
+ 17.3.0
+ Simple Python wrapper around the OpenSSL library.
+ Apache-2.0
+
+
+ python-pysocks
+ 1.6.7
+ A Python SOCKS client module
+ BSD
+
+
+ python-pytest-runner
+ 2.12.1
+ Invoke py.test as distutils command with dependency resolution.
+ MIT
+
+
+ python-pytest
+ 3.2.2
+ Simple powerful teting with python.
+ MIT
+
+
+ python-pyyaml
+ 3.11
+ YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. . PyYAML features a complete YAML 1.1 parser Unicode support pickle support capable extension API and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. . PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistance.
+ MIT
+
+
+ python-requests
+ 2.18.4
+ Python HTTP for Humans.
+ Apache-2.0
+
+
+ python-rfc3987
+ 1.3.7
+ Parsing and validation of URIs (RFC 3986) and IRIs (RFC 3987).
+ GPL-3.0
+
+
+ python-setuptools-scm
+ 1.15.6
+ the blessed package to manage your versions by scm tags.
+ MIT
+
+
+ python-setuptools
+ 36.2.7
+ Download build install upgrade and uninstall Python packages.
+ MIT
+
+
+ python-six
+ 1.11.0
+ Python 2 and 3 compatibility library.
+ MIT
+
+
+ python-strict-rfc3339
+ 0.7
+ Strict simple lightweight RFC3339 function.s.
+ GPL-3.0
+
+
+ python-typing
+ 3.6.2
+ Simple Python module defined by PEP 484..
+ Python-2.0
+
+
+ python-urllib3
+ 1.22
+ Python HTTP library with thread-safe connection pooling file post support sanity friendly and more.
+ MIT
+
+
+ python-vcversioner
+ 2.16.0.0
+ Python vcversioner automagically update the project's version.
+ ISC
+
+
+ python
+ 2.7.13
+ The Python Programming Language.
+ Python-2.0
+
+
+ python3-netifaces
+ 0.10.6
+ Portable network interface information.
+ MIT
+
+
+ python3-pip
+ 9.0.1
+ The PyPA recommended tool for installing Python packages.
+ MIT
+
+
+ python3-setuptools
+ 36.2.7
+ Download build install upgrade and uninstall Python packages.
+ MIT
+
+
+ python3-six
+ 1.10.0
+ Python 2 and 3 compatibility library.
+ MIT
+
+
+ python3-twisted
+ 13.2.0
+ Twisted is an event-driven networking framework written in Python and licensed under the LGPL. Twisted supports TCP UDP SSL/TLS multicast Unix sockets a large number of protocols (including HTTP NNTP IMAP SSH IRC FTP and others) and much more.
+ MIT
+
+
+ python3-zopeinterface
+ 4.4.3
+ Interface definitions for Zope products.
+ ZPL-2.1
+
+
+ python3
+ 3.5.3
+ The Python Programming Language.
+ Python-2.0
+
+
+ qemu-helper
+ 1.0
+ Helper utilities needed by the runqemu script.
+ GPL-2.0
+
+
+ qemu
+ 2.11.1
+ Fast open source processor emulator.
+ GPL-2.0, LGPL-2.1
+
+
+ qemuwrapper
+ 1.0
+ QEMU wrapper script.
+ MIT
+
+
+ quilt
+ 0.65
+ Tool for working with series of patches.
+ GPL-2.0
+
+
+ randrproto
+ 1.5.0
+ This package provides the wire protocol for the X Resize Rotate and Reflect extension. This extension provides the ability to resize rotate and reflect the root window of a screen.
+ MIT
+
+
+ readline
+ 7.0
+ The GNU Readline library provides a set of functions for use by applications that allow users to edit command lines as they are typed in. Both Emacs and vi editing modes are available. The Readline library includes additional functions to maintain a list of previously-entered command lines to recall and perhaps reedit those lines and perform csh-like history expansion on previous commands.
+ GPL-3.0
+
+
+ regexp
+ 1.5
+ Java Regular Expression package
+ Apache-2.0
+
+
+ renderproto
+ 0.11.1
+ This package provides the wire protocol for the X Rendering extension. This is the basis the image composition within the X window system.
+ MIT
+
+
+ rhino
+ 1.7r4
+ Lexical analyzer generator for Java
+ MPL-2.0
+
+
+ rpm
+ 4.13.90
+ The RPM Package Manager (RPM) is a powerful command line driven package management system capable of installing uninstalling verifying querying and updating software packages. Each software package consists of an archive of files along with information about the package like its version a description etc.
+ GPL-2.0
+
+
+ rrdtool
+ 1.6.0
+ High performance data logging and graphing system for time series data.
+ GPL-2.0
+
+
+ rsync
+ 3.1.3
+ File synchronization tool.
+ GPL-3.0
+
+
+ run-postinsts
+ 1.0
+ Runs postinstall scripts on first boot of the target device.
+ MIT
+
+
+ runc-docker
+ 1.0.0-rc3
+ runc is a CLI tool for spawning and running containers according to the OCI specification.
+ Apache-2.0
+
+
+ sbsigntool
+ 0.6
+ Utilities for signing UEFI binaries for use with secure boot.
+ GPL-3.0
+
+
+ sed
+ 4.2.2
+ Stream EDitor (text filtering utility).
+ GPL-3.0
+
+
+ seloader
+ 0.4.6
+ The SELoader is designed to authenticate the non-PE files such as grub configuration initrd grub modules which cannot be verified by the MOK Verify Protocol registered by shim loader. In order to conveniently authenticate the PE file with gBS->LoadImage() and gBS->StartImage() the SELoader hooks EFI Security2 Architectural Protocol and employs MOK Verify Protocol to verify the PE file. If only UEFI Secure Boot is enabled the SELoader just simplily calls gBS->LoadImage() and gBS->StartImage() to allow BIOS to verify PE file. The SELoader publishes MOK2 Verify Protocol which provides a flexible interface to allow the bootloader to verify the file file buffer or memory buffer without knowing the file format.
+ BSD-3-Clause
+
+
+ servlet2.3
+ 4.1.37
+ Servlet API 2.3 (from Tomcat 4.1)
+ Apache-2.0
+
+
+ shadow-securetty
+ 4.2.1
+ Provider of the machine specific securetty file.
+ MIT
+
+
+ shadow-sysroot
+ 4.2.1
+ Shadow utils requirements for useradd.bbclass.
+ BSD, Artistic-1.0
+
+
+ shadow
+ 4.2.1
+ Tools to change and administer password and group data.
+ BSD, Artistic-1.0
+
+
+ shared-mime-info
+ 1.8
+ Shared MIME type database and specification.
+ LGPL-2.0
+
+
+ shim
+ 12
+ shim is a trivial EFI application that when run attempts to open and execute another application. It will initially attempt to do this via the standard EFI LoadImage() and StartImage() calls. If these fail (because secure boot is enabled and the binary is not signed with an appropriate key for instance) it will then validate the binary against a built-in certificate. If this succeeds and if the binary or signing key are not blacklisted then shim will relocate and execute the binary.
+ BSD-2-Clause
+
+
+ simpleproxy
+ 1.0
+ Simpleproxy.
+ GPL-2.0
+
+
+ slang
+ 2.3.1a
+ S-Lang is an interpreted language and a programming library. The S-Lang language was designed so that it can be easily embedded into a program to provide the program with a powerful extension language. The S-Lang library provided in this package provides the S-Lang extension language. S-Lang's syntax resembles C which makes it easy to recode S-Lang procedures in C if you need to.
+ GPL-2.0
+
+
+ sqlite3
+ 3.20.0
+ Embeddable SQL database engine.
+ PD
+
+
+ squashfs-tools
+ 4.3
+ Tools for manipulating SquashFS filesystems.
+ GPL-2.0, PD
+
+
+ sshpass
+ 1.06
+ Tool for non-interactivly performing ssh password authentication
+ GPL-2.0
+
+
+ swig
+ 3.0.12
+ SWIG - Simplified Wrapper and Interface Generator.
+ BSD, GPL-3.0
+
+
+ sysfsutils
+ 2.1.0
+ Tools for working with the sysfs virtual filesystem. The tool 'systool' can query devices by bus class and topology.
+ GPL-2.0, LGPL-2.1
+
+
+ sysklogd
+ 1.5.1
+ The sysklogd package implements two system log daemons: syslogd klogd
+ GPL-2.0, BSD
+
+
+ syslinux
+ 6.03
+ Multi-purpose linux bootloader.
+ GPL-2.0
+
+
+ systemd-boot
+ 234
+ systemd is a system and service 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.
+ GPL-2.0, LGPL-2.1
+
+
+ systemd-compat-units
+ 1.0
+ Enhances systemd compatilibity with existing SysVinit scripts.
+ MIT
+
+
+ systemd-serialgetty
+ 1.0
+ Serial terminal support for systemd.
+ GPL-2.0
+
+
+ systemd-systemctl
+ 1.0
+ Wrapper for enabling systemd services.
+ MIT
+
+
+ systemd
+ 234
+ systemd is a system and service 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.
+ GPL-2.0, LGPL-2.1
+
+
+ tar
+ 1.29
+ GNU tar saves many files together into a single tape or disk archive and can restore individual files from the archive.
+ GPL-3.0
+
+
+ tcl
+ 8.6.7
+ Tool Command Language.
+ tcl, BSD-3-Clause
+
+
+ tcpdump
+ 4.9.2
+ A sophisticated network protocol analyzer.
+ BSD
+
+
+ texinfo-dummy
+ 1.0
+ Fake version of the texinfo utility suite.
+ MIT
+
+
+ thin-provisioning-tools
+ 0.6.3
+ A suite of tools for manipulating the metadata of the dm-thin device-mapper target.
+ GPL-3.0
+
+
+ tunctl
+ 1.5
+ Tool for controlling the Linux TUN/TAP driver.
+ GPL-2.0
+
+
+ tzcode
+ 2018c
+ tzcode timezone zoneinfo utils -- zic zdump tzselect.
+ PD, BSD, BSD-3-Clause
+
+
+ tzdata
+ 2018c
+ Timezone data.
+ PD, BSD, BSD-3-Clause
+
+
+ udev-extraconf
+ 1.1
+ Extra machine specific configuration files for udev specifically blacklist information.
+ MIT
+
+
+ unifdef
+ 2.11
+ Selectively remove #ifdef statements from sources.
+ BSD-2-Clause
+
+
+ unzip
+ 6.0
+ Utilities for extracting and viewing files in .zip archives.
+ BSD-3-Clause
+
+
+ update-rc.d
+ 0.7
+ update-rc.d is a utility that allows the management of symlinks to the initscripts in the /etc/rcN.d directory structure.
+ GPL-2.0
+
+
+ usb-modeswitch-data
+ 20170205
+ Data files for usbmodeswitch.
+ GPL-2.0
+
+
+ usb-modeswitch
+ 2.5.0
+ A mode switching tool for controlling 'flip flop' (multiple device) USB gear.
+ GPL-2.0
+
+
+ usbutils
+ 013
+ Contains the lsusb utility for inspecting the devices connected to the USB bus.
+ GPL-2.0, GPL-3.0
+
+
+ util-linux
+ 2.30
+ Util-linux includes a suite of basic system administration utilities commonly found on most Linux systems. Some of the more important utilities include disk partitioning kernel message management filesystem creation and system login.
+ GPL-2.0, LGPL-2.1, BSD
+
+
+ util-macros
+ 1.19.1
+ M4 autotools macros used by various X.org programs.
+ MIT
+
+
+ v86d
+ 0.1.10
+ User support binary for the uvesafb kernel module.
+ GPL-2.0
+
+
+ vala
+ 0.36.4
+ Vala is a C#-like language dedicated to ease GObject programming. Vala compiles to plain C and has no runtime environment nor penalities whatsoever.
+ LGPL-2.1
+
+
+ volatile-binds
+ 1.0
+ Volatile bind mount setup and configuration for read-only-rootfs
+ MIT
+
+
+ web-installer-backend
+ 0.1
+ Web installer go server
+ Enea, BSD-3-Clause
+
+
+ web-installer-frontend
+ 0.1
+ Web installer post-install application
+ Enea, Apache-2.0, BSD, BSD-2-Clause, BSD-3-Clause, CC-BY-4.0, ISC, MIT, Zlib
+
+
+ which
+ 2.21
+ Which is a utility that prints out the full path of the executables that bash(1) would execute when the passed program names would have been entered on the shell prompt. It does this by using the exact same algorithm as bash.
+ GPL-3.0
+
+
+ wireless-regdb
+ 2020.11.20
+ Wireless Central Regulatory Domain Database.
+ ISC
+
+
+ wpa-supplicant
+ 2.6
+ Client for Wi-Fi Protected Access (WPA).
+ BSD
+
+
+ xalan-j
+ 2.7.1
+ Java XSLT processor
+ Apache-2.0
+
+
+ xcb-proto
+ 1.12
+ Function prototypes for the X protocol C-language Binding (XCB). XCB is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
+ MIT
+
+
+ xerces-j
+ 2.11.0
+ Reference implementation of XNI the Xerces Native Interface and also a fully conforming XML Schema processor.
+ Apache-2.0
+
+
+ xextproto
+ 7.3.0
+ This package provides the wire protocol for several X extensions. These protocol extensions include DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. In addition a small set of utility functions are also available.
+ MIT
+
+
+ xkeyboard-config
+ 2.21
+ The non-arch keyboard configuration database for X Window. The goal is to provide the consistent well-structured frequently released open source of X keyboard configuration data for X Window System implementations. The project is targeted to XKB-based systems.
+ MIT
+
+
+ xml-commons-resolver1.1
+ 1.2
+ Library to resolve various public or system identifiers into accessible URLs (Java)
+ Apache-2.0
+
+
+ xproto
+ 7.0.31
+ This package provides the basic headers for the X Window System.
+ MIT
+
+
+ xtrans
+ 1.3.5
+ The X Transport Interface is intended to combine all system and transport specific code into a single place. This API should be used by all libraries clients and servers of the X Window System. Use of this API should allow the addition of new types of transports and support for new platforms without making any changes to the source except in the X Transport Interface code.
+ MIT
+
+
+ xz
+ 5.2.3
+ Utilities for managing LZMA compressed files.
+ GPL-2.0, GPL-3.0-with-autoconf-exception, LGPL-2.1, PD
+
+
+ yajl
+ 2.1.0
+ YAJL is a small event-driven (SAX-style) JSON parser written in ANSI C and a small validating JSON generator.
+ ISC
+
+
+ zip
+ 3.0
+ Compressor/archiver for creating and modifying .zip files.
+ BSD-3-Clause
+
+
+ zisofs-tools
+ 1.0.8
+ Utilities for creating compressed CD-ROM filesystems.
+ GPL-2.0
+
+
+ zlib
+ 1.2.11
+ Zlib is a general-purpose patent-free lossless data compression library which is used by many different programs.
+ Zlib
+
+
+
+
+
+
+ Open Source Licenses
+
+AFL-2.0
+
+
+The Academic Free License
+ v. 2.0
+
+This Academic Free License (the "License") applies to any original work of authorship
+(the "Original Work") whose owner (the "Licensor") has placed the following notice
+immediately following the copyright notice for the Original Work:
+Licensed under the Academic Free License version 2.0
+
+1) Grant of Copyright License. Licensor hereby grants You a world-wide, royalty-free,
+non-exclusive, perpetual, sublicenseable license to do the following:
+a) to reproduce the Original Work in copies;
+
+b) to prepare derivative works ("Derivative Works") based upon the Original Work;
+
+c) to distribute copies of the Original Work and Derivative Works to the public;
+
+d) to perform the Original Work publicly; and
+
+e) to display the Original Work publicly.
+
+2) Grant of Patent License. Licensor hereby grants You a world-wide, royalty-free,
+non-exclusive, perpetual, sublicenseable license, under patent claims owned or
+controlled by the Licensor that are embodied in the Original Work as furnished by the
+Licensor, to make, use, sell and offer for sale the Original Work and Derivative
+Works.
+
+3) Grant of Source Code License. The term "Source Code" means the preferred form of
+the Original Work for making modifications to it and all available documentation
+describing how to modify the Original Work. Licensor hereby agrees to provide a
+machine-readable copy of the Source Code of the Original Work along with each copy of
+the Original Work that Licensor distributes. Licensor reserves the right to satisfy
+this obligation by placing a machine-readable copy of the Source Code in an
+information repository reasonably calculated to permit inexpensive and convenient
+access by You for as long as Licensor continues to distribute the Original Work, and
+by publishing the address of that information repository in a notice immediately
+following the copyright notice that applies to the Original Work.
+
+4) Exclusions From License Grant. Neither the names of Licensor, nor the names of any
+contributors to the Original Work, nor any of their trademarks or service marks, may
+be used to endorse or promote products derived from this Original Work without express
+prior written permission of the Licensor. Nothing in this License shall be deemed to
+grant any rights to trademarks, copyrights, patents, trade secrets or any other
+intellectual property of Licensor except as expressly stated herein. No patent
+license is granted to make, use, sell or offer to sell embodiments of any patent
+claims other than the licensed claims defined in Section 2. No right is granted to
+the trademarks of Licensor even if such marks are included in the Original Work.
+Nothing in this License shall be interpreted to prohibit Licensor from licensing under
+different terms from this License any Original Work that Licensor otherwise would have
+a right to license.
+
+5) This section intentionally omitted.
+
+6) Attribution Rights. You must retain, in the Source Code of any Derivative Works
+that You create, all copyright, patent or trademark notices from the Source Code of
+the Original Work, as well as any notices of licensing and any descriptive text
+identified therein as an "Attribution Notice." You must cause the Source Code for any
+Derivative Works that You create to carry a prominent Attribution Notice reasonably
+calculated to inform recipients that You have modified the Original Work.
+
+7) Warranty of Provenance and Disclaimer of Warranty. Licensor warrants that the
+copyright in and to the Original Work and the patent rights granted herein by Licensor
+are owned by the Licensor or are sublicensed to You under the terms of this License
+with the permission of the contributor(s) of those copyrights and patent rights.
+Except as expressly stated in the immediately proceeding sentence, the Original Work
+is provided under this License on an "AS IS" BASIS and WITHOUT WARRANTY, either
+express or implied, including, without limitation, the warranties of NON-INFRINGEMENT,
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+QUALITY OF THE ORIGINAL WORK IS WITH YOU. This DISCLAIMER OF WARRANTY constitutes an
+essential part of this License. No license to Original Work is granted hereunder
+except under this disclaimer.
+
+8) Limitation of Liability. Under no circumstances and under no legal theory, whether
+in tort (including negligence), contract, or otherwise, shall the Licensor be liable
+to any person for any direct, indirect, special, incidental, or consequential damages
+of any character arising as a result of this License or the use of the Original Work
+including, without limitation, damages for loss of goodwill, work stoppage, computer
+failure or malfunction, or any and all other commercial damages or losses. This
+limitation of liability shall not apply to liability for death or personal injury
+resulting from Licensor`s negligence to the extent applicable law prohibits such
+limitation. Some jurisdictions do not allow the exclusion or limitation of incidental
+or consequential damages, so this exclusion and limitation may not apply to You.
+
+9) Acceptance and Termination. If You distribute copies of the Original Work or a
+Derivative Work, You must make a reasonable effort under the circumstances to obtain
+the express assent of recipients to the terms of this License. Nothing else but this
+License (or another written agreement between Licensor and You) grants You permission
+to create Derivative Works based upon the Original Work or to exercise any of the
+rights granted in Section 1 herein, and any attempt to do so except under the terms of
+this License (or another written agreement between Licensor and You) is expressly
+prohibited by U.S. copyright law, the equivalent laws of other countries, and by
+international treaty. Therefore, by exercising any of the rights granted to You in
+Section 1 herein, You indicate Your acceptance of this License and all of its terms
+and conditions.
+
+10) Termination for Patent Action. This License shall terminate automatically and You
+may no longer exercise any of the rights granted to You by this License as of the date
+You commence an action, including a cross-claim or counterclaim, for patent
+infringement (i) against Licensor with respect to a patent applicable to software or
+(ii) against any entity with respect to a patent applicable to the Original Work (but
+excluding combinations of the Original Work with other software or hardware).
+
+11) Jurisdiction, Venue and Governing Law. Any action or suit relating to this License
+may be brought only in the courts of a jurisdiction wherein the Licensor resides or in
+which Licensor conducts its primary business, and under the laws of that jurisdiction
+excluding its conflict-of-law provisions. The application of the United Nations
+Convention on Contracts for the International Sale of Goods is expressly excluded.
+Any use of the Original Work outside the scope of this License or after its
+termination shall be subject to the requirements and penalties of the U.S. Copyright
+Act, 17 U.S.C. ¤ 101 et seq., the equivalent laws of other countries, and
+international treaty. This section shall survive the termination of this License.
+
+12) Attorneys Fees. In any action to enforce the terms of this License or seeking
+damages relating thereto, the prevailing party shall be entitled to recover its costs
+and expenses, including, without limitation, reasonable attorneys` fees and costs
+incurred in connection with such action, including any appeal of such action. This
+section shall survive the termination of this License.
+
+13) Miscellaneous. This License represents the complete agreement concerning the
+subject matter hereof. If any provision of this License is held to be unenforceable,
+such provision shall be reformed only to the extent necessary to make it enforceable.
+
+14) Definition of "You" in This License. "You" throughout this License, whether in
+upper or lower case, means an individual or a legal entity exercising rights under,
+and complying with all of the terms of, this License. For legal entities, "You"
+includes any entity that controls, is controlled by, or is under common control with
+you. For purposes of this definition, "control" means (i) the power, direct or
+indirect, to cause the direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares,
+or (iii) beneficial ownership of such entity.
+
+15) Right to Use. You may use the Original Work in all ways not otherwise restricted
+or conditioned by this License or by law, and Licensor promises not to interfere with
+or be responsible for such uses by You.
+
+This license is Copyright (C) 2003 Lawrence E. Rosen. All rights reserved.
+Permission is hereby granted to copy and distribute this license without modification.
+This license may not be modified without the express written permission of its
+copyright owner.
+
+
+
+
+AMD
+
+� 2005 Advanced Micro Devices, Inc. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that existing copyright notices
+are retained in all copies, this notice is included verbatim in any
+distributions, and the terms and conditions hererin are met.
+
+Use of the this software manifests acceptance of the terms of this
+license by performance.
+
+The name of Advanced Micro Devices, Inc. may not be used to endorse or
+promote products derived from this software without specific prior
+written permission.
+
+THIS SOFTWARE IS PROVIDED BY ADVANCED MICRO DEVICES, INC. "AS IS" AND ANY
+EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+PURPOSE AND NON-INFRINGEMENT, OR THOSE ARISING FROM CUSTOM OF TRADE OR
+COURSE OF USAGE ARE DISCLAIMED.
+
+IN NO EVENT SHALL ADVANCED MICRO DEVICES, INC. BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED, AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE ITS DOCUMENTATION OR ANY DERIVATIVES
+THEREOF, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BY USING THIS
+SOFTWARE WITHOUT CHARGE, YOU ACCEPT THIS ALLOCATION OF RISK. THIS
+DISCLAIMER OF LIABILITY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE.
+ADVANCED MICRO DEVICES, INC. HAS NO OBLIGATION TO PROVIDE MAINTENANCE,
+SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS OF THIS SOFTWARE.
+
+In the redistribution and use of this software, each party shall at all
+times comply with all applicable governmental laws, statutes, ordinances,
+rules, regulations, orders, and other requirements, including without
+limitation such governmental requirements applicable to environmental
+protection, health, safety, wages, hours, equal employment opportunity,
+nondiscrimination, working conditions, import or export control, and
+transportation. Without limiting the foregoing, each party shall adhere
+to the U.S. Export Administration Regulations (EAR), currently found at
+15 C.F.R. Sections 730 through 744, and, unless properly authorized by
+the U.S. Government, shall not (1) export, re-export or release restricted
+technology, software, or source code to a national of a country in Country
+Groups D:1 or E:1, or (2) export to Country Groups D:1 or E:1 the direct
+product of such technology or software, if such foreign produced direct
+product is subject to national security controls as identified on the
+Commerce Control List (currently found in Supplement 1 to Section 774 of EAR).
+These export requirements shall survive any expiration or termination
+of this agreement.
+
+
+
+Apache-2.0
+
+
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don`t include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+
+
+
+Artistic-1.0
+
+
+The Artistic License
+Preamble
+
+The intent of this document is to state the conditions under which a Package may be
+copied, such that the Copyright Holder maintains some semblance of artistic control
+over the development of the package, while giving the users of the package the right
+to use and distribute the Package in a more-or-less customary fashion, plus the right
+to make reasonable modifications.
+
+Definitions:
+
+"Package" refers to the collection of files distributed by the Copyright Holder, and
+derivatives of that collection of files created through textual modification.
+"Standard Version" refers to such a Package if it has not been modified, or has been
+modified in accordance with the wishes of the Copyright Holder.
+"Copyright Holder" is whoever is named in the copyright or copyrights for the package.
+"You" is you, if you`re thinking about copying or distributing this Package.
+"Reasonable copying fee" is whatever you can justify on the basis of media cost,
+duplication charges, time of people involved, and so on. (You will not be required to
+justify it to the Copyright Holder, but only to the computing community at large as a
+market that must bear the fee.)
+"Freely Available" means that no fee is charged for the item itself, though there may
+be fees involved in handling the item. It also means that recipients of the item may
+redistribute it under the same conditions they received it.
+1. You may make and give away verbatim copies of the source form of the Standard
+Version of this Package without restriction, provided that you duplicate all of the
+original copyright notices and associated disclaimers.
+
+2. You may apply bug fixes, portability fixes and other modifications derived from the
+Public Domain or from the Copyright Holder. A Package modified in such a way shall
+still be considered the Standard Version.
+
+3. You may otherwise modify your copy of this Package in any way, provided that you
+insert a prominent notice in each changed file stating how and when you changed that
+file, and provided that you do at least ONE of the following:
+
+a) place your modifications in the Public Domain or otherwise make them Freely
+Available, such as by posting said modifications to Usenet or an equivalent medium, or
+placing the modifications on a major archive site 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.
+
+4. You may distribute the programs of this Package in object code or executable form,
+provided that you do at least ONE of the following:
+
+a) distribute a Standard Version of the executables and library files, together with
+instructions (in the manual page or equivalent) on where to get the Standard Version.
+
+b) accompany the distribution with the machine-readable source of the Package with
+your modifications.
+
+c) accompany any non-standard executables with their corresponding Standard Version
+executables, giving the non-standard executables non-standard names, and clearly
+documenting the differences in manual pages (or equivalent), together with
+instructions on where to get the Standard Version.
+
+d) make other distribution arrangements with the Copyright Holder.
+
+5. You may charge a reasonable copying fee for any distribution of this Package. You
+may charge any fee you choose for support of this Package. You may not charge a fee
+for this Package itself. However, you may distribute this Package in aggregate with
+other (possibly commercial) programs as part of a larger (possibly commercial)
+software distribution provided that you do not advertise this Package as a product of
+your own.
+
+6. The scripts and library files supplied as input to or produced as output from the
+programs of this Package do not automatically fall under the copyright of this
+Package, but belong to whomever generated them, and may be sold commercially, and may
+be aggregated with this Package.
+
+7. C or perl subroutines supplied by you and linked into this Package shall not be
+considered part of this Package.
+
+8. The name of the Copyright Holder may not be used to endorse or promote products
+derived from this software without specific prior written permission.
+
+9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
+INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS
+FOR A PARTICULAR PURPOSE.
+
+The End
+
+
+
+
+Artistic-2.0
+
+
+ The Artistic License 2.0
+
+ Copyright (c) 2000-2006, The Perl Foundation.
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+Preamble
+
+This license establishes the terms under which a given free software
+Package may be copied, modified, distributed, and/or redistributed.
+The intent is that the Copyright Holder maintains some artistic
+control over the development of that Package while still keeping the
+Package available as open source and free software.
+
+You are always permitted to make arrangements wholly outside of this
+license directly with the Copyright Holder of a given Package. If the
+terms of this license do not permit the full use that you propose to
+make of the Package, you should contact the Copyright Holder and seek
+a different licensing arrangement.
+
+Definitions
+
+ "Copyright Holder" means the individual(s) or organization(s)
+ named in the copyright notice for the entire Package.
+
+ "Contributor" means any party that has contributed code or other
+ material to the Package, in accordance with the Copyright Holder`s
+ procedures.
+
+ "You" and "your" means any person who would like to copy,
+ distribute, or modify the Package.
+
+ "Package" means the collection of files distributed by the
+ Copyright Holder, and derivatives of that collection and/or of
+ those files. A given Package may consist of either the Standard
+ Version, or a Modified Version.
+
+ "Distribute" means providing a copy of the Package or making it
+ accessible to anyone else, or in the case of a company or
+ organization, to others outside of your company or organization.
+
+ "Distributor Fee" means any fee that you charge for Distributing
+ this Package or providing support for this Package to another
+ party. It does not mean licensing fees.
+
+ "Standard Version" refers to the Package if it has not been
+ modified, or has been modified only in ways explicitly requested
+ by the Copyright Holder.
+
+ "Modified Version" means the Package, if it has been changed, and
+ such changes were not explicitly requested by the Copyright
+ Holder.
+
+ "Original License" means this Artistic License as Distributed with
+ the Standard Version of the Package, in its current version or as
+ it may be modified by The Perl Foundation in the future.
+
+ "Source" form means the source code, documentation source, and
+ configuration files for the Package.
+
+ "Compiled" form means the compiled bytecode, object code, binary,
+ or any other form resulting from mechanical transformation or
+ translation of the Source form.
+
+
+Permission for Use and Modification Without Distribution
+
+(1) You are permitted to use the Standard Version and create and use
+Modified Versions for any purpose without restriction, provided that
+you do not Distribute the Modified Version.
+
+
+Permissions for Redistribution of the Standard Version
+
+(2) You may Distribute verbatim copies of the Source form of the
+Standard Version of this Package in any medium without restriction,
+either gratis or for a Distributor Fee, provided that you duplicate
+all of the original copyright notices and associated disclaimers. At
+your discretion, such verbatim copies may or may not include a
+Compiled form of the Package.
+
+(3) You may apply any bug fixes, portability changes, and other
+modifications made available from the Copyright Holder. The resulting
+Package will still be considered the Standard Version, and as such
+will be subject to the Original License.
+
+
+Distribution of Modified Versions of the Package as Source
+
+(4) You may Distribute your Modified Version as Source (either gratis
+or for a Distributor Fee, and with or without a Compiled form of the
+Modified Version) provided that you clearly document how it differs
+from the Standard Version, including, but not limited to, documenting
+any non-standard features, executables, or modules, and provided that
+you do at least ONE of the following:
+
+ (a) make the Modified Version available to the Copyright Holder
+ of the Standard Version, under the Original License, so that the
+ Copyright Holder may include your modifications in the Standard
+ Version.
+
+ (b) ensure that installation of your Modified Version does not
+ prevent the user installing or running the Standard Version. In
+ addition, the Modified Version must bear a name that is different
+ from the name of the Standard Version.
+
+ (c) allow anyone who receives a copy of the Modified Version to
+ make the Source form of the Modified Version available to others
+ under
+
+ (i) the Original License or
+
+ (ii) a license that permits the licensee to freely copy,
+ modify and redistribute the Modified Version using the same
+ licensing terms that apply to the copy that the licensee
+ received, and requires that the Source form of the Modified
+ Version, and of any works derived from it, be made freely
+ available in that license fees are prohibited but Distributor
+ Fees are allowed.
+
+
+Distribution of Compiled Forms of the Standard Version
+or Modified Versions without the Source
+
+(5) You may Distribute Compiled forms of the Standard Version without
+the Source, provided that you include complete instructions on how to
+get the Source of the Standard Version. Such instructions must be
+valid at the time of your distribution. If these instructions, at any
+time while you are carrying out such distribution, become invalid, you
+must provide new instructions on demand or cease further distribution.
+If you provide valid instructions or cease distribution within thirty
+days after you become aware that the instructions are invalid, then
+you do not forfeit any of your rights under this license.
+
+(6) You may Distribute a Modified Version in Compiled form without
+the Source, provided that you comply with Section 4 with respect to
+the Source of the Modified Version.
+
+
+Aggregating or Linking the Package
+
+(7) You may aggregate the Package (either the Standard Version or
+Modified Version) with other packages and Distribute the resulting
+aggregation provided that you do not charge a licensing fee for the
+Package. Distributor Fees are permitted, and licensing fees for other
+components in the aggregation are permitted. The terms of this license
+apply to the use and Distribution of the Standard or Modified Versions
+as included in the aggregation.
+
+(8) You are permitted to link Modified and Standard Versions with
+other works, to embed the Package in a larger work of your own, or to
+build stand-alone binary or bytecode versions of applications that
+include the Package, and Distribute the result without restriction,
+provided the result does not expose a direct interface to the Package.
+
+
+Items That are Not Considered Part of a Modified Version
+
+(9) Works (including, but not limited to, modules and scripts) that
+merely extend or make use of the Package, do not, by themselves, cause
+the Package to be a Modified Version. In addition, such works are not
+considered parts of the Package itself, and are not subject to the
+terms of this license.
+
+
+General Provisions
+
+(10) Any use, modification, and distribution of the Standard or
+Modified Versions is governed by this Artistic License. By using,
+modifying or distributing the Package, you accept this license. Do not
+use, modify, or distribute the Package, if you do not accept this
+license.
+
+(11) If your Modified Version has been derived from a Modified
+Version made by someone other than you, you are nevertheless required
+to ensure that your Modified Version complies with the requirements of
+this license.
+
+(12) This license does not grant you the right to use any trademark,
+service mark, tradename, or logo of the Copyright Holder.
+
+(13) This license includes the non-exclusive, worldwide,
+free-of-charge patent license to make, have made, use, offer to sell,
+sell, import and otherwise transfer the Package with respect to any
+patent claims licensable by the Copyright Holder that are necessarily
+infringed by the Package. If you institute patent litigation
+(including a cross-claim or counterclaim) against any party alleging
+that the Package constitutes direct or contributory patent
+infringement, then this Artistic License to you shall terminate on the
+date that such litigation is filed.
+
+(14) Disclaimer of Warranty:
+THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS
+IS` AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
+NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL
+LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL
+BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+BSD
+
+Copyright (c) The Regents of the University of California.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. Neither the name of the University nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+
+
+BSD-2-Clause
+
+
+The FreeBSD Copyright
+
+Copyright 1992-2010 The FreeBSD Project. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this list of
+conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright notice, this list of
+conditions and the following disclaimer in the documentation and/or other materials
+provided with the distribution.
+THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS`` AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD
+PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+The views and conclusions contained in the software and documentation are those of the
+authors and should not be interpreted as representing official policies, either
+expressed or implied, of the FreeBSD Project.
+
+
+
+
+BSD-3-Clause
+
+
+Copyright (c) <YEAR>, <OWNER>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this list of
+conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright notice, this list of
+conditions and the following disclaimer in the documentation and/or other materials
+provided with the distribution.
+Neither the name of the <ORGANIZATION> nor the names of its contributors may be
+used to endorse or promote products derived from this software without specific prior
+written permission.
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
+SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
+TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
+WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGE.
+
+
+
+
+BSD-4-Clause
+
+
+Copyright (c) <year>, <copyright holder>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+3. All advertising materials mentioning features or use of this software
+ must display the following acknowledgement:
+ This product includes software developed by the <organization>.
+4. Neither the name of the <organization> nor the
+ names of its contributors may be used to endorse or promote products
+ derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY <COPYRIGHT HOLDER> ``AS IS`` AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+BSL-1.0
+
+
+Boost Software License - Version 1.0 - August 17th, 2003
+
+Permission is hereby granted, free of charge, to any person or organization
+obtaining a copy of the software and accompanying documentation covered by
+this license (the "Software") to use, reproduce, display, distribute,
+execute, and transmit the Software, and to prepare derivative works of the
+Software, and to permit third-parties to whom the Software is furnished to
+do so, all subject to the following:
+
+The copyright notices in the Software and this entire statement, including
+the above license grant, this restriction and the following disclaimer,
+must be included in all copies of the Software, in whole or in part, and
+all derivative works of the Software, unless such copies or derivative
+works are solely in the form of machine-executable object code generated by
+a source language processor.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
+SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
+FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
+ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.
+
+
+
+
+CC-BY-4.0
+
+Attribution 4.0 International
+
+=======================================================================
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and
+does not provide legal services or legal advice. Distribution of
+Creative Commons public licenses does not create a lawyer-client or
+other relationship. Creative Commons makes its licenses and related
+information available on an "as-is" basis. Creative Commons gives no
+warranties regarding its licenses, any material licensed under their
+terms and conditions, or any related information. Creative Commons
+disclaims all liability for damages resulting from their use to the
+fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and
+conditions that creators and other rights holders may use to share
+original works of authorship and other material subject to copyright
+and certain other rights specified in the public license below. The
+following considerations are for informational purposes only, are not
+exhaustive, and do not form part of our licenses.
+
+ Considerations for licensors: Our public licenses are
+ intended for use by those authorized to give the public
+ permission to use material in ways otherwise restricted by
+ copyright and certain other rights. Our licenses are
+ irrevocable. Licensors should read and understand the terms
+ and conditions of the license they choose before applying it.
+ Licensors should also secure all rights necessary before
+ applying our licenses so that the public can reuse the
+ material as expected. Licensors should clearly mark any
+ material not subject to the license. This includes other CC-
+ licensed material, or material used under an exception or
+ limitation to copyright. More considerations for licensors:
+ wiki.creativecommons.org/Considerations_for_licensors
+
+ Considerations for the public: By using one of our public
+ licenses, a licensor grants the public permission to use the
+ licensed material under specified terms and conditions. If
+ the licensor's permission is not necessary for any reason--for
+ example, because of any applicable exception or limitation to
+ copyright--then that use is not regulated by the license. Our
+ licenses grant only permissions under copyright and certain
+ other rights that a licensor has authority to grant. Use of
+ the licensed material may still be restricted for other
+ reasons, including because others have copyright or other
+ rights in the material. A licensor may make special requests,
+ such as asking that all changes be marked or described.
+ Although not required by our licenses, you are encouraged to
+ respect those requests where reasonable. More_considerations
+ for the public:
+ wiki.creativecommons.org/Considerations_for_licensees
+
+=======================================================================
+
+Creative Commons Attribution 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree
+to be bound by the terms and conditions of this Creative Commons
+Attribution 4.0 International Public License ("Public License"). To the
+extent this Public License may be interpreted as a contract, You are
+granted the Licensed Rights in consideration of Your acceptance of
+these terms and conditions, and the Licensor grants You such rights in
+consideration of benefits the Licensor receives from making the
+Licensed Material available under these terms and conditions.
+
+
+Section 1 -- Definitions.
+
+ a. Adapted Material means material subject to Copyright and Similar
+ Rights that is derived from or based upon the Licensed Material
+ and in which the Licensed Material is translated, altered,
+ arranged, transformed, or otherwise modified in a manner requiring
+ permission under the Copyright and Similar Rights held by the
+ Licensor. For purposes of this Public License, where the Licensed
+ Material is a musical work, performance, or sound recording,
+ Adapted Material is always produced where the Licensed Material is
+ synched in timed relation with a moving image.
+
+ b. Adapter's License means the license You apply to Your Copyright
+ and Similar Rights in Your contributions to Adapted Material in
+ accordance with the terms and conditions of this Public License.
+
+ c. Copyright and Similar Rights means copyright and/or similar rights
+ closely related to copyright including, without limitation,
+ performance, broadcast, sound recording, and Sui Generis Database
+ Rights, without regard to how the rights are labeled or
+ categorized. For purposes of this Public License, the rights
+ specified in Section 2(b)(1)-(2) are not Copyright and Similar
+ Rights.
+
+ d. Effective Technological Measures means those measures that, in the
+ absence of proper authority, may not be circumvented under laws
+ fulfilling obligations under Article 11 of the WIPO Copyright
+ Treaty adopted on December 20, 1996, and/or similar international
+ agreements.
+
+ e. Exceptions and Limitations means fair use, fair dealing, and/or
+ any other exception or limitation to Copyright and Similar Rights
+ that applies to Your use of the Licensed Material.
+
+ f. Licensed Material means the artistic or literary work, database,
+ or other material to which the Licensor applied this Public
+ License.
+
+ g. Licensed Rights means the rights granted to You subject to the
+ terms and conditions of this Public License, which are limited to
+ all Copyright and Similar Rights that apply to Your use of the
+ Licensed Material and that the Licensor has authority to license.
+
+ h. Licensor means the individual(s) or entity(ies) granting rights
+ under this Public License.
+
+ i. Share means to provide material to the public by any means or
+ process that requires permission under the Licensed Rights, such
+ as reproduction, public display, public performance, distribution,
+ dissemination, communication, or importation, and to make material
+ available to the public including in ways that members of the
+ public may access the material from a place and at a time
+ individually chosen by them.
+
+ j. Sui Generis Database Rights means rights other than copyright
+ resulting from Directive 96/9/EC of the European Parliament and of
+ the Council of 11 March 1996 on the legal protection of databases,
+ as amended and/or succeeded, as well as other essentially
+ equivalent rights anywhere in the world.
+
+ k. You means the individual or entity exercising the Licensed Rights
+ under this Public License. Your has a corresponding meaning.
+
+
+Section 2 -- Scope.
+
+ a. License grant.
+
+ 1. Subject to the terms and conditions of this Public License,
+ the Licensor hereby grants You a worldwide, royalty-free,
+ non-sublicensable, non-exclusive, irrevocable license to
+ exercise the Licensed Rights in the Licensed Material to:
+
+ a. reproduce and Share the Licensed Material, in whole or
+ in part; and
+
+ b. produce, reproduce, and Share Adapted Material.
+
+ 2. Exceptions and Limitations. For the avoidance of doubt, where
+ Exceptions and Limitations apply to Your use, this Public
+ License does not apply, and You do not need to comply with
+ its terms and conditions.
+
+ 3. Term. The term of this Public License is specified in Section
+ 6(a).
+
+ 4. Media and formats; technical modifications allowed. The
+ Licensor authorizes You to exercise the Licensed Rights in
+ all media and formats whether now known or hereafter created,
+ and to make technical modifications necessary to do so. The
+ Licensor waives and/or agrees not to assert any right or
+ authority to forbid You from making technical modifications
+ necessary to exercise the Licensed Rights, including
+ technical modifications necessary to circumvent Effective
+ Technological Measures. For purposes of this Public License,
+ simply making modifications authorized by this Section 2(a)
+ (4) never produces Adapted Material.
+
+ 5. Downstream recipients.
+
+ a. Offer from the Licensor -- Licensed Material. Every
+ recipient of the Licensed Material automatically
+ receives an offer from the Licensor to exercise the
+ Licensed Rights under the terms and conditions of this
+ Public License.
+
+ b. No downstream restrictions. You may not offer or impose
+ any additional or different terms or conditions on, or
+ apply any Effective Technological Measures to, the
+ Licensed Material if doing so restricts exercise of the
+ Licensed Rights by any recipient of the Licensed
+ Material.
+
+ 6. No endorsement. Nothing in this Public License constitutes or
+ may be construed as permission to assert or imply that You
+ are, or that Your use of the Licensed Material is, connected
+ with, or sponsored, endorsed, or granted official status by,
+ the Licensor or others designated to receive attribution as
+ provided in Section 3(a)(1)(A)(i).
+
+ b. Other rights.
+
+ 1. Moral rights, such as the right of integrity, are not
+ licensed under this Public License, nor are publicity,
+ privacy, and/or other similar personality rights; however, to
+ the extent possible, the Licensor waives and/or agrees not to
+ assert any such rights held by the Licensor to the limited
+ extent necessary to allow You to exercise the Licensed
+ Rights, but not otherwise.
+
+ 2. Patent and trademark rights are not licensed under this
+ Public License.
+
+ 3. To the extent possible, the Licensor waives any right to
+ collect royalties from You for the exercise of the Licensed
+ Rights, whether directly or through a collecting society
+ under any voluntary or waivable statutory or compulsory
+ licensing scheme. In all other cases the Licensor expressly
+ reserves any right to collect such royalties.
+
+
+Section 3 -- License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the
+following conditions.
+
+ a. Attribution.
+
+ 1. If You Share the Licensed Material (including in modified
+ form), You must:
+
+ a. retain the following if it is supplied by the Licensor
+ with the Licensed Material:
+
+ i. identification of the creator(s) of the Licensed
+ Material and any others designated to receive
+ attribution, in any reasonable manner requested by
+ the Licensor (including by pseudonym if
+ designated);
+
+ ii. a copyright notice;
+
+ iii. a notice that refers to this Public License;
+
+ iv. a notice that refers to the disclaimer of
+ warranties;
+
+ v. a URI or hyperlink to the Licensed Material to the
+ extent reasonably practicable;
+
+ b. indicate if You modified the Licensed Material and
+ retain an indication of any previous modifications; and
+
+ c. indicate the Licensed Material is licensed under this
+ Public License, and include the text of, or the URI or
+ hyperlink to, this Public License.
+
+ 2. You may satisfy the conditions in Section 3(a)(1) in any
+ reasonable manner based on the medium, means, and context in
+ which You Share the Licensed Material. For example, it may be
+ reasonable to satisfy the conditions by providing a URI or
+ hyperlink to a resource that includes the required
+ information.
+
+ 3. If requested by the Licensor, You must remove any of the
+ information required by Section 3(a)(1)(A) to the extent
+ reasonably practicable.
+
+ 4. If You Share Adapted Material You produce, the Adapter's
+ License You apply must not prevent recipients of the Adapted
+ Material from complying with this Public License.
+
+
+Section 4 -- Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that
+apply to Your use of the Licensed Material:
+
+ a. for the avoidance of doubt, Section 2(a)(1) grants You the right
+ to extract, reuse, reproduce, and Share all or a substantial
+ portion of the contents of the database;
+
+ b. if You include all or a substantial portion of the database
+ contents in a database in which You have Sui Generis Database
+ Rights, then the database in which You have Sui Generis Database
+ Rights (but not its individual contents) is Adapted Material; and
+
+ c. You must comply with the conditions in Section 3(a) if You Share
+ all or a substantial portion of the contents of the database.
+
+For the avoidance of doubt, this Section 4 supplements and does not
+replace Your obligations under this Public License where the Licensed
+Rights include other Copyright and Similar Rights.
+
+
+Section 5 -- Disclaimer of Warranties and Limitation of Liability.
+
+ a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
+ EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
+ AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
+ ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
+ IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
+ WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
+ PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
+ ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
+ KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
+ ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
+
+ b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
+ TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
+ NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
+ INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
+ COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
+ USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
+ ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
+ DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
+ IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
+
+ c. The disclaimer of warranties and limitation of liability provided
+ above shall be interpreted in a manner that, to the extent
+ possible, most closely approximates an absolute disclaimer and
+ waiver of all liability.
+
+
+Section 6 -- Term and Termination.
+
+ a. This Public License applies for the term of the Copyright and
+ Similar Rights licensed here. However, if You fail to comply with
+ this Public License, then Your rights under this Public License
+ terminate automatically.
+
+ b. Where Your right to use the Licensed Material has terminated under
+ Section 6(a), it reinstates:
+
+ 1. automatically as of the date the violation is cured, provided
+ it is cured within 30 days of Your discovery of the
+ violation; or
+
+ 2. upon express reinstatement by the Licensor.
+
+ For the avoidance of doubt, this Section 6(b) does not affect any
+ right the Licensor may have to seek remedies for Your violations
+ of this Public License.
+
+ c. For the avoidance of doubt, the Licensor may also offer the
+ Licensed Material under separate terms or conditions or stop
+ distributing the Licensed Material at any time; however, doing so
+ will not terminate this Public License.
+
+ d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
+ License.
+
+
+Section 7 -- Other Terms and Conditions.
+
+ a. The Licensor shall not be bound by any additional or different
+ terms or conditions communicated by You unless expressly agreed.
+
+ b. Any arrangements, understandings, or agreements regarding the
+ Licensed Material not stated herein are separate from and
+ independent of the terms and conditions of this Public License.
+
+
+Section 8 -- Interpretation.
+
+ a. For the avoidance of doubt, this Public License does not, and
+ shall not be interpreted to, reduce, limit, restrict, or impose
+ conditions on any use of the Licensed Material that could lawfully
+ be made without permission under this Public License.
+
+ b. To the extent possible, if any provision of this Public License is
+ deemed unenforceable, it shall be automatically reformed to the
+ minimum extent necessary to make it enforceable. If the provision
+ cannot be reformed, it shall be severed from this Public License
+ without affecting the enforceability of the remaining terms and
+ conditions.
+
+ c. No term or condition of this Public License will be waived and no
+ failure to comply consented to unless expressly agreed to by the
+ Licensor.
+
+ d. Nothing in this Public License constitutes or may be interpreted
+ as a limitation upon, or waiver of, any privileges and immunities
+ that apply to the Licensor or You, including from the legal
+ processes of any jurisdiction or authority.
+
+
+=======================================================================
+
+Creative Commons is not a party to its public
+licenses. Notwithstanding, Creative Commons may elect to apply one of
+its public licenses to material it publishes and in those instances
+will be considered the ”Licensor.” The text of the Creative Commons
+public licenses is dedicated to the public domain under the CC0 Public
+Domain Dedication. Except for the limited purpose of indicating that
+material is shared under a Creative Commons public license or as
+otherwise permitted by the Creative Commons policies published at
+creativecommons.org/policies, Creative Commons does not authorize the
+use of the trademark "Creative Commons" or any other trademark or logo
+of Creative Commons without its prior written consent including,
+without limitation, in connection with any unauthorized modifications
+to any of its public licenses or any other arrangements,
+understandings, or agreements concerning use of licensed material. For
+the avoidance of doubt, this paragraph does not form part of the
+public licenses.
+
+Creative Commons may be contacted at creativecommons.org.
+
+
+
+CDDL-1.0
+
+
+COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
+Version 1.0
+1. Definitions.
+
+1.1. “Contributor” means each individual or entity that creates or
+contributes to the creation of Modifications.
+
+1.2. “Contributor Version” means the combination of the Original
+Software, prior Modifications used by a Contributor (if any), and the Modifications
+made by that particular Contributor.
+
+1.3. “Covered Software” means (a) the Original Software, or (b)
+Modifications, or (c) the combination of files containing Original Software with files
+containing Modifications, in each case including portions thereof.
+
+1.4. “Executable” means the Covered Software in any form other
+than Source Code.
+
+1.5. “Initial Developer” means the individual or entity that first
+makes Original Software available under this License.
+
+1.6. “Larger Work” means a work which combines Covered Software or
+portions thereof with code not governed by the terms of this License.
+
+1.7. “License” means this document.
+
+1.8. “Licensable” means having the right to grant, to the maximum
+extent possible, whether at the time of the initial grant or subsequently acquired,
+any and all of the rights conveyed herein.
+
+1.9. “Modifications” means the Source Code and Executable form of
+any of the following:
+
+A. Any file that results from an addition to, deletion from or modification of the
+contents of a file containing Original Software or previous Modifications;
+
+B. Any new file that contains any part of the Original Software or previous
+Modification; or
+
+C. Any new file that is contributed or otherwise made available under the terms of
+this License.
+
+1.10. “Original Software” means the Source Code and Executable
+form of computer software code that is originally released under this License.
+
+1.11. “Patent Claims” means any patent claim(s), now owned or
+hereafter acquired, including without limitation, method, process, and apparatus
+claims, in any patent Licensable by grantor.
+
+1.12. “Source Code” means (a) the common form of computer software
+code in which modifications are made and (b) associated documentation included in or
+with such code.
+
+1.13. “You” (or “Your”) means an individual or
+a legal entity exercising rights under, and complying with all of the terms of, this
+License. For legal entities, “You” includes any entity which
+controls, is controlled by, or is under common control with You. For purposes of this
+definition, “control” means (a) the power, direct or indirect, to
+cause the direction or management of such entity, whether by contract or otherwise, or
+(b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial
+ownership of such entity.
+
+2. License Grants.
+
+2.1. The Initial Developer Grant.
+
+Conditioned upon Your compliance with Section 3.1 below and subject to third party
+intellectual property claims, the Initial Developer hereby grants You a world-wide,
+royalty-free, non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark) Licensable by
+Initial Developer, to use, reproduce, modify, display, perform, sublicense and
+distribute the Original Software (or portions thereof), with or without Modifications,
+and/or as part of a Larger Work; and
+
+(b) under Patent Claims infringed by the making, using or selling of Original
+Software, to make, have made, use, practice, sell, and offer for sale, and/or
+otherwise dispose of the Original Software (or portions thereof).
+
+(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial
+Developer first distributes or otherwise makes the Original Software available to a
+third party under the terms of this License.
+
+(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code
+that You delete from the Original Software, or (2) for infringements caused by: (i)
+the modification of the Original Software, or (ii) the combination of the Original
+Software with other software or devices.
+
+2.2. Contributor Grant.
+
+Conditioned upon Your compliance with Section 3.1 below and subject to third party
+intellectual property claims, each Contributor hereby grants You a world-wide,
+royalty-free, non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark) Licensable by
+Contributor to use, reproduce, modify, display, perform, sublicense and distribute the
+Modifications created by such Contributor (or portions thereof), either on an
+unmodified basis, with other Modifications, as Covered Software and/or as part of a
+Larger Work; and
+
+(b) under Patent Claims infringed by the making, using, or selling of Modifications
+made by that Contributor either alone and/or in combination with its Contributor
+Version (or portions of such combination), to make, use, sell, offer for sale, have
+made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or
+portions thereof); and (2) the combination of Modifications made by that Contributor
+with its Contributor Version (or portions of such combination).
+
+(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
+Contributor first distributes or otherwise makes the Modifications available to a
+third party.
+
+(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any
+code that Contributor has deleted from the Contributor Version; (2) for infringements
+caused by: (i) third party modifications of Contributor Version, or (ii) the
+combination of Modifications made by that Contributor with other software (except as
+part of the Contributor Version) or other devices; or (3) under Patent Claims
+infringed by Covered Software in the absence of Modifications made by that
+Contributor.
+
+3. Distribution Obligations.
+
+3.1. Availability of Source Code.
+
+Any Covered Software that You distribute or otherwise make available in Executable
+form must also be made available in Source Code form and that Source Code form must be
+distributed only under the terms of this License. You must include a copy of this
+License with every copy of the Source Code form of the Covered Software You distribute
+or otherwise make available. You must inform recipients of any such Covered Software
+in Executable form as to how they can obtain such Covered Software in Source Code form
+in a reasonable manner on or through a medium customarily used for software exchange.
+
+3.2. Modifications.
+
+The Modifications that You create or to which You contribute are governed by the terms
+of this License. You represent that You believe Your Modifications are Your original
+creation(s) and/or You have sufficient rights to grant the rights conveyed by this
+License.
+
+3.3. Required Notices.
+
+You must include a notice in each of Your Modifications that identifies You as the
+Contributor of the Modification. You may not remove or alter any copyright, patent or
+trademark notices contained within the Covered Software, or any notices of licensing
+or any descriptive text giving attribution to any Contributor or the Initial
+Developer.
+
+3.4. Application of Additional Terms.
+
+You may not offer or impose any terms on any Covered Software in Source Code form that
+alters or restricts the applicable version of this License or the
+recipients’ rights hereunder. You may choose to offer, and to charge a fee
+for, warranty, support, indemnity or liability obligations to one or more recipients
+of Covered Software. However, you may do so only on Your own behalf, and not on behalf
+of the Initial Developer or any Contributor. You must make it absolutely clear that
+any such warranty, support, indemnity or liability obligation is offered by You alone,
+and You hereby agree to indemnify the Initial Developer and every Contributor for any
+liability incurred by the Initial Developer or such Contributor as a result of
+warranty, support, indemnity or liability terms You offer.
+
+3.5. Distribution of Executable Versions.
+
+You may distribute the Executable form of the Covered Software under the terms of this
+License or under the terms of a license of Your choice, which may contain terms
+different from this License, provided that You are in compliance with the terms of
+this License and that the license for the Executable form does not attempt to limit or
+alter the recipient’s rights in the Source Code form from the rights set
+forth in this License. If You distribute the Covered Software in Executable form under
+a different license, You must make it absolutely clear that any terms which differ
+from this License are offered by You alone, not by the Initial Developer or
+Contributor. You hereby agree to indemnify the Initial Developer and every Contributor
+for any liability incurred by the Initial Developer or such Contributor as a result of
+any such terms You offer.
+
+3.6. Larger Works.
+
+You may create a Larger Work by combining Covered Software with other code not
+governed by the terms of this License and distribute the Larger Work as a single
+product. In such a case, You must make sure the requirements of this License are
+fulfilled for the Covered Software.
+
+4. Versions of the License.
+
+4.1. New Versions.
+
+Sun Microsystems, Inc. is the initial license steward and may publish revised and/or
+new versions of this License from time to time. Each version will be given a
+distinguishing version number. Except as provided in Section 4.3, no one other than
+the license steward has the right to modify this License.
+
+4.2. Effect of New Versions.
+
+You may always continue to use, distribute or otherwise make the Covered Software
+available under the terms of the version of the License under which You originally
+received the Covered Software. If the Initial Developer includes a notice in the
+Original Software prohibiting it from being distributed or otherwise made available
+under any subsequent version of the License, You must distribute and make the Covered
+Software available under the terms of the version of the License under which You
+originally received the Covered Software. Otherwise, You may also choose to use,
+distribute or otherwise make the Covered Software available under the terms of any
+subsequent version of the License published by the license steward.
+
+4.3. Modified Versions.
+
+When You are an Initial Developer and You want to create a new license for Your
+Original Software, You may create and use a modified version of this License if You:
+(a) rename the license and remove any references to the name of the license steward
+(except to note that the license differs from this License); and (b) otherwise make it
+clear that the license contains terms which differ from this License.
+
+5. DISCLAIMER OF WARRANTY.
+
+COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS”
+BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
+LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT
+FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
+PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
+DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR)
+ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
+WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE
+IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
+
+6. TERMINATION.
+
+6.1. This License and the rights granted hereunder will terminate automatically if You
+fail to comply with terms herein and fail to cure such breach within 30 days of
+becoming aware of the breach. Provisions which, by their nature, must remain in effect
+beyond the termination of this License shall survive.
+
+6.2. If You assert a patent infringement claim (excluding declaratory judgment
+actions) against Initial Developer or a Contributor (the Initial Developer or
+Contributor against whom You assert such claim is referred to as
+“Participant”) alleging that the Participant Software (meaning the
+Contributor Version where the Participant is a Contributor or the Original Software
+where the Participant is the Initial Developer) directly or indirectly infringes any
+patent, then any and all rights granted directly or indirectly to You by such
+Participant, the Initial Developer (if the Initial Developer is not the Participant)
+and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days
+notice from Participant terminate prospectively and automatically at the expiration of
+such 60 day notice period, unless if within such 60 day period You withdraw Your claim
+with respect to the Participant Software against such Participant either unilaterally
+or pursuant to a written agreement with Participant.
+
+6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user
+licenses that have been validly granted by You or any distributor hereunder prior to
+termination (excluding licenses granted to You by any distributor) shall survive
+termination.
+
+7. LIMITATION OF LIABILITY.
+
+UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
+CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR
+ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE
+TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
+CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,
+WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL
+DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF
+SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
+PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT
+APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
+EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
+LIMITATION MAY NOT APPLY TO YOU.
+
+8. U.S. GOVERNMENT END USERS.
+
+The Covered Software is a “commercial item,” as that term is
+defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of “commercial computer
+software” (as that term is defined at 48 C.F.R. §
+252.227-7014(a)(1)) and “commercial computer software
+documentation” as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
+Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
+1995), all U.S. Government End Users acquire Covered Software with only those rights
+set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes,
+any other FAR, DFAR, or other clause or provision that addresses Government rights in
+computer software under this License.
+
+9. MISCELLANEOUS.
+
+This License represents the complete agreement concerning subject matter hereof. If
+any provision of this License is held to be unenforceable, such provision shall be
+reformed only to the extent necessary to make it enforceable. This License shall be
+governed by the law of the jurisdiction specified in a notice contained within the
+Original Software (except to the extent applicable law, if any, provides otherwise),
+excluding such jurisdiction’s conflict-of-law provisions. Any litigation
+relating to this License shall be subject to the jurisdiction of the courts located in
+the jurisdiction and venue specified in a notice contained within the Original
+Software, with the losing party responsible for costs, including, without limitation,
+court costs and reasonable attorneys’ fees and expenses. The application of
+the United Nations Convention on Contracts for the International Sale of Goods is
+expressly excluded. Any law or regulation which provides that the language of a
+contract shall be construed against the drafter shall not apply to this License. You
+agree that You alone are responsible for compliance with the United States export
+administration regulations (and the export control laws and regulation of any other
+countries) when You use, distribute or otherwise make available any Covered Software.
+
+10. RESPONSIBILITY FOR CLAIMS.
+
+As between Initial Developer and the Contributors, each party is responsible for
+claims and damages arising, directly or indirectly, out of its utilization of rights
+under this License and You agree to work with Initial Developer and Contributors to
+distribute such responsibility on an equitable basis. Nothing herein is intended or
+shall be deemed to constitute any admission of liability.
+
+
+
+
+CDS
+
+This software is copyrighted by Cadence Design Systems, Inc., and other
+parties. The following terms apply to all files associated with the
+software unless explicitly disclaimed in individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+-----------------------------------------------------------------------
+ Following is the original agreement for the Tcl/Tk software from
+ Sun Microsystems.
+-----------------------------------------------------------------------
+
+This software is copyrighted by the Regents of the University of
+California, Sun Microsystems, Inc., and other parties. The following
+terms apply to all files associated with the software unless explicitly
+disclaimed in individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+
+
+CPL-1.0
+
+
+Common Public License Version 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
+LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
+CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+a) in the case of the initial Contributor, the initial code and
+documentation distributed under this Agreement, and
+
+b) in the case of each subsequent Contributor:
+
+i) changes to the Program, and
+
+ii) additions to the Program;
+
+where such changes and/or additions to the Program originate from and are
+distributed by that particular Contributor. A Contribution `originates` from a
+Contributor if it was added to the Program by such Contributor itself or anyone
+acting on such Contributor`s behalf. Contributions do not include additions to
+the Program which: (i) are separate modules of software distributed in
+conjunction with the Program under their own license agreement, and (ii) are not
+derivative works of the Program.
+
+"Contributor" means any person or entity that distributes the Program.
+
+"Licensed Patents " mean patent claims licensable by a Contributor which are
+necessarily infringed by the use or sale of its Contribution alone or when
+combined with the Program.
+
+"Program" means the Contributions distributed in accordance with this Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement,
+including all Contributors.
+
+2. GRANT OF RIGHTS
+
+a) Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide, royalty-free copyright license to
+reproduce, prepare derivative works of, publicly display, publicly perform,
+distribute and sublicense the Contribution of such Contributor, if any, and such
+derivative works, in source code and object code form.
+
+b) Subject to the terms of this Agreement, each Contributor hereby grants
+Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
+Patents to make, use, sell, offer to sell, import and otherwise transfer the
+Contribution of such Contributor, if any, in source code and object code form.
+This patent license shall apply to the combination of the Contribution and the
+Program if, at the time the Contribution is added by the Contributor, such
+addition of the Contribution causes such combination to be covered by the
+Licensed Patents. The patent license shall not apply to any other combinations
+which include the Contribution. No hardware per se is licensed hereunder.
+
+c) Recipient understands that although each Contributor grants the licenses
+to its Contributions set forth herein, no assurances are provided by any
+Contributor that the Program does not infringe the patent or other intellectual
+property rights of any other entity. Each Contributor disclaims any liability to
+Recipient for claims brought by any other entity based on infringement of
+intellectual property rights or otherwise. As a condition to exercising the
+rights and licenses granted hereunder, each Recipient hereby assumes sole
+responsibility to secure any other intellectual property rights needed, if any.
+For example, if a third party patent license is required to allow Recipient to
+distribute the Program, it is Recipient`s responsibility to acquire that license
+before distributing the Program.
+
+d) Each Contributor represents that to its knowledge it has sufficient
+copyright rights in its Contribution, if any, to grant the copyright license set
+forth in this Agreement.
+
+3. REQUIREMENTS
+
+A Contributor may choose to distribute the Program in object code form under its
+own license agreement, provided that:
+
+a) it complies with the terms and conditions of this Agreement; and
+
+b) its license agreement:
+
+i) effectively disclaims on behalf of all Contributors all warranties and
+conditions, express and implied, including warranties or conditions of title and
+non-infringement, and implied warranties or conditions of merchantability and
+fitness for a particular purpose;
+
+ii) effectively excludes on behalf of all Contributors all liability for
+damages, including direct, indirect, special, incidental and consequential
+damages, such as lost profits;
+
+iii) states that any provisions which differ from this Agreement are offered
+by that Contributor alone and not by any other party; and
+
+iv) states that source code for the Program is available from such
+Contributor, and informs licensees how to obtain it in a reasonable manner on or
+through a medium customarily used for software exchange.
+
+When the Program is made available in source code form:
+
+a) it must be made available under this Agreement; and
+
+b) a copy of this Agreement must be included with each copy of the Program.
+
+Contributors may not remove or alter any copyright notices contained within the
+Program.
+
+Each Contributor must identify itself as the originator of its Contribution, if
+any, in a manner that reasonably allows subsequent Recipients to identify the
+originator of the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities with
+respect to end users, business partners and the like. While this license is
+intended to facilitate the commercial use of the Program, the Contributor who
+includes the Program in a commercial product offering should do so in a manner
+which does not create potential liability for other Contributors. Therefore, if
+a Contributor includes the Program in a commercial product offering, such
+Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
+every other Contributor ("Indemnified Contributor") against any losses, damages
+and costs (collectively "Losses") arising from claims, lawsuits and other legal
+actions brought by a third party against the Indemnified Contributor to the
+extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product
+offering. The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement. In order
+to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
+Contributor in writing of such claim, and b) allow the Commercial Contributor to
+control, and cooperate with the Commercial Contributor in, the defense and any
+related settlement negotiations. The Indemnified Contributor may participate in
+any such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial product
+offering, Product X. That Contributor is then a Commercial Contributor. If that
+Commercial Contributor then makes performance claims, or offers warranties
+related to Product X, those performance claims and warranties are such
+Commercial Contributor`s responsibility alone. Under this section, the
+Commercial Contributor would have to defend claims against the other
+Contributors related to those performance claims and warranties, and if a court
+requires any other Contributor to pay any damages as a result, the Commercial
+Contributor must pay those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
+IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
+NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
+Recipient is solely responsible for determining the appropriateness of using and
+distributing the Program and assumes all risks associated with its exercise of
+rights under this Agreement, including but not limited to the risks and costs of
+program errors, compliance with applicable laws, damage to or loss of data,
+programs or equipment, and unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
+CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
+PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
+GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under applicable
+law, it shall not affect the validity or enforceability of the remainder of the
+terms of this Agreement, and without further action by the parties hereto, such
+provision shall be reformed to the minimum extent necessary to make such
+provision valid and enforceable.
+
+If Recipient institutes patent litigation against a Contributor with respect to
+a patent applicable to software (including a cross-claim or counterclaim in a
+lawsuit), then any patent licenses granted by that Contributor to such Recipient
+under this Agreement shall terminate as of the date such litigation is filed. In
+addition, if Recipient institutes patent litigation against any entity
+(including a cross-claim or counterclaim in a lawsuit) alleging that the Program
+itself (excluding combinations of the Program with other software or hardware)
+infringes such Recipient`s patent(s), then such Recipient`s rights granted under
+Section 2(b) shall terminate as of the date such litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it fails to
+comply with any of the material terms or conditions of this Agreement and does
+not cure such failure in a reasonable period of time after becoming aware of
+such noncompliance. If all Recipient`s rights under this Agreement terminate,
+Recipient agrees to cease use and distribution of the Program as soon as
+reasonably practicable. However, Recipient`s obligations under this Agreement
+and any licenses granted by Recipient relating to the Program shall continue and
+survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement, but in
+order to avoid inconsistency the Agreement is copyrighted and may only be
+modified in the following manner. The Agreement Steward reserves the right to
+publish new versions (including revisions) of this Agreement from time to time.
+No one other than the Agreement Steward has the right to modify this Agreement.
+IBM is the initial Agreement Steward. IBM may assign the responsibility to serve
+as the Agreement Steward to a suitable separate entity. Each new version of the
+Agreement will be given a distinguishing version number. The Program (including
+Contributions) may always be distributed subject to the version of the Agreement
+under which it was received. In addition, after a new version of the Agreement
+is published, Contributor may elect to distribute the Program (including its
+Contributions) under the new version. Except as expressly stated in Sections
+2(a) and 2(b) above, Recipient receives no rights or licenses to the
+intellectual property of any Contributor under this Agreement, whether
+expressly, by implication, estoppel or otherwise. All rights in the Program not
+expressly granted under this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and the
+intellectual property laws of the United States of America. No party to this
+Agreement will bring a legal action under this Agreement more than one year
+after the cause of action arose. Each party waives its rights to a jury trial in
+any resulting litigation.
+
+
+
+
+CUP
+
+CUP PARSER GENERATOR COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
+
+Copyright 1996 by Scott Hudson, Frank Flannery, C. Scott Ananian
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted,
+provided that the above copyright notice appear in all copies and that
+both the copyright notice and this permission notice and warranty
+disclaimer appear in supporting documentation, and that the names of
+the authors or their employers not be used in advertising or publicity
+pertaining to distribution of the software without specific, written
+prior permission.
+
+The authors and their employers disclaim all warranties with regard to
+this software, including all implied warranties of merchantability and
+fitness. In no event shall the authors or their employers be liable
+for any special, indirect or consequential damages or any damages
+whatsoever resulting from loss of use, data or profits, whether in an
+action of contract, negligence or other tortious action, arising out of
+or in connection with the use or performance of this software.
+
+
+
+EPL-1.0
+
+
+Eclipse Public License - v 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE
+("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES
+RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+a) in the case of the initial Contributor, the initial code and documentation
+distributed under this Agreement, and
+b) in the case of each subsequent Contributor:
+i) changes to the Program, and
+ii) additions to the Program;
+where such changes and/or additions to the Program originate from and are distributed
+by that particular Contributor. A Contribution `originates` from a Contributor if it
+was added to the Program by such Contributor itself or anyone acting on such
+Contributor`s behalf. Contributions do not include additions to the Program which: (i)
+are separate modules of software distributed in conjunction with the Program under
+their own license agreement, and (ii) are not derivative works of the Program.
+"Contributor" means any person or entity that distributes the Program.
+
+"Licensed Patents" mean patent claims licensable by a Contributor which are
+necessarily infringed by the use or sale of its Contribution alone or when combined
+with the Program.
+
+"Program" means the Contributions distributed in accordance with this Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement, including all
+Contributors.
+
+2. GRANT OF RIGHTS
+
+a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
+non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare
+derivative works of, publicly display, publicly perform, distribute and sublicense the
+Contribution of such Contributor, if any, and such derivative works, in source code
+and object code form.
+b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
+non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make,
+use, sell, offer to sell, import and otherwise transfer the Contribution of such
+Contributor, if any, in source code and object code form. This patent license shall
+apply to the combination of the Contribution and the Program if, at the time the
+Contribution is added by the Contributor, such addition of the Contribution causes
+such combination to be covered by the Licensed Patents. The patent license shall not
+apply to any other combinations which include the Contribution. No hardware per se is
+licensed hereunder.
+c) Recipient understands that although each Contributor grants the licenses to its
+Contributions set forth herein, no assurances are provided by any Contributor that the
+Program does not infringe the patent or other intellectual property rights of any
+other entity. Each Contributor disclaims any liability to Recipient for claims brought
+by any other entity based on infringement of intellectual property rights or
+otherwise. As a condition to exercising the rights and licenses granted hereunder,
+each Recipient hereby assumes sole responsibility to secure any other intellectual
+property rights needed, if any. For example, if a third party patent license is
+required to allow Recipient to distribute the Program, it is Recipient`s
+responsibility to acquire that license before distributing the Program.
+d) Each Contributor represents that to its knowledge it has sufficient copyright
+rights in its Contribution, if any, to grant the copyright license set forth in this
+Agreement.
+3. REQUIREMENTS
+
+A Contributor may choose to distribute the Program in object code form under its own
+license agreement, provided that:
+
+a) it complies with the terms and conditions of this Agreement; and
+b) its license agreement:
+i) effectively disclaims on behalf of all Contributors all warranties and conditions,
+express and implied, including warranties or conditions of title and non-infringement,
+and implied warranties or conditions of merchantability and fitness for a particular
+purpose;
+ii) effectively excludes on behalf of all Contributors all liability for damages,
+including direct, indirect, special, incidental and consequential damages, such as
+lost profits;
+iii) states that any provisions which differ from this Agreement are offered by that
+Contributor alone and not by any other party; and
+iv) states that source code for the Program is available from such Contributor, and
+informs licensees how to obtain it in a reasonable manner on or through a medium
+customarily used for software exchange.
+When the Program is made available in source code form:
+
+a) it must be made available under this Agreement; and
+b) a copy of this Agreement must be included with each copy of the Program.
+Contributors may not remove or alter any copyright notices contained within the
+Program.
+
+Each Contributor must identify itself as the originator of its Contribution, if any,
+in a manner that reasonably allows subsequent Recipients to identify the originator of
+the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities with respect
+to end users, business partners and the like. While this license is intended to
+facilitate the commercial use of the Program, the Contributor who includes the Program
+in a commercial product offering should do so in a manner which does not create
+potential liability for other Contributors. Therefore, if a Contributor includes the
+Program in a commercial product offering, such Contributor ("Commercial Contributor")
+hereby agrees to defend and indemnify every other Contributor ("Indemnified
+Contributor") against any losses, damages and costs (collectively "Losses") arising
+from claims, lawsuits and other legal actions brought by a third party against the
+Indemnified Contributor to the extent caused by the acts or omissions of such
+Commercial Contributor in connection with its distribution of the Program in a
+commercial product offering. The obligations in this section do not apply to any
+claims or Losses relating to any actual or alleged intellectual property infringement.
+In order to qualify, an Indemnified Contributor must: a) promptly notify the
+Commercial Contributor in writing of such claim, and b) allow the Commercial
+Contributor to control, and cooperate with the Commercial Contributor in, the defense
+and any related settlement negotiations. The Indemnified Contributor may participate
+in any such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial product offering,
+Product X. That Contributor is then a Commercial Contributor. If that Commercial
+Contributor then makes performance claims, or offers warranties related to Product X,
+those performance claims and warranties are such Commercial Contributor`s
+responsibility alone. Under this section, the Commercial Contributor would have to
+defend claims against the other Contributors related to those performance claims and
+warranties, and if a court requires any other Contributor to pay any damages as a
+result, the Commercial Contributor must pay those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS"
+BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED
+INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
+NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient
+is solely responsible for determining the appropriateness of using and distributing
+the Program and assumes all risks associated with its exercise of rights under this
+Agreement , including but not limited to the risks and costs of program errors,
+compliance with applicable laws, damage to or loss of data, programs or equipment, and
+unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
+CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS),
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR
+DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under applicable law,
+it shall not affect the validity or enforceability of the remainder of the terms of
+this Agreement, and without further action by the parties hereto, such provision shall
+be reformed to the minimum extent necessary to make such provision valid and
+enforceable.
+
+If Recipient institutes patent litigation against any entity (including a cross-claim
+or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations
+of the Program with other software or hardware) infringes such Recipient`s patent(s),
+then such Recipient`s rights granted under Section 2(b) shall terminate as of the date
+such litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it fails to comply with
+any of the material terms or conditions of this Agreement and does not cure such
+failure in a reasonable period of time after becoming aware of such noncompliance. If
+all Recipient`s rights under this Agreement terminate, Recipient agrees to cease use
+and distribution of the Program as soon as reasonably practicable. However,
+Recipient`s obligations under this Agreement and any licenses granted by Recipient
+relating to the Program shall continue and survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement, but in order to
+avoid inconsistency the Agreement is copyrighted and may only be modified in the
+following manner. The Agreement Steward reserves the right to publish new versions
+(including revisions) of this Agreement from time to time. No one other than the
+Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is
+the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to
+serve as the Agreement Steward to a suitable separate entity. Each new version of the
+Agreement will be given a distinguishing version number. The Program (including
+Contributions) may always be distributed subject to the version of the Agreement under
+which it was received. In addition, after a new version of the Agreement is published,
+Contributor may elect to distribute the Program (including its Contributions) under
+the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
+receives no rights or licenses to the intellectual property of any Contributor under
+this Agreement, whether expressly, by implication, estoppel or otherwise. All rights
+in the Program not expressly granted under this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and the intellectual
+property laws of the United States of America. No party to this Agreement will bring a
+legal action under this Agreement more than one year after the cause of action arose.
+Each party waives its rights to a jury trial in any resulting litigation.
+
+
+
+
+Elfutils-Exception
+
+ This file describes the limits of the Exception under which you are allowed
+ to distribute Non-GPL Code in linked combination with Red Hat elfutils.
+ For the full text of the license, please see one of the header files
+ included with the source distribution or the file COPYING found in the
+ top level directory of the source.
+
+ The Approved Interfaces are the functions declared in the files:
+
+ libelf.h
+ libdw.h
+ libdwfl.h
+
+
+
+
+FSF-Unlimited
+
+Copyright (C) 1997-2010 Free Software Foundation, Inc.
+This file is free software; the Free Software Foundation
+gives unlimited permission to copy and/or distribute it,
+with or without modifications, as long as this notice is preserved.
+
+
+
+FreeType
+
+ The FreeType Project LICENSE
+ ----------------------------
+
+ 2006-Jan-27
+
+ Copyright 1996-2002, 2006 by
+ David Turner, Robert Wilhelm, and Werner Lemberg
+
+
+
+Introduction
+============
+
+ The FreeType Project is distributed in several archive packages;
+ some of them may contain, in addition to the FreeType font engine,
+ various tools and contributions which rely on, or relate to, the
+ FreeType Project.
+
+ This license applies to all files found in such packages, and
+ which do not fall under their own explicit license. The license
+ affects thus the FreeType font engine, the test programs,
+ documentation and makefiles, at the very least.
+
+ This license was inspired by the BSD, Artistic, and IJG
+ (Independent JPEG Group) licenses, which all encourage inclusion
+ and use of free software in commercial and freeware products
+ alike. As a consequence, its main points are that:
+
+ o We don't promise that this software works. However, we will be
+ interested in any kind of bug reports. (`as is' distribution)
+
+ o You can use this software for whatever you want, in parts or
+ full form, without having to pay us. (`royalty-free' usage)
+
+ o You may not pretend that you wrote this software. If you use
+ it, or only parts of it, in a program, you must acknowledge
+ somewhere in your documentation that you have used the
+ FreeType code. (`credits')
+
+ We specifically permit and encourage the inclusion of this
+ software, with or without modifications, in commercial products.
+ We disclaim all warranties covering The FreeType Project and
+ assume no liability related to The FreeType Project.
+
+
+ Finally, many people asked us for a preferred form for a
+ credit/disclaimer to use in compliance with this license. We thus
+ encourage you to use the following text:
+
+ """
+ Portions of this software are copyright � <year> The FreeType
+ Project (www.freetype.org). All rights reserved.
+ """
+
+ Please replace <year> with the value from the FreeType version you
+ actually use.
+
+
+Legal Terms
+===========
+
+0. Definitions
+--------------
+
+ Throughout this license, the terms `package', `FreeType Project',
+ and `FreeType archive' refer to the set of files originally
+ distributed by the authors (David Turner, Robert Wilhelm, and
+ Werner Lemberg) as the `FreeType Project', be they named as alpha,
+ beta or final release.
+
+ `You' refers to the licensee, or person using the project, where
+ `using' is a generic term including compiling the project's source
+ code as well as linking it to form a `program' or `executable'.
+ This program is referred to as `a program using the FreeType
+ engine'.
+
+ This license applies to all files distributed in the original
+ FreeType Project, including all source code, binaries and
+ documentation, unless otherwise stated in the file in its
+ original, unmodified form as distributed in the original archive.
+ If you are unsure whether or not a particular file is covered by
+ this license, you must contact us to verify this.
+
+ The FreeType Project is copyright (C) 1996-2000 by David Turner,
+ Robert Wilhelm, and Werner Lemberg. All rights reserved except as
+ specified below.
+
+1. No Warranty
+--------------
+
+ THE FREETYPE PROJECT IS PROVIDED `AS IS' WITHOUT WARRANTY OF ANY
+ KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+ WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE. IN NO EVENT WILL ANY OF THE AUTHORS OR COPYRIGHT HOLDERS
+ BE LIABLE FOR ANY DAMAGES CAUSED BY THE USE OR THE INABILITY TO
+ USE, OF THE FREETYPE PROJECT.
+
+2. Redistribution
+-----------------
+
+ This license grants a worldwide, royalty-free, perpetual and
+ irrevocable right and license to use, execute, perform, compile,
+ display, copy, create derivative works of, distribute and
+ sublicense the FreeType Project (in both source and object code
+ forms) and derivative works thereof for any purpose; and to
+ authorize others to exercise some or all of the rights granted
+ herein, subject to the following conditions:
+
+ o Redistribution of source code must retain this license file
+ (`FTL.TXT') unaltered; any additions, deletions or changes to
+ the original files must be clearly indicated in accompanying
+ documentation. The copyright notices of the unaltered,
+ original files must be preserved in all copies of source
+ files.
+
+ o Redistribution in binary form must provide a disclaimer that
+ states that the software is based in part of the work of the
+ FreeType Team, in the distribution documentation. We also
+ encourage you to put an URL to the FreeType web page in your
+ documentation, though this isn't mandatory.
+
+ These conditions apply to any software derived from or based on
+ the FreeType Project, not just the unmodified files. If you use
+ our work, you must acknowledge us. However, no fee need be paid
+ to us.
+
+3. Advertising
+--------------
+
+ Neither the FreeType authors and contributors nor you shall use
+ the name of the other for commercial, advertising, or promotional
+ purposes without specific prior written permission.
+
+ We suggest, but do not require, that you use one or more of the
+ following phrases to refer to this software in your documentation
+ or advertising materials: `FreeType Project', `FreeType Engine',
+ `FreeType library', or `FreeType Distribution'.
+
+ As you have not signed this license, you are not required to
+ accept it. However, as the FreeType Project is copyrighted
+ material, only this license, or another one contracted with the
+ authors, grants you the right to use, distribute, and modify it.
+ Therefore, by using, distributing, or modifying the FreeType
+ Project, you indicate that you understand and accept all the terms
+ of this license.
+
+4. Contacts
+-----------
+
+ There are two mailing lists related to FreeType:
+
+ o freetype@nongnu.org
+
+ Discusses general use and applications of FreeType, as well as
+ future and wanted additions to the library and distribution.
+ If you are looking for support, start in this list if you
+ haven't found anything to help you in the documentation.
+
+ o freetype-devel@nongnu.org
+
+ Discusses bugs, as well as engine internals, design issues,
+ specific licenses, porting, etc.
+
+ Our home page can be found at
+
+ http://www.freetype.org
+
+
+--- end of FTL.TXT ---
+
+
+
+
+GPL-1.0
+
+
+GNU General Public License, version 1
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 1, February 1989
+
+ Copyright (C) 1989 Free Software Foundation, Inc.
+ 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The license agreements of most software companies try to keep users
+at the mercy of those companies. By contrast, our General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. The
+General Public License applies to the Free Software Foundation`s
+software and to any other program whose authors commit to using it.
+You can use it for your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Specifically, the General Public License is designed to make
+sure that you have the freedom to give away or sell copies of free
+software, that you receive source code or can get it if you want it,
+that you can change the software or use pieces of it in new free
+programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of a such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author`s protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors` reputations.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any program or other work which
+contains a notice placed by the copyright holder saying it may be
+distributed under the terms of this General Public License. The
+"Program", below, refers to any such program or work, and a "work based
+on the Program" means either the Program or any work containing the
+Program or a portion of it, either verbatim or with modifications. Each
+licensee is addressed as "you".
+
+ 1. You may copy and distribute verbatim copies of the Program`s source
+code as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice and
+disclaimer of warranty; keep intact all the notices that refer to this
+General Public License and to the absence of any warranty; and give any
+other recipients of the Program a copy of this General Public License
+along with the Program. You may charge a fee for the physical act of
+transferring a copy.
+
+ 2. You may modify your copy or copies of the Program or any portion of
+it, and copy and distribute such modifications under the terms of Paragraph
+1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating that
+ you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish, that
+ in whole or in part contains the Program or any part thereof, either
+ with or without modifications, to be licensed at no charge to all
+ third parties under the terms of this General Public License (except
+ that you may choose to grant warranty protection to some or all
+ third parties, at your option).
+
+ c) If the modified program normally reads commands interactively when
+ run, you must cause it, when started running for such interactive use
+ in the simplest and most usual way, to print or display an
+ announcement including an appropriate copyright notice and a notice
+ that there is no warranty (or else, saying that you provide a
+ warranty) and that users may redistribute the program under these
+ conditions, and telling the user how to view a copy of this General
+ Public License.
+
+ d) You may charge a fee for the physical act of transferring a
+ copy, and you may at your option offer warranty protection in
+ exchange for a fee.
+
+Mere aggregation of another independent work with the Program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other work under the scope of these terms.
+
+ 3. You may copy and distribute the Program (or a portion or derivative of
+it, under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+ a) accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal charge
+ for the cost of distribution) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+Source code for a work means the preferred form of the work for making
+modifications to it. For an executable file, complete source code means
+all the source code for all modules it contains; but, as a special
+exception, it need not include source code for modules which are standard
+libraries that accompany the operating system on which the executable
+file runs, or for standard header files or definitions files that
+accompany that operating system.
+
+ 4. You may not copy, modify, sublicense, distribute or transfer the
+Program except as expressly provided under this General Public License.
+Any attempt otherwise to copy, modify, sublicense, distribute or transfer
+the Program is void, and will automatically terminate your rights to use
+the Program under this License. However, parties who have received
+copies, or rights to use copies, from you under this General Public
+License will not have their licenses terminated so long as such parties
+remain in full compliance.
+
+ 5. By copying, distributing or modifying the Program (or any work based
+on the Program) you indicate your acceptance of this license to do so,
+and all its terms and conditions.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the original
+licensor to copy, distribute or modify the Program subject to these
+terms and conditions. You may not impose any further restrictions on the
+recipients` exercise of the rights granted herein.
+
+ 7. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of the license which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+the license, you may choose any version ever published by the Free Software
+Foundation.
+
+ 8. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ 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
+the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program`s name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 1, or (at your option)
+ any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19xx name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w`.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c` for details.
+
+The hypothetical commands `show w` and `show c` should show the
+appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than `show w` and `show
+c`; they could even be mouse-clicks or menu items--whatever suits your
+program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ program `Gnomovision` (a program to direct compilers to make passes
+ at assemblers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+That`s all there is to it!
+
+
+
+
+GPL-2.0
+
+
+GNU GENERAL PUBLIC LICENSE
+
+Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public License is intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users. This General Public License applies to most of the Free Software
+Foundation`s software and to any other program whose authors commit to using it. (Some
+other Free Software Foundation software is covered by the GNU Lesser General Public
+License instead.) You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for this service if you wish), that you receive
+source code or can get it if you want it, that you can change the software or use
+pieces of it in new free programs; and that you know you can do these things.
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you
+these rights or to ask you to surrender the rights. These restrictions translate to
+certain responsibilities for you if you distribute copies of the software, or if you
+modify it.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee,
+you must give the recipients all the rights that you have. You must make sure that
+they, too, receive or can get the source code. And you must show them these terms so
+they know their rights.
+
+We protect your rights with two steps: (1) copyright the software, and (2) offer you
+this license which gives you legal permission to copy, distribute and/or modify the
+software.
+
+Also, for each author`s protection and ours, we want to make certain that everyone
+understands that there is no warranty for this free software. If the software is
+modified by someone else and passed on, we want its recipients to know that what they
+have is not the original, so that any problems introduced by others will not reflect
+on the original authors` reputations.
+
+Finally, any free program is threatened constantly by software patents. We wish to
+avoid the danger that redistributors of a free program will individually obtain patent
+licenses, in effect making the program proprietary. To prevent this, we have made it
+clear that any patent must be licensed for everyone`s free use or not licensed at all.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License applies to any program or other work which contains a notice placed by
+the copyright holder saying it may be distributed under the terms of this General
+Public License. The "Program", below, refers to any such program or work, and a "work
+based on the Program" means either the Program or any derivative work under copyright
+law: that is to say, a work containing the Program or a portion of it, either verbatim
+or with modifications and/or translated into another language. (Hereinafter,
+translation is included without limitation in the term "modification".) Each licensee
+is addressed as "you".
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running the Program is not restricted,
+and the output from the Program is covered only if its contents constitute a work
+based on the Program (independent of having been made by running the Program). Whether
+that is true depends on what the Program does.
+
+1. You may copy and distribute verbatim copies of the Program`s source code as you
+receive it, in any medium, provided that you conspicuously and appropriately publish
+on each copy an appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any warranty; and
+give any other recipients of the Program a copy of this License along with the
+Program.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Program or any portion of it, thus
+forming a work based on the Program, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+a) You must cause the modified files to carry prominent notices stating that you
+changed the files and the date of any change.
+b) You must cause any work that you distribute or publish, that in whole or in part
+contains or is derived from the Program or any part thereof, to be licensed as a whole
+at no charge to all third parties under the terms of this License.
+c) If the modified program normally reads commands interactively when run, you must
+cause it, when started running for such interactive use in the most ordinary way, to
+print or display an announcement including an appropriate copyright notice and a
+notice that there is no warranty (or else, saying that you provide a warranty) and
+that users may redistribute the program under these conditions, and telling the user
+how to view a copy of this License. (Exception: if the Program itself is interactive
+but does not normally print such an announcement, your work based on the Program is
+not required to print an announcement.)
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Program, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Program,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program with the
+Program (or with a work based on the Program) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+3. You may copy and distribute the Program (or a work based on it, under Section 2) in
+object code or executable form under the terms of Sections 1 and 2 above provided that
+you also do one of the following:
+
+a) Accompany it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a medium customarily
+used for software interchange; or,
+b) Accompany it with a written offer, valid for at least three years, to give any
+third party, for a charge no more than your cost of physically performing source
+distribution, a complete machine-readable copy of the corresponding source code, to be
+distributed under the terms of Sections 1 and 2 above on a medium customarily used for
+software interchange; or,
+c) Accompany it with the information you received as to the offer to distribute
+corresponding source code. (This alternative is allowed only for noncommercial
+distribution and only if you received the program in object code or executable form
+with such an offer, in accord with Subsection b above.)
+The source code for a work means the preferred form of the work for making
+modifications to it. For an executable work, complete source code means all the source
+code for all modules it contains, plus any associated interface definition files, plus
+the scripts used to control compilation and installation of the executable. However,
+as a special exception, the source code distributed need not include anything that is
+normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+If distribution of executable or object code is made by offering access to copy from a
+designated place, then offering equivalent access to copy the source code from the
+same place counts as distribution of the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+4. You may not copy, modify, sublicense, or distribute the Program except as expressly
+provided under this License. Any attempt otherwise to copy, modify, sublicense or
+distribute the Program is void, and will automatically terminate your rights under
+this License. However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such parties remain in
+full compliance.
+
+5. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Program or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Program or works based on it.
+
+6. Each time you redistribute the Program (or any work based on the Program), the
+recipient automatically receives a license from the original licensor to copy,
+distribute or modify the Program subject to these terms and conditions. You may not
+impose any further restrictions on the recipients` exercise of the rights granted
+herein. You are not responsible for enforcing compliance by third parties to this
+License.
+
+7. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Program at all. For example, if a patent license would not permit royalty-free
+redistribution of the Program by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply and the section as a
+whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system,
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+8. If the distribution and/or use of the Program is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Program under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+9. The Free Software Foundation may publish revised and/or new versions of the General
+Public License from time to time. Such new versions will be similar in spirit to the
+present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Program does not
+specify a version number of this License, you may choose any version ever published by
+the Free Software Foundation.
+
+10. If you wish to incorporate parts of the Program into other free programs whose
+distribution conditions are different, write to the author to ask for permission. For
+software which is copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our decision will be
+guided by the two goals of preserving the free status of all derivatives of our free
+software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
+WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+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 the "copyright" line and a pointer to where the
+full notice is found.
+
+one line to give the program`s name and an idea of what it does.
+Copyright (C) yyyy name of author
+
+This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License
+as published by the Free Software Foundation; either version 2
+of the License, or (at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this when it starts
+in an interactive mode:
+
+Gnomovision version 69, Copyright (C) year name of author
+Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
+type `show w`. This is free software, and you are welcome
+to redistribute it under certain conditions; type `show c`
+for details.
+The hypothetical commands `show w` and `show c` should show the appropriate parts of
+the General Public License. Of course, the commands you use may be called something
+other than `show w` and `show c`; they could even be mouse-clicks or menu
+items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample;
+alter the names:
+
+Yoyodyne, Inc., hereby disclaims all copyright
+interest in the program `Gnomovision`
+(which makes passes at compilers) written
+by James Hacker.
+
+signature of Ty Coon, 1 April 1989
+Ty Coon, President of Vice
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may consider it
+more useful to permit linking proprietary applications with the library. If this is
+what you want to do, use the GNU Lesser General Public License instead of this
+License.
+
+
+
+
+GPL-2.0-with-GCC-exception
+
+
+insert GPL v2 text here
+
+GCC Linking Exception
+In addition to the permissions in the GNU General Public License, the Free
+Software Foundation gives you unlimited permission to link the compiled version
+of this file into combinations with other programs, and to distribute those
+combinations without any restriction coming from the use of this file. (The
+General Public License restrictions do apply in other respects; for example,
+they cover modification of the file, and distribution when not linked into a
+combine executable.)
+
+
+
+
+
+
+
+
+
+GPL-2.0-with-classpath-exception
+
+
+insert GPL v2 license text here
+
+Linking this library statically or dynamically with other modules is making a combined
+work based on this library. Thus, the terms and conditions of the GNU General Public
+License cover the whole combination.
+
+As a special exception, the copyright holders of this library give you permission to
+link this library with independent modules to produce an executable, regardless of the
+license terms of these independent modules, and to copy and distribute the resulting
+executable under terms of your choice, provided that you also meet, for each linked
+independent module, the terms and conditions of the license of that module. An
+independent module is a module which is not derived from or based on this library. If
+you modify this library, you may extend this exception to your version of the library,
+but you are not obligated to do so. If you do not wish to do so, delete this exception
+statement from your version.
+
+
+
+
+GPL-3.0
+
+GNU GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+Preamble
+
+The GNU General Public License is a free, copyleft license for software and other
+kinds of works.
+
+The licenses for most software and other practical works are designed to take away
+your freedom to share and change the works. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change all versions of a
+program--to make sure it remains free software for all its users. We, the Free
+Software Foundation, use the GNU General Public License for most of our software; it
+applies also to any other work released this way by its authors. You can apply it to
+your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for them if you wish), that you receive source
+code or can get it if you want it, that you can change the software or use pieces of
+it in new free programs, and that you know you can do these things.
+
+To protect your rights, we need to prevent others from denying you these rights or
+asking you to surrender the rights. Therefore, you have certain responsibilities if
+you distribute copies of the software, or if you modify it: responsibilities to
+respect the freedom of others.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee,
+you must pass on to the recipients the same freedoms that you received. You must make
+sure that they, too, receive or can get the source code. And you must show them these
+terms so they know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps: (1) assert
+copyright on the software, and (2) offer you this License giving you legal permission
+to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains that there is no
+warranty for this free software. For both users' and authors' sake, the GPL requires
+that modified versions be marked as changed, so that their problems will not be
+attributed erroneously to authors of previous versions.
+
+Some devices are designed to deny users access to install or run modified versions of
+the software inside them, although the manufacturer can do so. This is fundamentally
+incompatible with the aim of protecting users' freedom to change the software. The
+systematic pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we have designed
+this version of the GPL to prohibit the practice for those products. If such problems
+arise substantially in other domains, we stand ready to extend this provision to those
+domains in future versions of the GPL, as needed to protect the freedom of users.
+
+Finally, every program is threatened constantly by software patents. States should not
+allow patents to restrict development and use of software on general-purpose
+computers, but in those that do, we wish to avoid the special danger that patents
+applied to a free program could make it effectively proprietary. To prevent this, the
+GPL assures that patents cannot be used to render the program non-free.
+
+The precise terms and conditions for copying, distribution and modification follow.
+TERMS AND CONDITIONS
+0. Definitions.
+
+”This License” refers to version 3 of the GNU General Public License.
+
+”Copyright” also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+”The Program” refers to any copyrightable work licensed under this
+License. Each licensee is addressed as ”you”. ”Licensees”
+and ”recipients” may be individuals or organizations.
+
+To ”modify” a work means to copy from or adapt all or part of the work in
+a fashion requiring copyright permission, other than the making of an exact copy. The
+resulting work is called a ”modified version” of the earlier work or a
+work ”based on” the earlier work.
+
+A ”covered work” means either the unmodified Program or a work based on
+the Program.
+
+To ”propagate” a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for infringement under
+applicable copyright law, except executing it on a computer or modifying a private
+copy. Propagation includes copying, distribution (with or without modification),
+making available to the public, and in some countries other activities as well.
+
+To ”convey” a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through a computer
+network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays ”Appropriate Legal Notices” to the
+extent that it includes a convenient and prominently visible feature that (1) displays
+an appropriate copyright notice, and (2) tells the user that there is no warranty for
+the work (except to the extent that warranties are provided), that licensees may
+convey the work under this License, and how to view a copy of this License. If the
+interface presents a list of user commands or options, such as a menu, a prominent
+item in the list meets this criterion.
+1. Source Code.
+
+The ”source code” for a work means the preferred form of the work for
+making modifications to it. ”Object code” means any non-source form of a
+work.
+
+A ”Standard Interface” means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of interfaces
+specified for a particular programming language, one that is widely used among
+developers working in that language.
+
+The ”System Libraries” of an executable work include anything, other than
+the work as a whole, that (a) is included in the normal form of packaging a Major
+Component, but which is not part of that Major Component, and (b) serves only to
+enable use of the work with that Major Component, or to implement a Standard Interface
+for which an implementation is available to the public in source code form. A
+”Major Component”, in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system (if any) on which
+the executable work runs, or a compiler used to produce the work, or an object code
+interpreter used to run it.
+
+The ”Corresponding Source” for a work in object code form means all the
+source code needed to generate, install, and (for an executable work) run the object
+code and to modify the work, including scripts to control those activities. However,
+it does not include the work's System Libraries, or general-purpose tools or generally
+available free programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source includes interface
+definition files associated with source files for the work, and the source code for
+shared libraries and dynamically linked subprograms that the work is specifically
+designed to require, such as by intimate data communication or control flow between
+those subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate
+automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+2. Basic Permissions.
+
+All rights granted under this License are granted for the term of copyright on the
+Program, and are irrevocable provided the stated conditions are met. This License
+explicitly affirms your unlimited permission to run the unmodified Program. The output
+from running a covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your rights of fair use
+or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without
+conditions so long as your license otherwise remains in force. You may convey covered
+works to others for the sole purpose of having them make modifications exclusively for
+you, or provide you with facilities for running those works, provided that you comply
+with the terms of this License in conveying all material for which you do not control
+copyright. Those thus making or running the covered works for you must do so
+exclusively on your behalf, under your direction and control, on terms that prohibit
+them from making any copies of your copyrighted material outside their relationship
+with you.
+
+Conveying under any other circumstances is permitted solely under the conditions
+stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological measure under any
+applicable law fulfilling obligations under article 11 of the WIPO copyright treaty
+adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention
+of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of
+technological measures to the extent such circumvention is effected by exercising
+rights under this License with respect to the covered work, and you disclaim any
+intention to limit operation or modification of the work as a means of enforcing,
+against the work's users, your or third parties' legal rights to forbid circumvention
+of technological measures.
+4. Conveying Verbatim Copies.
+
+You may convey verbatim copies of the Program's source code as you receive it, in any
+medium, provided that you conspicuously and appropriately publish on each copy an
+appropriate copyright notice; keep intact all notices stating that this License and
+any non-permissive terms added in accord with section 7 apply to the code; keep intact
+all notices of the absence of any warranty; and give all recipients a copy of this
+License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer
+support or warranty protection for a fee.
+5. Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to produce it from
+the Program, in the form of source code under the terms of section 4, provided that
+you also meet all of these conditions:
+
+ * a) The work must carry prominent notices stating that you modified it, and
+giving a relevant date.
+ * b) The work must carry prominent notices stating that it is released under this
+License and any conditions added under section 7. This requirement modifies the
+requirement in section 4 to ”keep intact all notices”.
+ * c) You must license the entire work, as a whole, under this License to anyone
+who comes into possession of a copy. This License will therefore apply, along with any
+applicable section 7 additional terms, to the whole of the work, and all its parts,
+regardless of how they are packaged. This License gives no permission to license the
+work in any other way, but it does not invalidate such permission if you have
+separately received it.
+ * d) If the work has interactive user interfaces, each must display Appropriate
+Legal Notices; however, if the Program has interactive interfaces that do not display
+Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are
+not by their nature extensions of the covered work, and which are not combined with it
+such as to form a larger program, in or on a volume of a storage or distribution
+medium, is called an ”aggregate” if the compilation and its resulting
+copyright are not used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work in an aggregate
+does not cause this License to apply to the other parts of the aggregate.
+6. Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms of sections 4 and 5,
+provided that you also convey the machine-readable Corresponding Source under the
+terms of this License, in one of these ways:
+
+ * a) Convey the object code in, or embodied in, a physical product (including a
+physical distribution medium), accompanied by the Corresponding Source fixed on a
+durable physical medium customarily used for software interchange.
+ * b) Convey the object code in, or embodied in, a physical product (including a
+physical distribution medium), accompanied by a written offer, valid for at least
+three years and valid for as long as you offer spare parts or customer support for
+that product model, to give anyone who possesses the object code either (1) a copy of
+the Corresponding Source for all the software in the product that is covered by this
+License, on a durable physical medium customarily used for software interchange, for a
+price no more than your reasonable cost of physically performing this conveying of
+source, or (2) access to copy the Corresponding Source from a network server at no
+charge.
+ * c) Convey individual copies of the object code with a copy of the written offer
+to provide the Corresponding Source. This alternative is allowed only occasionally and
+noncommercially, and only if you received the object code with such an offer, in
+accord with subsection 6b.
+ * d) Convey the object code by offering access from a designated place (gratis or
+for a charge), and offer equivalent access to the Corresponding Source in the same way
+through the same place at no further charge. You need not require recipients to copy
+the Corresponding Source along with the object code. If the place to copy the object
+code is a network server, the Corresponding Source may be on a different server
+(operated by you or a third party) that supports equivalent copying facilities,
+provided you maintain clear directions next to the object code saying where to find
+the Corresponding Source. Regardless of what server hosts the Corresponding Source,
+you remain obligated to ensure that it is available for as long as needed to satisfy
+these requirements.
+ * e) Convey the object code using peer-to-peer transmission, provided you inform
+other peers where the object code and Corresponding Source of the work are being
+offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the
+Corresponding Source as a System Library, need not be included in conveying the object
+code work.
+
+A ”User Product” is either (1) a ”consumer product”, which
+means any tangible personal property which is normally used for personal, family, or
+household purposes, or (2) anything designed or sold for incorporation into a
+dwelling. In determining whether a product is a consumer product, doubtful cases shall
+be resolved in favor of coverage. For a particular product received by a particular
+user, ”normally used” refers to a typical or common use of that class of
+product, regardless of the status of the particular user or of the way in which the
+particular user actually uses, or expects or is expected to use, the product. A
+product is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent the only
+significant mode of use of the product.
+
+”Installation Information” for a User Product means any methods,
+procedures, authorization keys, or other information required to install and execute
+modified versions of a covered work in that User Product from a modified version of
+its Corresponding Source. The information must suffice to ensure that the continued
+functioning of the modified object code is in no case prevented or interfered with
+solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for
+use in, a User Product, and the conveying occurs as part of a transaction in which the
+right of possession and use of the User Product is transferred to the recipient in
+perpetuity or for a fixed term (regardless of how the transaction is characterized),
+the Corresponding Source conveyed under this section must be accompanied by the
+Installation Information. But this requirement does not apply if neither you nor any
+third party retains the ability to install modified object code on the User Product
+(for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to
+continue to provide support service, warranty, or updates for a work that has been
+modified or installed by the recipient, or for the User Product in which it has been
+modified or installed. Access to a network may be denied when the modification itself
+materially and adversely affects the operation of the network or violates the rules
+and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with
+this section must be in a format that is publicly documented (and with an
+implementation available to the public in source code form), and must require no
+special password or key for unpacking, reading or copying.
+7. Additional Terms.
+
+”Additional permissions” are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions. Additional
+permissions that are applicable to the entire Program shall be treated as though they
+were included in this License, to the extent that they are valid under applicable law.
+If additional permissions apply only to part of the Program, that part may be used
+separately under those permissions, but the entire Program remains governed by this
+License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional
+permissions from that copy, or from any part of it. (Additional permissions may be
+written to require their own removal in certain cases when you modify the work.) You
+may place additional permissions on material, added by you to a covered work, for
+which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered
+work, you may (if authorized by the copyright holders of that material) supplement the
+terms of this License with terms:
+
+ * a) Disclaiming warranty or limiting liability differently from the terms of
+sections 15 and 16 of this License; or
+ * b) Requiring preservation of specified reasonable legal notices or author
+attributions in that material or in the Appropriate Legal Notices displayed by works
+containing it; or
+ * c) Prohibiting misrepresentation of the origin of that material, or requiring
+that modified versions of such material be marked in reasonable ways as different from
+the original version; or
+ * d) Limiting the use for publicity purposes of names of licensors or authors of
+the material; or
+ * e) Declining to grant rights under trademark law for use of some trade names,
+trademarks, or service marks; or
+ * f) Requiring indemnification of licensors and authors of that material by anyone
+who conveys the material (or modified versions of it) with contractual assumptions of
+liability to the recipient, for any liability that these contractual assumptions
+directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered ”further
+restrictions” within the meaning of section 10. If the Program as you received
+it, or any part of it, contains a notice stating that it is governed by this License
+along with a term that is a further restriction, you may remove that term. If a
+license document contains a further restriction but permits relicensing or conveying
+under this License, you may add to a covered work material governed by the terms of
+that license document, provided that the further restriction does not survive such
+relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the
+relevant source files, a statement of the additional terms that apply to those files,
+or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a
+separately written license, or stated as exceptions; the above requirements apply
+either way.
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this
+License. Any attempt otherwise to propagate or modify it is void, and will
+automatically terminate your rights under this License (including any patent licenses
+granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a
+particular copyright holder is reinstated (a) provisionally, unless and until the
+copyright holder explicitly and finally terminates your license, and (b) permanently,
+if the copyright holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if
+the copyright holder notifies you of the violation by some reasonable means, this is
+the first time you have received notice of violation of this License (for any work)
+from that copyright holder, and you cure the violation prior to 30 days after your
+receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of
+parties who have received copies or rights from you under this License. If your rights
+have been terminated and not permanently reinstated, you do not qualify to receive new
+licenses for the same material under section 10.
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the
+Program. Ancillary propagation of a covered work occurring solely as a consequence of
+using peer-to-peer transmission to receive a copy likewise does not require
+acceptance. However, nothing other than this License grants you permission to
+propagate or modify any covered work. These actions infringe copyright if you do not
+accept this License. Therefore, by modifying or propagating a covered work, you
+indicate your acceptance of this License to do so.
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license
+from the original licensors, to run, modify and propagate that work, subject to this
+License. You are not responsible for enforcing compliance by third parties with this
+License.
+
+An ”entity transaction” is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an organization, or
+merging organizations. If propagation of a covered work results from an entity
+transaction, each party to that transaction who receives a copy of the work also
+receives whatever licenses to the work the party's predecessor in interest had or
+could give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if the predecessor
+has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or
+affirmed under this License. For example, you may not impose a license fee, royalty,
+or other charge for exercise of rights granted under this License, and you may not
+initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging
+that any patent claim is infringed by making, using, selling, offering for sale, or
+importing the Program or any portion of it.
+11. Patents.
+
+A ”contributor” is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The work thus licensed
+is called the contributor's ”contributor version”.
+
+A contributor's ”essential patent claims” are all patent claims owned or
+controlled by the contributor, whether already acquired or hereafter acquired, that
+would be infringed by some manner, permitted by this License, of making, using, or
+selling its contributor version, but do not include claims that would be infringed
+only as a consequence of further modification of the contributor version. For purposes
+of this definition, ”control” includes the right to grant patent
+sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license
+under the contributor's essential patent claims, to make, use, sell, offer for sale,
+import and otherwise run, modify and propagate the contents of its contributor
+version.
+
+In the following three paragraphs, a ”patent license” is any express
+agreement or commitment, however denominated, not to enforce a patent (such as an
+express permission to practice a patent or covenant not to sue for patent
+infringement). To ”grant” such a patent license to a party means to make
+such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the
+Corresponding Source of the work is not available for anyone to copy, free of charge
+and under the terms of this License, through a publicly available network server or
+other readily accessible means, then you must either (1) cause the Corresponding
+Source to be so available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner consistent with
+the requirements of this License, to extend the patent license to downstream
+recipients. ”Knowingly relying” means you have actual knowledge that, but
+for the patent license, your conveying the covered work in a country, or your
+recipient's use of the covered work in a country, would infringe one or more
+identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey,
+or propagate by procuring conveyance of, a covered work, and grant a patent license to
+some of the parties receiving the covered work authorizing them to use, propagate,
+modify or convey a specific copy of the covered work, then the patent license you
+grant is automatically extended to all recipients of the covered work and works based
+on it.
+
+A patent license is ”discriminatory” if it does not include within the
+scope of its coverage, prohibits the exercise of, or is conditioned on the
+non-exercise of one or more of the rights that are specifically granted under this
+License. You may not convey a covered work if you are a party to an arrangement with a
+third party that is in the business of distributing software, under which you make
+payment to the third party based on the extent of your activity of conveying the work,
+and under which the third party grants, to any of the parties who would receive the
+covered work from you, a discriminatory patent license (a) in connection with copies
+of the covered work conveyed by you (or copies made from those copies), or (b)
+primarily for and in connection with specific products or compilations that contain
+the covered work, unless you entered into that arrangement, or that patent license was
+granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied
+license or other defenses to infringement that may otherwise be available to you under
+applicable patent law.
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that
+contradict the conditions of this License, they do not excuse you from the conditions
+of this License. If you cannot convey a covered work so as to satisfy simultaneously
+your obligations under this License and any other pertinent obligations, then as a
+consequence you may not convey it at all. For example, if you agree to terms that
+obligate you to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this License would be
+to refrain entirely from conveying the Program.
+13. Use with the GNU Affero General Public License.
+
+Notwithstanding any other provision of this License, you have permission to link or
+combine any covered work with a work licensed under version 3 of the GNU Affero
+General Public License into a single combined work, and to convey the resulting work.
+The terms of this License will continue to apply to the part which is the covered
+work, but the special requirements of the GNU Affero General Public License, section
+13, concerning interaction through a network will apply to the combination as such.
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies that a
+certain numbered version of the GNU General Public License ”or any later
+version” applies to it, you have the option of following the terms and
+conditions either of that numbered version or of any later version published by the
+Free Software Foundation. If the Program does not specify a version number of the GNU
+General Public License, you may choose any version ever published by the Free Software
+Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU
+General Public License can be used, that proxy's public statement of acceptance of a
+version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions. However, no
+additional obligations are imposed on any author or copyright holder as a result of
+your choosing to follow a later version.
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM ”AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
+EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
+QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
+DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
+WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be
+given local legal effect according to their terms, reviewing courts shall apply local
+law that most closely approximates an absolute waiver of all civil liability in
+connection with the Program, unless a warranty or assumption of liability accompanies
+a copy of the Program in return for a fee.
+
+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 the ”copyright” line and a pointer to
+where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program does terminal interaction, make it output a short notice like this when
+it starts in an interactive mode:
+
+ <program> Copyright (C) <year> <name of author>
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate parts of
+the General Public License. Of course, your program's commands might be different; for
+a GUI interface, you would use an ”about box”.
+
+You should also get your employer (if you work as a programmer) or school, if any, to
+sign a ”copyright disclaimer” for the program, if necessary. For more
+information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+The GNU General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may consider it
+more useful to permit linking proprietary applications with the library. If this is
+what you want to do, use the GNU Lesser General Public License instead of this
+License. But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
+
+
+
+GPL-3.0-with-GCC-exception
+
+
+insert GPL v3 text here
+
+GCC RUNTIME LIBRARY EXCEPTION
+Version 3.1, 31 March 2009
+
+General information:
+http://www.gnu.org/licenses/gcc-exception.html
+Copyright (C) 2009 Free Software Foundation, Inc. <http://fsf.org/>
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+This GCC Runtime Library Exception ("Exception") is an additional permission under
+section 7 of the GNU General Public License, version 3 ("GPLv3"). It applies to a
+given file (the "Runtime Library") that bears a notice placed by the copyright holder
+of the file stating that the file is governed by GPLv3 along with this Exception.
+When you use GCC to compile a program, GCC may combine portions of certain GCC header
+files and runtime libraries with the compiled program. The purpose of this Exception
+is to allow compilation of non-GPL (including proprietary) programs to use, in this
+way, the header files and runtime libraries covered by this Exception.
+
+0. Definitions.
+A file is an "Independent Module" if it either requires the Runtime Library for
+execution after a Compilation Process, or makes use of an interface provided by the
+Runtime Library, but is not otherwise based on the Runtime Library.
+"GCC" means a version of the GNU Compiler Collection, with or without modifications,
+governed by version 3 (or a specified later version) of the GNU General Public License
+(GPL) with the option of using any subsequent versions published by the FSF.
+"GPL-compatible Software" is software whose conditions of propagation, modification
+and use would permit combination with GCC in accord with the license of GCC.
+"Target Code" refers to output from any compiler for a real or virtual target
+processor architecture, in executable form or suitable for input to an assembler,
+loader, linker and/or execution phase. Notwithstanding that, Target Code does not
+include data in any format that is used as a compiler intermediate representation, or
+used for producing a compiler intermediate representation.
+The "Compilation Process" transforms code entirely represented in non-intermediate
+languages designed for human-written code, and/or in Java Virtual Machine byte code,
+into Target Code. Thus, for example, use of source code generators and preprocessors
+need not be considered part of the Compilation Process, since the Compilation Process
+can be understood as starting with the output of the generators or preprocessors.
+A Compilation Process is "Eligible" if it is done using GCC, alone or with other
+GPL-compatible software, or if it is done without using any work based on GCC. For
+example, using non-GPL-compatible Software to optimize any GCC intermediate
+representations would not qualify as an Eligible Compilation Process.
+
+1. Grant of Additional Permission.
+You have permission to propagate a work of Target Code formed by combining the Runtime
+Library with Independent Modules, even if such propagation would otherwise violate the
+terms of GPLv3, provided that all Target Code was generated by Eligible Compilation
+Processes. You may then convey such a combination under terms of your choice,
+consistent with the licensing of the Independent Modules.
+
+2. No Weakening of GCC Copyleft.
+The availability of this Exception does not imply any general presumption that
+third-party software is unaffected by the copyleft requirements of the license of GCC.
+
+
+
+
+GPL-3.0-with-autoconf-exception
+
+
+insert GPL v3 text here
+
+AUTOCONF CONFIGURE SCRIPT EXCEPTION
+
+Version 3.0, 18 August 2009
+
+Copyright © 2009 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+
+This Exception is an additional permission under section 7 of the GNU General Public
+License, version 3 ("GPLv3"). It applies to a given file that bears a notice placed by
+the copyright holder of the file stating that the file is governed by GPLv3 along with
+this Exception.
+
+The purpose of this Exception is to allow distribution of Autoconf`s typical output
+under terms of the recipient`s choice (including proprietary).
+
+0. Definitions.
+"Covered Code" is the source or object code of a version of Autoconf that is a covered
+work under this License.
+
+"Normally Copied Code" for a version of Autoconf means all parts of its Covered Code
+which that version can copy from its code (i.e., not from its input file) into its
+minimally verbose, non-debugging and non-tracing output.
+
+"Ineligible Code" is Covered Code that is not Normally Copied Code.
+
+1. Grant of Additional Permission.
+You have permission to propagate output of Autoconf, even if such propagation would
+otherwise violate the terms of GPLv3. However, if by modifying Autoconf you cause any
+Ineligible Code of the version you received to become Normally Copied Code of your
+modified version, then you void this Exception for the resulting covered work. If you
+convey that resulting covered work, you must remove this Exception in accordance with
+the second paragraph of Section 7 of GPLv3.
+
+2. No Weakening of Autoconf Copyleft.
+The availability of this Exception does not imply any general presumption that
+third-party software is unaffected by the copyleft requirements of the license of
+Autoconf.
+
+
+
+
+ICU
+
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright (c) 1995-2012 International Business Machines Corporation and others
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this
+software and associated documentation files (the "Software"), to deal in the Software
+without restriction, including without limitation the rights to use, copy, modify,
+merge, publish, distribute, and/or sell copies of the Software, and to permit persons
+to whom the Software is furnished to do so, provided that the above copyright
+notice(s) and this permission notice appear in all copies of the Software and that
+both the above copyright notice(s) and this permission notice appear in supporting
+documentation.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
+INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
+PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
+SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
+LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
+SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder shall not be used
+in advertising or otherwise to promote the sale, use or other dealings in this
+Software without prior written authorization of the copyright holder.
+
+All trademarks and registered trademarks mentioned herein are the property of their
+respective owners.
+
+
+
+IPL-1.0
+
+
+IBM Public License Version 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM
+PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
+OF THE PROGRAM CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+"Contribution" means:
+
+in the case of International Business Machines Corporation ("IBM"), the Original
+Program, and
+in the case of each Contributor,
+changes to the Program, and
+additions to the Program;
+where such changes and/or additions to the Program originate from and
+are distributed by that particular Contributor. A Contribution
+`originates` from a Contributor if it was added to the Program by
+such Contributor itself or anyone acting on such Contributor`s
+behalf. Contributions do not include additions to the Program which:
+(i) are separate modules of software distributed in conjunction with
+the Program under their own license agreement, and (ii) are not
+derivative works of the Program.
+
+"Contributor" means IBM and any other entity that distributes the Program.
+
+"Licensed Patents " mean patent claims licensable by a
+Contributor which are necessarily infringed by the use or sale of its
+Contribution alone or when combined with the Program.
+
+"Original Program" means the original version of the software
+accompanying this Agreement as released by IBM, including source
+code, object code and documentation, if any.
+
+"Program" means the Original Program and Contributions.
+
+"Recipient" means anyone who receives the Program under this
+Agreement, including all Contributors.
+
+2. GRANT OF RIGHTS
+Subject to the terms of this Agreement, each Contributor hereby
+grants Recipient a non-exclusive, worldwide, royalty-free copyright
+license to reproduce, prepare derivative works of, publicly display,
+publicly perform, distribute and sublicense the Contribution of such
+Contributor, if any, and such derivative works, in source code and
+object code form.
+Subject to the terms of this Agreement, each Contributor hereby
+grants Recipient a non-exclusive, worldwide, royalty-free patent
+license under Licensed Patents to make, use, sell, offer to sell,
+import and otherwise transfer the Contribution of such Contributor,
+if any, in source code and object code form. This patent license
+shall apply to the combination of the Contribution and the Program
+if, at the time the Contribution is added by the Contributor, such
+addition of the Contribution causes such combination to be covered by
+the Licensed Patents. The patent license shall not apply to any
+other combinations which include the Contribution. No hardware per
+se is licensed hereunder.
+
+Recipient understands that although each Contributor grants the
+licenses to its Contributions set forth herein, no assurances are
+provided by any Contributor that the Program does not infringe the
+patent or other intellectual property rights of any other entity.
+Each Contributor disclaims any liability to Recipient for claims
+brought by any other entity based on infringement of intellectual
+property rights or otherwise. As a condition to exercising the
+rights and licenses granted hereunder, each Recipient hereby assumes
+sole responsibility to secure any other intellectual property rights
+needed, if any. For example, if a third party patent license is
+required to allow Recipient to distribute the Program, it is
+Recipient`s responsibility to acquire that license before
+distributing the Program.
+Each Contributor represents that to its knowledge it has
+sufficient copyright rights in its Contribution, if any, to grant the
+copyright license set forth in this Agreement.
+3. REQUIREMENTS
+A Contributor may choose to distribute
+the Program in object code form under its own license agreement,
+provided that:
+
+it complies with the terms and conditions of this Agreement; and
+its license agreement:
+effectively disclaims on behalf of all Contributors all warranties
+and conditions, express and implied, including warranties or
+conditions of title and non-infringement, and implied warranties or
+conditions of merchantability and fitness for a particular purpose;
+effectively excludes on behalf of all Contributors all liability
+for damages, including direct, indirect, special, incidental and
+consequential damages, such as lost profits;
+states that any provisions which differ from this Agreement are
+offered by that Contributor alone and not by any other party; and
+
+states that source code for the Program is available from such
+Contributor, and informs licensees how to obtain it in a reasonable
+manner on or through a medium customarily used for software exchange.
+When the Program is made available in source code form:
+
+it must be made available under this Agreement; and
+a copy of this Agreement must be included with each copy of the
+Program.
+Each Contributor must include the following in a conspicuous location in the Program:
+
+Copyright (C) 1996, 1999 International Business Machines Corporation and others. All
+Rights Reserved.
+
+In addition, each Contributor must identify itself as the originator
+of its Contribution, if any, in a manner that reasonably allows
+subsequent Recipients to identify the originator of the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+Commercial distributors of software may accept certain
+responsibilities with respect to end users, business partners and the
+like. While this license is intended to facilitate the commercial
+use of the Program, the Contributor who includes the Program in a
+commercial product offering should do so in a manner which does not
+create potential liability for other Contributors. Therefore, if a
+Contributor includes the Program in a commercial product offering,
+such Contributor ("Commercial Contributor") hereby agrees to defend
+and indemnify every other Contributor ("Indemnified Contributor")
+against any losses, damages and costs (collectively "Losses") arising
+from claims, lawsuits and other legal actions brought by a third
+party against the Indemnified Contributor to the extent caused by the
+acts or omissions of such Commercial Contributor in connection with
+its distribution of the Program in a commercial product offering.
+The obligations in this section do not apply to any claims or Losses
+relating to any actual or alleged intellectual property infringement.
+In order to qualify, an Indemnified Contributor must: a) promptly
+notify the Commercial Contributor in writing of such claim, and b)
+allow the Commercial Contributor to control, and cooperate with the
+Commercial Contributor in, the defense and any related settlement
+negotiations. The Indemnified Contributor may participate in any
+such claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial
+product offering, Product X. That Contributor is then a Commercial
+Contributor. If that Commercial Contributor then makes performance
+claims, or offers warranties related to Product X, those performance
+claims and warranties are such Commercial Contributor`s
+responsibility alone. Under this section, the Commercial Contributor
+would have to defend claims against the other Contributors related to
+those performance claims and warranties, and if a court requires any
+other Contributor to pay any damages as a result, the Commercial
+Contributor must pay those damages.
+
+5. NO WARRANTY
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS
+PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
+WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY
+OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
+responsible for determining the appropriateness of using and
+distributing the Program and assumes all risks associated with its
+exercise of rights under this Agreement, including but not limited to
+the risks and costs of program errors, compliance with applicable
+laws, damage to or loss of data, programs or equipment, and
+unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT
+NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
+TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
+THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
+GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+If any provision of this Agreement is invalid or unenforceable under
+applicable law, it shall not affect the validity or enforceability of
+the remainder of the terms of this Agreement, and without further
+action by the parties hereto, such provision shall be reformed to the
+minimum extent necessary to make such provision valid and enforceable.
+
+If Recipient institutes patent litigation against a Contributor with
+respect to a patent applicable to software (including a cross-claim
+or counterclaim in a lawsuit), then any patent licenses granted by
+that Contributor to such Recipient under this Agreement shall
+terminate as of the date such litigation is filed. In addition, if
+Recipient institutes patent litigation against any entity (including
+a cross-claim or counterclaim in a lawsuit) alleging that the Program
+itself (excluding combinations of the Program with other software or
+hardware) infringes such Recipient`s patent(s), then such Recipient`s
+rights granted under Section 2(b) shall terminate as of the date such
+litigation is filed.
+
+All Recipient`s rights under this Agreement shall terminate if it
+fails to comply with any of the material terms or conditions of this
+Agreement and does not cure such failure in a reasonable period of
+time after becoming aware of such noncompliance. If all Recipient`s
+rights under this Agreement terminate, Recipient agrees to cease use
+and distribution of the Program as soon as reasonably practicable.
+However, Recipient`s obligations under this Agreement and any
+licenses granted by Recipient relating to the Program shall continue
+and survive.
+
+IBM may publish new versions (including revisions) of this Agreement
+from time to time. Each new version of the Agreement will be given a
+distinguishing version number. The Program (including Contributions)
+may always be distributed subject to the version of the Agreement
+under which it was received. In addition, after a new version of the
+Agreement is published, Contributor may elect to distribute the
+Program (including its Contributions) under the new version. No one
+other than IBM has the right to modify this Agreement. Except as
+expressly stated in Sections 2(a) and 2(b) above, Recipient receives
+no rights or licenses to the intellectual property of any Contributor
+under this Agreement, whether expressly, by implication, estoppel or
+otherwise. All rights in the Program not expressly granted under
+this Agreement are reserved.
+
+This Agreement is governed by the laws of the State of New York and
+the intellectual property laws of the United States of America. No
+party to this Agreement will bring a legal action under this
+Agreement more than one year after the cause of action arose. Each
+party waives its rights to a jury trial in any resulting litigation.
+
+
+
+
+ISC
+
+
+ISC License:
+
+Copyright © 2004-2010 by Internet Systems Consortium, Inc. ("ISC")
+Copyright © 1995-2003 by Internet Software Consortium
+
+Permission to use, copy, modify, and/or distribute this software for any purpose with
+or without fee is hereby granted, provided that the above copyright notice and this
+permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
+SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT
+SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
+DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
+OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
+THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+
+
+
+JLEX
+
+ JLEX COPYRIGHT NOTICE, LICENSE, AND DISCLAIMER
+ Copyright 1996-2000 by Elliot Joel Berk and C. Scott Ananian
+
+ Permission to use, copy, modify, and distribute this software and its
+ documentation for any purpose and without fee is hereby granted,
+ provided that the above copyright notice appear in all copies and that
+ both the copyright notice and this permission notice and warranty
+ disclaimer appear in supporting documentation, and that the name of
+ the authors or their employers not be used in advertising or publicity
+ pertaining to distribution of the software without specific, written
+ prior permission.
+
+ The authors and their employers disclaim all warranties with regard to
+ this software, including all implied warranties of merchantability and
+ fitness. In no event shall the authors or their employers be liable
+ for any special, indirect or consequential damages or any damages
+ whatsoever resulting from loss of use, data or profits, whether in an
+ action of contract, negligence or other tortious action, arising out
+ of or in connection with the use or performance of this software.
+
+
+
+LGPL-2.0
+
+GNU LIBRARY GENERAL PUBLIC LICENSE
+
+
+
+Version 2, June 1991
+
+
+
+Copyright (C) 1991 Free Software Foundation, Inc.
+
+51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies
+
+of this license document, but changing it is not allowed.
+
+
+
+[This is the first released version of the library GPL. It is
+
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+Preamble
+
+
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public Licenses are intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users.
+
+
+
+This license, the Library General Public License, applies to some specially designated
+Free Software Foundation software, and to any other libraries whose authors decide to
+use it. You can use it for your libraries, too.
+
+
+
+When we speak of free software, we are referring to freedom, not price. Our General
+Public Licenses are designed to make sure that you have the freedom to distribute
+copies of free software (and charge for this service if you wish), that you receive
+source code or can get it if you want it, that you can change the software or use
+pieces of it in new free programs; and that you know you can do these things.
+
+
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you
+these rights or to ask you to surrender the rights. These restrictions translate to
+certain responsibilities for you if you distribute copies of the library, or if you
+modify it.
+
+
+
+For example, if you distribute copies of the library, whether gratis or for a fee, you
+must give the recipients all the rights that we gave you. You must make sure that
+they, too, receive or can get the source code. If you link a program with the library,
+you must provide complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling it. And you must
+show them these terms so they know their rights.
+
+
+
+Our method of protecting your rights has two steps: (1) copyright the library, and (2)
+offer you this license which gives you legal permission to copy, distribute and/or
+modify the library.
+
+
+
+Also, for each distributor's protection, we want to make certain that everyone
+understands that there is no warranty for this free library. If the library is
+modified by someone else and passed on, we want its recipients to know that what they
+have is not the original version, so that any problems introduced by others will not
+reflect on the original authors' reputations.
+
+
+
+Finally, any free program is threatened constantly by software patents. We wish to
+avoid the danger that companies distributing free software will individually obtain
+patent licenses, thus in effect transforming the program into proprietary software. To
+prevent this, we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+
+
+Most GNU software, including some libraries, is covered by the ordinary GNU General
+Public License, which was designed for utility programs. This license, the GNU Library
+General Public License, applies to certain designated libraries. This license is quite
+different from the ordinary one; be sure to read it in full, and don't assume that
+anything in it is the same as in the ordinary license.
+
+
+
+The reason we have a separate public license for some libraries is that they blur the
+distinction we usually make between modifying or adding to a program and simply using
+it. Linking a program with a library, without changing the library, is in some sense
+simply using the library, and is analogous to running a utility program or application
+program. However, in a textual and legal sense, the linked executable is a combined
+work, a derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+
+
+Because of this blurred distinction, using the ordinary General Public License for
+libraries did not effectively promote software sharing, because most developers did
+not use the libraries. We concluded that weaker conditions might promote sharing
+better.
+
+
+
+However, unrestricted linking of non-free programs would deprive the users of those
+programs of all benefit from the free status of the libraries themselves. This Library
+General Public License is intended to permit developers of non-free programs to use
+free libraries, while preserving your freedom as a user of such programs to change the
+free libraries that are incorporated in them. (We have not seen how to achieve this as
+regards changes in header files, but we have achieved it as regards changes in the
+actual functions of the Library.) The hope is that this will lead to faster
+development of free libraries.
+
+
+
+The precise terms and conditions for copying, distribution and modification follow.
+Pay close attention to the difference between a "work based on the library" and a
+"work that uses the library". The former contains code derived from the library, while
+the latter only works together with the library.
+
+
+
+Note that it is possible for a library to be covered by the ordinary General Public
+License rather than by this special one.
+
+
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+
+
+0. This License Agreement applies to any software library which contains a notice
+placed by the copyright holder or other authorized party saying it may be distributed
+under the terms of this Library General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+
+
+A "library" means a collection of software functions and/or data prepared so as to be
+conveniently linked with application programs (which use some of those functions and
+data) to form executables.
+
+
+
+The "Library", below, refers to any such software library or work which has been
+distributed under these terms. A "work based on the Library" means either the Library
+or any derivative work under copyright law: that is to say, a work containing the
+Library or a portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is included without
+limitation in the term "modification".)
+
+
+
+"Source code" for a work means the preferred form of the work for making modifications
+to it. For a library, complete source code means all the source code for all modules
+it contains, plus any associated interface definition files, plus the scripts used to
+control compilation and installation of the library.
+
+
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running a program using the Library is
+not restricted, and output from such a program is covered only if its contents
+constitute a work based on the Library (independent of the use of the Library in a
+tool for writing it). Whether that is true depends on what the Library does and what
+the program that uses the Library does.
+
+
+
+1. You may copy and distribute verbatim copies of the Library's complete source code
+as you receive it, in any medium, provided that you conspicuously and appropriately
+publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
+intact all the notices that refer to this License and to the absence of any warranty;
+and distribute a copy of this License along with the Library.
+
+
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+
+
+2. You may modify your copy or copies of the Library or any portion of it, thus
+forming a work based on the Library, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+
+
+a) The modified work must itself be a software library.
+
+b) You must cause the files modified to carry prominent notices stating that you
+changed the files and the date of any change.
+
+c) You must cause the whole of the work to be licensed at no charge to all third
+parties under the terms of this License.
+
+d) If a facility in the modified Library refers to a function or a table of data to be
+supplied by an application program that uses the facility, other than as an argument
+passed when the facility is invoked, then you must make a good faith effort to ensure
+that, in the event an application does not supply such function or table, the facility
+still operates, and performs whatever part of its purpose remains meaningful.
+
+(For example, a function in a library to compute square roots has a purpose that is
+entirely well-defined independent of the application. Therefore, Subsection 2d
+requires that any application-supplied function or table used by this function must be
+optional: if the application does not supply it, the square root function must still
+compute square roots.)
+
+
+
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Library, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Library,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Library.
+
+
+
+In addition, mere aggregation of another work not based on the Library with the
+Library (or with a work based on the Library) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+
+
+3. You may opt to apply the terms of the ordinary GNU General Public License instead
+of this License to a given copy of the Library. To do this, you must alter all the
+notices that refer to this License, so that they refer to the ordinary GNU General
+Public License, version 2, instead of to this License. (If a newer version than
+version 2 of the ordinary GNU General Public License has appeared, then you can
+specify that version instead if you wish.) Do not make any other change in these
+notices.
+
+
+
+Once this change is made in a given copy, it is irreversible for that copy, so the
+ordinary GNU General Public License applies to all subsequent copies and derivative
+works made from that copy.
+
+
+
+This option is useful when you wish to copy part of the code of the Library into a
+program that is not a library.
+
+
+
+4. You may copy and distribute the Library (or a portion or derivative of it, under
+Section 2) in object code or executable form under the terms of Sections 1 and 2 above
+provided that you accompany it with the complete corresponding machine-readable source
+code, which must be distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange.
+
+
+
+If distribution of object code is made by offering access to copy from a designated
+place, then offering equivalent access to copy the source code from the same place
+satisfies the requirement to distribute the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+
+
+5. A program that contains no derivative of any portion of the Library, but is
+designed to work with the Library by being compiled or linked with it, is called a
+"work that uses the Library". Such a work, in isolation, is not a derivative work of
+the Library, and therefore falls outside the scope of this License.
+
+
+
+However, linking a "work that uses the Library" with the Library creates an executable
+that is a derivative of the Library (because it contains portions of the Library),
+rather than a "work that uses the library". The executable is therefore covered by
+this License. Section 6 states terms for distribution of such executables.
+
+
+
+When a "work that uses the Library" uses material from a header file that is part of
+the Library, the object code for the work may be a derivative work of the Library even
+though the source code is not. Whether this is true is especially significant if the
+work can be linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+
+
+If such an object file uses only numerical parameters, data structure layouts and
+accessors, and small macros and small inline functions (ten lines or less in length),
+then the use of the object file is unrestricted, regardless of whether it is legally a
+derivative work. (Executables containing this object code plus portions of the Library
+will still fall under Section 6.)
+
+
+
+Otherwise, if the work is a derivative of the Library, you may distribute the object
+code for the work under the terms of Section 6. Any executables containing that work
+also fall under Section 6, whether or not they are linked directly with the Library
+itself.
+
+
+
+6. As an exception to the Sections above, you may also compile or link a "work that
+uses the Library" with the Library to produce a work containing portions of the
+Library, and distribute that work under terms of your choice, provided that the terms
+permit modification of the work for the customer's own use and reverse engineering for
+debugging such modifications.
+
+
+
+You must give prominent notice with each copy of the work that the Library is used in
+it and that the Library and its use are covered by this License. You must supply a
+copy of this License. If the work during execution displays copyright notices, you
+must include the copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one of these things:
+
+
+
+a) Accompany the work with the complete corresponding machine-readable source code for
+the Library including whatever changes were used in the work (which must be
+distributed under Sections 1 and 2 above); and, if the work is an executable linked
+with the Library, with the complete machine-readable "work that uses the Library", as
+object code and/or source code, so that the user can modify the Library and then
+relink to produce a modified executable containing the modified Library. (It is
+understood that the user who changes the contents of definitions files in the Library
+will not necessarily be able to recompile the application to use the modified
+definitions.)
+
+b) Accompany the work with a written offer, valid for at least three years, to give
+the same user the materials specified in Subsection 6a, above, for a charge no more
+than the cost of performing this distribution.
+
+c) If distribution of the work is made by offering access to copy from a designated
+place, offer equivalent access to copy the above specified materials from the same
+place.
+
+d) Verify that the user has already received a copy of these materials or that you
+have already sent this user a copy.
+
+For an executable, the required form of the "work that uses the Library" must include
+any data and utility programs needed for reproducing the executable from it. However,
+as a special exception, the source code distributed need not include anything that is
+normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+
+
+It may happen that this requirement contradicts the license restrictions of other
+proprietary libraries that do not normally accompany the operating system. Such a
+contradiction means you cannot use both them and the Library together in an executable
+that you distribute.
+
+
+
+7. You may place library facilities that are a work based on the Library side-by-side
+in a single library together with other library facilities not covered by this
+License, and distribute such a combined library, provided that the separate
+distribution of the work based on the Library and of the other library facilities is
+otherwise permitted, and provided that you do these two things:
+
+
+
+a) Accompany the combined library with a copy of the same work based on the Library,
+uncombined with any other library facilities. This must be distributed under the terms
+of the Sections above.
+
+b) Give prominent notice with the combined library of the fact that part of it is a
+work based on the Library, and explaining where to find the accompanying uncombined
+form of the same work.
+
+8. You may not copy, modify, sublicense, link with, or distribute the Library except
+as expressly provided under this License. Any attempt otherwise to copy, modify,
+sublicense, link with, or distribute the Library is void, and will automatically
+terminate your rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses terminated so long
+as such parties remain in full compliance.
+
+
+
+9. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Library or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Library or works based on it.
+
+
+
+10. Each time you redistribute the Library (or any work based on the Library), the
+recipient automatically receives a license from the original licensor to copy,
+distribute, link with or modify the Library subject to these terms and conditions. You
+may not impose any further restrictions on the recipients' exercise of the rights
+granted herein. You are not responsible for enforcing compliance by third parties to
+this License.
+
+
+
+11. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Library at all. For example, if a patent license would not permit royalty-free
+redistribution of the Library by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply, and the section as a
+whole is intended to apply in other circumstances.
+
+
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+
+
+12. If the distribution and/or use of the Library is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Library under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+
+
+13. The Free Software Foundation may publish revised and/or new versions of the
+Library General Public License from time to time. Such new versions will be similar in
+spirit to the present version, but may differ in detail to address new problems or
+concerns.
+
+
+
+Each version is given a distinguishing version number. If the Library specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Library does not
+specify a license version number, you may choose any version ever published by the
+Free Software Foundation.
+
+
+
+14. If you wish to incorporate parts of the Library into other free programs whose
+distribution conditions are incompatible with these, write to the author to ask for
+permission. For software which is copyrighted by the Free Software Foundation, write
+to the Free Software Foundation; we sometimes make exceptions for this. Our decision
+will be guided by the two goals of preserving the free status of all derivatives of
+our free software and of promoting the sharing and reuse of software generally.
+
+
+
+NO WARRANTY
+
+
+
+15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+
+
+16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
+WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+
+
+END OF TERMS AND CONDITIONS
+
+
+
+How to Apply These Terms to Your New Libraries
+
+
+
+If you develop a new library, and you want it to be of the greatest possible use to
+the public, we recommend making it free software that everyone can redistribute and
+change. You can do so by permitting redistribution under these terms (or,
+alternatively, under the terms of the ordinary General Public License).
+
+
+
+To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
+where the full notice is found.
+
+
+
+one line to give the library's name and an idea of what it does.
+
+Copyright (C) year name of author
+
+
+
+This library is free software; you can redistribute it and/or
+
+modify it under the terms of the GNU Library General Public
+
+License as published by the Free Software Foundation; either
+
+version 2 of the License, or (at your option) any later version.
+
+
+
+This library is distributed in the hope that it will be useful,
+
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+
+Library General Public License for more details.
+
+
+
+You should have received a copy of the GNU Library General Public
+
+License along with this library; if not, write to the
+
+Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+
+Boston, MA 02110-1301, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
+alter the names:
+
+
+
+Yoyodyne, Inc., hereby disclaims all copyright interest in
+
+the library `Frob' (a library for tweaking knobs) written
+
+by James Random Hacker.
+
+
+
+signature of Ty Coon, 1 April 1990
+
+Ty Coon, President of Vice
+
+That's all there is to it!
+
+
+
+
+LGPL-2.1
+
+
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 2.1, February 1999
+
+Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and
+change it. By contrast, the GNU General Public Licenses are intended to guarantee your
+freedom to share and change free software--to make sure the software is free for all
+its users.
+
+This license, the Lesser General Public License, applies to some specially designated
+software packages--typically libraries--of the Free Software Foundation and other
+authors who decide to use it. You can use it too, but we suggest you first think
+carefully about whether this license or the ordinary General Public License is the
+better strategy to use in any particular case, based on the explanations below.
+
+When we speak of free software, we are referring to freedom of use, not price. Our
+General Public Licenses are designed to make sure that you have the freedom to
+distribute copies of free software (and charge for this service if you wish); that you
+receive source code or can get it if you want it; that you can change the software and
+use pieces of it in new free programs; and that you are informed that you can do these
+things.
+
+To protect your rights, we need to make restrictions that forbid distributors to deny
+you these rights or to ask you to surrender these rights. These restrictions translate
+to certain responsibilities for you if you distribute copies of the library or if you
+modify it.
+
+For example, if you distribute copies of the library, whether gratis or for a fee, you
+must give the recipients all the rights that we gave you. You must make sure that
+they, too, receive or can get the source code. If you link other code with the
+library, you must provide complete object files to the recipients, so that they can
+relink them with the library after making changes to the library and recompiling it.
+And you must show them these terms so they know their rights.
+
+We protect your rights with a two-step method: (1) we copyright the library, and (2)
+we offer you this license, which gives you legal permission to copy, distribute and/or
+modify the library.
+
+To protect each distributor, we want to make it very clear that there is no warranty
+for the free library. Also, if the library is modified by someone else and passed on,
+the recipients should know that what they have is not the original version, so that
+the original author`s reputation will not be affected by problems that might be
+introduced by others.
+
+Finally, software patents pose a constant threat to the existence of any free program.
+We wish to make sure that a company cannot effectively restrict the users of a free
+program by obtaining a restrictive license from a patent holder. Therefore, we insist
+that any patent license obtained for a version of the library must be consistent with
+the full freedom of use specified in this license.
+
+Most GNU software, including some libraries, is covered by the ordinary GNU General
+Public License. This license, the GNU Lesser General Public License, applies to
+certain designated libraries, and is quite different from the ordinary General Public
+License. We use this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+When a program is linked with a library, whether statically or using a shared library,
+the combination of the two is legally speaking a combined work, a derivative of the
+original library. The ordinary General Public License therefore permits such linking
+only if the entire combination fits its criteria of freedom. The Lesser General Public
+License permits more lax criteria for linking other code with the library.
+
+We call this license the "Lesser" General Public License because it does Less to
+protect the user`s freedom than the ordinary General Public License. It also provides
+other free software developers Less of an advantage over competing non-free programs.
+These disadvantages are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain special
+circumstances.
+
+For example, on rare occasions, there may be a special need to encourage the widest
+possible use of a certain library, so that it becomes a de-facto standard. To achieve
+this, non-free programs must be allowed to use the library. A more frequent case is
+that a free library does the same job as widely used non-free libraries. In this case,
+there is little to gain by limiting the free library to free software only, so we use
+the Lesser General Public License.
+
+In other cases, permission to use a particular library in non-free programs enables a
+greater number of people to use a large body of free software. For example, permission
+to use the GNU C Library in non-free programs enables many more people to use the
+whole GNU operating system, as well as its variant, the GNU/Linux operating system.
+
+Although the Lesser General Public License is Less protective of the users` freedom,
+it does ensure that the user of a program that is linked with the Library has the
+freedom and the wherewithal to run that program using a modified version of the
+Library.
+
+The precise terms and conditions for copying, distribution and modification follow.
+Pay close attention to the difference between a "work based on the library" and a
+"work that uses the library". The former contains code derived from the library,
+whereas the latter must be combined with the library in order to run.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License Agreement applies to any software library or other program which
+contains a notice placed by the copyright holder or other authorized party saying it
+may be distributed under the terms of this Lesser General Public License (also called
+"this License"). Each licensee is addressed as "you".
+
+A "library" means a collection of software functions and/or data prepared so as to be
+conveniently linked with application programs (which use some of those functions and
+data) to form executables.
+
+The "Library", below, refers to any such software library or work which has been
+distributed under these terms. A "work based on the Library" means either the Library
+or any derivative work under copyright law: that is to say, a work containing the
+Library or a portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is included without
+limitation in the term "modification".)
+
+"Source code" for a work means the preferred form of the work for making modifications
+to it. For a library, complete source code means all the source code for all modules
+it contains, plus any associated interface definition files, plus the scripts used to
+control compilation and installation of the library.
+
+Activities other than copying, distribution and modification are not covered by this
+License; they are outside its scope. The act of running a program using the Library is
+not restricted, and output from such a program is covered only if its contents
+constitute a work based on the Library (independent of the use of the Library in a
+tool for writing it). Whether that is true depends on what the Library does and what
+the program that uses the Library does.
+
+1. You may copy and distribute verbatim copies of the Library`s complete source code
+as you receive it, in any medium, provided that you conspicuously and appropriately
+publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
+intact all the notices that refer to this License and to the absence of any warranty;
+and distribute a copy of this License along with the Library.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your
+option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Library or any portion of it, thus
+forming a work based on the Library, and copy and distribute such modifications or
+work under the terms of Section 1 above, provided that you also meet all of these
+conditions:
+
+a) The modified work must itself be a software library.
+b) You must cause the files modified to carry prominent notices stating that you
+changed the files and the date of any change.
+c) You must cause the whole of the work to be licensed at no charge to all third
+parties under the terms of this License.
+d) If a facility in the modified Library refers to a function or a table of data to be
+supplied by an application program that uses the facility, other than as an argument
+passed when the facility is invoked, then you must make a good faith effort to ensure
+that, in the event an application does not supply such function or table, the facility
+still operates, and performs whatever part of its purpose remains meaningful.
+(For example, a function in a library to compute square roots has a purpose that is
+entirely well-defined independent of the application. Therefore, Subsection 2d
+requires that any application-supplied function or table used by this function must be
+optional: if the application does not supply it, the square root function must still
+compute square roots.)
+
+These requirements apply to the modified work as a whole. If identifiable sections of
+that work are not derived from the Library, and can be reasonably considered
+independent and separate works in themselves, then this License, and its terms, do not
+apply to those sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on the Library,
+the distribution of the whole must be on the terms of this License, whose permissions
+for other licensees extend to the entire whole, and thus to each and every part
+regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to
+work written entirely by you; rather, the intent is to exercise the right to control
+the distribution of derivative or collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library with the
+Library (or with a work based on the Library) on a volume of a storage or distribution
+medium does not bring the other work under the scope of this License.
+
+3. You may opt to apply the terms of the ordinary GNU General Public License instead
+of this License to a given copy of the Library. To do this, you must alter all the
+notices that refer to this License, so that they refer to the ordinary GNU General
+Public License, version 2, instead of to this License. (If a newer version than
+version 2 of the ordinary GNU General Public License has appeared, then you can
+specify that version instead if you wish.) Do not make any other change in these
+notices.
+
+Once this change is made in a given copy, it is irreversible for that copy, so the
+ordinary GNU General Public License applies to all subsequent copies and derivative
+works made from that copy.
+
+This option is useful when you wish to copy part of the code of the Library into a
+program that is not a library.
+
+4. You may copy and distribute the Library (or a portion or derivative of it, under
+Section 2) in object code or executable form under the terms of Sections 1 and 2 above
+provided that you accompany it with the complete corresponding machine-readable source
+code, which must be distributed under the terms of Sections 1 and 2 above on a medium
+customarily used for software interchange.
+
+If distribution of object code is made by offering access to copy from a designated
+place, then offering equivalent access to copy the source code from the same place
+satisfies the requirement to distribute the source code, even though third parties are
+not compelled to copy the source along with the object code.
+
+5. A program that contains no derivative of any portion of the Library, but is
+designed to work with the Library by being compiled or linked with it, is called a
+"work that uses the Library". Such a work, in isolation, is not a derivative work of
+the Library, and therefore falls outside the scope of this License.
+
+However, linking a "work that uses the Library" with the Library creates an executable
+that is a derivative of the Library (because it contains portions of the Library),
+rather than a "work that uses the library". The executable is therefore covered by
+this License. Section 6 states terms for distribution of such executables.
+
+When a "work that uses the Library" uses material from a header file that is part of
+the Library, the object code for the work may be a derivative work of the Library even
+though the source code is not. Whether this is true is especially significant if the
+work can be linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+If such an object file uses only numerical parameters, data structure layouts and
+accessors, and small macros and small inline functions (ten lines or less in length),
+then the use of the object file is unrestricted, regardless of whether it is legally a
+derivative work. (Executables containing this object code plus portions of the Library
+will still fall under Section 6.)
+
+Otherwise, if the work is a derivative of the Library, you may distribute the object
+code for the work under the terms of Section 6. Any executables containing that work
+also fall under Section 6, whether or not they are linked directly with the Library
+itself.
+
+6. As an exception to the Sections above, you may also combine or link a "work that
+uses the Library" with the Library to produce a work containing portions of the
+Library, and distribute that work under terms of your choice, provided that the terms
+permit modification of the work for the customer`s own use and reverse engineering for
+debugging such modifications.
+
+You must give prominent notice with each copy of the work that the Library is used in
+it and that the Library and its use are covered by this License. You must supply a
+copy of this License. If the work during execution displays copyright notices, you
+must include the copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one of these things:
+
+a) Accompany the work with the complete corresponding machine-readable source code for
+the Library including whatever changes were used in the work (which must be
+distributed under Sections 1 and 2 above); and, if the work is an executable linked
+with the Library, with the complete machine-readable "work that uses the Library", as
+object code and/or source code, so that the user can modify the Library and then
+relink to produce a modified executable containing the modified Library. (It is
+understood that the user who changes the contents of definitions files in the Library
+will not necessarily be able to recompile the application to use the modified
+definitions.)
+b) Use a suitable shared library mechanism for linking with the Library. A suitable
+mechanism is one that (1) uses at run time a copy of the library already present on
+the user`s computer system, rather than copying library functions into the executable,
+and (2) will operate properly with a modified version of the library, if the user
+installs one, as long as the modified version is interface-compatible with the version
+that the work was made with.
+c) Accompany the work with a written offer, valid for at least three years, to give
+the same user the materials specified in Subsection 6a, above, for a charge no more
+than the cost of performing this distribution.
+d) If distribution of the work is made by offering access to copy from a designated
+place, offer equivalent access to copy the above specified materials from the same
+place.
+e) Verify that the user has already received a copy of these materials or that you
+have already sent this user a copy.
+For an executable, the required form of the "work that uses the Library" must include
+any data and utility programs needed for reproducing the executable from it. However,
+as a special exception, the materials to be distributed need not include anything that
+is normally distributed (in either source or binary form) with the major components
+(compiler, kernel, and so on) of the operating system on which the executable runs,
+unless that component itself accompanies the executable.
+
+It may happen that this requirement contradicts the license restrictions of other
+proprietary libraries that do not normally accompany the operating system. Such a
+contradiction means you cannot use both them and the Library together in an executable
+that you distribute.
+
+7. You may place library facilities that are a work based on the Library side-by-side
+in a single library together with other library facilities not covered by this
+License, and distribute such a combined library, provided that the separate
+distribution of the work based on the Library and of the other library facilities is
+otherwise permitted, and provided that you do these two things:
+
+a) Accompany the combined library with a copy of the same work based on the Library,
+uncombined with any other library facilities. This must be distributed under the terms
+of the Sections above.
+b) Give prominent notice with the combined library of the fact that part of it is a
+work based on the Library, and explaining where to find the accompanying uncombined
+form of the same work.
+8. You may not copy, modify, sublicense, link with, or distribute the Library except
+as expressly provided under this License. Any attempt otherwise to copy, modify,
+sublicense, link with, or distribute the Library is void, and will automatically
+terminate your rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses terminated so long
+as such parties remain in full compliance.
+
+9. You are not required to accept this License, since you have not signed it. However,
+nothing else grants you permission to modify or distribute the Library or its
+derivative works. These actions are prohibited by law if you do not accept this
+License. Therefore, by modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and all its terms and
+conditions for copying, distributing or modifying the Library or works based on it.
+
+10. Each time you redistribute the Library (or any work based on the Library), the
+recipient automatically receives a license from the original licensor to copy,
+distribute, link with or modify the Library subject to these terms and conditions. You
+may not impose any further restrictions on the recipients` exercise of the rights
+granted herein. You are not responsible for enforcing compliance by third parties with
+this License.
+
+11. If, as a consequence of a court judgment or allegation of patent infringement or
+for any other reason (not limited to patent issues), conditions are imposed on you
+(whether by court order, agreement or otherwise) that contradict the conditions of
+this License, they do not excuse you from the conditions of this License. If you
+cannot distribute so as to satisfy simultaneously your obligations under this License
+and any other pertinent obligations, then as a consequence you may not distribute the
+Library at all. For example, if a patent license would not permit royalty-free
+redistribution of the Library by all those who receive copies directly or indirectly
+through you, then the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any particular
+circumstance, the balance of the section is intended to apply, and the section as a
+whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other
+property right claims or to contest validity of any such claims; this section has the
+sole purpose of protecting the integrity of the free software distribution system
+which is implemented by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that system in
+reliance on consistent application of that system; it is up to the author/donor to
+decide if he or she is willing to distribute software through any other system and a
+licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence
+of the rest of this License.
+
+12. If the distribution and/or use of the Library is restricted in certain countries
+either by patents or by copyrighted interfaces, the original copyright holder who
+places the Library under this License may add an explicit geographical distribution
+limitation excluding those countries, so that distribution is permitted only in or
+among countries not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+13. The Free Software Foundation may publish revised and/or new versions of the Lesser
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library specifies a
+version number of this License which applies to it and "any later version", you have
+the option of following the terms and conditions either of that version or of any
+later version published by the Free Software Foundation. If the Library does not
+specify a license version number, you may choose any version ever published by the
+Free Software Foundation.
+
+14. If you wish to incorporate parts of the Library into other free programs whose
+distribution conditions are incompatible with these, write to the author to ask for
+permission. For software which is copyrighted by the Free Software Foundation, write
+to the Free Software Foundation; we sometimes make exceptions for this. Our decision
+will be guided by the two goals of preserving the free status of all derivatives of
+our free software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
+LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
+WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
+WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
+RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
+COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
+PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
+OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
+WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Libraries
+
+If you develop a new library, and you want it to be of the greatest possible use to
+the public, we recommend making it free software that everyone can redistribute and
+change. You can do so by permitting redistribution under these terms (or,
+alternatively, under the terms of the ordinary General Public License).
+
+To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
+where the full notice is found.
+
+one line to give the library`s name and an idea of what it does.
+Copyright (C) year name of author
+
+This library is free software; you can redistribute it and/or
+modify it under the terms of the GNU Lesser General Public
+License as published by the Free Software Foundation; either
+version 2.1 of the License, or (at your option) any later version.
+
+This library is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public
+License along with this library; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your school, if
+any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
+alter the names:
+
+Yoyodyne, Inc., hereby disclaims all copyright interest in
+the library `Frob` (a library for tweaking knobs) written
+by James Random Hacker.
+
+signature of Ty Coon, 1 April 1990
+Ty Coon, President of Vice
+That`s all there is to it!
+
+
+
+
+LGPL-3.0
+
+GNU LESSER GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document,
+but changing it is not allowed.
+
+This version of the GNU Lesser General Public License incorporates the terms and
+conditions of version 3 of the GNU General Public License, supplemented by the
+additional permissions listed below.
+0. Additional Definitions.
+
+As used herein, ”this License” refers to version 3 of the GNU Lesser
+General Public License, and the ”GNU GPL” refers to version 3 of the GNU
+General Public License.
+
+”The Library” refers to a covered work governed by this License, other
+than an Application or a Combined Work as defined below.
+
+An ”Application” is any work that makes use of an interface provided by
+the Library, but which is not otherwise based on the Library. Defining a subclass of a
+class defined by the Library is deemed a mode of using an interface provided by the
+Library.
+
+A ”Combined Work” is a work produced by combining or linking an
+Application with the Library. The particular version of the Library with which the
+Combined Work was made is also called the ”Linked Version”.
+
+The ”Minimal Corresponding Source” for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code for portions of
+the Combined Work that, considered in isolation, are based on the Application, and not
+on the Linked Version.
+
+The ”Corresponding Application Code” for a Combined Work means the object
+code and/or source code for the Application, including any data and utility programs
+needed for reproducing the Combined Work from the Application, but excluding the
+System Libraries of the Combined Work.
+1. Exception to Section 3 of the GNU GPL.
+
+You may convey a covered work under sections 3 and 4 of this License without being
+bound by section 3 of the GNU GPL.
+2. Conveying Modified Versions.
+
+If you modify a copy of the Library, and, in your modifications, a facility refers to
+a function or data to be supplied by an Application that uses the facility (other than
+as an argument passed when the facility is invoked), then you may convey a copy of the
+modified version:
+
+ * a) under this License, provided that you make a good faith effort to ensure
+that, in the event an Application does not supply the function or data, the facility
+still operates, and performs whatever part of its purpose remains meaningful, or
+ * b) under the GNU GPL, with none of the additional permissions of this License
+applicable to that copy.
+
+3. Object Code Incorporating Material from Library Header Files.
+
+The object code form of an Application may incorporate material from a header file
+that is part of the Library. You may convey such object code under terms of your
+choice, provided that, if the incorporated material is not limited to numerical
+parameters, data structure layouts and accessors, or small macros, inline functions
+and templates (ten or fewer lines in length), you do both of the following:
+
+ * a) Give prominent notice with each copy of the object code that the Library is
+used in it and that the Library and its use are covered by this License.
+ * b) Accompany the object code with a copy of the GNU GPL and this license
+document.
+
+4. Combined Works.
+
+You may convey a Combined Work under terms of your choice that, taken together,
+effectively do not restrict modification of the portions of the Library contained in
+the Combined Work and reverse engineering for debugging such modifications, if you
+also do each of the following:
+
+ * a) Give prominent notice with each copy of the Combined Work that the Library is
+used in it and that the Library and its use are covered by this License.
+ * b) Accompany the Combined Work with a copy of the GNU GPL and this license
+document.
+ * c) For a Combined Work that displays copyright notices during execution, include
+the copyright notice for the Library among these notices, as well as a reference
+directing the user to the copies of the GNU GPL and this license document.
+ * d) Do one of the following:
+ o 0) Convey the Minimal Corresponding Source under the terms of this
+License, and the Corresponding Application Code in a form suitable for, and under
+terms that permit, the user to recombine or relink the Application with a modified
+version of the Linked Version to produce a modified Combined Work, in the manner
+specified by section 6 of the GNU GPL for conveying Corresponding Source.
+ o 1) Use a suitable shared library mechanism for linking with the Library. A
+suitable mechanism is one that (a) uses at run time a copy of the Library already
+present on the user's computer system, and (b) will operate properly with a modified
+version of the Library that is interface-compatible with the Linked Version.
+ * e) Provide Installation Information, but only if you would otherwise be required
+to provide such information under section 6 of the GNU GPL, and only to the extent
+that such information is necessary to install and execute a modified version of the
+Combined Work produced by recombining or relinking the Application with a modified
+version of the Linked Version. (If you use option 4d0, the Installation Information
+must accompany the Minimal Corresponding Source and Corresponding Application Code. If
+you use option 4d1, you must provide the Installation Information in the manner
+specified by section 6 of the GNU GPL for conveying Corresponding Source.)
+
+5. Combined Libraries.
+
+You may place library facilities that are a work based on the Library side by side in
+a single library together with other library facilities that are not Applications and
+are not covered by this License, and convey such a combined library under terms of
+your choice, if you do both of the following:
+
+ * a) Accompany the combined library with a copy of the same work based on the
+Library, uncombined with any other library facilities, conveyed under the terms of
+this License.
+ * b) Give prominent notice with the combined library that part of it is a work
+based on the Library, and explaining where to find the accompanying uncombined form of
+the same work.
+
+6. Revised Versions of the GNU Lesser General Public License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Lesser
+General Public License from time to time. Such new versions will be similar in spirit
+to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library as you received
+it specifies that a certain numbered version of the GNU Lesser General Public License
+”or any later version” applies to it, you have the option of following
+the terms and conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you received it does not
+specify a version number of the GNU Lesser General Public License, you may choose any
+version of the GNU Lesser General Public License ever published by the Free Software
+Foundation.
+
+If the Library as you received it specifies that a proxy can decide whether future
+versions of the GNU Lesser General Public License shall apply, that proxy's public
+statement of acceptance of any version is permanent authorization for you to choose
+that version for the Library.
+
+
+
+Libpng
+
+
+This copy of the libpng notices is provided for your convenience. In case of
+any discrepancy between this copy and the notices in the file png.h that is
+included in the libpng distribution, the latter shall prevail.
+
+COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
+
+If you modify libpng you may insert additional notices immediately following
+this sentence.
+
+This code is released under the libpng license.
+
+libpng versions 1.2.6, August 15, 2004, through 1.4.5, December 9, 2010, are
+Copyright (c) 2004, 2006-2010 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-1.2.5
+with the following individual added to the list of Contributing Authors
+
+ Cosmin Truta
+
+libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are
+Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-1.0.6
+with the following individuals added to the list of Contributing Authors
+
+ Simon-Pierre Cadieux
+ Eric S. Raymond
+ Gilles Vollant
+
+and with the following additions to the disclaimer:
+
+ There is no warranty against interference with your enjoyment of the
+ library or against infringement. There is no warranty that our
+ efforts or the library will fulfill any of your particular purposes
+ or needs. This library is provided with all faults, and the entire
+ risk of satisfactory quality, performance, accuracy, and effort is with
+ the user.
+
+libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
+Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are
+distributed according to the same disclaimer and license as libpng-0.96,
+with the following individuals added to the list of Contributing Authors:
+
+ Tom Lane
+ Glenn Randers-Pehrson
+ Willem van Schaik
+
+libpng versions 0.89, June 1996, through 0.96, May 1997, are
+Copyright (c) 1996, 1997 Andreas Dilger
+Distributed according to the same disclaimer and license as libpng-0.88,
+with the following individuals added to the list of Contributing Authors:
+
+ John Bowler
+ Kevin Bracey
+ Sam Bushell
+ Magnus Holmgren
+ Greg Roelofs
+ Tom Tanner
+
+libpng versions 0.5, May 1995, through 0.88, January 1996, are
+Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.
+
+For the purposes of this copyright and license, "Contributing Authors"
+is defined as the following set of individuals:
+
+ Andreas Dilger
+ Dave Martindale
+ Guy Eric Schalnat
+ Paul Schmidt
+ Tim Wegner
+
+The PNG Reference Library is supplied "AS IS". The Contributing Authors
+and Group 42, Inc. disclaim all warranties, expressed or implied,
+including, without limitation, the warranties of merchantability and of
+fitness for any purpose. The Contributing Authors and Group 42, Inc.
+assume no liability for direct, indirect, incidental, special, exemplary,
+or consequential damages, which may result from the use of the PNG
+Reference Library, even if advised of the possibility of such damage.
+
+Permission is hereby granted to use, copy, modify, and distribute this
+source code, or portions hereof, for any purpose, without fee, subject
+to the following restrictions:
+
+1. The origin of this source code must not be misrepresented.
+
+2. Altered versions must be plainly marked as such and must not
+ be misrepresented as being the original source.
+
+3. This Copyright notice may not be removed or altered from any
+ source or altered source distribution.
+
+The Contributing Authors and Group 42, Inc. specifically permit, without
+fee, and encourage the use of this source code as a component to
+supporting the PNG file format in commercial products. If you use this
+source code in a product, acknowledgment is not required but would be
+appreciated.
+
+
+A "png_get_copyright" function is available, for convenient use in "about"
+boxes and the like:
+
+ printf("%s",png_get_copyright(NULL));
+
+Also, the PNG logo (in PNG format, of course) is supplied in the
+files "pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).
+
+Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a
+certification mark of the Open Source Initiative.
+
+Glenn Randers-Pehrson
+glennrp at users.sourceforge.net
+December 9, 2010
+
+
+
+
+MIT
+
+
+MIT License
+
+Copyright (c) <year> <copyright holders>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+
+
+
+MPL-1.0
+
+
+MOZILLA PUBLIC LICENSE
+Version 1.0
+
+1. Definitions.
+
+1.1. ``Contributor`` means each entity that creates or contributes to the creation of
+Modifications.
+1.2. ``Contributor Version`` means the combination of the Original Code, prior
+Modifications used by a Contributor, and the Modifications made by that particular
+Contributor.
+
+1.3. ``Covered Code`` means the Original Code or Modifications or the combination of
+the Original Code and Modifications, in each case including portions thereof.
+
+1.4. ``Electronic Distribution Mechanism`` means a mechanism generally accepted in the
+software development community for the electronic transfer of data.
+
+1.5. ``Executable`` means Covered Code in any form other than Source Code.
+
+1.6. ``Initial Developer`` means the individual or entity identified as the Initial
+Developer in the Source Code notice required by Exhibit A.
+
+1.7. ``Larger Work`` means a work which combines Covered Code or portions thereof with
+code not governed by the terms of this License.
+
+1.8. ``License`` means this document.
+
+1.9. ``Modifications`` means any addition to or deletion from the substance or
+structure of either the Original Code or any previous Modifications. When Covered Code
+is released as a series of files, a Modification is:
+
+A. Any addition to or deletion from the contents of a file containing Original Code or
+previous Modifications.
+
+B. Any new file that contains any part of the Original Code or previous Modifications.
+
+1.10. ``Original Code`` means Source Code of computer software code which is described
+in the Source Code notice required by Exhibit A as Original Code, and which, at the
+time of its release under this License is not already Covered Code governed by this
+License.
+
+1.11. ``Source Code`` means the preferred form of the Covered Code for making
+modifications to it, including all modules it contains, plus any associated interface
+definition files, scripts used to control compilation and installation of an
+Executable, or a list of source code differential comparisons against either the
+Original Code or another well known, available Covered Code of the Contributor`s
+choice. The Source Code can be in a compressed or archival form, provided the
+appropriate decompression or de-archiving software is widely available for no charge.
+
+1.12. ``You`` means an individual or a legal entity exercising rights under, and
+complying with all of the terms of, this License or a future version of this License
+issued under Section 6.1. For legal entities, ``You`` includes any entity which
+controls, is controlled by, or is under common control with You. For purposes of this
+definition, ``control`` means (a) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or otherwise, or (b)
+ownership of fifty percent (50%) or more of the outstanding shares or beneficial
+ownership of such entity.
+
+2. Source Code License.
+2.1. The Initial Developer Grant.
+The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive
+license, subject to third party intellectual property claims:
+(a) to use, reproduce, modify, display, perform, sublicense and distribute the
+Original Code (or portions thereof) with or without Modifications, or as part of a
+Larger Work; and
+
+(b) under patents now or hereafter owned or controlled by Initial Developer, to make,
+have made, use and sell (``Utilize``) the Original Code (or portions thereof), but
+solely to the extent that any such patent is reasonably necessary to enable You to
+Utilize the Original Code (or portions thereof) and not to any greater extent that may
+be necessary to Utilize further Modifications or combinations.
+
+2.2. Contributor Grant.
+Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license,
+subject to third party intellectual property claims:
+
+(a) to use, reproduce, modify, display, perform, sublicense and distribute the
+Modifications created by such Contributor (or portions thereof) either on an
+unmodified basis, with other Modifications, as Covered Code or as part of a Larger
+Work; and
+
+(b) under patents now or hereafter owned or controlled by Contributor, to Utilize the
+Contributor Version (or portions thereof), but solely to the extent that any such
+patent is reasonably necessary to enable You to Utilize the Contributor Version (or
+portions thereof), and not to any greater extent that may be necessary to Utilize
+further Modifications or combinations.
+
+3. Distribution Obligations.
+3.1. Application of License.
+The Modifications which You create or to which You contribute are governed by the
+terms of this License, including without limitation Section 2.2. The Source Code
+version of Covered Code may be distributed only under the terms of this License or a
+future version of this License released under Section 6.1, and You must include a copy
+of this License with every copy of the Source Code You distribute. You may not offer
+or impose any terms on any Source Code version that alters or restricts the applicable
+version of this License or the recipients` rights hereunder. However, You may include
+an additional document offering the additional rights described in Section 3.5.
+3.2. Availability of Source Code.
+Any Modification which You create or to which You contribute must be made available in
+Source Code form under the terms of this License either on the same media as an
+Executable version or via an accepted Electronic Distribution Mechanism to anyone to
+whom you made an Executable version available; and if made available via Electronic
+Distribution Mechanism, must remain available for at least twelve (12) months after
+the date it initially became available, or at least six (6) months after a subsequent
+version of that particular Modification has been made available to such recipients.
+You are responsible for ensuring that the Source Code version remains available even
+if the Electronic Distribution Mechanism is maintained by a third party.
+
+3.3. Description of Modifications.
+You must cause all Covered Code to which you contribute to contain a file documenting
+the changes You made to create that Covered Code and the date of any change. You must
+include a prominent statement that the Modification is derived, directly or
+indirectly, from Original Code provided by the Initial Developer and including the
+name of the Initial Developer in (a) the Source Code, and (b) in any notice in an
+Executable version or related documentation in which You describe the origin or
+ownership of the Covered Code.
+
+3.4. Intellectual Property Matters
+
+(a) Third Party Claims.
+If You have knowledge that a party claims an intellectual property right in particular
+functionality or code (or its utilization under this License), you must include a text
+file with the source code distribution titled ``LEGAL`` which describes the claim and
+the party making the claim in sufficient detail that a recipient will know whom to
+contact. If you obtain such knowledge after You make Your Modification available as
+described in Section 3.2, You shall promptly modify the LEGAL file in all copies You
+make available thereafter and shall take other steps (such as notifying appropriate
+mailing lists or newsgroups) reasonably calculated to inform those who received the
+Covered Code that new knowledge has been obtained.
+
+(b) Contributor APIs.
+If Your Modification is an application programming interface and You own or control
+patents which are reasonably necessary to implement that API, you must also include
+this information in the LEGAL file.
+
+3.5. Required Notices.
+You must duplicate the notice in Exhibit A in each file of the Source Code, and this
+License in any documentation for the Source Code, where You describe recipients`
+rights relating to Covered Code. If You created one or more Modification(s), You may
+add your name as a Contributor to the notice described in Exhibit A. If it is not
+possible to put such notice in a particular Source Code file due to its structure,
+then you must include such notice in a location (such as a relevant directory file)
+where a user would be likely to look for such a notice. You may choose to offer, and
+to charge a fee for, warranty, support, indemnity or liability obligations to one or
+more recipients of Covered Code. However, You may do so only on Your own behalf, and
+not on behalf of the Initial Developer or any Contributor. You must make it absolutely
+clear than any such warranty, support, indemnity or liability obligation is offered by
+You alone, and You hereby agree to indemnify the Initial Developer and every
+Contributor for any liability incurred by the Initial Developer or such Contributor as
+a result of warranty, support, indemnity or liability terms You offer.
+
+3.6. Distribution of Executable Versions.
+You may distribute Covered Code in Executable form only if the requirements of Section
+3.1-3.5 have been met for that Covered Code, and if You include a notice stating that
+the Source Code version of the Covered Code is available under the terms of this
+License, including a description of how and where You have fulfilled the obligations
+of Section 3.2. The notice must be conspicuously included in any notice in an
+Executable version, related documentation or collateral in which You describe
+recipients` rights relating to the Covered Code. You may distribute the Executable
+version of Covered Code under a license of Your choice, which may contain terms
+different from this License, provided that You are in compliance with the terms of
+this License and that the license for the Executable version does not attempt to limit
+or alter the recipient`s rights in the Source Code version from the rights set forth
+in this License. If You distribute the Executable version under a different license
+You must make it absolutely clear that any terms which differ from this License are
+offered by You alone, not by the Initial Developer or any Contributor. You hereby
+agree to indemnify the Initial Developer and every Contributor for any liability
+incurred by the Initial Developer or such Contributor as a result of any such terms
+You offer.
+
+3.7. Larger Works.
+You may create a Larger Work by combining Covered Code with other code not governed by
+the terms of this License and distribute the Larger Work as a single product. In such
+a case, You must make sure the requirements of this License are fulfilled for the
+Covered Code.
+
+4. Inability to Comply Due to Statute or Regulation.
+If it is impossible for You to comply with any of the terms of this License with
+respect to some or all of the Covered Code due to statute or regulation then You must:
+(a) comply with the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must be included
+in the LEGAL file described in Section 3.4 and must be included with all distributions
+of the Source Code. Except to the extent prohibited by statute or regulation, such
+description must be sufficiently detailed for a recipient of ordinary skill to be able
+to understand it.
+
+5. Application of this License.
+This License applies to code to which the Initial Developer has attached the notice in
+Exhibit A, and to related Covered Code.
+6. Versions of the License.
+6.1. New Versions.
+Netscape Communications Corporation (``Netscape``) may publish revised and/or new
+versions of the License from time to time. Each version will be given a distinguishing
+version number.
+6.2. Effect of New Versions.
+Once Covered Code has been published under a particular version of the License, You
+may always continue to use it under the terms of that version. You may also choose to
+use such Covered Code under the terms of any subsequent version of the License
+published by Netscape. No one other than Netscape has the right to modify the terms
+applicable to Covered Code created under this License.
+
+6.3. Derivative Works.
+If you create or use a modified version of this License (which you may only do in
+order to apply it to code which is not already Covered Code governed by this License),
+you must (a) rename Your license so that the phrases ``Mozilla``, ``MOZILLAPL``,
+``MOZPL``, ``Netscape``, ``NPL`` or any confusingly similar phrase do not appear
+anywhere in your license and (b) otherwise make it clear that your version of the
+license contains terms which differ from the Mozilla Public License and Netscape
+Public License. (Filling in the name of the Initial Developer, Original Code or
+Contributor in the notice described in Exhibit A shall not of themselves be deemed to
+be modifications of this License.)
+
+7. DISCLAIMER OF WARRANTY.
+COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS`` BASIS, WITHOUT WARRANTY OF
+ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT
+THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
+NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
+IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE
+INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
+SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL
+PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER
+THIS DISCLAIMER.
+8. TERMINATION.
+This License and the rights granted hereunder will terminate automatically if You fail
+to comply with terms herein and fail to cure such breach within 30 days of becoming
+aware of the breach. All sublicenses to the Covered Code which are properly granted
+shall survive any termination of this License. Provisions which, by their nature, must
+remain in effect beyond the termination of this License shall survive.
+9. LIMITATION OF LIABILITY.
+UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
+CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY
+DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU
+OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF
+ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK
+STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
+LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH
+DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
+PERSONAL INJURY RESULTING FROM SUCH PARTY`S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
+PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION
+OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY
+TO YOU.
+10. U.S. GOVERNMENT END USERS.
+The Covered Code is a ``commercial item,`` as that term is defined in 48 C.F.R. 2.101
+(Oct. 1995), consisting of ``commercial computer software`` and ``commercial computer
+software documentation,`` as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
+Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
+1995), all U.S. Government End Users acquire Covered Code with only those rights set
+forth herein.
+11. MISCELLANEOUS.
+This License represents the complete agreement concerning subject matter hereof. If
+any provision of this License is held to be unenforceable, such provision shall be
+reformed only to the extent necessary to make it enforceable. This License shall be
+governed by California law provisions (except to the extent applicable law, if any,
+provides otherwise), excluding its conflict-of-law provisions. With respect to
+disputes in which at least one party is a citizen of, or an entity chartered or
+registered to do business in, the United States of America: (a) unless otherwise
+agreed in writing, all disputes relating to this License (excepting any dispute
+relating to intellectual property rights) shall be subject to final and binding
+arbitration, with the losing party paying all costs of arbitration; (b) any
+arbitration relating to this Agreement shall be held in Santa Clara County,
+California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to
+this Agreement shall be subject to the jurisdiction of the Federal Courts of the
+Northern District of California, with venue lying in Santa Clara County, California,
+with the losing party responsible for costs, including without limitation, court costs
+and reasonable attorneys fees and expenses. The application of the United Nations
+Convention on Contracts for the International Sale of Goods is expressly excluded. Any
+law or regulation which provides that the language of a contract shall be construed
+against the drafter shall not apply to this License.
+12. RESPONSIBILITY FOR CLAIMS.
+Except in cases where another Contributor has failed to comply with Section 3.4, You
+are responsible for damages arising, directly or indirectly, out of Your utilization
+of rights under this License, based on the number of copies of Covered Code you made
+available, the revenues you received from utilizing such rights, and other relevant
+factors. You agree to work with affected parties to distribute responsibility on an
+equitable basis.
+EXHIBIT A.
+``The contents of this file are subject to the Mozilla Public License Version 1.0 (the
+"License"); you may not use this file except in compliance with the License. You may
+obtain a copy of the License at http://www.mozilla.org/MPL/
+Software distributed under the License is distributed on an "AS IS" basis, WITHOUT
+WARRANTY OF ANY KIND, either express or implied. See the License for the specific
+language governing rights and limitations under the License.
+
+The Original Code is ______________________________________.
+
+The Initial Developer of the Original Code is ________________________. Portions
+created by ______________________ are Copyright (C) ______ _______________________.
+All Rights Reserved.
+
+Contributor(s): ______________________________________.``
+
+
+
+
+MPL-2.0
+
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+ means each individual or legal entity that creates, contributes to
+ the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+ means the combination of the Contributions of others (if any) used
+ by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+ means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+ means Source Code Form to which the initial Contributor has attached
+ the notice in Exhibit A, the Executable Form of such Source Code
+ Form, and Modifications of such Source Code Form, in each case
+ including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+ means
+
+ (a) that the initial Contributor has attached the notice described
+ in Exhibit B to the Covered Software; or
+
+ (b) that the Covered Software was made available under the terms of
+ version 1.1 or earlier of the License, but not also under the
+ terms of a Secondary License.
+
+1.6. "Executable Form"
+ means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+ means a work that combines Covered Software with other material, in
+ a separate file or files, that is not Covered Software.
+
+1.8. "License"
+ means this document.
+
+1.9. "Licensable"
+ means having the right to grant, to the maximum extent possible,
+ whether at the time of the initial grant or subsequently, any and
+ all of the rights conveyed by this License.
+
+1.10. "Modifications"
+ means any of the following:
+
+ (a) any file in Source Code Form that results from an addition to,
+ deletion from, or modification of the contents of Covered
+ Software; or
+
+ (b) any new file in Source Code Form that contains any Covered
+ Software.
+
+1.11. "Patent Claims" of a Contributor
+ means any patent claim(s), including without limitation, method,
+ process, and apparatus claims, in any patent Licensable by such
+ Contributor that would be infringed, but for the grant of the
+ License, by the making, using, selling, offering for sale, having
+ made, import, or transfer of either its Contributions or its
+ Contributor Version.
+
+1.12. "Secondary License"
+ means either the GNU General Public License, Version 2.0, the GNU
+ Lesser General Public License, Version 2.1, the GNU Affero General
+ Public License, Version 3.0, or any later versions of those
+ licenses.
+
+1.13. "Source Code Form"
+ means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+ means an individual or a legal entity exercising rights under this
+ License. For legal entities, "You" includes any entity that
+ controls, is controlled by, or is under common control with You. For
+ purposes of this definition, "control" means (a) the power, direct
+ or indirect, to cause the direction or management of such entity,
+ whether by contract or otherwise, or (b) ownership of more than
+ fifty percent (50%) of the outstanding shares or beneficial
+ ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+ Licensable by such Contributor to use, reproduce, make available,
+ modify, display, perform, distribute, and otherwise exploit its
+ Contributions, either on an unmodified basis, with Modifications, or
+ as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+ for sale, have made, import, and otherwise transfer either its
+ Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+ or
+
+(b) for infringements caused by: (i) Your and any other third party's
+ modifications of Covered Software, or (ii) the combination of its
+ Contributions with other software (except as part of its Contributor
+ Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+ its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+ Form, as described in Section 3.1, and You must inform recipients of
+ the Executable Form how they can obtain a copy of such Source Code
+ Form by reasonable means in a timely manner, at a charge no more
+ than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+ License, or sublicense it under different terms, provided that the
+ license for the Executable Form does not attempt to limit or alter
+ the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+* *
+* 6. Disclaimer of Warranty *
+* ------------------------- *
+* *
+* Covered Software is provided under this License on an "as is" *
+* basis, without warranty of any kind, either expressed, implied, or *
+* statutory, including, without limitation, warranties that the *
+* Covered Software is free of defects, merchantable, fit for a *
+* particular purpose or non-infringing. The entire risk as to the *
+* quality and performance of the Covered Software is with You. *
+* Should any Covered Software prove defective in any respect, You *
+* (not any Contributor) assume the cost of any necessary servicing, *
+* repair, or correction. This disclaimer of warranty constitutes an *
+* essential part of this License. No use of any Covered Software is *
+* authorized under this License except under this disclaimer. *
+* *
+************************************************************************
+
+************************************************************************
+* *
+* 7. Limitation of Liability *
+* -------------------------- *
+* *
+* Under no circumstances and under no legal theory, whether tort *
+* (including negligence), contract, or otherwise, shall any *
+* Contributor, or anyone who distributes Covered Software as *
+* permitted above, be liable to You for any direct, indirect, *
+* special, incidental, or consequential damages of any character *
+* including, without limitation, damages for lost profits, loss of *
+* goodwill, work stoppage, computer failure or malfunction, or any *
+* and all other commercial damages or losses, even if such party *
+* shall have been informed of the possibility of such damages. This *
+* limitation of liability shall not apply to liability for death or *
+* personal injury resulting from such party's negligence to the *
+* extent applicable law prohibits such limitation. Some *
+* jurisdictions do not allow the exclusion or limitation of *
+* incidental or consequential damages, so this exclusion and *
+* limitation may not apply to You. *
+* *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+ This Source Code Form is subject to the terms of the Mozilla Public
+ License, v. 2.0. If a copy of the MPL was not distributed with this
+ file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+ This Source Code Form is "Incompatible With Secondary Licenses", as
+ defined by the Mozilla Public License, v. 2.0.
+
+
+
+OFL-1.1
+
+
+SIL OPEN FONT LICENSE
+
+Version 1.1 - 26 February 2007
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded,
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.
+
+
+
+
+OpenSSL
+
+
+OpenSSL License
+
+ ====================================================================
+ Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ 1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the
+ distribution.
+
+ 3. All advertising materials mentioning features or use of this
+ software must display the following acknowledgment:
+ "This product includes software developed by the OpenSSL Project
+ for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
+
+ 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
+ endorse or promote products derived from this software without
+ prior written permission. For written permission, please contact
+ openssl-core@openssl.org.
+
+ 5. Products derived from this software may not be called "OpenSSL"
+ nor may "OpenSSL" appear in their names without prior written
+ permission of the OpenSSL Project.
+
+ 6. Redistributions of any form whatsoever must retain the following
+ acknowledgment:
+ "This product includes software developed by the OpenSSL Project
+ for use in the OpenSSL Toolkit (http://www.openssl.org/)"
+
+ THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS`` AND ANY
+ EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
+ ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+ NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+ OF THE POSSIBILITY OF SUCH DAMAGE.
+ ====================================================================
+
+ This product includes cryptographic software written by Eric Young
+ (eay@cryptsoft.com). This product includes software written by Tim
+ Hudson (tjh@cryptsoft.com).
+
+
+ Original SSLeay License
+ -----------------------
+
+Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
+All rights reserved.
+
+ This package is an SSL implementation written
+ by Eric Young (eay@cryptsoft.com).
+ The implementation was written so as to conform with Netscapes SSL.
+
+ This library is free for commercial and non-commercial use as long as
+ the following conditions are aheared to. The following conditions
+ apply to all code found in this distribution, be it the RC4, RSA,
+ lhash, DES, etc., code; not just the SSL code. The SSL documentation
+ included with this distribution is covered by the same copyright terms
+ except that the holder is Tim Hudson (tjh@cryptsoft.com).
+
+ Copyright remains Eric Young`s, and as such any Copyright notices in
+ the code are not to be removed.
+ If this package is used in a product, Eric Young should be given attribution
+ as the author of the parts of the library used.
+ This can be in the form of a textual message at program startup or
+ in documentation (online or textual) provided with the package.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the copyright
+ notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ 3. All advertising materials mentioning features or use of this software
+ must display the following acknowledgement:
+ "This product includes cryptographic software written by
+ Eric Young (eay@cryptsoft.com)"
+ The word `cryptographic` can be left out if the rouines from the library
+ being used are not cryptographic related :-).
+ 4. If you include any Windows specific code (or a derivative thereof) from
+ the apps directory (application code) you must include an acknowledgement:
+ "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
+
+ THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS`` AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
+CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+ The licence and distribution terms for any publically available version or
+derivative of this code cannot be changed. i.e. this code cannot simply be copied and
+put under another distribution licence
+ [including the GNU Public Licence.]
+
+
+
+
+
+
+
+PD
+
+This is a placeholder for the Public Domain License
+
+
+
+Python-2.0
+
+
+PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
+--------------------------------------------
+
+1. This LICENSE AGREEMENT is between the Python Software Foundation
+("PSF"), and the Individual or Organization ("Licensee") accessing and
+otherwise using this software ("Python") in source or binary form and
+its associated documentation.
+
+2. Subject to the terms and conditions of this License Agreement, PSF
+hereby grants Licensee a nonexclusive, royalty-free, world-wide
+license to reproduce, analyze, test, perform and/or display publicly,
+prepare derivative works, distribute, and otherwise use Python
+alone or in any derivative version, provided, however, that PSF`s
+License Agreement and PSF`s notice of copyright, i.e., "Copyright (c)
+2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights
+Reserved" are retained in Python alone or in any derivative version
+prepared by Licensee.
+
+3. In the event Licensee prepares a derivative work that is based on
+or incorporates Python or any part thereof, and wants to make
+the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to Python.
+
+4. PSF is making Python available to Licensee on an "AS IS"
+basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
+FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
+A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
+OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+7. Nothing in this License Agreement shall be deemed to create any
+relationship of agency, partnership, or joint venture between PSF and
+Licensee. This License Agreement does not grant permission to use PSF
+trademarks or trade name in a trademark sense to endorse or promote
+products or services of Licensee, or any third party.
+
+8. By copying, installing or otherwise using Python, Licensee
+agrees to be bound by the terms and conditions of this License
+Agreement.
+
+BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
+-------------------------------------------
+
+BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
+
+1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
+office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
+Individual or Organization ("Licensee") accessing and otherwise using
+this software in source or binary form and its associated
+documentation ("the Software").
+
+2. Subject to the terms and conditions of this BeOpen Python License
+Agreement, BeOpen hereby grants Licensee a non-exclusive,
+royalty-free, world-wide license to reproduce, analyze, test, perform
+and/or display publicly, prepare derivative works, distribute, and
+otherwise use the Software alone or in any derivative version,
+provided, however, that the BeOpen Python License is retained in the
+Software, alone or in any derivative version prepared by Licensee.
+
+3. BeOpen is making the Software available to Licensee on an "AS IS"
+basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
+SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
+AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
+DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+5. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+6. This License Agreement shall be governed by and interpreted in all
+respects by the law of the State of California, excluding conflict of
+law provisions. Nothing in this License Agreement shall be deemed to
+create any relationship of agency, partnership, or joint venture
+between BeOpen and Licensee. This License Agreement does not grant
+permission to use BeOpen trademarks or trade names in a trademark
+sense to endorse or promote products or services of Licensee, or any
+third party. As an exception, the "BeOpen Python" logos available at
+http://www.pythonlabs.com/logos.html may be used according to the
+permissions granted on that web page.
+
+7. By copying, installing or otherwise using the software, Licensee
+agrees to be bound by the terms and conditions of this License
+Agreement.
+
+CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
+---------------------------------------
+
+1. This LICENSE AGREEMENT is between the Corporation for National
+Research Initiatives, having an office at 1895 Preston White Drive,
+Reston, VA 20191 ("CNRI"), and the Individual or Organization
+("Licensee") accessing and otherwise using Python 1.6.1 software in
+source or binary form and its associated documentation.
+
+2. Subject to the terms and conditions of this License Agreement, CNRI
+hereby grants Licensee a nonexclusive, royalty-free, world-wide
+license to reproduce, analyze, test, perform and/or display publicly,
+prepare derivative works, distribute, and otherwise use Python 1.6.1
+alone or in any derivative version, provided, however, that CNRI`s
+License Agreement and CNRI`s notice of copyright, i.e., "Copyright (c)
+1995-2001 Corporation for National Research Initiatives; All Rights
+Reserved" are retained in Python 1.6.1 alone or in any derivative
+version prepared by Licensee. Alternately, in lieu of CNRI`s License
+Agreement, Licensee may substitute the following text (omitting the
+quotes): "Python 1.6.1 is made available subject to the terms and
+conditions in CNRI`s License Agreement. This Agreement together with
+Python 1.6.1 may be located on the Internet using the following
+unique, persistent identifier (known as a handle): 1895.22/1013. This
+Agreement may also be obtained from a proxy server on the Internet
+using the following URL: http://hdl.handle.net/1895.22/1013".
+
+3. In the event Licensee prepares a derivative work that is based on
+or incorporates Python 1.6.1 or any part thereof, and wants to make
+the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to Python 1.6.1.
+
+4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
+basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+
+5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
+1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
+A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
+OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+
+7. This License Agreement shall be governed by the federal
+intellectual property law of the United States, including without
+limitation the federal copyright law, and, to the extent such
+U.S. federal law does not apply, by the law of the Commonwealth of
+Virginia, excluding Virginia`s conflict of law provisions.
+Notwithstanding the foregoing, with regard to derivative works based
+on Python 1.6.1 that incorporate non-separable material that was
+previously distributed under the GNU General Public License (GPL), the
+law of the Commonwealth of Virginia shall govern this License
+Agreement only as to issues arising under or with respect to
+Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
+License Agreement shall be deemed to create any relationship of
+agency, partnership, or joint venture between CNRI and Licensee. This
+License Agreement does not grant permission to use CNRI trademarks or
+trade name in a trademark sense to endorse or promote products or
+services of Licensee, or any third party.
+
+8. By clicking on the "ACCEPT" button where indicated, or by copying,
+installing or otherwise using Python 1.6.1, Licensee agrees to be
+bound by the terms and conditions of this License Agreement.
+
+ACCEPT
+
+CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
+--------------------------------------------------
+
+Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
+The Netherlands. All rights reserved.
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted,
+provided that the above copyright notice appear in all copies and that
+both that copyright notice and this permission notice appear in
+supporting documentation, and that the name of Stichting Mathematisch
+Centrum or CWI not be used in advertising or publicity pertaining to
+distribution of the software without specific, written prior
+permission.
+
+STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
+THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
+FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
+OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+
+
+
+SAX-PD
+
+
+Copyright Status for SAX
+
+SAX is free!
+
+In fact, it`s not possible to own a license to SAX, since it`s been placed in the
+public domain.
+
+No Warranty
+
+Because SAX is released to the public domain, there is no warranty for the design or
+for the software implementation, to the extent permitted by applicable law. Except
+when otherwise stated in writing the copyright holders and/or other parties provide
+SAX "as is" without warranty of any kind, either expressed or implied, including, but
+not limited to, the implied warranties of merchantability and fitness for a particular
+purpose. The entire risk as to the quality and performance of SAX is with you. Should
+SAX prove defective, you assume the cost of all necessary servicing, repair or
+correction.
+
+In no event unless required by applicable law or agreed to in writing will any
+copyright holder, or any other party who may modify and/or redistribute SAX, be liable
+to you for damages, including any general, special, incidental or consequential
+damages arising out of the use or inability to use SAX (including but not limited to
+loss of data or data being rendered inaccurate or losses sustained by you or third
+parties or a failure of the SAX to operate with any other programs), even if such
+holder or other party has been advised of the possibility of such damages.
+
+Copyright Disclaimers
+
+This page includes statements to that effect by David Megginson, who would have been
+able to claim copyright for the original work.
+
+SAX 1.0
+
+Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of
+the XML-DEV mailing list, is hereby released into the public domain.
+
+No one owns SAX: you may use it freely in both commercial and non-commercial
+applications, bundle it with your software distribution, include it on a CD-ROM, list
+the source code in a book, mirror the documentation at your own web site, or use it in
+any other way you see fit.
+
+David Megginson, Megginson Technologies Ltd.
+1998-05-11
+
+SAX 2.0
+
+I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release
+all of the SAX 2.0 source code, compiled code, and documentation contained in this
+distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of
+fitness for any purpose.
+
+David Megginson, Megginson Technologies Ltd.
+2000-05-05
+
+
+
+
+SMAIL_GPL
+
+This is the Debian GNU/Linux package debianutils.
+
+It is an original Debian package. Programs in it were maintained by
+Guy Maor <maor@debian.org>, and are now maintained by Clint Adams
+<schizo@debian.org>.
+
+All its programs except readlink, savelog, and which may be
+redistributed under the terms of the GNU GPL, Version 2 or later,
+found on Debian systems in the file /usr/share/common-licenses/GPL.
+
+which is in the public domain.
+
+readlink is Copyright (c) 1997 Kenneth Stailey, and may also be
+distributed under the terms of the BSD copyright.
+
+savelog may be redistributed under the following terms: (The rest of
+this file consists of savelog's distribution terms.)
+
+#ident "@(#)smail:RELEASE-3_2:COPYING,v 1.2 1996/06/14 18:59:10 woods Exp"
+
+ SMAIL GENERAL PUBLIC LICENSE
+ (Clarified 11 Feb 1988)
+
+ Copyright (C) 1988 Landon Curt Noll & Ronald S. Karr
+ Copyright (C) 1992 Ronald S. Karr
+ Copyleft (GNU) 1988 Landon Curt Noll & Ronald S. Karr
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license, but changing it is not allowed. You can also
+ use this wording to make the terms for other programs.
+
+ The license agreements of most software companies keep you at the
+mercy of those companies. By contrast, our general public license is
+intended to give everyone the right to share SMAIL. To make sure that
+you get the rights we want you to have, we need to make restrictions
+that forbid anyone to deny you these rights or to ask you to surrender
+the rights. Hence this license agreement.
+
+ Specifically, we want to make sure that you have the right to give
+away copies of SMAIL, that you receive source code or else can get it
+if you want it, that you can change SMAIL or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To make sure that everyone has such rights, we have to forbid you to
+deprive anyone else of these rights. For example, if you distribute
+copies of SMAIL, you must give the recipients all the rights that you
+have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+ Also, for our own protection, we must make certain that everyone
+finds out that there is no warranty for SMAIL. If SMAIL is modified by
+someone else and passed on, we want its recipients to know that what
+they have is not what we distributed, so that any problems introduced
+by others will not reflect on our reputation.
+
+ Therefore we (Landon Curt Noll and Ronald S. Karr) make the following
+terms which say what you must do to be allowed to distribute or change
+SMAIL.
+
+
+ COPYING POLICIES
+
+ 1. You may copy and distribute verbatim copies of SMAIL source code
+as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy a valid copyright notice "Copyright
+(C) 1988 Landon Curt Noll & Ronald S. Karr" (or with whatever year is
+appropriate); keep intact the notices on all files that refer to this
+License Agreement and to the absence of any warranty; and give any
+other recipients of the SMAIL program a copy of this License
+Agreement along with the program. You may charge a distribution fee
+for the physical act of transferring a copy.
+
+ 2. You may modify your copy or copies of SMAIL or any portion of it,
+and copy and distribute such modifications under the terms of
+Paragraph 1 above, provided that you also do the following:
+
+ a) cause the modified files to carry prominent notices stating
+ that you changed the files and the date of any change; and
+
+ b) cause the whole of any work that you distribute or publish,
+ that in whole or in part contains or is a derivative of SMAIL or
+ any part thereof, to be licensed at no charge to all third
+ parties on terms identical to those contained in this License
+ Agreement (except that you may choose to grant more extensive
+ warranty protection to some or all third parties, at your option).
+
+ c) You may charge a distribution fee for the physical act of
+ transferring a copy, and you may at your option offer warranty
+ protection in exchange for a fee.
+
+Mere aggregation of another unrelated program with this program (or its
+derivative) on a volume of a storage or distribution medium does not bring
+the other program under the scope of these terms.
+
+ 3. You may copy and distribute SMAIL (or a portion or derivative of it,
+under Paragraph 2) in object code or executable form under the terms of
+Paragraphs 1 and 2 above provided that you also do one of the following:
+
+ a) accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ b) accompany it with a written offer, valid for at least three
+ years, to give any third party free (except for a nominal
+ shipping charge) a complete machine-readable copy of the
+ corresponding source code, to be distributed under the terms of
+ Paragraphs 1 and 2 above; or,
+
+ c) accompany it with the information you received as to where the
+ corresponding source code may be obtained. (This alternative is
+ allowed only for non-commercial distribution and only if you
+ received the program in object code or executable form alone.)
+
+For an executable file, complete source code means all the source code for
+all modules it contains; but, as a special exception, it need not include
+source code for modules which are standard libraries that accompany the
+operating system on which the executable file runs.
+
+ 4. You may not copy, sublicense, distribute or transfer SMAIL
+except as expressly provided under this License Agreement. Any attempt
+otherwise to copy, sublicense, distribute or transfer SMAIL is void and
+your rights to use the program under this License agreement shall be
+automatically terminated. However, parties who have received computer
+software programs from you with this License Agreement will not have
+their licenses terminated so long as such parties remain in full compliance.
+
+ 5. If you wish to incorporate parts of SMAIL into other free
+programs whose distribution conditions are different, write to Landon
+Curt Noll & Ronald S. Karr via the Free Software Foundation at 51
+Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. We have not yet
+worked out a simple rule that can be stated here, but we will often
+permit this. We will be guided by the two goals of preserving the
+free status of all derivatives of our free software and of promoting
+the sharing and reuse of software.
+
+Your comments and suggestions about our licensing policies and our
+software are welcome! This contract was based on the contract made by
+the Free Software Foundation. Please contact the Free Software
+Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
+USA, or call (617) 542-5942 for details on copylefted material in
+general.
+
+ NO WARRANTY
+
+ BECAUSE SMAIL IS LICENSED FREE OF CHARGE, WE PROVIDE ABSOLUTELY NO
+WARRANTY, TO THE EXTENT PERMITTED BY APPLICABLE STATE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING, LANDON CURT NOLL & RONALD S. KARR AND/OR
+OTHER PARTIES PROVIDE SMAIL "AS IS" WITHOUT WARRANTY OF ANY KIND,
+EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF SMAIL IS WITH
+YOU. SHOULD SMAIL PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
+NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL LANDON CURT NOLL &
+RONALD S. KARR AND/OR ANY OTHER PARTY WHO MAY MODIFY AND REDISTRIBUTE
+SMAIL AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+LOST PROFITS, LOST MONIES, OR OTHER SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
+(INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
+INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE
+PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) SMAIL, EVEN IF YOU HAVE
+BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY
+ANY OTHER PARTY.
+
+
+
+SUN
+
+SUN MICROSYSTEMS, INC. THROUGH ITS SUN MICROSYSTEMS LABORATORIES
+DIVISION ("SUN") WILL LICENSE THIS SOFTWARE AND THE ACCOMPANYING
+DOCUMENTATION TO YOU (a "Licensee") ONLY ON YOUR ACCEPTANCE OF ALL
+THE TERMS SET FORTH BELOW.
+
+Sun grants Licensee a non-exclusive, royalty-free right to download,
+install, compile, use, copy and distribute the Software, modify or
+otherwise create derivative works from the Software (each, a
+"Modification") and distribute any Modification in source code and/or
+binary code form to its customers with a license agreement containing
+these terms and noting that the Software has been modified. The
+Software is copyrighted by Sun and other third parties and Licensee
+shall retain and reproduce all copyright and other notices presently
+on the Software. As between Sun and Licensee, Sun is the sole owner of
+all rights in and to the Software other than the limited rights
+granted to Licensee herein; Licensee will own its Modifications,
+expressly subject to Sun's continuing ownership of the
+Software. Licensee will, at its expense, defend and indemnify Sun and
+its licensors from and against any third party claims, including costs
+and reasonable attorneys' fees, and be wholly responsible for any
+liabilities arising out of or related to Licensee's development, use
+or distribution of the Software or Modifications. Any distribution of
+the Software and Modifications must comply with all applicable United
+States export control laws.
+
+THE SOFTWARE IS BEING PROVIDED TO LICENSEE "AS IS" AND ALL EXPRESS OR
+IMPLIED CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
+ARE DISCLAIMED. IN NO EVENT WILL SUN BE LIABLE HEREUNDER FOR ANY
+DIRECT DAMAGES OR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES OF ANY KIND.
+
+
+
+Sleepycat
+
+
+The Sleepycat License
+Copyright (c) 1990-1999
+Sleepycat Software. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Redistributions in any form must be accompanied by information on
+how to obtain complete source code for the DB software and any
+accompanying software that uses the DB software. The source code
+must either be included in the distribution or be available for no
+more than the cost of distribution plus a nominal fee, and must be
+freely redistributable under reasonable conditions. For an
+executable file, complete source code means the source code for all
+modules it contains. It does not include source code for modules or
+files that typically accompany the major components of the operating
+system on which the executable file runs.
+THIS SOFTWARE IS PROVIDED BY SLEEPYCAT SOFTWARE ``AS IS`` AND ANY EXPRESS
+OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
+NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL SLEEPYCAT SOFTWARE
+BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
+THE POSSIBILITY OF SUCH DAMAGE.
+
+Copyright (c) 1990, 1993, 1994, 1995
+The Regents of the University of California. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Neither the name of the University nor the names of its contributors
+may be used to endorse or promote products derived from this software
+without specific prior written permission.
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS`` AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+Copyright (c) 1995, 1996
+The President and Fellows of Harvard University. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+Neither the name of the University nor the names of its contributors
+may be used to endorse or promote products derived from this software
+without specific prior written permission.
+THIS SOFTWARE IS PROVIDED BY HARVARD AND ITS CONTRIBUTORS ``AS IS`` AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL HARVARD OR ITS CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+
+
+
+UCB
+
+ Copyright (c) 1987, 1989, 1990, 1991, 1992, 1993, 1994
+ The Regents of the University of California. All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ 3. Neither the name of the University nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ SUCH DAMAGE.
+
+
+
+Unicode
+
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright 1991-2015 Unicode, Inc. All rights reserved.
+Distributed under the Terms of Use in
+http://www.unicode.org/copyright.html.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Unicode data files and any associated documentation
+(the "Data Files") or Unicode software and any associated documentation
+(the "Software") to deal in the Data Files or Software
+without restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, and/or sell copies of
+the Data Files or Software, and to permit persons to whom the Data Files
+or Software are furnished to do so, provided that
+(a) this copyright and permission notice appear with all copies
+of the Data Files or Software,
+(b) this copyright and permission notice appear in associated
+documentation, and
+(c) there is clear notice in each modified Data File or in the Software
+as well as in the documentation associated with the Data File(s) or
+Software that the data or software has been modified.
+
+THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
+ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT OF THIRD PARTY RIGHTS.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
+NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
+DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
+DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+PERFORMANCE OF THE DATA FILES OR SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder
+shall not be used in advertising or otherwise to promote the sale,
+use or other dealings in these Data Files or Software without prior
+written authorization of the copyright holder.
+
+
+
+W3C
+
+
+W3C SOFTWARE NOTICE AND LICENSE
+This work (and included software, documentation such as READMEs, or other related
+items) is being provided by the copyright holders under the following license.
+License
+By obtaining, using and/or copying this work, you (the licensee) agree that you have
+read, understood, and will comply with the following terms and conditions.
+Permission to copy, modify, and distribute this software and its documentation, with
+or without modification, for any purpose and without fee or royalty is hereby granted,
+provided that you include the following on ALL copies of the software and
+documentation or portions thereof, including modifications:
+The full text of this NOTICE in a location viewable to users of the redistributed or
+derivative work.
+Any pre-existing intellectual property disclaimers, notices, or terms and conditions.
+If none exist, the W3C Software Short Notice should be included (hypertext is
+preferred, text is permitted) within the body of any redistributed or derivative code.
+Notice of any changes or modifications to the files, including the date changes were
+made. (We recommend you provide URIs to the location from which the code is derived.)
+Disclaimers
+THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
+REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
+WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF
+THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
+TRADEMARKS OR OTHER RIGHTS.
+COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
+The name and trademarks of copyright holders may NOT be used in advertising or
+publicity pertaining to the software without specific, written prior permission. Title
+to copyright in this software and any associated documentation will at all times
+remain with copyright holders.
+Notes
+This version: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
+This formulation of W3C`s notice and license became active on December 31 2002. This
+version removes the copyright ownership notice such that this license can be used with
+materials other than those owned by the W3C, reflects that ERCIM is now a host of the
+W3C, includes references to this specific dated version of the license, and removes
+the ambiguous grant of "use". Otherwise, this version is the same as the previous
+version and is written so as to preserve the Free Software Foundation`s assessment of
+GPL compatibility and OSI`s certification under the Open Source Definition.
+
+
+
+
+ZPL-2.1
+
+
+ZPL 2.1
+Zope Public License (ZPL) Version 2.1
+
+A copyright notice accompanies this license document that identifies the copyright
+holders.
+
+This license has been certified as open source. It has also been designated as GPL
+compatible by the Free Software Foundation (FSF).
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+Redistributions in source code must retain the accompanying copyright notice, this
+list of conditions, and the following disclaimer.
+Redistributions in binary form must reproduce the accompanying copyright notice, this
+list of conditions, and the following disclaimer in the documentation and/or other
+materials provided with the distribution.
+Names of the copyright holders must not be used to endorse or promote products derived
+from this software without prior written permission from the copyright holders.
+The right to distribute this software or to use it for any purpose does not give you
+the right to use Servicemarks (sm) or Trademarks (tm) of the copyright holders. Use of
+them is covered by separate agreement with the copyright holders.
+If any files are modified, you must cause the modified files to carry prominent
+notices stating that you changed the files and the date of any change.
+Disclaimer
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS`` AND ANY EXPRESSED OR
+IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
+THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+
+
+
+Zlib
+
+
+zlib License
+
+
+ This software is provided `as-is`, without any express or implied
+ warranty. In no event will the authors be held liable for any damages
+ arising from the use of this software.
+
+ Permission is granted to anyone to use this software for any purpose,
+ including commercial applications, and to alter it and redistribute it
+ freely, subject to the following restrictions:
+
+ 1. The origin of this software must not be misrepresented; you must not
+ claim that you wrote the original software. If you use this software
+ in a product, an acknowledgment in the product documentation would be
+ appreciated but is not required.
+ 2. Altered source versions must be plainly marked as such, and must not be
+ misrepresented as being the original software.
+ 3. This notice may not be removed or altered from any source distribution.
+
+
+
+
+
+copyleft-next-0.3.0
+
+ copyleft-next 0.3.0 ("this License")
+ Release date: 2013-05-16
+
+1. License Grants; No Trademark License
+
+ Subject to the terms of this License, I grant You:
+
+ a) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
+ copyright license, to reproduce, Distribute, prepare derivative works
+ of, publicly perform and publicly display My Work.
+
+ b) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
+ patent license under Licensed Patents to make, have made, use, sell,
+ offer for sale, and import Covered Works.
+
+ This License does not grant any rights in My name, trademarks, service
+ marks, or logos.
+
+2. Distribution: General Conditions
+
+ You may Distribute Covered Works, provided that You (i) inform
+ recipients how they can obtain a copy of this License; (ii) satisfy the
+ applicable conditions of sections 3 through 6; and (iii) preserve all
+ Legal Notices contained in My Work (to the extent they remain
+ pertinent). "Legal Notices" means copyright notices, license notices,
+ license texts, and author attributions, but does not include logos,
+ other graphical images, trademarks or trademark legends.
+
+3. Conditions for Distributing Derived Works; Outbound GPL Compatibility
+
+ If You Distribute a Derived Work, You must license the entire Derived
+ Work as a whole under this License, with prominent notice of such
+ licensing. This condition may not be avoided through such means as
+ separate Distribution of portions of the Derived Work. You may
+ additionally license the Derived Work under the GPL, so that the
+ recipient may further Distribute the Derived Work under either this
+ License or the GPL.
+
+4. Condition Against Further Restrictions; Inbound License Compatibility
+
+ When Distributing a Covered Work, You may not impose further
+ restrictions on the exercise of rights in the Covered Work granted under
+ this License. This condition is not excused merely because such
+ restrictions result from Your compliance with conditions or obligations
+ extrinsic to this License (such as a court order or an agreement with a
+ third party).
+
+ However, You may Distribute a Covered Work incorporating material
+ governed by a license that is both OSI-Approved and FSF-Free as of the
+ release date of this License, provided that Your Distribution complies
+ with such other license.
+
+5. Conditions for Distributing Object Code
+
+ You may Distribute an Object Code form of a Covered Work, provided that
+ you accompany the Object Code with a URL through which the Corresponding
+ Source is made available, at no charge, by some standard or customary
+ means of providing network access to source code.
+
+ If you Distribute the Object Code in a physical product or tangible
+ storage medium ("Product"), the Corresponding Source must be available
+ through such URL for two years from the date of Your most recent
+ Distribution of the Object Code in the Product. However, if the Product
+ itself contains or is accompanied by the Corresponding Source (made
+ available in a customarily accessible manner), You need not also comply
+ with the first paragraph of this section.
+
+ Each recipient of the Covered Work from You is an intended third-party
+ beneficiary of this License solely as to this section 5, with the right
+ to enforce its terms.
+
+6. Symmetrical Licensing Condition for Upstream Contributions
+
+ If You Distribute a work to Me specifically for inclusion in or
+ modification of a Covered Work (a "Patch"), and no explicit licensing
+ terms apply to the Patch, You license the Patch under this License, to
+ the extent of Your copyright in the Patch. This condition does not
+ negate the other conditions of this License, if applicable to the Patch.
+
+7. Nullification of Copyleft/Proprietary Dual Licensing
+
+ If I offer to license, for a fee, a Covered Work under terms other than
+ a license that is OSI-Approved or FSF-Free as of the release date of this
+ License or a numbered version of copyleft-next released by the
+ Copyleft-Next Project, then the license I grant You under section 1 is no
+ longer subject to the conditions in sections 2 through 5.
+
+8. Copyleft Sunset
+
+ The conditions in sections 2 through 5 no longer apply once fifteen
+ years have elapsed from the date of My first Distribution of My Work
+ under this License.
+
+9. Pass-Through
+
+ When You Distribute a Covered Work, the recipient automatically receives
+ a license to My Work from Me, subject to the terms of this License.
+
+10. Termination
+
+ Your license grants under section 1 are automatically terminated if You
+
+ a) fail to comply with the conditions of this License, unless You cure
+ such noncompliance within thirty days after becoming aware of it, or
+
+ b) initiate a patent infringement litigation claim (excluding
+ declaratory judgment actions, counterclaims, and cross-claims)
+ alleging that any part of My Work directly or indirectly infringes
+ any patent.
+
+ Termination of Your license grants extends to all copies of Covered
+ Works You subsequently obtain. Termination does not terminate the
+ rights of those who have received copies or rights from You subject to
+ this License.
+
+ To the extent permission to make copies of a Covered Work is necessary
+ merely for running it, such permission is not terminable.
+
+11. Later License Versions
+
+ The Copyleft-Next Project may release new versions of copyleft-next,
+ designated by a distinguishing version number ("Later Versions").
+ Unless I explicitly remove the option of Distributing Covered Works
+ under Later Versions, You may Distribute Covered Works under any Later
+ Version.
+
+** 12. No Warranty **
+** **
+** My Work is provided "as-is", without warranty. You bear the risk **
+** of using it. To the extent permitted by applicable law, each **
+** Distributor of My Work excludes the implied warranties of title, **
+** merchantability, fitness for a particular purpose and **
+** non-infringement. **
+
+** 13. Limitation of Liability **
+** **
+** To the extent permitted by applicable law, in no event will any **
+** Distributor of My Work be liable to You for any damages **
+** whatsoever, whether direct, indirect, special, incidental, or **
+** consequential damages, whether arising under contract, tort **
+** (including negligence), or otherwise, even where the Distributor **
+** knew or should have known about the possibility of such damages. **
+
+14. Severability
+
+ The invalidity or unenforceability of any provision of this License
+ does not affect the validity or enforceability of the remainder of
+ this License. Such provision is to be reformed to the minimum extent
+ necessary to make it valid and enforceable.
+
+15. Definitions
+
+ "Copyleft-Next Project" means the project that maintains the source
+ code repository at <https://gitorious.org/copyleft-next/> as of the
+ release date of this License.
+
+ "Corresponding Source" of a Covered Work in Object Code form means (i)
+ the Source Code form of the Covered Work; (ii) all scripts,
+ instructions and similar information that are reasonably necessary for
+ a skilled developer to generate such Object Code from the Source Code
+ provided under (i); and (iii) a list clearly identifying all Separate
+ Works (other than those provided in compliance with (ii)) that were
+ specifically used in building and (if applicable) installing the
+ Covered Work (for example, a specified proprietary compiler including
+ its version number). Corresponding Source must be machine-readable.
+
+ "Covered Work" means My Work or a Derived Work.
+
+ "Derived Work" means a work of authorship that copies from, modifies,
+ adapts, is based on, is a derivative work of, transforms, translates or
+ contains all or part of My Work, such that copyright permission is
+ required. The following are not Derived Works: (i) Mere Aggregation;
+ (ii) a mere reproduction of My Work; and (iii) if My Work fails to
+ explicitly state an expectation otherwise, a work that merely makes
+ reference to My Work.
+
+ "Distribute" means to distribute, transfer or make a copy available to
+ someone else, such that copyright permission is required.
+
+ "Distributor" means Me and anyone else who Distributes a Covered Work.
+
+ "FSF-Free" means classified as 'free' by the Free Software Foundation.
+
+ "GPL" means a version of the GNU General Public License or the GNU
+ Affero General Public License.
+
+ "I"/"Me"/"My" refers to the individual or legal entity that places My
+ Work under this License. "You"/"Your" refers to the individual or legal
+ entity exercising rights in My Work under this License. A legal entity
+ includes each entity that controls, is controlled by, or is under
+ common control with such legal entity. "Control" means (a) the power to
+ direct the actions of such legal entity, whether by contract or
+ otherwise, or (b) ownership of more than fifty percent of the
+ outstanding shares or beneficial ownership of such legal entity.
+
+ "Licensed Patents" means all patent claims licensable royalty-free by
+ Me, now or in the future, that are necessarily infringed by making,
+ using, or selling My Work, and excludes claims that would be infringed
+ only as a consequence of further modification of My Work.
+
+ "Mere Aggregation" means an aggregation of a Covered Work with a
+ Separate Work.
+
+ "My Work" means the particular work of authorship I license to You
+ under this License.
+
+ "Object Code" means any form of a work that is not Source Code.
+
+ "OSI-Approved" means approved as 'Open Source' by the Open Source
+ Initiative.
+
+ "Separate Work" means a work that is separate from and independent of a
+ particular Covered Work and is not by its nature an extension or
+ enhancement of the Covered Work, and/or a runtime library, standard
+ library or similar component that is used to generate an Object Code
+ form of a Covered Work.
+
+ "Source Code" means the preferred form of a work for making
+ modifications to it.
+
+
+
+tcl
+
+This software is copyrighted by the Regents of the University of
+California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
+Corporation and other parties. The following terms apply to all files
+associated with the software unless explicitly disclaimed in
+individual files.
+
+The authors hereby grant permission to use, copy, modify, distribute,
+and license this software and its documentation for any purpose, provided
+that existing copyright notices are retained in all copies and that this
+notice is included verbatim in any distributions. No written agreement,
+license, or royalty fee is required for any of the authorized uses.
+Modifications to this software may be copyrighted by their authors
+and need not follow the licensing terms described here, provided that
+the new terms are clearly indicated on the first page of each file where
+they apply.
+
+IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
+FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
+DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
+IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
+NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
+MODIFICATIONS.
+
+GOVERNMENT USE: If you are acquiring this software on behalf of the
+U.S. government, the Government shall have only "Restricted Rights"
+in the software and related documentation as defined in the Federal
+Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
+are acquiring the software on behalf of the Department of Defense, the
+software shall be classified as "Commercial Computer Software" and the
+Government shall have only "Restricted Rights" as defined in Clause
+252.227-7014 (b) (3) of DFARs. Notwithstanding the foregoing, the
+authors grant the U.S. Government and others acting in its behalf
+permission to use and distribute the software in accordance with the
+terms specified in this license.
+
+
+
+
+ Proprietary Licenses
+
+Enea
+
+ Copyright (C) 2006 by Enea.
+ All rights reserved.
+
+ This Software is furnished under a software license agreement and
+ may be used only in accordance with the terms of such agreement.
+ Any other use or reproduction is prohibited. No title to and
+ ownership of the Software is hereby transferred.
+
+ PROPRIETARY NOTICE
+ This Software consists of confidential information.
+ Trade secret law and copyright law protect this Software.
+ The above notice of copyright on this Software does not indicate
+ any actual or intended publication of such Software.
+
+
+
+
diff --git a/doc/book-enea-edge-runtime-open-source/swcomp.mk b/doc/book-enea-edge-runtime-open-source/swcomp.mk
new file mode 100644
index 0000000..cec1da3
--- /dev/null
+++ b/doc/book-enea-edge-runtime-open-source/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-runtime-open-source
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Runtime Open Source Report"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-edge-system-test-specification/doc/book.xml b/doc/book-enea-edge-system-test-specification/doc/book.xml
new file mode 100644
index 0000000..bcc2dcd
--- /dev/null
+++ b/doc/book-enea-edge-system-test-specification/doc/book.xml
@@ -0,0 +1,27 @@
+
+
+]>
+
+ Enea Edge System Test Specification
+
+ Release Version
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-system-test-specification/doc/configuration.xml b/doc/book-enea-edge-system-test-specification/doc/configuration.xml
new file mode 100644
index 0000000..62d9b72
--- /dev/null
+++ b/doc/book-enea-edge-system-test-specification/doc/configuration.xml
@@ -0,0 +1,53 @@
+
+
+ Configuration
+
+
+ Test Objects
+
+ The test objects for the Test Harness are the Enea Edge and
+ Enea Edge Management installations performed as indicated in the Components chapter of the .
+
+
+
+ Test Environment
+
+ To set up the required Test Harness environment please refer to
+ Getting Started with the Automation Framework
+ and Test Harness in the .
+
+
+
+ Preconditions and Execution
+
+ Please refer to section Prerequisites in the
+ and section Installation and Initial Setup in the
+
+ for more details.
+
+
+ Before running any test case, make sure the uCPE device(s) needed
+ have been added to the Enea Edge Management.
+
+
+ For detailed execution steps of the sample test cases included with
+ the Test Harness please see the following chapter.
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-system-test-specification/doc/overview.xml b/doc/book-enea-edge-system-test-specification/doc/overview.xml
new file mode 100644
index 0000000..07c5ef7
--- /dev/null
+++ b/doc/book-enea-edge-system-test-specification/doc/overview.xml
@@ -0,0 +1,109 @@
+
+
+ Overview
+
+ This document describes the Test Harness (TH) sample test cases for
+ the System Testing of Enea Edge, and the necessary environment setup
+ to run these tests successfully.
+
+
+ Definitions and Acronyms
+
+
+ Definitions
+
+
+
+
+
+
+ Component
+
+ Description
+
+
+
+
+
+ Enea Edge
+
+ The Enea Edge (with ODM) Runtime and the
+ Enea Edge Management.
+
+
+
+
+
+
+ Acronyms
+
+
+
+
+
+
+ Component
+
+ Description
+
+
+
+
+
+ AF
+
+ Automation Framework for Enea Edge.
+
+
+
+ JSON
+
+ JavaScript Object Notation.
+
+
+
+ NIC
+
+ Network Interface Card.
+
+
+
+ NFV
+
+ Network Functions Virtualization.
+
+
+
+ ODM
+
+ Enea Element On Device Management.
+
+
+
+ OVS
+
+ Open vSwitch.
+
+
+
+ TH
+
+ Test Harness for Enea Edge.
+
+
+
+ Enea Edge Management
+
+ Enea Universal Customer Premises Equipment Manager.
+
+
+
+ VNF
+
+ Virtualized Network Function.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-system-test-specification/doc/sample_test_cases.xml b/doc/book-enea-edge-system-test-specification/doc/sample_test_cases.xml
new file mode 100644
index 0000000..b1bfa1e
--- /dev/null
+++ b/doc/book-enea-edge-system-test-specification/doc/sample_test_cases.xml
@@ -0,0 +1,1804 @@
+
+
+ Sample Test Cases
+
+ The test cases specified in this chapter are implemented as a Sample
+ Test Suite included in the TH.
+
+
+ VNF, Device and Network Smoke Test Cases
+
+ The following is an automated test suite that acts as basic smoke
+ tests for Enea Edge, and as a sanity-check test suite for the AF and
+ TH.
+
+
+ VNF - Onboard a VNF Image
+
+ Description: Onboarding a VNF
+ Image into the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/onboardVNFImage.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/vnf/onboardVNFRaw.py
+
+
+
+ Preconditions:
+
+
+
+ Add the VNF Image in the vnf_image folder
+ in the QCOW2 format: <AF-TH-install-dir>/vnf_image/<VNF-Image-name>.qcow2
+
+
+
+ A VNF Image JSON configuration file is created:
+ <AF-TH-install-dir>/vnf_config/<VNF-Descriptor-name>/<VNF-Descriptor-name>.json Example: <AF-TH-install-dir>/vnf_config/fortigateImage/fortigateImage.json
+
+
+
+ Action: Run the
+ onboardVNFImage.yml Ansible Playbook with the
+ <VNF-Image-name> and the
+ <VNF-Descriptor-name> as extra-vars:
+ ansible-playbook playbooks/onboardVNFImage.yml -e "vnfb=<VNF-Image-name> \
+vnfd=<VNF-Descriptor-name>"
+
+ Result: Output of the test case
+ run using the Test Harness:# Onboard VNF Image task result
+<VNF-Descriptor-name> successfully onboarded! Note: The test will not fail if the VNF Image is
+ already onboarded. The output will instead contain: # debug <VNF-Descriptor-name> already onboarded!
+
+
+
+ VNF - Offboard a VNF
+
+ Description: Removing a VNF
+ Descriptor from the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/offboardVNF.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/vnf/offboardVNF.py
+
+
+
+ Precondition: The VNF has been
+ previously onboarded in the Enea Edge Management instance.
+
+ Action: Run the
+ offboardVNF.yml Ansible Playbook with the
+ <VNF-Descriptor-name> as extra-vars:
+ ansible-playbook playbooks/offboardVNF.yml -e "vnfd=<VNF-Descriptor-name>"
+
+ Result: Output of the test case
+ run using the Test Harness: # Remove Descriptor task result
+<VNF-Descriptor-name> was removed! Note: The test will not fail if the VNF
+ Descriptor does not exist. The output will instead contain:
+ # debug No Descriptor with name <VNF-Descriptor-name>!
+
+
+
+ Device - Add a device
+
+ Description: Adding a uCPE device
+ to the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/addDevice.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/addDevice.py
+
+
+
+ Precondition: A device JSON
+ configuration file must be created: <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json
+
+ Example: <AF-TH-install-dir>/lab_config/intelc3850-2/intelc3850-2.json
+
+ Action: Run the
+ addDevice.yml Ansible playbook with the
+ <Device-name> as extra-vars: ansible-playbook playbooks/addDevice.yml -e "device=<Device-name>"
+
+ Result: Output of the test case
+ run using the Test Harness: # Add Device task result
+<Device-name> device was added! Note: The test will not fail if the device
+ already exists. The output will instead contain: # debug
+<Device-name> device already exists!
+
+
+
+ Device - Upload a Edge image
+
+ Description: Upload a Edge
+ image file onto the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/uploadImage.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/uploadImage.py
+
+
+
+ Precondition: The image path must
+ already exist.
+
+ Action: Run the
+ uploadImage.yml Ansible playbook with the
+ <Image-path> and
+ <Upgrade-type> as extra-vars:
+
+ ansible-playbook playbooks/deleteUpgradeFile.yml -e \
+image_path="<Image-path>" -e upgrade_type="<Upgrade-type>"
+
+ Example: ansible-playbook playbooks/uploadImage.yml -e \
+image_path="/tmp/enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \
+upgrade_type="xeon_d"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ TASK [Upload NFVA image -- Run uploadImage.py module from automation_framework]
+localhost : ok=1 changed=1 unreachable=0 failed=0 Note: The test will fail if the image file has
+ already been uploaded.
+
+ TASK [Upload NFVA image -- Run uploadImage.py module from automation_framework]
+ok=0 changed=0 unreachable=0 failed=1
+
+# debug
+A file with the same name is already uploaded.
+
+
+
+ Device - Delete Upgraded File
+
+ Description: Deleting an uploaded
+ Edge image file from the Enea Edge Management. For details please refer
+ to:
+
+
+
+ <AF-TH-install-dir>/playbooks/deleteUpgradeFile.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/deleteUpgradeFile.py
+
+
+
+ Preconditions: The image file
+ must already be uploaded onto the Enea Edge Management.
+
+ Action: Run the
+ deleteUpgradeFile.yml Ansible Playbook with the
+ <Image-name> as extra-vars:ansible-playbook playbooks/deleteUpgradeFile.yml -e \
+image_name="<Image-name>"
+
+ Example: ansible-playbook playbooks/deleteUpgradeFile.yml -e \
+image_name="enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2"
+
+ Result: Output of the test case
+ run using the Test Harness:TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework]
+localhost : ok=1 changed=1 unreachable=0 failed=0
+ Note: The test will fail if the image
+ file does not exist: TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework]
+ok=0 changed=0 unreachable=0 failed=1
+
+# debug
+No oid found for '<image_name>' image name
+
+
+
+ Device - Clear information about upgrades of uCPE devices
+
+ Description: Clear information
+ about upgrades of uCPE devices. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/clearCompletedUpgradesInfo.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/clearCompletedUpgradesInfo.py
+
+
+
+ Preconditions: No preconditions
+ needed.
+
+ Action: Run the
+ clearCompletedUpgradesInfo.yml Ansible
+ Playbook:ansible-playbook playbooks/clearCompletedUpgradesInfo.yml
+
+ Result: Output of the test case
+ run using the Test Harness:TASK [Clear completed info about upgrading -- Run \
+clearCompletedUpgradesInfo.py module from automation framework]]
+localhost : ok=1 changed=1 unreachable=0 failed=0
+
+
+
+ Device - Install and Activate a Edge image
+
+ Description: Installing and
+ Activating a Edge image on a uCPE device from the Enea Edge Management.
+ For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/installAndActivate.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/installAndActivate.py
+
+
+
+ Preconditions:
+
+ The device must be previously added to the Enea Edge Management
+ instance.
+
+
+
+ The image file must already be uploaded onto the Enea Edge
+ Management.
+
+
+
+ Action: Run the
+ installAndActivate.yml Ansible Playbook with the
+ <Image-name> ,
+ <Upgrade-type> , and the
+ <Device-name> as extra-vars:ansible-playbook playbooks/installAndActivate.yml -e \
+image_name="<Image_name>" -e upgrade_type="<Upgrade_type>" -e \
+device="<Device-name>"
+
+ Example: ansible-playbook playbooks/installAndActivate.yml -e \
+image_name="enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \
+upgrade_type=xeon_d -e device=inteld1521-16"
+
+ Result: Output of the test case
+ run using the Test Harness:TASK \
+[Install And Activate -- Run installAndActivate.py module from automation_framework]
+localhost : ok=1 changed=1 unreachable=0 failed=0
+ Note: The test will fail if the image
+ has already been installed on the uCPE device:TASK \
+[Install And Activate -- Run installAndActivate.py module from automation_framework]
+ok=0 changed=0 unreachable=0 failed=1
+
+# debug
+Duplicate entry - Release already installed
+
+
+
+ Device - Upload, Install and Activate a Edge image on a
+ uCPE device
+
+ Description: Upload, install and
+ activate a Edge image on a uCPE device from the Enea Edge Management. For
+ details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/installNFVAImage.yml
+
+
+
+ The playbook imports the previously described
+ playbooks:
+
+
+
+ playbooks/waitDeviceUp.yml
+
+
+
+ playbook/uploadImage.yml
+
+
+
+ playbook/installAndActivate.yml
+
+
+
+ playbook/deleteUpgradeFile.yml
+
+
+
+ playbook/clearCompletedUpgradesInfo.yml
+
+
+
+
+
+ Preconditions:
+
+
+
+ The device has to be previously added to the Enea Edge Management
+ instance.
+
+
+
+ A device JSON configuration file must be created:
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json
+
+
+
+ Action: Run the
+ installNFVAImage.yml Ansible Playbook with the
+ <Image-path> ,
+ <Image-name> ,
+ <Upgrade-type> , and the
+ <Device-name> as extra-vars: ansible-playbook playbooks/installNFVAImage.yml -e \
+device="<Device-name>" -e image_path="<Image-path>" -e \
+image_name="<Image-name>" -e upgrade_type="<Upgrade-type>"
+
+ Example: ansible-playbook playbooks/installNFVAImage.yml -e \
+device="inteld1521-16" -e \
+image_path=/tmp/enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \
+image_name=enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \
+upgrade_type=xeon_d
+
+ Result: Output of the test case
+ run using the Test Harness:localhost : ok=1 changed=1 unreachable=0 failed=0
+ Note: The test will fail if the one
+ imported playbook fails:ok=0 changed=0 unreachable=0 failed=1
+
+
+
+ Device - Wait a Device
+
+ Description: Wait for a uCPE
+ device to connect to the Enea Edge Management. For details please refer
+ to:
+
+
+
+ <AF-TH-install-dir>/playbooks/waitDeviceUp.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/waitDeviceUp.py
+
+
+
+ Preconditions:
+
+
+
+ The device has to be previously added to the Enea Edge Management
+ instance.
+
+
+
+ The device JSON configuration file must exist:
+ <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json
+
+
+
+ Action: Run the
+ waitDeviceUp.yml Ansible Playbook with the
+ <Device-name> as extra-vars: ansible-playbook playbooks/waitDeviceUp.yml -e "device=<Device-name>"
+
+ Result: Output of the test case
+ run using the Test Harness:# Wait Device task result
+<Device-name> device is connected! Note: The test will fail if the device does not
+ exist or it is not connected.
+
+
+
+ Device - Remove a Device
+
+ Description: Removing a uCPE
+ device from the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/removeDevice.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/removeDevice.py
+
+
+
+ Preconditions:
+
+
+
+ The device has to be previously added to the Enea Edge Management
+ instance.
+
+
+
+ The device JSON configuration file must exist:
+ <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json
+
+
+
+ Action: Run the
+ removeDevice.yml Ansible Playbook with the
+ <Device-name> as extra-vars: ansible-playbook playbooks/removeDevice.yml -e "device=<Device-name>"
+
+ Result: Output of the test case
+ run using the Test Harness:# Remove Device task result
+<Device-name> device was removed! Note: The test will not fail if the device does
+ not exist. The output will contain: # debug
+<Device-name> device was not found!
+
+
+
+ Network - Bind a NIC
+
+ Description: Binding a physical
+ network interface (NIC) to a device. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/bindNIC.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/network/bindNetworkInterface.py
+
+
+
+ Preconditions:
+
+
+
+ A device must have been previously added and connected to the
+ Enea Edge Management instance.
+
+
+
+ A NIC JSON configuration file must exist: <AF-TH-install-dir>/lab_config/<Device-name>/<NIC>.json
+
+ Example: <AF-TH-install-dir>/lab_config/intelc3850-2/wan_nic.json
+<AF-TH-install-dir>/lab_config/intelc3850-2/lan_nic.json
+
+
+
+ Action: Run the
+ bindNIC.yml Ansible Playbook with the
+ <Device-name> and
+ <NIC> as extra-vars: ansible-playbook playbooks/bindNIC.yml -e "device=<Device-name> nic=<NIC>"
+
+ Result: Output of the test case
+ run using the Test Harness:# Bind NIC task result
+<NIC> binded successfully! Note: The test will not fail if the NIC is
+ already bound, it will be unbound and bound again with the provided
+ configuration.
+
+
+
+ Network - Unbind a NIC
+
+ Description: Unbinding a physical
+ network interface (NIC) from a device. For details please refer
+ to:
+
+
+
+ <AF-TH-install-dir>/playbooks/unbindNIC.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/network/unbindNetworkInterface.py
+
+
+
+ Preconditions:
+
+
+
+ A NIC is bound to a device in a Enea Edge Management instance.
+
+
+
+ A NIC JSON configuration file exists: <AF-TH-install-dir>/lab_config/<Device-name>/<NIC>.json
+
+
+
+ Action: Run the
+ unbindNIC.yml Ansible Playbook with the
+ <Device-name> and
+ <NIC> as extra-vars: ansible-playbook playbooks/unbindNIC.yml -e "device=<Device-name> nic=<NIC>"
+
+ Result: Output of the test case
+ run using the Test Harness: # Unbind NIC task result
+<NIC> unbinded! Note:
+ The test will not fail if the NIC is not bound. The output will instead
+ contain:# debug
+<NIC> is not binded!
+
+
+
+ Network - Create a Bridge
+
+ Description: Creating an OVS
+ network bridge on a uCPE device. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/addBridge.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/network/newNetworkBridge.py
+
+
+
+ Preconditions:
+
+ A NIC is bound to a device in a Enea Edge Management
+ instance.
+
+
+
+ A Bridge JSON configuration file exists:<AF-TH-install-dir>/lab_config/<Device-name>/<Bridge-name>.json
+
+ Example: <AF-TH-install-dir>/lab_config/intelc3850-2/wan_br.json
+<AF-TH-install-dir>/lab_config/intelc3850-2/lan_br.json
+
+
+
+ Action: Run the
+ addBridge.yml Ansible Playbook with the
+ <Device-name> and the
+ <Bridge-name> as extra-vars: ansible-playbook playbooks/addBridge.yml -e "device=<Device-name> bridge=<Bridge-name>"
+
+ Result: Output of the test case
+ run using the Test Harness: # Add Bridge task result
+<Bridge-name> network bridge was added! Note: The test will not fail if there already
+ exists a bridge with the same name. It will be deleted and the bridge
+ will be created again with the provided configuration.
+
+
+
+ Network - Remove a Bridge
+
+ Description: Removing an OVS
+ network bridge from a uCPE device. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/deleteBridge.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/network/delNetworkBridge.py
+
+
+
+ Preconditions:
+
+ A Bridge exists for a device in a Enea Edge Management
+ instance.
+
+
+
+ A Bridge JSON configuration file exists: <AF-TH-install-dir>/lab_config/<Device-name>/<Bridge-name>.json
+
+ Action: Run the
+ deleteBridge.yml Ansible Playbook with the
+ <Device-name> and the
+ <Bridge-name> as extra-vars: ansible-playbook playbooks/deleteBridge.yml -e "device=<Device-name> \
+bridge=<Bridge-name>"
+
+ Result: Output of the test case
+ run using the Test Harness: # Delete Bridge task result
+<Bridge-name> network bridge was deleted! Note: The test will not fail if the bridge does
+ not exist: # debug
+<Bridge-name> bridge not found!
+
+
+
+ Network - Configure a DPDK
+
+ Description: Enabling or
+ Disabling the DPDK support in OVS. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/configDPDK.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/network/configDPDK.py .
+
+
+
+ Precondition:
+
+ A device must have been previously added and connected to the Enea Edge
+ Management instance.
+
+ Action: Run the
+ configDPDK.yml Ansible Playbook with the
+ <Device-name> and
+ <enable/disable> as extra-vars:ansible-playbook playbooks/configDPDK.yml -e "device=<Device-name> \
+state=<enable/disable>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Configure DPDK task result
+DEBUG: Set DPDK state to <enable/disable> Note: DPDK use cannot be disabled if DPDK
+ interfaces are configured. The task will fail in this case.
+
+
+
+ Custom Scripts - Upload a Custom Script to the Enea Edge
+ Management
+
+ Description: Upload a Custom
+ Script to the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/uploadCustomScript.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/customScripts/upload.py .
+
+
+
+ Precondition:
+
+ <AF-TH-install-dir>/lab_config/customScripts
+ must contain a Custom Script file.
+
+ Action: Run the
+ uploadCustomScript.yml Ansible Playbook with the
+ <scriptName> and
+ <phase> as extra-vars: ansible-playbook playbooks/uploadCustomScript.yml -e "scriptName=<scriptName> \
+phase=
+<always-after-startup|once-after-startup|always-before-startup|once-before-startup>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Upload Custom Script task result
+DEBUG: "{{ scriptName }} was uploaded to Enea Edge Management!"
+
+
+
+ Custom Scripts - Upload a Custom Script from the Enea Edge Management to
+ a Device
+
+ Description: Upload a Custom
+ Script from the Enea Edge Management to a Device. For details please refer
+ to:
+
+
+
+ <AF-TH-install-dir>/playbooks/uploadCustomScriptOnDevice.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/customScripts/uploadOnDevice.py .
+
+
+
+ Preconditions:
+
+
+
+ A device must have been previously added and connected to the
+ Enea Edge Management instance.
+
+
+
+ A Custom Script must have been previously added to the Enea Edge
+ Management instance.
+
+
+
+ Action: Run the
+ uploadCustomScriptOnDevice.yml Ansible Playbook
+ with the <scriptName> ,
+ <phase> and
+ <deviceName> as extra-vars: ansible-playbook playbooks/uploadCustomScriptOnDevice.yml -e "scriptName=<scriptName> \
+phase=
+<always-after-startup|once-after-startup|always-before-startup|once-before-startup> \
+device=<deviceName>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Upload Custom Script on Device task result
+DEBUG: "{{ scriptName }} was uploaded to {{ device }}!"
+
+
+
+ Custom Scripts - Remove a Custom Script from the Enea Edge
+ Management
+
+ Description: Remove a Custom
+ Script from the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/removeCustomScript.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/customScripts/delete.py .
+
+
+
+ Precondition:
+
+ A Custom Script must have been previously added to the Enea Edge
+ Management.
+
+ Action: Run the
+ removeCustomScript.yml Ansible Playbook with the
+ <scriptName> and
+ <phase> as extra-vars: ansible-playbook playbooks/removeCustomScript.yml -e "scriptName=<scriptName> \
+phase=
+<always-after-startup|once-after-startup|always-before-startup|once-before-startup>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Remove Custom Script in phase from Enea Edge Management task result
+DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from Enea Edge Management!"
+
+
+
+ Custom Scripts - Remove a Custom Script from a Device
+
+ Description: Remove a Custom
+ Script from a Device. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/removeCustomScriptOnDevice.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/customScripts/deleteOnDevice.py .
+
+
+
+ Preconditions:
+
+
+
+ A device must have been previously added and connected to the
+ Enea Edge Management instance.
+
+
+
+ A Custom Script must have been previously added to the
+ Device.
+
+
+
+ Action: Run the
+ removeCustomScriptOnDevice.yml Ansible Playbook
+ with the <scriptName> ,
+ <phase> and
+ <deviceName> as extra-vars: ansible-playbook playbooks/removeCustomScriptOnDevice.yml -e "scriptName=<scriptName> \
+phase=
+<always-after-startup|once-after-startup|always-before-startup|once-before-startup> \
+device=<deviceName>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Remove Custom Script in phase from Device task result
+DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"
+
+
+
+ Offline Configuration - Add an Offline Configuration
+ Store
+
+ Description: Adding an Offline
+ Config Store to the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/addConfigStore.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/addConfigStore.py .
+
+
+
+ Precondition:
+
+ The Offline Configuration Store should not already exist on
+ the Enea Edge Management. If it exists, the test will report a
+ duplicate.
+
+
+
+ A store JSON file needs to exist: <AF-TH-install-dir>/lab_config/<device-name>/store.json
+
+
+
+ Action: Run the
+ addConfigStore.yml Ansible Playbook with the
+ <device-name> as extra-vars: ansible-playbook playbooks/addConfigStore.yml -e \
+"device=<device-name>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Add Config Store task result
+**********************************************************
+**********************************
+ * localhost - changed=False
+--------------------------------------------------
+ Config store for intelc3850-2 device was added!
+
+
+
+ Offline Configuration - Remove an Offline Configuration
+ Store
+
+ Description: Removing an Offline
+ Config Store from the Enea Edge Management. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/removeConfigStore.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/removeConfigStore.py .
+
+
+
+ Precondition:
+
+ The Offline Configuration Store the user wishes to remove should
+ exist in the Enea Edge Management. If it does not, the test will say so.
+
+ Action: Run the
+ removeConfigStore.yml Ansible Playbook with the
+ <store-name> as extra-vars: ansible-playbook playbooks/removeConfigStore.yml -e \
+"store=<store-name>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Remove Config Store task result **********************************
+*******************************************************
+ * localhost - changed=False
+ -- intelc3850-2 config store was removed! ---------
+
+
+
+ Offline Configuration - Add a network bridge to an Offline
+ Configuration Store
+
+ Description: Adding a network
+ bridge to an Offline Config Store in Enea Edge Management. For details please
+ refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/addOfflineBridge.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/network/newNetworkBridge.py .
+
+
+
+ Precondition:
+
+
+
+ The Offline Configuration Store should exist in the Enea Edge
+ Management. If it does not, the test will say so.
+
+
+
+ A Bridge JSON configuration file needs to exist:
+ <AF-TH-install-dir>/lab_config/<device-name>/<bridge-name>.json
+
+
+
+ Action: Run the
+ addOfflineBridge.yml Ansible Playbook with the
+ <device-name> ,
+ <store-name> and
+ <bridge-name> as extra-vars: ansible-playbook playbooks/addOfflineBridge.yml -e \
+"device=<device-name> store=<store-name> bridge=<bridge-name>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # debug *************************************************************
+******************************************************
+ * localhost - changed=False
+--------------------------------------------------
+ lan_br bridge already exists
+ --- will be deleted to create it with the provided configuration
+..
+# Add Bridge task result ********************************************
+******************************************************
+ * localhost - changed=False
+ -- lan_br network bridge was added! ------------
+
+ Note: if the bridge exists, it
+ will be removed and then re-added, as the output above shows.
+
+
+
+ Offline Configuration - Configure a DPDK
+
+ Description: Adding an "enable"
+ or "disable" DPDK state to an Offline Config Store. For details please
+ refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/configOfflineDPDK.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/network/configDPDK.py .
+
+
+
+ Precondition:
+
+ An empty Offline Configuration Store should exist in Enea Edge
+ Management.
+
+ Action: Run the
+ configOfflineDPDK.yml Ansible Playbook with the
+ <store-name> and
+ <enable/disable> as extra-vars:
+ ansible-playbook playbooks/configOfflineDPDK.yml -e \
+"store=<store-name> state=<enable/disable>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ DEBUG: Set DPDK state to disable
+INFO: Done
+
+ Note: the DPDK state cannot be
+ changed. Recreate the Offline Config Store and set the DPDK again if you
+ want to change the state.
+
+
+
+ Offline Configuration - Upload an offline configuration onto a
+ uCPE Device
+
+ Description: Uploading an offline
+ configuration to a uCPE Device. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/uploadConfigStore.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/uploadConfigStore.py .
+
+
+
+ Precondition:
+
+
+
+ The Offline Configuration Store should exist in the Enea Edge
+ Management.
+
+
+
+ The device should be connected to the Enea Edge Management.
+
+
+
+ Action: Run the
+ uploadConfigStore.yml Ansible Playbook with the
+ <store-name> and
+ <device-name> as extra-vars:
+
+ ansible-playbook playbooks/uploadConfigStore.yml -e \
+"store=<store-name> device=<device-name>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Upload Config Store task result ****************************
+ * localhost - changed=False ---------------
+ 2020-10-08 13:29:41,062 - INFO: Upload offline \
+ configuration to uCPE Device
+ 2020-10-08 13:30:01,315 - INFO: The '<store-name>' config \
+ store was successfully uploaded on device!
+ 2020-10-08 13:30:01,316 - INFO: Done
+
+
+
+ Offline Configuration - Get the offline configuration upload
+ status on the uCPE Device
+
+ Description: Get the offline
+ configuration upload status to a uCPE Device. For details please refer
+ to:
+
+
+
+ <AF-TH-install-dir>/playbooks/getUploadStatus.yml .
+
+
+
+ <AF-TH-install-dir>/automation_framework/device/getUploadStatus.py .
+
+
+
+ Precondition:
+
+
+
+ An upload of the offline configuration should be done on the
+ uCPE Device.
+
+
+
+ The device should be connected to the Enea Edge Management.
+
+
+
+ Action: Run the
+ getUploadStatus.yml Ansible Playbook with the
+ <device-name> as extra-vars:
+
+ ansible-playbook playbooks/getUploadStatus.yml -e \
+"device=<device-name>"
+
+ Result: Output of the test case
+ run using the Test Harness:
+
+ # Upload Config Store task result ****************************
+ * localhost - changed=False ---------------
+ 2020-10-08 14:13:24,422 - INFO: Get upload offline configure \
+ status on uCPE Device
+ 2020-10-08 14:13:24,521 - INFO: Successful: True
+ 2020-10-08 14:13:24,522 - INFO: Store name: <store-name>
+ 2020-10-08 14:13:24,523 - INFO: In progress: False
+ 2020-10-08 14:13:24,524 - INFO: A config store was successfully \
+ uploaded on device!
+ 2020-10-08 14:13:24,525 - INFO: Done
+
+
+
+
+ VNF Deployment and Lifecycle
+
+ The following details the automated suite that handles the testing
+ of the instantiation, lifecycle and destruction of a VNF for Enea Edge.
+
+
+ Instantiating a VNFI
+
+ Description: Creating a VNF
+ instance on a uCPE device. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/instantiateVNFI.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/vnf/instantiateVNFI.py
+
+
+
+ Preconditions:
+
+ A VNF Image is onboarded and a device is added and connected
+ to the Enea Edge Management. Depending on the VNF, other steps may be
+ required.
+
+
+
+ A VNFI JSON configuration file exists: <AF-TH-install-dir>/vnf_config/<VNF-Descriptor-name>/<VNFI-name>.json
+
+ Example: <AF-TH-install-dir>/vnf_config/fortigateImage/fortigateFWInstance.json
+
+
+
+ Action: Run the
+ instantiateVNFI.yml Ansible Playbook with the
+ <Device-name> ,
+ <VNF-Descriptor-name> and the
+ <VNFI-name> as extra-vars: ansible-playbook playbooks/instantiateVNFI.yml -e "device=<Device-name> \
+vnfd=<VNF-Descriptor-name> vnfi=<VNFI-name>"
+
+ Result: Output of the test case
+ run using the Test Harness: # Instantiate VNF task result
+<VNFI-name> was instantiated! Note: The test will not fail if the VNF instance
+ already exists. The output will instead contain: # debug
+<VNFI-name> already exists!
+
+
+
+ Controlling a VNFI
+
+ Description: Changing the status
+ of a VNF instance (Pause, Resume, Stop, Start). For details please refer
+ to:
+
+
+
+ <AF-TH-install-dir>/playbooks/controlVNFI.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/vnf/controlVNFI.py
+
+
+
+ Precondition: A VNF is
+ instantiated on a uCPE device.
+
+ Action: Run the
+ controlVNFI.yml Ansible Playbook with the
+ <Device-name> ,
+ <VNFI-name> and the
+ <Command> as extra-vars: ansible-playbook playbooks/controlVNFI.yml -e "device=<Device-name> \
+vnfi=<VNFI-name> status=<pause|resume|start|stop>"
+
+ Result: Output of the test case
+ run using the Test Harness: # Change VNFI Status task result
+<VNFI-name> status was set to <Command> Note: The test will not fail if the VNF instance
+ does not exist or if the specified command is not valid. Depending on
+ the case, the output will contain: # debug
+<VNFI-name> was not found! or# debug
+Invalid VNF Instance control command specified - <Command>
+
+
+
+ Destroying a VNFI
+
+ Description: Destroying a VNF
+ instance from a uCPE device. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/destroyVNFI.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/vnf/destroyVNFI.py
+
+
+
+ Precondition: A VNF is
+ instantiated on a uCPE device.
+
+ Action: Run the
+ destroyVNFI.yml Ansible Playbook with the
+ <Device-name> and the
+ <VNFI-name> as extra-vars: ansible-playbook playbooks/destroyVNFI.yml -e "device=<Device-name> \
+vnfi=<VNFI-name>" Result: Output of the test case run using the
+ Test Harness:# Destroy VNFI task result
+<VNFI-name> was destroyed! Note: The test will not fail if the VNF instance
+ does not exist. The output will instead contain: # debug
+<VNFI-name> was not found!
+
+
+
+
+ Service Creation and Lifecycle
+
+ This test suite contains more complex test cases designed to verify
+ service creation and service lifecycle management. These test cases also
+ serve as examples of how different services can be deployed using the
+ Automation Framework (AF) and the Test Harness (TH).
+
+
+ Fortigate VNF as a Firewall
+
+ This test case was implemented in two different ways to exemplify
+ both methods supported by the AF and TH to deploy such services.
+
+ How to deploy the FortiGate VNF as a
+ Firewall:
+
+
+
+ Add a uCPE device.
+
+
+
+ Wait for the uCPE device to be connected in the Enea Edge
+ Management.
+
+
+
+ Onboard the FortiGate VNF Image.
+
+
+
+ Bind 2 physical interfaces: wan_nic (this
+ physical interface has to be connected to the Lab Network) and
+ lan_nic .
+
+
+
+ Create 2 bridges: wan_br (using the
+ wan_nic interface) and lan_br
+ (using the lan_nic interface).
+
+
+
+ Instantiate the FortiGate VNF using the basic Firewall
+ configuration provided with your Enea Edge Release, and the
+ Fortigate License file.
+
+
+ Please contact the local Fortinet sales representatives in
+ your region to get the Fortigate License file.
+
+
+
+
+ For more information please refer to section FortiGate VNF as a Firewall in the
+
+ Manual.
+
+
+ FortigateFWInstance Test
+
+ Description: Instantiate the
+ FortiGate VNF as a Firewall and test it using an isolated network
+ namespace.
+
+ This example was implemented with the "Test Harness" method,
+ based on Ansible Playbooks. For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/fortigateFWService/instantiateFortigateFW.yml
+
+
+
+ <AF-TH-install-dir>/playbooks/fortigateFWService/testFortigateFWInstance.yml
+
+
+
+ <AF-TH-install-dir>/playbooks/fortigateFWService/cleanupTestFortigateFWInstance.yml
+
+
+
+ <AF-TH-install-dir>/playbooks/fortigateFWService/cleanupFortigateFWInstance.yml
+
+
+
+ Preconditions:
+
+
+
+ A device must have been previously added and connected to
+ the Enea Edge Management instance.
+
+
+
+ Add the Fortigate VNF Image
+ (fortios.qcow2 ) to the
+ <AF-TH-install-dir>/vnf_image
+ folder.
+
+
+
+ The device JSON configuration file is created:
+ <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json .
+
+
+
+ Add device settings in the hosts Ansible
+ inventory file under [fortigateFW] and remove
+ the intelc3850-2 example.
+
+ Example: intelc3850-2 ansible_host=172.24.12.114 ansible_port=22 \
+ansible_user=root ansible_pass=root
+
+
+
+ NIC JSON configuration files are created:
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/wan_nic.json
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/lan_nic.json
+
+
+
+
+
+ Bridge JSON configuration files are created:
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/wan_br.json
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/lan_br.json
+
+
+
+
+
+ Download the FortiGate VNF Firewall basic configuration file
+ from Enea, copy it into the
+ <AF-TH-install-dir>/vnf_config/fortigateImage
+ directory and rename it to
+ fortigateFW.conf .
+
+
+
+ Retrieve the FortiGate VNF license file from Fortinet or
+ Enea, copy it into the
+ <AF-TH-install-dir>/vnf_config/fortigateImage
+ directory and rename it to
+ fortigateLicense.lic .
+
+ For more information please refer to section FortiGate VNF as a Firewall in
+ the
+ Manual.
+
+
+
+ Action: Run the
+ instantiateFortigateFW.yml Ansible Playbook with
+ the <Device-name> as
+ extra-vars:ansible-playbook playbooks/fortigateFWService/instantiateFortigateFW.yml \
+-e "device=<Device-name>"
+
+ Result: Output of the test case
+ run using the Test Harness: # Test FortigateFWInstance task result
+FortigateFWInstance tested successfully!
+
+ Cleanup: Run the
+ cleanupFortigateFWInstance.yml Ansible Playbook
+ with the <Device-name> as extra-vars:
+ ansible-playbook playbooks/fortigateFWService/cleanupFortigateFWInstance.yml \
+-e "device=<Device-name>"
+
+
+
+ DeployFortigateFW Scenario
+
+ Description: Deploy the
+ Fortigate VNF as a Firewall. This example was implemented with the
+ "Automation Framework" method, based on the
+ unittestSuite.py Python module.
+
+ For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/unittestSuiteTest/deployFortigateFWScenario.yml
+
+
+
+ <AF-TH-install-dir>/playbooks/unittestSuiteTest/cleanupFortigateFWScenario.yml
+
+
+
+ <AF-TH-install-dir>/automation_framework/unittestSuite
+ directory.
+
+
+
+ Preconditions:
+
+
+
+ A device must have been previously added and connected to
+ the Enea Edge Management instance.
+
+
+
+ Add the FortiGate VNF Image
+ (fortios.qcow2 ) to the
+ <AF-TH-install-dir>/vnf_image
+ folder.
+
+
+
+ The device JSON configuration file is created:
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json .
+
+
+
+ The NIC JSON configuration files are created:
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/wan_nic.json
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/lan_nic.json
+
+
+
+ The Bridge JSON configuration files are created:
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/wan_br.json
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/lan_br.json
+
+
+
+ Download the FortiGate VNF Firewall basic configuration from
+ Enea, copy it into the
+ <AF-TH-install-dir>/vnf_config/fortigateImage
+ directory and rename it to
+ fortigateFW.conf .
+
+
+
+ Retrieve the FortiGate VNF license file from Fortinet or
+ Enea, copy it into the
+ <AF-TH-install-dir>/vnf_config/fortigateImage
+ directory and rename it to
+ fortigateLicense.lic .
+
+ For more details, please refer to:
+
+
+
+ FortiGate VNF as a
+ Firewall in the
+ Manual.
+
+
+
+ Python Unit-Test Suite in
+ .
+
+
+
+
+
+ Action: Run the
+ deployFortigateFWScenario.yml Ansible Playbook
+ with the <Device-name> as extra-vars:
+ ansible-playbook playbooks/unittestSuiteTest/deployFortigateFWScenario.yml \
+-e "device=<Device-name>"
+
+ Result: Output of the test case
+ run using the Test Harness: # unittestSuite Deploy Test task result
+FortigateFW Scenario deployed successfully!
+
+ Cleanup: Run the
+ cleanupFortigateFWScenario.yml Ansible Playbook
+ with the <Device-name> as extra-vars:
+ ansible-playbook playbooks/unittestSuiteTest/cleanupFortigateFWScenario.yml \
+-e "device=<Device-name>"
+
+
+
+
+ chainedVNFsService
+
+ Description: This sample test
+ case corresponds to the "VNF Chaining Example Use-case" from the Enea
+ Edge Example Use-cases manual.
+
+ For details please refer to:
+
+
+
+ <AF-TH-install-dir>/playbooks/chainedVNFsService/chainedVNFsService.yml
+
+
+
+ <AF-TH-install-dir>/playbooks/chainedVNFsService/testChainedVNFsService.yml
+
+
+
+ <AF-TH-install-dir>/playbooks/chainedVNFsService/cleanupChainedVNFsService.yml
+
+
+
+ Preconditions:
+
+
+
+ Two devices must have been previously added and connected to
+ the Enea Edge Management instance.
+
+
+
+ Add the Fortigate VNF Image
+ (fortios.qcow2 ) to the
+ vnf_image folder.
+
+
+
+ Add the Juniper vSRX VNF Image
+ (juniper.qcow2 ) to the
+ vnf_image folder.
+
+
+
+ The device JSON configuration file(s) is created, e.g.:
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json .
+
+
+
+ Add device settings in the hosts Ansible
+ inventory file under [chainedVNFs] . Keep both
+ devices, the "site1" and "site2" entries, and update the values for
+ ansible_host , ansible_port ,
+ ansible_user and ansible_pass ,
+ as applicable.
+
+ Example:
+
+ site1 ansible_host=172.24.14.157 ansible_port=22 ansible_user=root \
+ansible_pass=root
+
+ site2 ansible_host=172.24.14.50 ansible_port=22 ansible_user=root \
+ansible_pass=root
+
+
+
+ NIC JSON configuration files are created for each of the
+ devices, where mgmt_nic is connected to the DHCP
+ from the Lab Network and wan_nic is connected
+ back to back to the other device:
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/mgmt_nic.json
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/wan_nic.json
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/lan_nic.json
+
+
+
+
+
+ Bridge JSON configuration files are created for each of the
+ devices:
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/vnf_mgmt_br.json
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/sfc_br.json
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/wan_br.json
+
+
+
+ <AF-TH-install-dir>/lab_config/<Device-name>/lan_br.json
+
+
+
+ Note that sample configuration files needed for devices' NICs
+ and bridges can be found in:
+ <AF-TH-install-dir>/lab_config/inteld1521-1
+ and
+ <AF-TH-install-dir>/lab_config/inteld1521-2 .
+
+
+
+ Retrieve the FortiGate VNF Firewall basic configuration files
+ from Enea (FortiFW-Site1.conf and
+ FortiFW-Site2.conf ), and copy them into the
+ <AF-TH-install-dir>/vnf_config/fortigateFWImage
+ directory.
+
+
+
+ Retrieve the FortiGate VNF license file from Fortinet or Enea,
+ copy it into the
+ <AF-TH-install-dir>/vnf_config/fortigateFWImage
+ directory and rename it to
+ fortigateLicense.lic .
+
+
+
+ Retrieve the Juniper vSRX basic configuration files from Enea
+ (vSRX-Site1.iso and
+ vSRX-Site2.iso ), and copy them into the
+ <AF-TH-install-dir>/vnf_config/junipervSRXImage
+ directory.
+
+
+
+ Retrieve the vSRX-domain-update-script
+ from Enea and copy it into the junipervSRXImage
+ directory.
+
+ Please refer to the Chapter concerning the VNF Chaining Example Use-case in the
+
+ manual for additional information about preconditions.
+
+
+
+ Action: Run the
+ chainedVNFsService.yml Ansible Playbook as
+ follows:ansible-playbook playbooks/chainedVNFsService/chainedVNFsService.yml \
+-e "site1=inteld1521-1 site2=inteld1521-2 arch=XeonD"
+
+ Note that "arch" may either be { XeonD | AtomC } depending on the
+ target set chosen.
+
+ Result: Output of the test case
+ run using the Test Harness: # testChainedVNFsService task result
+******************************************************************************
+ * site1 - changed=False ----------------------------------------------
+----
+<site1_lan-ip> ---> <site2_lan-ip>
+LAN-to-LAN connectivity (through VPN tunnel)tested successfully!
+
+ Cleanup: Run the
+ cleanupChainedVNFsService.yml Ansible Playbook as
+ follows: ansible-playbook playbooks/chainedVNFsService/cleanupChainedVNFsService.yml \
+-e "site1=inteld1521-1 site2=inteld1521-2 arch=XeonD"
+
+
+
+
+ Custom Scripts - Basic Test
+
+ The basic test script can be found in
+ <AF-TH-install-dir>/playbooks/customScripts/basicTest.yml .
+
+ The basicTest.yml script requires the following
+ steps:
+
+
+
+ Upload a Custom Script onto the Enea Edge Management.
+
+
+
+ Upload the Custom Script onto a Device.
+
+
+
+ Reboot the Device.
+
+
+
+ Wait for the Device to be up and running.
+
+
+
+ Remove the Custom Script from the Device.
+
+
+
+ Remove the Custom Script from the Enea Edge Management.
+
+
+
+ Preconditions:
+
+
+
+ A device must have been previously added and connected to the
+ Enea Edge Management.
+
+
+
+ The device JSON configuration file must have been created:
+ <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json .
+
+
+
+ The custom script should have been previously saved in
+ <AF-TH-install-dir>/lab_config/customScripts .
+
+
+
+ Add device settings in the hosts Ansible inventory file under
+ [customScriptDevice] and remove the inteld1521-1
+ example.
+
+
+
+ Example:
+
+ [customScriptDevice]
+inteld1521-1 ansible_host=172.24.12.73 ansible_port=22 ansible_user=root \
+ ansible_pass=root
+
+ Action: Run
+ basicTest.yml (example data for
+ test_success_after_always ):
+
+ ansible-playbook playbooks/customScripts/basicTest.yml -e "device=<Device-name>" \
+-e "scriptName=test_success_after_always" -e "phase=always-after-startup" \
+-e "expectedStatus=success"
+
+ Result: Output of
+ basicTest.yml :
+
+ test_success_after_always was uploaded to Enea Edge Management!
+test_success_after_always was uploaded to <Device-name>!
+
+<Device-name> device is connected!
+test_success_after_always from phase always-after-startup was removed \
+from <Device-name>!
+
+test_success_after_always from phase always-after-startup was removed \
+from Enea Edge Management!
+
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-system-test-specification/swcomp.mk b/doc/book-enea-edge-system-test-specification/swcomp.mk
new file mode 100755
index 0000000..2830cc3
--- /dev/null
+++ b/doc/book-enea-edge-system-test-specification/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-system-test-specification
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) System Test Specification"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-edge-telemetry-open-source/doc/README b/doc/book-enea-edge-telemetry-open-source/doc/README
new file mode 100644
index 0000000..1077acb
--- /dev/null
+++ b/doc/book-enea-edge-telemetry-open-source/doc/README
@@ -0,0 +1,4 @@
+The licenses.xml in the git repository of Enea NFV Access Open Source Report
+is the frozen version belonging to the last official release of Enea NFV Access.
+The contents must be generated from the release script to obtain the latest
+lists of packages and licenses.
diff --git a/doc/book-enea-edge-telemetry-open-source/doc/about.xml b/doc/book-enea-edge-telemetry-open-source/doc/about.xml
new file mode 100644
index 0000000..5366626
--- /dev/null
+++ b/doc/book-enea-edge-telemetry-open-source/doc/about.xml
@@ -0,0 +1,12 @@
+
+
+
+ About this Report
+
+ This document contains the open source and license information
+ pertaining to telemetry packages provided with Enea Edge .
+
\ No newline at end of file
diff --git a/doc/book-enea-edge-telemetry-open-source/doc/book.xml b/doc/book-enea-edge-telemetry-open-source/doc/book.xml
new file mode 100644
index 0000000..9b0aa33
--- /dev/null
+++ b/doc/book-enea-edge-telemetry-open-source/doc/book.xml
@@ -0,0 +1,15 @@
+
+
+]>
+
+ Enea Edge Telemetry Open Source Report
+ Release Version
+
+
+
+
+
+
diff --git a/doc/book-enea-edge-telemetry-open-source/doc/licenses.xml b/doc/book-enea-edge-telemetry-open-source/doc/licenses.xml
new file mode 100644
index 0000000..3cffaae
--- /dev/null
+++ b/doc/book-enea-edge-telemetry-open-source/doc/licenses.xml
@@ -0,0 +1,290 @@
+
+
+
+ Packages and Licenses
+
+
+ Packages
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Package Name
+ Version
+ Description
+ License
+
+
+
+
+
+
+
+ InfluxDB
+ 1.3.7
+ InfluxDB database for Telemetry
+ MIT License
+
+
+
+ Grafana
+ 4.6.3
+ Analytics and interactive visualization web application
+ Apache License 2.0
+
+
+
+
+
+
+
+
+ Open Source Licenses
+
+
+ InfluxDB
+
+ MIT License
+
+ Copyright (c) 2018 InfluxData
+
+ Permission is hereby granted, free of charge, to any person obtaining a copy
+ of this software and associated documentation files (the "Software"), to deal
+ in the Software without restriction, including without limitation the rights
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+ copies of the Software, and to permit persons to whom the Software is
+ furnished to do so, subject to the following conditions:
+
+ The above copyright notice and this permission notice shall be included in all
+ copies or substantial portions of the Software.
+
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+ SOFTWARE.
+
+
+
+ Grafana
+
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright 2015 Grafana Labs
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+
+
diff --git a/doc/book-enea-edge-telemetry-open-source/swcomp.mk b/doc/book-enea-edge-telemetry-open-source/swcomp.mk
new file mode 100644
index 0000000..cf28954
--- /dev/null
+++ b/doc/book-enea-edge-telemetry-open-source/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-edge-telemetry-open-source
+BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Telemetry Open Source Report"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/README b/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/README
deleted file mode 100644
index e546e6f..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/README
+++ /dev/null
@@ -1,3 +0,0 @@
-The licenses.xml in the git repository of Enea NFV Access AFTH Open Source Report
-is the frozen version belonging to the last official release of Enea NFV Access.
-
diff --git a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/about.xml b/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/about.xml
deleted file mode 100644
index 4dc19aa..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/about.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- About this Report
-
- This document contains the open source and license information
- pertaining to the Automation Framework and Test Harness provided with
- Enea Edge .
-
-
diff --git a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/book.xml b/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/book.xml
deleted file mode 100644
index f849ad4..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/book.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-]>
-
- Enea Edge Automation Framework and Test Harness Open Source Report
-
- Release Version
-
-
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/licenses.xml
deleted file mode 100644
index 76a34e2..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-open-source/doc/licenses.xml
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
-
- Packages and Licenses
-
-
- Packages
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Package Name
-
- Version
-
- Description
-
- License
-
-
-
-
-
- Automation Framework and Test Harness
-
-
-
- Configuration and Automation Framework for the Edge Manager
- GUI.
-
- ENEA-SRC-R2
-
-
-
- Automation Framework and Test Harness
-
-
-
- Configuration and Automation Framework for the Edge Manager
- GUI.
-
- ENEA-EXAMPLE-R2
-
-
-
-
-
-
-
-
-
- Proprietary Licenses
-
-
- ENEA-SRC-R2
-
- Copyright (C) 2019 by Enea.
- All rights reserved.
-
- This Software is furnished under a software license agreement and
- may be used only in accordance with the terms of such agreement.
- Any other use or reproduction is prohibited. No title to and
- ownership of the Software is hereby transferred.
-
- PROPRIETARY NOTICE
- This Software consists of confidential information.
- Trade secret law and copyright law protect this Software.
- The above notice of copyright on this Software does not indicate
- any actual or intended publication of such Software.
-
-
-
- ENEA-EXAMPLE-R2
-
- Copyright (C) 2019 by Enea Software AB.
- All rights reserved.
-
- This Example is furnished under a Software License Agreement and
- may be used only in accordance with the terms of such agreement.
- No title to and ownership of the Example is hereby transferred.
-
- The information in this Example is subject to change
- without notice and should not be construed as a commitment
- by Enea Software AB.
-
- DISCLAIMER
- This Example is delivered "AS IS", consequently
- Enea Software AB makes no representations or warranties,
- expressed or implied, for the Example.
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-open-source/swcomp.mk b/doc/book-enea-nfv-access-auto-fw-th-open-source/swcomp.mk
deleted file mode 100644
index 702e86f..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-open-source/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-auto-fw-th-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) AF&TH Open Source Report"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
deleted file mode 100644
index a569d59..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
+++ /dev/null
@@ -1,2800 +0,0 @@
-
-
- Automation Framework and Test Harness
-
-
- Automation Framework
-
- All Automation Framework sources are under the
- <AF-TH-install-dir>/automation_framework
- directory.
-
- The /device folder contains Python scripts for
- adding uCPE device(s), receiving uCPE events' reports, removing a uCPE
- device, waiting for a uCPE device to connect to the Enea Edge Management, as well
- as scripts for adding and removing an offline configuration store. This
- folder also contains scripts for uploading and removing an NFVA image into
- the Enea Edge Management, and for installing and activating a NFVA image on a uCPE
- Device.
-
- The /customScripts folder contains Python scripts
- for uploading custom scripts onto the Enea Edge Management and uCPE device(s), for
- removing custom scripts from the Enea Edge Management and uCPE device(s).
-
- The /network folder contains Python scripts for
- binding or unbinding a network interface to and from a uCPE device (DPDK
- or SR-IOV), creating or deleting an OVS network bridge, or dumping network
- interface information about the available interfaces. Three of the scripts
- mentioned here (binding, creating, deleting) are also applicable for an
- Offline Configuration Store.
-
-
- Commands within the network folder that include the option
- -o allow the user to perform the action
- in an offline configuration store alternative available for use at a
- later setup time. Commands that include the -n option refer to a uCPE device, with the
- operation being performed on uCPE device. All options contain either
- -n , -o
- or both. One of them must always be provided, if both are provided, -o
- has priority, and -n is thus ignored.
-
-
- The /unittestSuite folder contains JSON files for
- complex scenarios (multiple operations), as well as Python unit-test class
- and loader scripts for generating specific test cases for the available
- Python scripts. The generated test cases are injected into the Python
- unit-test suite class to be run using the Python unit-test
- framework.
-
- The /unittestSuite/config folder contains
- configuration files in JSON format that describe the list of test cases
- for a particular Python script. Each defined test case is a dictionary
- that must contain the test case name and arguments to be passed to the
- Python script for running the test case.
-
- The /unittestSuite/vnf_config directory contains
- symlinks for the Fortigate license file and for the
- /vnf_config/fortigateImage folder.
-
- The /vnf folder contains Python scripts for
- onboarding and offboarding a VNF image, instantiating a VNF, controlling a
- VNF instance or destroying an existing one.
-
- The eneaUcpeMgr.py file acts as a library for
- the (Python) Automation Framework scripts. It contains common functions
- and unit-test configuration options.
-
-
- Python Unit-Test Suite
-
- The Python unit-test class defined in the
- unittestSuite.py script provides a way to automate
- the execution of specific test cases for each supported Python
- script.
-
- This class requires a test suite configuration JSON file that
- contains a dictionary list of the Python scripts to be processed. Each
- dictionary must contain the path of the Python script to be loaded and
- the path to the file describing the test cases to be performed against
- the designated script.
-
- Steps for running the Python unit-test suite on the Enea Edge Management
- are provided below.
-
-
- Script Options
-
- $ python unittestSuite.py -h
-Usage: unittestSuite.py [options]
-
-Run selected unit-test suite against Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -n DEVICENAME, --deviceName=DEVICENAME
- Name of vCPE device (Virtual Infrastructure Manager)
- -s SUITEFILE, --suite=SUITEFILE
- Test suite configuration file in JSON format
- -d DESCRIPTION, --description=DESCRIPTION
- Test suite description
- -o OFFLINE, --offline=OFFLINE
- Offline Configuration(ZTP)
-
- Mandatory options:
- -H/--host, -n/--deviceName, -s/--suiteFile, -d/--description
-
-
-
- Configuring Unit-Test JSON File
-
- The Unit-Test suite JSON configuration file contains a list of
- dictionaries. Each dictionary indicates the path of the Python module
- to load and the test case's configuration file to be executed against
- the loaded module.
-
- Below is a sample unit-test configuration file, describing the
- Fortigate deployment scenario
- fortigateDeploy.json , found in
- <AF-TH-install-dir>/automation_framework/unittestSuite :
-
- [
- {
- "config": "config/waitDeviceUp.json",
- "module": "../device/waitDeviceUp.py"
- },
- {
- "config": "config/bindNetworkInterface.json",
- "module": "../network/bindNetworkInterface.py"
- },
- {
- "config": "config/newNetworkBridge.json",
- "module": "../network/newNetworkBridge.py"
- },
- {
- "config": "config/onboardVNFRaw.json",
- "module": "../vnf/onboardVNFRaw.py"
- },
- {
- "config": "config/instantiateVNFI.json",
- "module": "../vnf/instantiateVNFI.py"
- },
- {
- "config": "config/controlVNFI.json",
- "module": "../vnf/controlVNFI.py"
- }
-]
-
- Below is a sample unit-test configuration file, describing the
- Fortigate cleanup scenario
- fortigateCleanup.json :
-
- [
- {
- "config": "config/destroyVNFI.json",
- "module": "../vnf/destroyVNFI.py"
- },
- {
- "config": "config/delNetworkBridge.json",
- "module": "../network/delNetworkBridge.py"
- },
- {
- "config": "config/unbindNetworkInterface.json",
- "module": "../network/unbindNetworkInterface.py"
- },
- {
- "config": "config/offboardVNF.json",
- "module": "../vnf/offboardVNF.py"
- }
-]
-
- The config key contains the path to the test
- case's configuration file.
-
- The module key contains the path to the
- Python script to be executed.
-
-
-
- Unit-Test Configuration Options
-
- Unit-test behavior can be tweaked through setting any of the
- following options. This is done through the
- eneaUcpeMgr.py file:
-
- # Defaults for the framework
-username = "admin"
-password = "admin"
-host = None
-deviceName = None
-directory = "."
-ftpUsername = "ftp"
-ftpPassword = "ftp"
-ftpPort = "2021"
-
-# Stop the test run on the first error or failure
-failfast = True
-
-# Logging levels ordered by the highest severity:
-# CRITICAL 50
-# ERROR 40
-# WARNING 30
-# INFO 20
-# DEBUG 10
-# NOTSET 0
-fileLoggingLevel = logging.DEBUG
-consoleLoggingLevel = logging.INFO
-
-
-
- eneaUcpeMgr.py Options
-
-
-
-
-
-
-
-
-
-
- Option
-
- Description
-
-
-
-
-
- username
-
- The user authentication used to log into the
- Enea Edge Management. This can be overwritten by setting the Python
- unit-test suite command line option
- -u .
-
-
-
- password
-
- The password used to log into the Enea Edge Management. This
- can be overwritten by setting the Python unit-test suite
- command line option -p .
-
-
-
- host
-
- The IP address of the Enea Edge Management host. This can be
- overwritten by setting the Python unit-test suite command line
- option -H .
-
-
-
- devicename
-
- The name of the vCPE agent against which tests will be
- performed. This can be overwritten by setting the Python
- unit-test suite command line option
- -n .
-
-
-
- ftpUsername
-
- The user authentication used for the FTP connection
- when onboarding a VNF image. This can be overwritten by
- setting the Python script command line option
- -f .
-
-
-
- ftpPassword
-
- The password used for the FTP connection when
- onboarding a VNF image. This can be overwritten by setting the
- Python script command line option
- -w .
-
-
-
- ftpPort
-
- The port used for the FTP connection when onboarding a
- VNF image. This can be overwritten by setting the Python
- script command line option -P .
-
-
-
- failfast
-
- Describes the unit-test execution behavior on the first
- error or failure encountered.
-
-
-
- fileLoggingLevel
-
- Sets the file logging level.
-
-
-
- consoleLoggingLevel
-
- Sets the console logging level.
-
-
-
-
-
-
-
- Python Unit-Test Suite Logging
-
- Logging messages are displayed in the console and also saved to
- the specified log file. They are shown depending on the chosen logging
- level.
-
- Logging messages are ranked by their severity
- level:CRITICAL 50
-ERROR 40
-WARNING 30
-INFO 20
-DEBUG 10
-NOTSET 0
-
-
- Logging messages less severe than the set logging level will
- be ignored.
-
-
- Setting the console logging level to INFO is done through the
- consoleLoggingLevel option:consoleLoggingLevel = logging.INFO Setting
- the file logging level to DEBUG is done through the
- fileLoggingLevel option:fileLoggingLevel = logging.DEBUG
-
-
-
- Running Python Unit-Test Suite
-
-
- Please update all JSON configuration files to use the name of
- your vCPE agent device. In the following chapters, intelc3850-2 is
- used as an example.
-
-
- Below you'll find sample unit-test command line options for
- running the Fortigate deployment
- scenario:
-
- $ python unittestSuite.py -u admin -p admin -H localhost -n intelc3850-2 -s
-fortigateDeploy.json -d "Fortigate deployment scenario"
-
- Setting the console logging level to DEBUG:
-
- consoleLoggingLevel = logging.DEBUG
- Expected Output:
-
- 2020-04-15 07:58:40,668 - DEBUG: Started logging
-
-Running Fortigate deployment scenario...
-
-test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ...
-2020-04-15 07:58:40,681 - INFO: Wait uCPE device
-2020-04-15 07:58:40,722 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:58:40,723 - DEBUG: Session token is: 280028c0-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:58:40,746 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:58:40,747 - DEBUG: Wait for device 'intelc3850-2' to connect
-2020-04-15 07:58:41,769 - DEBUG: HACK: sleep 30s more
-2020-04-15 07:59:11,791 - DEBUG: HACK: continue
-2020-04-15 07:59:11,792 - INFO: Status: Connected
-2020-04-15 07:59:11,793 - INFO: Done
-2020-04-15 07:59:11,827 - DEBUG: Logging out and exiting...
-ok
-test 002: Bind lan NIC to DPDK (__main__.UnittestSuite) ...
-2020-04-15 07:59:11,832 - INFO: Bind NIC
-2020-04-15 07:59:11,868 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:11,870 - DEBUG: Session token is: 3a90a960-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:11,897 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:11,898 - DEBUG: Bind NIC 'eno6' to dpdk
-2020-04-15 07:59:12,952 - INFO: Done
-2020-04-15 07:59:12,983 - DEBUG: Logging out and exiting...
-ok
-test 003: Bind wan NIC to DPDK (__main__.UnittestSuite) ...
-2020-04-15 07:59:12,986 - INFO: Bind NIC
-2020-04-15 07:59:13,023 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:13,025 - DEBUG: Session token is: 3b410da0-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:13,048 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:13,050 - DEBUG: Bind NIC 'eno8' to dpdk
-2020-04-15 07:59:14,365 - INFO: Done
-2020-04-15 07:59:14,392 - DEBUG: Logging out and exiting...
-ok
-test 004: Creating network bridge LAN (__main__.UnittestSuite) ...
-2020-04-15 07:59:14,395 - INFO: New OVS network bridge
-2020-04-15 07:59:14,428 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:14,429 - DEBUG: Session token is: 3c174961-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:14,452 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:14,453 - DEBUG: Create new OVS network bridge 'lan_br'
-2020-04-15 07:59:14,454 - DEBUG: Attaching interface 'eno6' to bridge 'lan_br'
-2020-04-15 07:59:21,751 - INFO: Done
-2020-04-15 07:59:21,779 - DEBUG: Logging out and exiting...
-ok
-test 005: Creating network bridge WAN (__main__.UnittestSuite) ...
-2020-04-15 07:59:21,782 - INFO: New OVS network bridge
-2020-04-15 07:59:21,818 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:21,819 - DEBUG: Session token is: 407ec231-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:21,845 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:21,846 - DEBUG: Create new OVS network bridge 'wan_br'
-2020-04-15 07:59:21,847 - DEBUG: Attaching interface 'eno8' to bridge 'wan_br'
-2020-04-15 07:59:22,813 - INFO: Done
-2020-04-15 07:59:22,845 - DEBUG: Logging out and exiting...
-ok
-test 006: Onboarding Fortigate VNF (wizard API) (__main__.UnittestSuite) ...
-2020-04-15 07:59:22,849 - INFO: Onboard wizard
-2020-04-15 07:59:22,885 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:22,886 - DEBUG: Session token is: 4121b8f1-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:22,890 - DEBUG: FTP file '../../vnf_image/fortios.qcow2' on host \
-'localhost', port '2021'
-2020-04-15 07:59:23,127 - DEBUG: Onboard VNF raw: fortios.qcow2
-2020-04-15 07:59:27,107 - INFO: Done
-2020-04-15 07:59:27,140 - DEBUG: Logging out and exiting...
-ok
-test 007: Instantiate Fortigate VNF (__main__.UnittestSuite) ...
-2020-04-15 07:59:27,144 - INFO: Instantiate VNF
-2020-04-15 07:59:27,182 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:27,184 - DEBUG: Session token is: 43b16480-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:27,207 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:27,281 - DEBUG: Found VNF descriptor with name 'fortigateImage'
-2020-04-15 07:59:27,286 - DEBUG: Reading file content as text: \
-vnf_config/fortigateImage/fortigateFW.conf
-2020-04-15 07:59:27,359 - DEBUG: Encrypt file content: \
-vnf_config/fortigateImage/fortigateFW.conf
-2020-04-15 07:59:27,364 - DEBUG: Reading file content as text: \
-vnf_config/fortigateImage/fortigateLicense.lic
-2020-04-15 07:59:27,407 - DEBUG: Encrypt file content: \
-vnf_config/fortigateImage/fortigateLicense.lic
-2020-04-15 07:59:27,409 - DEBUG: Instantiate fortigateImage VNF on 'intelc3850-2'
-2020-04-15 07:59:32,720 - INFO: Done
-2020-04-15 07:59:32,747 - DEBUG: Logging out and exiting...
-ok
-test 008: Pause Fortigate VNF instance (__main__.UnittestSuite) ...
-2020-04-15 07:59:32,840 - INFO: Control VNF
-2020-04-15 07:59:32,877 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:32,880 - DEBUG: Session token is: 47166170-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:32,904 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:32,954 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
-2020-04-15 07:59:32,955 - DEBUG: Control VNF instance 'intelc3850-2', command: pause
-2020-04-15 07:59:33,114 - INFO: Done
-2020-04-15 07:59:33,138 - DEBUG: Logging out and exiting...
-ok
-test 009: Resume Fortigate VNF instance (__main__.UnittestSuite) ...
-2020-04-15 07:59:33,142 - INFO: Control VNF
-2020-04-15 07:59:33,174 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:33,177 - DEBUG: Session token is: 4743b300-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:33,209 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:33,257 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
-2020-04-15 07:59:33,258 - DEBUG: Control VNF instance 'intelc3850-2', command: resume
-2020-04-15 07:59:33,365 - INFO: Done
-2020-04-15 07:59:33,389 - DEBUG: Logging out and exiting...
-ok
-test 010: Stop Fortigate VNF instance (__main__.UnittestSuite) ...
-2020-04-15 07:59:33,393 - INFO: Control VNF
-2020-04-15 07:59:33,436 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:33,438 - DEBUG: Session token is: 476aea10-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:33,467 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:33,511 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
-2020-04-15 07:59:33,513 - DEBUG: Control VNF instance 'intelc3850-2', command: stop
-2020-04-15 07:59:33,865 - INFO: Done
-2020-04-15 07:59:33,891 - DEBUG: Logging out and exiting...
-ok
-test 011: Start Fortigate VNF instance (__main__.UnittestSuite) ...
-2020-04-15 07:59:33,895 - INFO: Control VNF
-2020-04-15 07:59:33,931 - DEBUG: Login successful on host 'localhost'
-2020-04-15 07:59:33,932 - DEBUG: Session token is: 47b70e41-7ede-11ea-a9a8-02429dc76bdd
-2020-04-15 07:59:33,956 - DEBUG: Found device with name 'intelc3850-2'
-2020-04-15 07:59:34,013 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
-2020-04-15 07:59:34,015 - DEBUG: Control VNF instance 'intelc3850-2', command: start
-2020-04-15 07:59:36,599 - INFO: Done
-2020-04-15 07:59:36,623 - DEBUG: Logging out and exiting...
-ok
-
-----------------------------------------------------------------------
-Ran 11 tests in 55.946s
-
-OK
-
- Below you'll find sample unit-test command line options for
- running the Fortigate cleanup
- scenario:
-
- $ python unittestSuite.py -u admin -p admin -H localhost -n intelc3850-2 -s
-fortigateCleanup.json -d "Fortigate cleanup scenario"
-
- Setting the console logging level to INFO:
-
- consoleLoggingLevel = logging.INFO
-
- Expected Output:
-
- Running Fortigate cleanup scenario...
-
-test 001: Destroying Fortigate VNF (__main__.UnittestSuite) ...
-2020-04-15 08:03:40,756 - INFO: Destroy VNF
-2020-04-15 08:03:41,358 - INFO: Done
-ok
-test 002: Deleting network bridge LAN (__main__.UnittestSuite) ...
-2020-04-15 08:03:41,494 - INFO: Delete OVS network bridge
-2020-04-15 08:03:41,731 - INFO: Done
-ok
-test 003: Deleting network bridge WAN (__main__.UnittestSuite) ...
-2020-04-15 08:03:41,766 - INFO: Delete OVS network bridge
-2020-04-15 08:03:43,270 - INFO: Done
-ok
-test 004: Unbind lan NIC from DPDK (__main__.UnittestSuite) ...
-2020-04-15 08:03:43,375 - INFO: Unbind NIC
-2020-04-15 08:03:45,405 - INFO: Done
-ok
-test 005: Unbind wan NIC from DPDK (__main__.UnittestSuite) ...
-2020-04-15 08:03:45,434 - INFO: Unbind NIC
-2020-04-15 08:03:47,633 - INFO: Done
-ok
-test 006: Offboarding Fortigate VNF (__main__.UnittestSuite) ...
-2020-04-15 08:03:47,701 - INFO: Offboard VNF
-2020-04-15 08:03:47,919 - INFO: Done
-ok
-
-----------------------------------------------------------------------
-Ran 6 tests in 7.192s
-
-OK
-
-
-
-
- Adding a uCPE Device
-
- Steps for adding, configuring and running a uCPE device onto the
- Enea Edge Management are described below .
-
-
- Script Options
-
- $ python addDevice.py -h
-Usage: addDevice.py [options]
-
-Add a uCPE device in Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f DEVICEFILE, --file=DEVICEFILE
- File containing uCPE Information in JSON format
-
- Mandatory options:
- -H/--host, -f/--file
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed for adding a uCPE device
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the arguments passed to the
- addDevice Python module.
-
- Sample configuration file in JSON
- format:
-
- [
- {
- "name": "Add VCPE Agent device ",
- "args": "-f ../../lab_config/intelc3850-2/intelc3850-2.json"
- }
-]
-
- Sample
- intelc3850-2.json configuration
- file:
-
- {
- "name": "intelc3850-2",
- "deviceGroupingTags": " ",
- "description": "",
- "address": "172.24.12.114",
- "version": "2.4.0",
- "port": "22",
- "username": "root",
- "password": "root",
- "certificate": null,
- "passphrase": null,
- "callHome": "false",
- "maintMode": "false",
- "deviceId": "intelc3850-2"
-}
-
-
-
- Running the Python Module
-
- The addDevice Python module can be executed
- independently by running the following command:
-
- $ python addDevice.py -u admin -p admin -H localhost -f config/device.json
-2019-03-07 17:33:10,755 - DEBUG: Started logging
-2019-03-07 17:33:10,756 - INFO: Add uCPE device
-2019-03-07 17:33:10,975 - DEBUG: Login successful on host 'localhost'
-2019-03-07 17:33:10,979 - DEBUG: Session token is: 508b6ea2-40ee-11e9-a81f525400d08e1d
-2019-03-07 17:33:11,049 - DEBUG: Add new device 'intelc3850-2' to Enea Edge Management host
-2019-03-07 17:33:11,483 - INFO: Done
-2019-03-07 17:33:11,501 - DEBUG: Logging out and exiting....
-
-
-
-
- Removing a uCPE Device
-
- Steps for removing a uCPE device from the Enea Edge Management are
- described below.
-
-
- Script Options
-
- $ python removeDevice.py -h
-Usage: removeDevice.py [options]
-
-Remove a uCPE from Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f DEVICEFILE, --file=DEVICEFILE
- File containing uCPE Information in JSON format
-
- Mandatory options:
- -H/--host, -f/--file
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to remove a uCPE device
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the arguments passed to the
- removeDevice Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Remove VCPE Agent device ",
- "args": "-f ../../lab_config/intelc3850-2/intelc3850-2.json"
- }
-]
-
- Sample
- intelc3850-2.json configuration
- file:
-
- {
- "name": "intelc3850-2"
-}
-
-
-
- Running the Python Module
-
- The removeDevice Python module can be
- executed individually by running the following command:
-
- $ python removeDevice.py -u admin -p admin -H localhost -f
-../../lab_config/intelc3850-2/intelc3850-2.json
-2019-03-07 17:33:56,834 - DEBUG: Started logging
-2019-03-07 17:33:56,835 - INFO: Remove uCPE device
-2019-03-07 17:33:56,856 - DEBUG: Login successful on host 'localhost'
-2019-03-07 17:33:56,856 - DEBUG: Session token is: 6bebcb43-40ee-11e9-a81f525400d08e1d
-2019-03-07 17:33:56,856 - DEBUG: Delete device 'intelc3850-2' from Enea Edge Management
-host
-2019-03-07 17:33:56,875 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 17:33:57,159 - INFO: Done
-2019-03-07 17:33:57,171 - DEBUG: Logging out and exiting...
-
-
-
-
- Waiting a uCPE Device
-
- Steps and details for how to Wait a uCPE device to connect to the
- Enea Edge Management after installation, are described below.
-
-
- Script Options
-
- $ python waitDeviceUp.py -h
-Usage: waitDeviceUp.py [options]
-
-Wait for uCPE to connect to the Enea Edge Management after installation.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f DEVICEFILE, --file=DEVICEFILE
- File containing uCPE Information in JSON format
- -t TIMEOUT, --timeout=TIMEOUT
- Time in seconds for maximum wait period, default =
- instant
-
- Mandatory options:
- -H/--host, -f/--file
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to wait a uCPE device should
- contain a list of dictionaries. Each dictionary indicates the test
- case name and the test case arguments passed to the
- waitDeviceUp Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Wait VCPE Agent device be up",
- "args": "-f ../../lab_config/intelc3850-2/intelc3850-2.json -t 60"
- }
-]
-
- Sample
- intelc3850-2.json configuration
- file:
-
- {
- "name": "intelc3850-2"
-}
-
-
-
- Running the Python Module
-
- The waitDeviceUp Python module can be
- executed individually by running the following command
- line:$ python waitDeviceUp.py -u admin -p admin -H localhost -t 60 -f
-../../lab_config/intelc3850-2/intelc3850-2.json
-2019-03-07 18:03:21,132 - DEBUG: Started logging
-2019-03-07 18:03:21,133 - INFO: Wait uCPE device
-2019-03-07 18:03:21,149 - DEBUG: Login successful on host 'localhost'
-2019-03-07 18:03:21,149 - DEBUG: Session token is: 8785b1a0-40f2-11e9-a81f525400d08e1d
-2019-03-07 18:03:21,157 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 18:03:21,157 - DEBUG: Wait for device 'intelc3850-2' to connect
-2019-03-07 18:03:29,356 - DEBUG: Status: Connected
-2019-03-07 18:03:29,356 - INFO: Done
-2019-03-07 18:03:29,365 - DEBUG: Logging out and exiting...
-
-
-
-
- Printing the uCPE Device Log
-
- Steps and details on how to Print the events log for a specific
- uCPE device installed in the Enea Edge Management, are explained below.
-
-
- Script Options
-
- $ python getEventsForUcpe.py -h
-Usage: getEventsForUcpe.py [options]
-
-Print the events log for a specific uCPE installed in Enea Edge Management.
-
-Options:
---version show program's version number and exit
--h, --help show this help message and exit
--u USERNAME, --username=USERNAME Enea Edge Management login username
--p PASSWORD, --password=PASSWORD Enea Edge Management login password
--H HOST, --host=HOST Enea Edge Management host name or IP address
--f DEVICEFILE, --file=DEVICEFILE File containing uCPE Information in JSON format
--s SEVERITY, --severity=SEVERITY Event severity level (Critical|Major|Minor)
-
-Mandatory options:
--H/--host, -f/--file
-
-
-
- Configuring the JSON File
-
- Sample
- intelc3850-2.json configuration
- file:
-
- {
- "name": "intelc3850-2",
- "deviceId": "intelc3850-2",
- "deviceGroupingTags": " ",
- "description": "",
-"address": "172.24.12.114",
- "port": "22",
- "username": "root",
- "password": "root",
- "certificate": null,
- "passphrase": null,
- "callHome": "false",
- "maintMode": "false"
-}
-
-
-
-
- Running the Python Module
-
- The getEventsForUcpe Python module can be
- executed individually by running the following command:
-
- $ python getEventsForUcpe.py -H localhost -f \
-../../lab_config/intelc3850-2/intelc3850-2.json
-
-2019-07-04 13:48:31,289 - DEBUG: Started logging
-2019-07-04 13:48:31,290 - INFO: Dump uCPE events
-2019-07-04 13:48:31,336 - DEBUG: Login successful on host '172.24.3.108'
-2019-07-04 13:48:31,336 - DEBUG: Session token is: a53c68d3-9e51-11e9-a715-5254007632e2
-2019-07-04 13:48:31,356 - DEBUG: Found device with name 'intelc3850-2'
-2019-07-04 13:48:31,357 - DEBUG:
-Events on device: intelc3850-2 and severity: 1000
-2019-07-04 13:48:31,450 - DEBUG: Dumping 1 events
-2019-07-04 13:48:31,450 - DEBUG: Device Disconnected | Alarm | Device | None | \
- 2019-07-04 09:57:40.042
-2019-07-04 13:48:31,469 - DEBUG: Dumping 0 events
-2019-07-04 13:48:31,469 - INFO: Done
-2019-07-04 13:48:31,488 - DEBUG: Logging out and exiting...
-
-
-
-
- Enabling or Disabling the DPDK
-
- Steps and details on how to enable or disable the DPDK are
- explained below.
-
-
- Script Options
-
- $ python configDPDK.py -h
-Usage: configDPDK.py [options]
-
-Configure DPDK
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -s STATE, --state=STATE
- Enable/Disable
- -n DEVICENAME, --device-name=DEVICENAME
- Name of the device
- -o STORENAME, --store-name=STORENAME
- Name of the store
-
- Mandatory options:
- -H/--host, -s/--state, -n/--device-name or -o/--store-name
-
-
-
- Running the Python Module
-
- The configDPDK Python module can be executed
- individually by running the following command lines:
-
- To Enable DPDK:
-
- $ python configDPDK.py -s enable -n intelc3850-2
-
-2020-01-06 08:35:16,820 - DEBUG: Started logging
-2020-01-06 08:35:16,821 - INFO: Configure DPDK
-2020-01-06 08:35:16,870 - DEBUG: Login successful on host '172.24.3.90'
-2020-01-06 08:35:16,871 - DEBUG: Session token is: 601149e0-3089-11ea-b0c7-525400b7889f
-2020-01-06 08:35:16,894 - DEBUG: Found device with name 'inteld1521-1'
-2020-01-06 08:35:16,895 - DEBUG: Set DPDK state to enable
-2020-01-06 08:35:16,936 - INFO: Done
-2020-01-06 08:35:16,961 - DEBUG: Logging out and exiting...
-
- To Disable DPDK:
-
- $ python configDPDK.py -s disable -n intelc3850-2
-
-2020-01-06 08:33:57,157 - DEBUG: Started logging
-2020-01-06 08:33:57,158 - INFO: Configure DPDK
-2020-01-06 08:33:57,215 - DEBUG: Login successful on host '172.24.3.90'
-2020-01-06 08:33:57,216 - DEBUG: Session token is: 3096e670-3089-11ea-b0c7-525400b7889f
-2020-01-06 08:33:57,239 - DEBUG: Found device with name 'inteld1521-1'
-2020-01-06 08:33:57,241 - DEBUG: Set DPDK state to disable
-2020-01-06 08:33:57,284 - INFO: Done
-2020-01-06 08:33:57,310 - DEBUG: Logging out and exiting...
-
-
-
-
- Binding a Network Interface
-
- How to Bind a physical network interface to a DPDK, Standard or
- SR-IOV is detailed below.
-
-
- Script Options
-
- $ python bindNetworkInterface.py -h
-Usage: bindNetworkInterface.py [options]
-
-Binds a physical network interface to a DPDK or SR-IOV.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f NICFILE, --file=NICFILE
- File containing network interface Information in JSON
- format
- -n DEVICENAME, --device-name=DEVICENAME
- Name of the device
- -o STORENAME, --store-name=STORENAME
- Name of the store
-
- Mandatory options:
- -H/--host, -f/--file, -n/--device-name or -o/--store-name
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to bind a physical network
- interface should contain a list of dictionaries. Each dictionary
- indicates the test case name and the test case arguments passed to the
- bindNetworkInterface Python module.
-
- Sample unit-test JSON file
- format: [
- {
- "name": "Bind lan NIC to DPDK",
- "args": "-f ../../lab_config/intelc3850-2/lan_nic.json"
- },
- {
- "name": "Bind wan NIC to DPDK",
- "args": "-f ../../lab_config/intelc3850-2/wan_nic.json"
- },
- {
- "name": "Bind wan/lan NIC to SR-IOV",
- "args": "-f ../../lab_config/intelc3850-2/sriov_nic.json"
- },
- {
- "name": "Bind wan/lan NIC to Standard",
- "args": "-f ../../lab_config/intelc3850-2/std_nic.json"
- }
-] Sample
- lan_nic.json configuration
- file: {
- "name": "enp4s0f0",
- "type": "dpdk",
- "subType": "vfio-pci"
-} Sample
- wan_nic.json configuration
- file: {
- "name": "enp4s0f1",
- "type": "dpdk",
- "subType": "vfio-pci"
-} Sample
- sriov_nic.json configuration
- file: {
- "name": "enp4s0f1",
- "type": "sr-iov",
- "subType": "adapter-pool",
- "sriovNumVfs": "2"
-} Sample
- std_nic.json configuration
- file: {
- "name": "eno2",
- "type": "standard"
-}
-
-
-
- Running the Python Module
-
- The bindNetworkInterface Python module can be
- executed individually by running the following command line:
-
- $ python bindNetworkInterface.py -u admin -p admin -H localhost -f
-../../lab_config/intelc3850-2/lan_nic.json -n intelc3850-2
-2019-03-07 18:03:29,365 - DEBUG: Started logging
-2019-03-07 18:03:29,366 - INFO: Bind NIC
-2019-03-07 18:03:29,406 - DEBUG: Login successful on host 'localhost'
-2019-03-07 18:03:29,406 - DEBUG: Session token is: 8c719cb0-40f2-11e9-a81f525400d08e1d
-2019-03-07 18:03:29,415 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 18:03:29,415 - DEBUG: Bind NIC '0000:01:00.1'
-2019-03-07 18:03:30,030 - INFO: Done
-2019-03-07 18:03:30,067 - DEBUG: Logging out and exiting...
-
-
-
-
- Unbinding a Network Interface
-
- How to Unbind a physical network interface from a DPDK or SR-IOV
- is described below.
-
-
- Script Options
-
- $ python unbindNetworkInterface.py -h
-Usage: unbindNetworkInterface.py [options]
-
-Unbinds a physical interface to the DPDK or SR-IOV.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f NICFILE, --file=NICFILE
- File containing network interface Information in JSON
- format
- -n DEVICENAME, --device-name=DEVICENAME
- Name of the device
-
- Mandatory options:
- -H/--host, -f/--file, -n/--device-name
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to unbind a network interface
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the test case arguments passed to the
- unbindNetworkInterface Python module.
-
- Sample unit-test JSON file
- format: [
- {
- "name": "Unbind lan NIC from DPDK",
- "args": "-f ../../lab_config/intelc3850-2/lan_nic.json"
- },
- {
- name": "Unbind wan NIC from DPDK",
- "args": "-f ../../lab_config/intelc3850-2/wan_nic.json"
- }
-]
-
- Sample lan_nic.json
- configuration file:
-
- {
- "name": "enp4s0f0",
- "type": "dpdk"
-}
-
- Sample wan_nic.json
- configuration file:
-
- {
- "name": "enp4s0f1",
- "type": "dpdk",
-}
-
-
-
-
- Running the Python Module
-
- The unbindNetworkInterface Python module
- can be executed individually by running the following command
- line:
-
- $ python unbindNetworkInterface.py -u admin -p admin -H localhost -f
-../../lab_config/intelc3850-2/lan_nic.json -n intelc3850-2
-2019-03-07 17:33:54,377 - DEBUG: Started logging
-2019-03-07 17:33:54,378 - INFO: Unbind NIC
-2019-03-07 17:33:54,431 - DEBUG: Login successful on host 'localhost'
-2019-03-07 17:33:54,432 - DEBUG: Session token is: 6a77a1d1-40ee-11e9-a81f525400d08e1d
-2019-03-07 17:33:54,467 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 17:33:54,468 - DEBUG: Unbind NIC '0000:01:00.1'
-2019-03-07 17:33:55,616 - INFO: Done
-2019-03-07 17:33:55,659 - DEBUG: Logging out and exiting...
-
-
-
-
- Getting a Network Interface
-
- Details and steps on how to List the network interfaces for a
- device, are described below.
-
-
- Script Options
-
- $ python getNetworkInterfaces.py -h
-2019-07-04 16:35:50,496 - DEBUG: Started logging
-2019-07-04 16:35:50,496 - INFO: Dump NICs
-Usage: getNetworkInterfaces.py [options]
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -n DEVICENAME, --device-name=DEVICENAME Name of the uCPE to get network /
- interfaces from
-
- Mandatory options:
- -H/--host, -n/--device-name
-
-
-
- Running the Python Module
-
- The getNetworkInterfaces Python module can be
- executed individually by running the following command:
-
- $ python getNetworkInterfaces.py -H localhost -n intelc3850-2
-2020-01-07 05:58:03,630 - DEBUG: Started logging
-2020-01-07 05:58:03,630 - INFO: Dump NICs
-2020-01-07 05:58:03,687 - DEBUG: Login successful on host '172.24.3.90'
-2020-01-07 05:58:03,688 - DEBUG: Session token is: 93dd3cd0-313c-11ea-b0c7-525400b7889f
-2020-01-07 05:58:03,715 - DEBUG: Found device with name 'intelc3850-2'
-2020-01-07 05:58:03,717 - DEBUG:
-----------------External Network Interfaces for intelc3850-2----------------
-2020-01-07 05:58:07,622 - DEBUG: eno4 DpdkTypes: [u'igb_uio', u'vfio-pci'] \
-MacAddress: 0c:c4:7a:fb:85:dfsriov(7)
-2020-01-07 05:58:07,624 - DEBUG:
-2020-01-07 05:58:07,656 - DEBUG:
-----------------Configured External Network Interfaces for intelc3850-2----------------
-2020-01-07 05:58:07,657 - DEBUG: eno3 DpdkType: vfio-pci ID: \
-47556b22-b5c2-4acb-b3cb-09b1f024b3a7
-2020-01-07 05:58:07,658 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \
-2c06b4f7-6814-4432-8765-a9d0cd5303c1
-2020-01-07 05:58:07,659 - DEBUG: enp1s0f0 DpdkTypes: [u'igb_uio', u'vfio-pci'] \
-MacAddress: ac:1f:6b:2d:ee:58sriov(63)
-2020-01-07 05:58:07,660 - DEBUG:
-2020-01-07 05:58:07,690 - DEBUG:
-----------------Configured External Network Interfaces for intelc3850-2----------------
-2020-01-07 05:58:07,691 - DEBUG: eno3 DpdkType: vfio-pci ID: \
-47556b22-b5c2-4acb-b3cb-09b1f024b3a7
-2020-01-07 05:58:07,692 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \
-2c06b4f7-6814-4432-8765-a9d0cd5303c1
-2020-01-07 05:58:07,693 - DEBUG: eno2 DpdkTypes: [u'igb_uio', u'vfio-pci'] \
-MacAddress: 0c:c4:7a:fb:85:ddsriov(7)
-2020-01-07 05:58:07,695 - DEBUG:
-2020-01-07 05:58:07,724 - DEBUG:
-----------------Configured External Network Interfaces for intelc3850-2----------------
-2020-01-07 05:58:07,725 - DEBUG: eno3 DpdkType: vfio-pci ID: \
-47556b22-b5c2-4acb-b3cb-09b1f024b3a7
-2020-01-07 05:58:07,726 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \
-2c06b4f7-6814-4432-8765-a9d0cd5303c1
-2020-01-07 05:58:07,727 - DEBUG: eno1 DpdkTypes: [u'igb_uio', u'vfio-pci'] \
-MacAddress: 0c:c4:7a:fb:85:dcsriov(7)
-2020-01-07 05:58:07,728 - DEBUG:
-2020-01-07 05:58:07,760 - DEBUG:
-----------------Configured External Network Interfaces for intelc3850-2----------------
-2020-01-07 05:58:07,761 - DEBUG: eno3 DpdkType: vfio-pci ID: \
-47556b22-b5c2-4acb-b3cb-09b1f024b3a7
-2020-01-07 05:58:07,761 - DEBUG: enp1s0f1 DpdkType: vfio-pci ID: \
-2c06b4f7-6814-4432-8765-a9d0cd5303c1
-2020-01-07 05:58:07,762 - DEBUG:
-2020-01-07 05:58:07,763 - INFO: Done
-2020-01-07 05:58:07,787 - DEBUG: Logging out and exiting...
-
-
-
-
- Creating an OVS Network Bridge
-
- Instructions on how to Create an OVS Bridge on a device are
- detailed below.
-
-
- Script Options
-
- $ python newNetworkBridge.py -h
-Usage: newNetworkBridge.py [options]
-
-Create an OVS Bridge on a device.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f OVSFILE, --file=OVSFILE
- File containing OVS bridge Information in JSON format
- -n DEVICENAME, --device-name=DEVICENAME
- Name of the device
- -o STORENAME, --store-name=STORENAME
- Name of the store
-
- Mandatory options:
- -H/--host, -f/--file, -n/--device-name or -o/--store-name
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to create a new network
- bridge should contain a list of dictionaries. Each dictionary
- indicates the test case name and the test case arguments passed to the
- newNetworkBridge Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Creating network bridge LAN ",
- "args": "-f ../../lab_config/intelc3850-2/lan_br.json"
- },
- {
- "name": "Creating network bridge WAN ",
- "args": "-f ../../lab_config/intelc3850-2/wan_br.json"
- }
-]
-
- Sample lan_br.json
- configuration file:
-
- {
- "name": "lan_br",
- "interfaces": ["enp4s0f0"]
-}
-
- Sample wan_br.json
- configuration file:
-
- {
- "name": "wan_br",
- "interfaces": ["enp4s0f1"]
-}
-
-
-
- Running the Python Module
-
- The newNetworkBridge Python module can be
- executed individually by running the following command line:
-
- $ python newNetworkBridge.py -u admin -p admin -H localhost -f
-../../lab_config/intelc3850-2/lan_br.json -n intelc3850-2
-2019-03-07 18:03:30,767 - DEBUG: Started logging
-2019-03-07 18:03:30,768 - INFO: New OVS network bridge
-2019-03-07 18:03:30,801 - DEBUG: Login successful on host 'localhost'
-2019-03-07 18:03:30,801 - DEBUG: Session token is: 8d454061-40f2-11e9-a81f525400d08e1d
-2019-03-07 18:03:30,811 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 18:03:30,812 - DEBUG: Create new OVS network bridge 'lan_br'
-2019-03-07 18:03:37,358 - INFO: Done
-2019-03-07 18:03:37,402 - DEBUG: Logging out and exiting...
-
-
-
-
- Deleting an OVS Network Bridge
-
- How to Delete an OVS Bridge from a device is detailed in the
- following.
-
-
- Script Options
-
- $ python delNetworkBridge.py -h
-Usage: delNetworkBridge.py [options]
-
-Delete an OVS Bridge from a device.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f OVSFILE, --file=OVSFILE
- File containing OVS bridge Information in JSON format
- -n DEVICENAME, --device-name=DEVICENAME
- Name of the device
- -o STORENAME, --store-name=STORENAME
- Name of the store
-
- Mandatory options:
- -H/--host, -f/--file, -n/--device-name or -o/--store-name
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to delete a network bridge
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the test case arguments passed to the
- delNetworkBridge Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Deleting network bridge LAN ",
- "args": "-f ../../lab_config/intelc3850-2/lan_br.json"
- },
- {
- "name": "Deleting network bridge WAN ",
- "args": "-f ../../lab_config/intelc3850-2/wan_br.json"
- }
-]
-
- Sample lan_br.json
- configuration file:
-
- {
- "name" : "lan_br"
-}
-
- Sample wan_br.json
- configuration file:
-
- {
- "name" : "wan_br"
-}
-
-
-
- Running the Python Module
-
- The delNetworkBridge Python module can be
- executed individually by running the following command line:
-
- $ python delNetworkBridge.py -u admin -p admin -H localhost -f
-../../lab_config/intelc3850-2/lan_br.json -n intelc3850-2
-2019-03-07 17:33:51,712 - DEBUG: Started logging
-2019-03-07 17:33:51,713 - INFO: Delete OVS network bridge
-2019-03-07 17:33:51,751 - DEBUG: Login successful on host 'localhost'
-2019-03-07 17:33:51,752 - DEBUG: Session token is: 68e08711-40ee-11e9-a81f525400d08e1d
-2019-03-07 17:33:51,768 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 17:33:51,768 - DEBUG: Delete OVS network bridge 'lan_br'
-2019-03-07 17:33:52,839 - INFO: Done
-2019-03-07 17:33:52,872 - DEBUG: Logging out and exiting...
-
-
-
-
- Onboarding a VNF Image Raw
-
- How to Onboard a VNF image in the Enea Edge Management based upon its raw
- constituents, is detailed in depth below.
-
-
- Script Options
-
- $ python onboardVNFRaw.py -h
-Usage: onboardVNFRaw.py [options]
-
-Onboard a VNF in Enea Edge Management based upon its raw constituents.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f FTPUSERNAME, --ftpUsername=FTPUSERNAME
- Username for FTP
- -w FTPPASSWORD, --ftpPassword=FTPPASSWORD
- FTP password
- -P FTPPORT, --ftpPort=FTPPORT
- FTP port
- -i IMAGEPATH, --imagePath=IMAGEPATH
- VNF image path
- -b IMAGEINFO, --imageInfo=IMAGEINFO
- File name of VNF image information in JSON format
-
- Mandatory options:
- -H/--host, -b/--imageInfo, -i/--imagePath
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to onboard a VNF image Raw
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the test case arguments passed to the
- onboardVNFRaw Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Onboarding Fortigate VNF (wizard API)",
- "args": "-b ../../vnf_config/fortigateImage/fortigateImage.json -i
-../../vnf_images/fortios.qcow2"
- }
-]
-
- Sample
- fortigateImage.json configuration
- file: {
- "name" : "fortigateImage",
- "version" : "1.0",
- "description" : "Fortigate VNF Image",
- "provider" : "Fortinet, Inc",
- "numVcpus" : 1,
- "imageFormat" : "QCOW2",
- "memoryInMb" : 1024,
- "storageInGb" : 20,
- "image" : "fortios.qcow2",
- "interfaces" : [
- {
- "name" : "external",
- "type" : "PhysicalPort",
- "description" : "External interface"
- },
- {
- "name" : "in",
- "type" : "PhysicalPort",
- "description" : "Incoming interface"
- },
- {
- "name" : "out",
- "type" : "PhysicalPort",
- "description" : "Outgoing interface"
- }
- ],
- "cloudInitDataSource" : "ConfigDrive",
- "cloudInitDriveType" : "cdrom",
- "cloudInitContentParams" : [
- {
- "path" : "License",
- "description" : "Operational license"
- }
- ]
-}
-
-
-
- Running the Python Module
-
- The onboardVNFRaw Python module can be
- executed individually by running the following command line:
-
- $ python onboardVNFRaw.py -u admin -p admin -f ftp -w ftp -H localhost -b b
-../../vnf_config/fortigateImage/fortigateImage.json -i
-../../vnf_images/fortios.qcow2
-2019-03-07 18:03:37,791 - DEBUG: Started logging
-2019-03-07 18:03:37,792 - INFO: Onboard wizard
-2019-03-07 18:03:37,859 - DEBUG: Login successful on host 'localhost'
-2019-03-07 18:03:37,859 - DEBUG: Session token is: 91770330-40f2-11e9-a81f525400d08e1d
-2019-03-07 18:03:37,860 - DEBUG: FTP file '../../vnf_images/fortios.qcow2' on host
-'localhost', port '2021'
-2019-03-07 18:03:38,027 - DEBUG: Onboard VNF raw: fortios.qcow2
-2019-03-07 18:03:41,701 - INFO: Done
-2019-03-07 18:03:41,748 - DEBUG: Logging out and exiting...
-
-
-
-
- Offboarding a VNF
-
- Steps on how to Offboard a VNF from the Enea Edge Management are detailed
- below.
-
-
- Script Options
-
- $ python offboardVNF.py -h
-Usage: offboardVNF.py [options]
-
-Offboard a VNF from Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -n VNFDNAME, --vnfdName=VNFDNAME
- Name of VNF descriptor to offboard
-
- Mandatory options:
- -H/--host, -n/--vnfdName
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to offboard a VNF should
- contain a list of dictionaries. Each dictionary indicates the test
- case name and the test case arguments passed to the
- offboardVNF Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Offboarding Fortigate VNF ",
- "args": "-n fortigateImage"
- }
-]
-
-
-
- Running the Python Module
-
- The offboardVNF Python module can be
- executed individually by running the following command line:
-
- $ python offboardVNF.py -u admin -p admin -H localhost -n fortigateImage
-2019-03-07 17:33:56,523 - DEBUG: Started logging
-2019-03-07 17:33:56,524 - INFO: Offboard VNF
-2019-03-07 17:33:56,557 - DEBUG: Login successful on host 'localhost'
-2019-03-07 17:33:56,557 - DEBUG: Session token is: 6bbe2b90-40ee-11e9-a81f525400d08e1d
-2019-03-07 17:33:56,682 - DEBUG: Found VNF descriptor with name 'fortigateImage'
-2019-03-07 17:33:56,683 - DEBUG: Offboard VNF: fortigateImage
-2019-03-07 17:33:56,811 - INFO: Done
-2019-03-07 17:33:56,834 - DEBUG: Logging out and exiting...
-
-
-
-
- Instantiating a VNF
-
- Instantiating a VNF via the Enea Edge Management is detailed below.
-
-
- Script Options
-
- $ python instantiateVNFI.py -h
-Usage: instantiateVNFI.py [options]
-
-Instantiate a VNF via Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -t VNFTYPE, --vnfType=VNFTYPE
- VNF Type (Name of VNF descriptor)
- -n VIMDEVICENAME, --device-name=VIMDEVICENAME
- Name of the device
- -f PROPSFILE, --file=PROPSFILE
- File containing VNF instance properties in JSON format
-
- Mandatory options:
- -H/--host, -t/--vnfType, -n/--device-name, -f/--file
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to instantiate a VNF should
- contain a list of dictionaries. Each dictionary indicates the test
- case name and the test case arguments passed to the
- instantiateVNFI Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Instantiate Fortigate VNF ",
- "args": "-t fortigateImage -f
-../../vnf_config/fortigateImage/fortigateFWInstance.json"
- }
-]
-
- The VNF instance JSON configuration file is specific to each
- VNF.
-
-
-
- Running the Python Module
-
- The instantiateVNFI Python module can be
- executed individually by running the following command line:
-
- $ python instantiateVNFI.py -u admin -p admin -H localhost -n intelc3850-2 -t
-fortigateImage -f ../../vnf_config/fortigateImage/fortigateFWInstance.json
-2019-03-07 18:03:41,777 - DEBUG: Started logging
-2019-03-07 18:03:41,778 - INFO: Instantiate VNF
-2019-03-07 18:03:41,813 - DEBUG: Login successful on host 'localhost'
-2019-03-07 18:03:41,815 - DEBUG: Session token is: 93d69e10-40f2-11e9-a81f525400d08e1d
-2019-03-07 18:03:41,834 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 18:03:41,878 - DEBUG: Found VNF descriptor with name 'fortigateImage'
-2019-03-07 18:03:41,888 - DEBUG: Encrypt string content:
-cloudInit("vnf_config/fortigateImage/fortigateFW.conf")
-2019-03-07 18:03:41,889 - DEBUG: Encrypt string content:
-License("vnf_config/fortigateImage/fortigateLicense.lic")
-2019-03-07 18:03:41,889 - DEBUG: Instantiate fortigateImage VNF on 'intelc3850-2'
-2019-03-07 18:03:49,887 - INFO: Done
-2019-03-07 18:03:49,921 - DEBUG: Logging out and exiting...
-
-
-
-
- Controlling a VNF Instance
-
- How to Control a VNF instance from the Enea Edge Management is
- detailed below.
-
-
- If a sequence of commands aiming to change the state of the VNF
- (start/stop/suspend/shutdown) is issued rapidly, certain VNFs might
- become unresponsive. Depending on the actual VNF, the time required
- between life-cycle operations may vary from several seconds to half a
- minute or even more. If a VNF becomes unresponsive, the only possible
- action is to "Force Delete" the instance from the Enea Edge Management.
-
-
-
- Script Options
-
- $ python controlVNFI.py -h
-Usage: controlVNFI.py [options]
-
-Controls a VNF instance from Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -i VNFINSTANCENAME, --vnfInstanceName=VNFINSTANCENAME
- Name of VNF instance
- -n VIMDEVICENAME, --device-name=VIMDEVICENAME
- Name of the device
- -c COMMAND, --command=COMMAND
- Control command (stop, start, pause or resume)
-
- Mandatory options:
- -H/--host, -i/--vnfInstanceName, -n/--device-name, -c/--command
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to control a VNF instance
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the test case arguments passed to the
- controlVNFI Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Pause Fortigate VNF instance",
- "args": "-i fortigateFWInstance -c pause"
- },
- {
- "name": "Resume Fortigate VNF instance",
- "args": "-i fortigateFWInstance -c resume"
- },
- {
- "name": "Stop Fortigate VNF instance ",
- "args": "-i fortigateFWInstance -c stop"
- },
- {
- "name": "Start Fortigate VNF instance",
- "args": "-i fortigateFWInstance -c start"
- }
-]
-
-
-
- Running the Python Module
-
- The controlVNFI Python module can be
- executed individually by running the following command line:
-
- $ python controlVNFI.py -u admin -p admin -H localhost -n intelc3850-2 -i
-fortigateFWInstance -c stop
-2019-03-07 18:03:51,991 - DEBUG: Started logging
-2019-03-07 18:03:51,992 - INFO: Control VNF
-2019-03-07 18:03:52,031 - DEBUG: Login successful on host 'localhost'
-2019-03-07 18:03:52,031 - DEBUG: Session token is: 99ed9ba3-40f2-11e9-a81f525400d08e1d
-2019-03-07 18:03:52,046 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 18:03:52,073 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
-2019-03-07 18:03:52,073 - DEBUG: Control VNF instance 'intelc3850-2', command: stop
-2019-03-07 18:03:53,011 - INFO: Done
-2019-03-07 18:03:53,047 - DEBUG: Logging out and exiting...
-
-
-
-
- Destroying a VNF Instance
-
- Steps and options on how to Destroy a VNF instance from the Enea
- Edge Management are described below.
-
-
- Script Options
-
- $ python destroyVNFI.py -h
-Usage: destroyVNFI.py [options]
-
-Destroys a VNF instance from Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -i VNFINSTANCENAME, --vnfInstanceName=VNFINSTANCENAME
- Name of VNF instance
- -n VIMDEVICENAME, --device-name=VIMDEVICENAME
- Name of the device
-
- Mandatory options:
- -H/--host, -i/--vnfInstanceName, -n/--device-name
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to destroy a VNF instance
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the test case arguments passed to the
- destroyVNFI Python module.
-
- Sample unit-test JSON file
- format: [
- {
- "name": "Destroying Fortigate VNF ",
- "args": "-i fortigateFWInstance"
- }
-]
-
-
-
- Running the Python Module
-
- The destroyVNFI Python module can be
- executed individually by running the following command line:
-
- $ python destroyVNFI.py -u admin -p admin -H localhost -n intelc3850-2 -i
-fortigateFWInstance
-2019-03-07 17:33:51,025 - DEBUG: Started logging
-2019-03-07 17:33:51,026 - INFO: Destroy VNF
-2019-03-07 17:33:51,119 - DEBUG: Login successful on host 'localhost'
-2019-03-07 17:33:51,119 - DEBUG: Session token is: 68803ea5-40ee-11e9-a81f525400d08e1d
-2019-03-07 17:33:51,128 - DEBUG: Found device with name 'intelc3850-2'
-2019-03-07 17:33:51,148 - DEBUG: Found VNF instance with name 'fortigateFWInstance'
-2019-03-07 17:33:51,149 - DEBUG: Destroy VNF: fortigateFWInstance
-2019-03-07 17:33:51,655 - INFO: Done
-2019-03-07 17:33:51,712 - DEBUG: Logging out and exiting...
-
-
-
-
- Uploading a Enea Edge image onto the Enea Edge Management
-
- Steps and options on how to Upload a Enea Edge image onto the
- Enea Edge Management are described below.
-
-
- Script Options
-
- $ python uploadImage.py -h
-Upload NFVA image on Enea Edge Management
-Usage: uploadImage.py [options]
-
-Upload NFVA image on Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f FILENAME, --fileName=FILENAME
- Path to NFVA image file name
- -m MODULE, --module=MODULE
- Module name (default is: VcpeAgent)
- -t UPGRADETYPE, --upgradeType=UPGRADETYPE
- Upgrade Type depends on architecture: xeon_d or
- atom_c3000
-
- Mandatory options:
- -H/--host, -f/--fileName, -m/--module, -t/--upgradeType
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to upload a Enea Edge image
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the test case arguments passed to the
- uploadImage Python module.
-
- Sample unit-test JSON file
- format: [
- {
- "name": "Upload NFVA image on Enea Edge Management",
- "args": "-f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d"
- }
-]
-
-
-
- Running the Python Module
-
- The uploadImage Python module can be
- executed individually by running the following command line:
-
- $ python uploadImage.py -u admin -p admin -H localhost \
--f /tmp/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d
-2020-02-28 11:38:42,754 - DEBUG: Started logging
-2020-02-28 11:38:42,755 - INFO: Upload NFVA image on Enea Edge Management
-2020-02-28 11:38:43,307 - DEBUG: Login successful on host 'localhost'
-2020-02-28 11:38:43,308 - DEBUG: Session token is: 7da3f960-5a16-11ea-a3de-5652b3ac1c30
-2020-02-28 11:41:29,148 - INFO: Verify image validation flag
-2020-02-28 11:41:29,149 - INFO: Valid flag: True
-2020-02-28 11:41:29,344 - INFO: The image \
-'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' was successfully uploaded
-2020-02-28 11:41:29,344 - INFO: Done
-2020-02-28 11:41:29,388 - DEBUG: Logging out and exiting...
-
-
-
-
- Deleting a Enea Edge image file from the
- Enea Edge Management
-
- Steps and options on how to Delete a Enea Edge image from the
- Enea Edge Management are described below.
-
-
- Script Options
-
- $ python deleteUpgradeFile.py -h
-Delete NFVA image from Enea Edge Management
-Usage: deleteUpgradeFile.py [options]
-
-Delete NFVA image from Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -i IMAGENAME, --imageName=IMAGENAME
- NFVA Image name
- -m MODULE, --module=MODULE
- Module name - default is VcpeAgent
-
- Mandatory options:
- -H/--host, -i/--imageName, -m/--module.
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to delete a Enea Edge image
- should contain a list of dictionaries. Each dictionary indicates the
- test case name and the test case arguments passed to the
- deleteUpgradeFile Python module.
-
- Sample unit-test JSON file
- format: [
- {
- "name": "Delete NFVA image on Enea Edge Management",
- "args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2"
- }
-]
-
-
-
- Running the Python Module
-
- The deleteUpgradeFile Python module can be
- executed individually by running the following command line:
-
- $ python deleteUpgradeFile.py -u admin -p admin -H localhost -i \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
-2020-02-28 12:06:20,111 - DEBUG: Started logging
-2020-02-28 12:06:20,112 - INFO: Delete NFVA image from Enea Edge Management
-2020-02-28 12:06:20,210 - DEBUG: Login successful on host 'localhost'
-2020-02-28 12:06:20,211 - DEBUG: Session token is: 594b2d50-5a1a-11ea-a3de-5652b3ac1c30
-2020-02-28 12:06:20,255 - INFO: The image \
-'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' was successfully found
-2020-02-28 12:06:20,256 - INFO: The oid for \
-'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' image name is as follows: \
-VcpeAgent/xeon_d/enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
-2020-02-28 12:06:20,449 - INFO: The 'enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2' \
-image was successfully removed
-2020-02-28 12:06:20,479 - INFO: Done
-2020-02-28 12:06:20,517 - DEBUG: Logging out and exiting...
-
-
-
-
- Installing and activating a Enea Edge image on an uCPE device
- from the Enea Edge Management
-
- Steps and options on how to Install and Activate a Enea Edge
- image on an uCPE device from the Enea Edge Management are described
- below.
-
-
- Script Options
-
- $ python installAndActivate.py -h
-Install and activate NFVA image from Enea Edge Management
-Usage: installAndActivate.py [options]
-
-Install and activate NFVA image from Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -i IMAGENAME, --imageName=IMAGENAME
- Image name
- -m MODULE, --module=MODULE
- Module name -- VcpeAgent
- -t UPGRADETYPE, --upgradeType=UPGRADETYPE
- Upgrade Type -- xeon_d or atom_c3000
- -d DEVICENAME, --deviceName=DEVICENAME
- Device Name
-
- Mandatory options:
- -H/--host, -i/--imageName, -t/--upgradeType, -d/--deviceName,
- -m/--module
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to install and activate a Enea Edge
- image on a uCPE device from the Enea Edge Management should
- contain a list of dictionaries. Each dictionary indicates the test
- case name and the test case arguments passed to the
- installAndActivate Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Install and activate NFVA image on uCPE device from Enea Edge Management",
- "args": "-i enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16"
- }
-]
-
-
-
- Running the Python Module
-
- The installAndActivate Python module can be
- executed individually by running the following command line:
-
- $ python installAndActivate.py -u admin -p admin -H localhost -i \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 -t xeon_d -d inteld1521-16
-2020-02-28 12:36:46,137 - DEBUG: Started logging
-2020-02-28 12:36:46,138 - INFO: Install and activate NFVA image from Enea Edge Management
-2020-02-28 12:36:46,288 - DEBUG: Login successful on host 'localhost'
-2020-02-28 12:36:46,288 - DEBUG: Session token is: 99b7cde0-5a1e-11ea-a3de-5652b3ac1c30
-2020-02-28 12:36:46,325 - DEBUG: Found device with name 'inteld1521-16'
-2020-02-28 12:36:46,459 - INFO: Display info about NFVA installation \
-[inteld1521-16:1001:172.24.12.152] Install Started
-2020-02-28 12:36:46,492 - INFO: Transferring Image: \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
-2020-02-28 12:36:56,552 - INFO: Verifying Release [1]
-2020-02-28 12:37:06,599 - INFO: Verifying Release [2]
-2020-02-28 12:37:16,652 - INFO: Validating Upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2
-2020-02-28 12:37:26,713 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [3]
-2020-02-28 12:37:36,770 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [5]
-2020-02-28 12:37:46,819 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [7]
-2020-02-28 12:37:56,879 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [9]
-2020-02-28 12:38:06,920 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [11]
-2020-02-28 12:38:16,975 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [13]
-2020-02-28 12:38:27,019 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [15]
-2020-02-28 12:38:37,091 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [18]
-2020-02-28 12:38:47,133 - INFO: Validating upgrade to \
-enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2 [20]
-2020-02-28 12:38:57,186 - INFO: Waiting for release to become active
-2020-02-28 12:39:07,231 - INFO: Upgrade Request Complete
-2020-02-28 12:39:17,242 - INFO: Installation completed!
-2020-02-28 12:39:17,243 - INFO: Done
-2020-02-28 12:39:17,294 - DEBUG: Logging out and exiting...
-
-
-
-
- Clearing information about completed upgrades of uCPE devices
- from the Enea Edge Management
-
- Steps and options on how to clear information about completed
- upgrades of uCPE devices from the Enea Edge Management are described
- below.
-
-
- Script Options
-
- $ python clearCompletedUpgradesInfo.py -h
-Clear info about completed upgrades
-Usage: clearCompletedUpgradesInfo.py [options]
-
-Clear info about completed upgrades
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
-
- Mandatory options:
- -H/--host
-
-
-
- Configuring the JSON File
-
- No JSON configuration file is needed to clear information about
- completed upgrades of uCPE devices from the Enea Edge Management. The
- clearCompletedUpgradesInfo Python module can be
- run without a JSON file as a parameter.
-
-
-
- Running the Python Module
-
- The clearCompletedUpgradesInfo Python
- module can be executed individually by running the following command
- line:
-
- $ python clearCompletedUpgradesInfo.py -u admin -p admin -H localhost
-2020-02-28 12:51:55,861 - DEBUG: Started logging
-2020-02-28 12:51:55,862 - INFO: Clear info about completed upgrades
-2020-02-28 12:51:55,950 - DEBUG: Login successful on host 'localhost'
-2020-02-28 12:51:55,951 - DEBUG: Session token is: b7eb83e0-5a20-11ea-a3de-5652b3ac1c30
-2020-02-28 12:51:55,993 - INFO: Done
-2020-02-28 12:51:56,025 - DEBUG: Logging out and exiting...
-
-
-
-
- Uploading a Custom Script to the Enea Edge Management
-
- Steps and options on how to upload a custom script to the
- Enea Edge Management are described below.
-
-
- Script Options
-
- $ python customScripts/upload.py -h
-2020-04-14 10:26:23,582 - INFO: Upload Custom Script
-Usage: upload.py [options]
-
-Add a Custom Script to Enea Edge Management
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -f CUSTOMSCRIPT, --file=CUSTOMSCRIPT
- Custom Script File
- -e PHASE, --phase=PHASE
- Execution phase. Must be one of the following: once-
- before-startup | always-before-startup | once-after-
- startup | always-after-startup
-
- Mandatory options:
- -H/--host, -f/--file, -e/--phase
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to upload a Custom Script to
- the Enea Edge Management must contain a list of dictionaries. Each dictionary
- indicates the test case name and the test case arguments passed to the
- customScripts/upload Python module.
-
- Sample unit-test JSON file
- format:
-
- [
- {
- "name": "Uploading a Custom Script to the Enea Edge Management",
- "args": "-f ../../lab_config/customScripts/test_success_after_always \
- -e always-after-startup"
- }
-]
-
-
-
- Running the Python Module
-
- The customScripts/upload Python module can
- be executed individually by running the following command line:
-
- $ python automation_framework/customScripts/upload.py \
--f lab_config/customScripts/test_success_after_always -e always-after-startup
-2020-04-14 14:08:02,824 - DEBUG: Started logging
-2020-04-14 14:08:02,915 - INFO: Upload Custom Script
-2020-04-14 14:08:02,994 - DEBUG: Login successful on host '172.24.3.109'
-2020-04-14 14:08:02,995 - DEBUG: Session token is: 97544990-7e48-11ea-835c-02423a1c239f
-2020-04-14 14:08:02,996 - DEBUG: Upload test_success_after_always to Enea Edge Management. \
-Content: #!/bin/bash
-echo test_success_after_always
-2020-04-14 14:08:03,138 - INFO: Done
-2020-04-14 14:08:03,169 - DEBUG: Logging out and exiting...
-
-
-
-
- Uploading a Custom Script from the Enea Edge Management to a
- Device
-
- Steps and options on how to upload a custom script from the
- Enea Edge Management to a Device are described below.
-
-
- Script Options
-
- $ python customScripts/uploadOnDevice.py -h
-2020-04-14 10:27:05,614 - INFO: Upload Custom Script on Device
-Usage: uploadOnDevice.py [options]
-
-Add a Custom Script to a Device
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
- Custom Script Name that resides on Enea Edge Management
- -e PHASE, --phase=PHASE
- Execution phase. Must be one of the following: once-
- before-startup | always-before-startup | once-after-
- startup | always-after-startup
- -n DEVICENAME, --device-name=DEVICENAME
- Name of the device
- -r, --reboot Reboot the device after uploading
-
- Mandatory options:
- -H/--host, -c/--customScriptName, -e/--phase, -n/--device-name
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to upload a Custom Script
- from the Enea Edge Management to a Device must contain a list of dictionaries.
- Each dictionary indicates the test case name and the test case
- arguments passed to the
- customScripts/uploadOnDevice Python
- module.
-
- Sample unit-test JSON file
- format:
-
- [
-{
-"name": "Uploading a Custom Script from Enea Edge Management to device",
-"args": "-c test_success_after_always -e always-after-startup -n inteld1521-6"
-}
-]
-
-
-
- Running the Python Module
-
- The customScripts/uploadOnDevice Python
- module can be executed individually by running the following command
- line:
-
- $ python automation_framework/customScripts/uploadOnDevice.py -c \
-test_success_after_always -e always-after-startup -n inteld1521-6
-2020-04-14 14:26:26,205 - DEBUG: Started logging
-2020-04-14 14:26:26,206 - INFO: Upload Custom Script on Device
-2020-04-14 14:26:26,251 - DEBUG: Login successful on host '172.24.3.109'
-2020-04-14 14:26:26,252 - DEBUG: Session token is: 28ebcb10-7e4b-11ea-835c-02423a1c239f
-2020-04-14 14:26:26,286 - DEBUG: Found device with name 'inteld1521-6'
-2020-04-14 14:26:26,287 - DEBUG: Upload test_success_after_always to inteld1521-6
-2020-04-14 14:26:26,314 - INFO: Done
-2020-04-14 14:26:26,341 - DEBUG: Logging out and exiting...
-
-
-
-
- Removing a Custom Script from the Enea Edge Management
-
- Steps and options on how to remove a custom script from the
- Enea Edge Management are described below.
-
-
- Script Options
-
- $ python customScripts/delete.py -h
-2020-04-14 14:36:52,010 - INFO: Delete Custom Script on Enea Edge Management
-Usage: delete.py [options]
-
-Delete a Custom Script from a Device
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
- Custom Script Name that resides on a Device
- -e PHASE, --phase=PHASE
- Execution phase. Must be one of the following: once-
- before-startup | always-before-startup | once-after-
- startup | always-after-startup
-
- Mandatory options:
- -H/--host, -e/--phase
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to remove a Custom Script
- from the Enea Edge Managementdid you mean device or
- Enea Edge Management? must contain a list of dictionaries. Each dictionary
- indicates the test case name and the test case arguments passed to the
- customScripts/delete Python module.
-
- Sample unit-test JSON file
- format:
-
- [
-{
-"name": "Removing a Custom Script from Enea Edge Management",
-"args": "-c test_success_after_always -e always-after-startup"
-}
-]
-
-
-
- Running the Python Module
-
- The customScripts/delete Python module can
- be executed individually by running the following command line:
-
- $ python automation_framework/customScripts/delete.py -c \
-test_success_after_always -e always-after-startup
-2020-04-14 14:39:22,042 - DEBUG: Started logging
-2020-04-14 14:39:22,042 - INFO: Delete Custom Script on Enea Edge Management
-2020-04-14 14:39:22,081 - DEBUG: Login successful on host '172.24.3.109'
-2020-04-14 14:39:22,082 - DEBUG: Session token is: f75a83a0-7e4c-11ea-835c-02423a1c239f
-2020-04-14 14:39:22,099 - DEBUG: Found custom script: 'test_success_after_always'
-2020-04-14 14:39:22,099 - DEBUG: Delete script test_success_after_always, \
-phase always-after-startup from Enea Edge Management
-2020-04-14 14:39:22,118 - INFO: Done
-2020-04-14 14:39:22,135 - DEBUG: Logging out and exiting...
-
-
-
-
- Removing a Custom Script from a Device
-
- Steps and options on how to remove a custom script from a device
- are described below.
-
-
- Script Options
-
- $ python customScripts/deleteOnDevice.py -h
-2020-04-14 10:27:23,536 - INFO: Delete Custom Script on Device
-Usage: deleteOnDevice.py [options]
-
-Delete a Custom Script from a Device
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -c CUSTOMSCRIPTNAME, --customScriptName=CUSTOMSCRIPTNAME
- Custom Script Name that resides on a Device
- -e PHASE, --phase=PHASE
- Execution phase. Must be one of the following: once-
- before-startup | always-before-startup | once-after-
- startup | always-after-startup
- -n DEVICENAME, --device-name=DEVICENAME
- Name of the device
-
- Mandatory options:
- -H/--host, -n/--device-name
-
-
-
- Configuring the JSON File
-
- The JSON configuration file needed to remove a Custom Script
- from a device must contain a list of dictionaries. Each dictionary
- indicates the test case name and the test case arguments passed to the
- customScripts/deleteOnDevice Python
- module.
-
- Sample unit-test JSON file
- format:
-
- [
-{
-"name": "Removing a Custom Script from device",
-"args": "-c test_success_after_always -e always-after-startup -n inteld1521-6"
-}
-]
-
-
-
- Running the Python Module
-
- The customScripts/deleteOnDevice Python
- module can be executed individually by running the following command
- line:
-
- $ python automation_framework/customScripts/deleteOnDevice.py -c \
-test_success_after_always -e always-after-startup -n inteld1521-6
-2020-04-14 14:33:52,288 - DEBUG: Started logging
-2020-04-14 14:33:52,288 - INFO: Delete Custom Script on Device
-2020-04-14 14:33:52,327 - DEBUG: Login successful on host '172.24.3.109'
-2020-04-14 14:33:52,327 - DEBUG: Session token is: 32cde4f0-7e4c-11ea-835c-02423a1c239f
-2020-04-14 14:33:52,349 - DEBUG: Found device with name 'inteld1521-6'
-2020-04-14 14:33:52,349 - DEBUG: Delete test_success_after_always, \
-phase always-after-startup from inteld1521-6
-2020-04-14 14:33:52,373 - INFO: Done
-2020-04-14 14:33:52,391 - DEBUG: Logging out and exiting...
-
-
-
-
- Custom Script - Full Example
-
- All Python API used in this example are described in detail in the following sections.
-
- The list of custom scripts can be found in
- <AF-TH-install-dir>/lab_config/customScripts :
-
-
-
- test_fail_after_always . Phase:
- always-after-startup.
-
-
-
- test_fail_after_once . Phase:
- once-after-startup.
-
-
-
- test_fail_before_always . Phase:
- always-before-startup.
-
-
-
- test_fail_before_once . Phase:
- once-before-startup.
-
-
-
- test_success_after_always . Phase:
- always-after-startup.
-
-
-
- test_success_after_once . Phase:
- once-after-startup.
-
-
-
- test_success_before_always . Phase:
- always-before-startup.
-
-
-
- test_success_before_once . Phase:
- once-before-startup.
-
-
-
-
- The following example uses the
- test_success_after_always custom script.
-
-
-
- Uploading a Custom Script to the Enea Edge Management
-
- $ python automation_framework/customScripts/upload.py \
--f lab_config/customScripts/test_success_after_always -e always-after-startup
-2020-04-14 14:08:02,824 - DEBUG: Started logging
-2020-04-14 14:08:02,915 - INFO: Upload Custom Script
-2020-04-14 14:08:02,994 - DEBUG: Login successful on host '172.24.3.109'
-2020-04-14 14:08:02,995 - DEBUG: Session token is: 97544990-7e48-11ea-835c-02423a1c239f
-2020-04-14 14:08:02,996 - DEBUG: Upload test_success_after_always to Enea Edge Management. \
-Content: #!/bin/bash
-echo test_success_after_always
-2020-04-14 14:08:03,138 - INFO: Done
-2020-04-14 14:08:03,169 - DEBUG: Logging out and exiting...
-
-
-
- Uploading a Custom Script from the Enea Edge Management to a
- Device
-
- $ python automation_framework/customScripts/uploadOnDevice.py -c \
-test_success_after_always -e always-after-startup -n inteld1521-6
-2020-04-14 14:26:26,205 - DEBUG: Started logging
-2020-04-14 14:26:26,206 - INFO: Upload Custom Script on Device
-2020-04-14 14:26:26,251 - DEBUG: Login successful on host '172.24.3.109'
-2020-04-14 14:26:26,252 - DEBUG: Session token is: 28ebcb10-7e4b-11ea-835c-02423a1c239f
-2020-04-14 14:26:26,286 - DEBUG: Found device with name 'inteld1521-6'
-2020-04-14 14:26:26,287 - DEBUG: Upload test_success_after_always to inteld1521-6
-2020-04-14 14:26:26,314 - INFO: Done
-2020-04-14 14:26:26,341 - DEBUG: Logging out and exiting...
-
-
-
- Removing a Custom Script from a Device
-
- $ python automation_framework/customScripts/deleteOnDevice.py -c \
-test_success_after_always -e always-after-startup -n inteld1521-6
-2020-04-14 14:33:52,288 - DEBUG: Started logging
-2020-04-14 14:33:52,288 - INFO: Delete Custom Script on Device
-2020-04-14 14:33:52,327 - DEBUG: Login successful on host '172.24.3.109'
-2020-04-14 14:33:52,327 - DEBUG: Session token is: 32cde4f0-7e4c-11ea-835c-02423a1c239f
-2020-04-14 14:33:52,349 - DEBUG: Found device with name 'inteld1521-6'
-2020-04-14 14:33:52,349 - DEBUG: Delete test_success_after_always, \
-phase always-after-startup from inteld1521-6
-2020-04-14 14:33:52,373 - INFO: Done
-2020-04-14 14:33:52,391 - DEBUG: Logging out and exiting...
-
-
-
- Removing a Custom Script from the Enea Edge Management
-
- $ python automation_framework/customScripts/delete.py -c \
-test_success_after_always -e always-after-startup
-2020-04-14 14:39:22,042 - DEBUG: Started logging
-2020-04-14 14:39:22,042 - INFO: Delete Custom Script on Enea Edge Management
-2020-04-14 14:39:22,081 - DEBUG: Login successful on host '172.24.3.109'
-2020-04-14 14:39:22,082 - DEBUG: Session token is: f75a83a0-7e4c-11ea-835c-02423a1c239f
-2020-04-14 14:39:22,099 - DEBUG: Found custom script: 'test_success_after_always'
-2020-04-14 14:39:22,099 - DEBUG: Delete script test_success_after_always, \
-phase always-after-startup from Enea Edge Management
-2020-04-14 14:39:22,118 - INFO: Done
-2020-04-14 14:39:22,135 - DEBUG: Logging out and exiting...
-
-
-
-
- Adding an Offline Configuration Store
-
- Steps and options on how to add a Config Store in the
- Enea Edge Management are described below.
-
-
- Script Options
-
- To add a config store in the Enea Edge Management use the
- addConfigStore.py script detailed below. Bear in
- mind a CONFIGSTORE json file is needed to
- successfully run the script in order to add an offline configuration
- store.
-
-
-
- Configuring the JSON file
-
- Example of a CONFIGSTORE json file:
-
- {
- "descr": "intelc3850-2",
- "version": "2.4.0",
- "deviceGroupingTags": "",
- "deviceId": "intelc3850-2",
- "name": "intelc3850-2"
-}
-
-
-
- Running the Python Module
-
- Adding an offline config store in the Enea Edge Management using
- the command line:
-
- python automation_framework/device/addConfigStore.py -f \
-lab_config/inteld1521-16/store.json
-2020-10-16 09:35:51,084 - INFO: Add offline config store
-2020-10-16 09:35:51,160 - INFO: Done
-
-
-
-
- Uploading an Offline Configuration Store to an uCPE
- Device
-
- Steps and options on how to upload a config store to a device are
- described below.
-
-
- Script options
-
- To upload a config store to a uCPE Device use the
- uploadConfigStore.py script detailed
- below.
-
- python uploadConfigStore.py -h
-Usage: uploadConfigStore.py [options]
-
-Upload offline configuration to uCPE Device.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -s STORE, --store=STORE
- Offline config store name
- -d DEVICE, --device=DEVICE
- Device Name
-
- Mandatory options:
- -H/--host, -s/--store, -d/--device
-
-
-
- Running the Python Modules
-
- python automation_framework/device/uploadConfigStore.py -s inteld1521-16 \
--d inteld1521-16
-2020-10-16 09:37:29,074 - INFO: Upload offline configuration to uCPE Device
-2020-10-16 09:37:49,321 - INFO: The 'inteld1521-16' config store was successfully \
-uploaded on device!
-2020-10-16 09:37:49,322 - INFO: Done
-
-
-
-
- Checking the Upload of an Offline Configuration Store
-
- Steps and options on how to check an upload of a Config Store to a
- Device are described below.
-
-
- Script options
-
- To check an upload a config store to a uCPE Device use the
- getUploadStatus.py script detailed below.
-
- python getUploadStatus.py -h
-Usage: getUploadStatus.py [options]
-
-Get upload offline configure status on uCPE Device.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -d DEVICE, --device=DEVICE
- Device Name
-
- Mandatory options:
- -H/--host, -d/--device
-
-
-
- Running the Python Modules
-
- python automation_framework/device/getUploadStatus.py -d inteld1521-16
-2020-10-16 09:38:33,388 - INFO: Get upload offline configure status on uCPE Device
-2020-10-16 09:38:33,486 - INFO: Successful: True
-2020-10-16 09:38:33,487 - INFO: Store name: inteld1521-16
-2020-10-16 09:38:33,488 - INFO: In progress: False
-2020-10-16 09:38:33,489 - INFO: A config store was successfully uploaded on device!
-2020-10-16 09:38:33,490 - INFO: Done
-
-
-
-
- Removing an Offline Configuration Store in the
- Enea Edge Management
-
- Steps and options on how to remove an upload of a Config Store
- from the Enea Edge Management are described below.
-
-
- Modifications of an Offline Configurations Store are not
- possible post deployment in the Enea Edge Management, as there is no option
- for changing script states (e.g. changing the DPDK state in the
- configDPDK.py python script or unbinding
- interfaces). The offline store must be deleted and the new
- state(s)/changes added in, before being deployed anew. This was not
- deemed necessary for the current ZTP functionality.
-
-
-
- Script options
-
- To remove a config store from the Enea Edge Management use the
- removeConfigStore.py script detailed
- below.
-
- python removeConfigStore.py -h
-Usage: removeConfigStore.py [options]
-
-Remove a config store from Enea Edge Management.
-
-Options:
- --version show program's version number and exit
- -h, --help show this help message and exit
- -u USERNAME, --username=USERNAME
- Enea Edge Management login username
- -p PASSWORD, --password=PASSWORD
- Enea Edge Management login password
- -H HOST, --host=HOST Enea Edge Management host name or IP address
- -o STORENAME, --store-name=STORENAME
- Name of the Offline Config Store
-
- Mandatory options:
- -H/--host, -o/--store-name
-
-
-
- Running the Python Modules
-
- python automation_framework/device/removeConfigStore.py -o inteld1521-16
-2020-10-16 09:39:39,127 - INFO: Remove offline config store
-2020-10-16 09:39:39,289 - INFO: Done
-
-
-
-
-
- Test Harness
-
- All Test Harness sources are under the
- <AF-TH-install-dir> directory and the host file
- is the Ansible inventory file. See the complete tree listing at the
- beginning of this chapter for details.
-
- The Ansible based Test Harness represents an example of how to
- structure all the files needed for creating automated test cases using the
- AF and provides a way to implement them. The
- ansible.cfg file contains an example of the Ansible
- default configuration. It offers the possibility to display the Ansible
- console output in different ways, by setting the
- stdout_callback option to selective
- or debug . The default value for this option is set to
- selective to print only certain tasks. It is
- recommended to switch to debug when a test fails. By
- setting the parameter any_errors_fatal to
- True , task failures will be considered fatal errors
- (the play execution will stop). and why would this stop of play
- execution help in this debugging scenario
-
- All Playbooks that execute AF python modules run on
- localhost . New entries have to be created for direct
- communication over SSH with the boards, as done in the
- [fortigateFW] example.
-
- The setup_env.sh script sets up the
- testHarness test environment by creating
- testHarness-venv python virtualenv , executing requests
- needed by Automation Framework python modules and installing
- Ansible.
-
- The Ansible package version installed in the test environment is
- 2.9.6. The playbooks are based on this version of Ansible.
-
- The /playbooks directory contains all the
- implemented Ansible Playbooks. For more details please refer to the Sample Test Cases Chapter in the
- Manual.
-
- The /uCPEM_config directory stores JSON
- configuration files needed for the setup of the Enea Edge Management used by TH.
- One configuration file is needed per Enea Edge Management installation, to be used
- in the TH.
-
- The /vnf_image directory stores the VNF Images
- needed by the Ansible Playbooks (i.e. the sample test cases).
-
- The /lab_config directory stores the JSON
- configuration files related to a device (devices, NICs and bridges) as
- well as sample custom scripts. Each subfolder should be named exactly like
- the device name and should contain all the related configuration files
- needed for the test cases to be run on it.
-
- The /vnf_config directory stores the
- configuration files related to a VNF Descriptor and VNF instances.
- Typically these include a VNF Image JSON, VNF Instance JSON, VNF license
- and any other files required by the type of the VNF. Each subfolder should
- be named exactly like the name of the VNF Descriptor and should contain
- all the related configuration files needed for test cases to be run using
- this VNF.
-
- The /log directory is created when the
- setup_env.sh is run. When test cases are run, the
- Ansible and the Python logs are stored in the
- ansible.log and debug.log files,
- respectively.
-
-
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml
deleted file mode 100644
index 6398606..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-]>
-
- Enea Enea Edge Automation Framework and Test Harness User Guide
-
- Release Version
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
deleted file mode 100644
index 24a7a29..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
+++ /dev/null
@@ -1,137 +0,0 @@
-
-
- Components
-
- An overview of the Enea Edge Runtime and the Edge Management
- in cooperation with the Automation Framework and Test Harness, will
- be presented in detail.
-
-
- Component Overview
-
-
-
-
-
-
-
-
-
- Enea Edge
-
- Enea Edge is comprised of the Enea Edge Management and the Enea
- Edge Runtime.
-
-
- Enea Edge Management
-
- The Enea Edge Management application needs to be installed on a
- supported platform. Upon installation, the system will be set up to
- manage Enea Edge "devices", these are the virtualized CPE devices
- used in testing.
-
- For more on Enea Edge Management installation instructions, please
- refer to the section on how to Installing the Enea Edge Management in the
-
- Manual.
-
-
-
- Enea Edge Runtime
-
- One or more uCPE devices running the Enea Edge Runtime
- are required as hosts to run the VNF(s). The uCPE device is
- known to the Enea Edge Management as the "VcpeAgent" device module.
-
-
- Before running any use case with the Automation Framework or the
- Test Harness, make sure the uCPE device(s) have been added to the Edge Management.
-
-
- Adding a VcpeAgent device can be done via two methods:
-
-
-
- Through the Enea Edge Management GUI. Add the device using the
- appropriate parameters by launching the UI under
- Devices -> Manage in the
- main screen.
-
-
-
- REST API. Invoke the Enea Edge Management REST API to add a
- device.
-
-
-
- For more on Enea Edge installation instructions, please
- refer to chapter Preparing the USB stick for installation of the
- Enea Edge Runtime in the
- Manual.
-
-
-
-
- Automation Framework
-
- Testing can be performed by running the available Python scripts
- against the Enea Edge Management REST API (Python samples supplied). This can be
- done by using the Python scripts individually or by using the Python
- unit-test suite that is able to automatically run test-cases defined for
- each available Python script.
-
- In either case, it is desirable to use a different host (instead of
- running the tests on the same system as the Enea Edge Management) in order to
- ensure that the Enea Edge Management is setup and installed correctly in terms of
- allowing external users to access it and use it effectively.
-
-
-
- Test Harness
-
- The Test Harness (TH) provides a way for driving configuration with
- Ansible Playbooks, by running the python modules from the Automation
- Framework (AF) and by direct connection over SSH to the boards that run
- Enea Edge.
-
- The Test Harness includes an automated test suite that
- contains:
-
-
-
- VNF, Device and Network Smoke Test Cases. A sample test suite
- that acts as basic smoke tests for Enea Edge and also as a
- sanity-check test suite for the AF and TH.
-
-
-
- VNF Deployment and Lifecycle. A sample test suite that verifies
- the instantiation, lifecycle control and destruction of a VNF for Enea
- Edge.
-
-
-
- Service Creation and Lifecycle. A sample test suite that
- contains complex test cases showcasing service creation and lifecycle
- management.
-
-
-
- For details about the test suites or test cases please refer to
- chapter Sample Test Cases in the
- Manual.
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
deleted file mode 100644
index 97666cf..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
+++ /dev/null
@@ -1,239 +0,0 @@
-
-
- Getting Started with the Automation Framework and Test
- Harness
-
-
- Prerequisites
-
- For installation of the Automation Framework and Test Harness a
- CentOS 7 host machine is needed with support for:
-
-
-
- Python 2.7.
-
-
-
- EPEL Repository:sudo yum install epel-release
-
-
-
- PIP package manager: sudo yum -y install python-pip
-
-
-
- Virtualenv tool: sudo pip install virtualenv
-
-
-
-
- The Automation Framework and Test Harness installation may be done
- on the same machine used for Enea Edge Management installation, although this is
- not encouraged. For more details see section Automation Framework in the .
-
-
-
-
- Environment
-
-
- Lab setup overview for Basic Setup
-
-
-
-
-
-
- The following enviroment setup is needed for running all tests
- defined in the
- manual:
-
- Lab Network
- Requirements
-
- DHCP enabled.
-
-
-
- Internet Connectivity.
-
-
-
- Enea Edge Management Host
- Requirements
-
-
-
- Running CentOS 7.
-
-
-
- Connected to the Lab Network.
-
-
-
- Enea Edge Management installed.
-
-
- For details on how to install the Enea Edge Management, see Installing the Enea Edge Management in the
-
- Manual.
-
-
-
-
- uCPE device
- Requirements
-
- Minimum of 4 Physical Network Devices.
-
-
-
- 4GB RAM and 4 cores (Intel C3000 or Xeon D).
-
-
-
- 2 Physical connections to the Lab Network.
-
-
-
- Enea Edge Runtime installed.
-
-
- For information on how to install Enea Edge refer to
- Preparing the USB stick for installation
- of the Enea Edge Runtime in the
- Manual.
-
-
-
- Lab Setup Overview for ChainedVNFsService
-
-
-
-
-
-
-
-
- uCPE device 1 and 2
- Requirements
-
- Minimum of 4 Physical Network Devices.
-
-
-
- 16GB RAM and 8 cores (Intel C3000 or Xeon D).
-
-
-
- 2 Physical connections to the Lab Network.
-
-
-
- 1 Physical connection back to back between both uCPE
- devices.
-
-
-
- Enea Edge Runtime installed.
-
-
-
-
-
- Installation and Initial Setup
-
-
-
- Unzip the
- Enea_NFV_Access_AF-TH_<version>-build<build_number>.zip
- archive file, provided by Enea, on a supported host machine.
-
- The directory in which the archive has been unpacked will be
- denoted as <AF-TH-installdir> .
-
-
-
- Enter the <AF-TH-install-dir> directory
- and run the setup_env.sh script to do the initial
- setup of the Test Harness environment: source setup_env.sh
-
-
-
- Set up the Enea Edge Management which will be used by the TH:
-
-
-
- Create the Enea Edge Management JSON config file in the
- <AF-TH-install-dir>/uCPEM_config/
- directory:{
-"ucpe_usr":"Enea Edge Management Username",
-"ucpe_pass":"Enea Edge Management Password",
-"ucpe_host":"Enea Edge Management IP/Hostname",
-"ftp_usr":"FTP Username",
-"ftp_pass":"FTP Password",
-"ftp_port":"FTP Port"
-} See the
- <AF-TH-install-dir>/uCPEM_config/ucpem01.json
- file as an example.
-
-
-
- Run the setupuCPEManager.yml Ansible
- Playbook with the JSON config path as a parameter:
- ansible-playbook playbooks/setupuCPEManager.yml -e\
-"@uCPEM_config/<config_name>.json"
-
- Example ansible-playbook playbooks/setupuCPEManager.yml -e\
-"@uCPEM_config/ucpem01.json"
-
-
-
-
-
-
- The steps presented in this section are to be executed only once,
- for the initial setup of the TH environment.
-
-
- After the initial setup, each session ends by closing the Python
- virtual environment through running deactivate from the
- <AF-THinstall-dir> directory.
-
- Subsequent use of the installation requires activating the Python
- virtual enviroment before using the Automation Framework and Test Harness:
- source
- <AF-TH-install-dir>/testHarness-venv/bin/activate .
-
- Furthermore, if a user wants to use a new Enea Edge Management instance for
- a new session, the user also has to re-run the
- setupuCPEManager.yml playbook with the corresponding
- JSON config for the new Enea Edge Management instance.
-
-
- Automation Framework and Test Harness History Information can be
- found in the AF&TH CHANGELOG file available in:
- <AF-TH-install-dir>/CHANGELOG
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png
deleted file mode 100755
index 0329450..0000000
Binary files a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png
deleted file mode 100755
index a384877..0000000
Binary files a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/environment_basicsetup.png b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/environment_basicsetup.png
deleted file mode 100755
index c30dcfd..0000000
Binary files a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/environment_basicsetup.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml
deleted file mode 100644
index b2486a0..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml
+++ /dev/null
@@ -1,188 +0,0 @@
-
-
- Overview
-
- This document describes the Automation Framework and Test Harness for
- Enea Edge, along with instructions regarding the necessary steps to
- run these software tools.
-
-
- Description
-
- The Automation Framework provides a way for driving configuration
- with Python scripting. It complements the Enea Edge Management GUI and uses
- the northbound REST APIs, given to provide full usability of the Enea Management
- features.
-
- The Test Harness is based on running Ansible Playbooks to complete
- different test cases, which make use of the Automation Framework Python
- modules and/or direct commands on the uCPE devices running the Enea Edge Runtime.
-
-
-
- Definitions and Acronyms
-
-
- Definitions
-
-
-
-
-
-
- Component
-
- Description
-
-
-
-
-
- Enea Edge
-
- The Enea Edge (with ODM) Runtime and the
- Enea Edge Management.
-
-
-
-
-
-
- Acronyms
-
-
-
-
-
-
- Component
-
- Description
-
-
-
-
-
- AF
-
- Automation Framework for Enea Edge.
-
-
-
- API
-
- Application Programming Interface.
-
-
-
- DHCP
-
- Dynamic Host Configuration Protocol.
-
-
-
- DPDK
-
- Data Plane Development Kit.
-
-
-
- FTP
-
- File Transfer Protocol.
-
-
-
- GUI
-
- Graphical User Interface.
-
-
-
- IP
-
- Internet Protocol.
-
-
-
- JSON
-
- JavaScript Object Notation.
-
-
-
- NIC
-
- Network Interface Card.
-
-
-
- NETCONF
-
- Network Configuration Protocol.
-
-
-
- NFV
-
- Network Functions Virtualization.
-
-
-
- ODM
-
- Enea Element On Device Management.
-
-
-
- OVS
-
- Open vSwitch.
-
-
-
- REST
-
- Representational State Transfer.
-
-
-
- SR-IOV
-
- Single Root Input/Output Virtualization.
-
-
-
- SSH
-
- Secure Shell.
-
-
-
- TH
-
- Test Harness for Enea Edge.
-
-
-
- Enea Edge Management
-
- Enea Universal Customer Premises Equipment Manager.
-
-
-
- VCPE
-
- Virtual Customer Premises Equipment.
-
-
-
- VNF
-
- Virtualized Network Function.
-
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
deleted file mode 100644
index a5cd664..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
- Troubleshooting Guide
-
- The following are best practices and possible solutions to problems
- that may occur during operation:
-
-
-
- All the Playbooks have to be run from the root directory of the
- Test Harness (TH) to avoid failures such as "File not found!", since the
- paths to the required configuration files are hardcoded into the
- Playbooks.
-
-
-
- If the setup_env.sh fails, for debugging remove
- &> /dev/null from the failed command. The
- output of the command will be printed, and will not be redirected to
- /dev/null anymore.
-
-
-
- When setting up the Enea Edge Management to be used by the TH through the
- setupuCPEManager.yml Playbook, if the uCPE
- username/password/host are incorrect or are missing, all the Sample test
- cases will fail. If the FTP username/password/port are wrong or are
- missing, the tests that require file transfer to the Enea Edge Management will
- fail.
-
-
-
- Ansible logs are not written into the
- log/ansible.log file when the
- stdout_callback is set to
- selective in the ansible.cfg file.
- For debugging, check the python logs from the
- log/debug.log file or change the
- stdout_callback to debug and rerun
- the test.
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk b/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk
deleted file mode 100755
index 6b65cff..0000000
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-auto-fw-th-user-guide
-BOOKDESC_$(BOOKPACKAGES) := "Enea Enea Edge $(PROD_VER) Automation Framework and Test Harness User Guide"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml b/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
deleted file mode 100644
index 89692b0..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/128t_vnf_router.xml
+++ /dev/null
@@ -1,715 +0,0 @@
-
-
- 128T VNF Router Example Use-case
-
- The 128T Networking Platform (128T) natively provides network-based
- security, control, and insight across data centers, wide-area networks
- (WAN), and edge locations for enterprises, service providers, and cloud
- companies alike.
-
-
- Prerequisites
-
- The following are needed for this example use case:
-
-
-
- 1 in band management port for device management.
-
-
-
- 1 in band management port for 128T VNF.
-
-
-
- 1 WAN interface for 128T.
-
-
-
- 1 LAN interface for 128T.
-
-
-
- The following files are needed for this example use-case:
-
-
-
- 128T router VNF image. Please contact 128 Technology to get a
- VNF image and its license file.
-
-
-
- cloud-init iso image.
-
-
-
-
- For data path validation, it may be required to generate a new
- cloud-init image to match your network configuration.
-
-
-
-
- 128T VNF Router
-
-
- 128T VNF Router Setup Overview
-
-
-
-
-
-
-
-
-
- Use-case Setup
-
- Configuring Network Interfaces on uCPE
- devices:
-
- Add the trgt uCPE device into Enea Edge Management:
- Devices -> Manage -> Add .
-
- Fill in the required fields with the following data:
-
-
- Device Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- Type
-
- Enea universal CPE
-
-
-
- Release
-
- 2.2.2
-
-
-
- Name
-
- trgt
-
-
-
- IP/DNS Address
-
- <unspecified>
-
-
-
- Description
-
- Target 1
-
-
-
- SSH Port
-
- 830
-
-
-
- SSH User Name
-
- root
-
-
-
- Password
-
- null
-
-
-
- Device ID
-
- Also configured during installation of the device
- (E.g.: Target-15).
-
-
-
- OK
-
- Green status indicates connection with uCPE device
- was established.
-
-
-
-
-
-
-
- In order to add the device on the map: Right-Click on
- Map -> Place Device -> trgt .
-
-
-
- Configure the virtualization infrastructure for 128T VNF by
- creating three OVS bridges and a host interface:
-
- Add the Host Interface by selecting the trgt device, then
- Configuration -> External Interfaces ->
- Configuration -> Add , and fill in the required fields
- with the following data:
-
-
- Host Interface Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- Source
-
- enp4s0f1 . The only interface
- available for LAN connection.
-
-
-
- networking-type
-
- dpdk
-
-
-
- dpdk-type
-
- vfio-pci
-
-
-
- Create
-
- <interface enp4s0f1 ready to be used in a LAN
- bridge.>
-
-
-
-
-
- Select the trgt device then: Configuration ->
- OpenVSwitch -> Bridges -> Add , and fill in the
- required fields for each bridge with the following data from each
- table:
-
-
- ibm_br Bridge Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- id
-
- <autogenerated - do not change>
-
-
-
- Name
-
- ibm_br
-
-
-
- ovs-bridge-type
-
- inbandMgmt
-
-
-
- Create
-
- The system will automatically select the
- physical interface that has access to Enea Edge
- Management.
-
-
-
-
-
-
- vnf_mgmt_br Bridge Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- id
-
- <autogenerated - do not change>
-
-
-
- Name
-
- vnf_mgmt_br
-
-
-
- ovs-bridge-type
-
- vnfMgmt
-
-
-
- vnf-mgmt-address
-
- 10.0.0.1
-
-
-
- Create
-
-
-
-
-
-
-
-
- lan_br Bridge Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- id
-
- <autogenerated - do not change>
-
-
-
- Name
-
- lan_br
-
-
-
- ovs-bridge-type
-
- dataPlane
-
-
-
- sub-type
-
- communication
-
-
-
- +
-
- Name: enp4s0f1 OK
-
-
-
- Create
-
-
-
-
-
-
-
-
-
- Onboarding the VNFs:
-
- Onboard the VM Image through VNF -> Descriptors ->
- On-board , and fill in the required fields with the following
- values:
-
-
- VM Image Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- VM image file
-
- centos_128t_with_ci.qcow2
-
-
-
- Image format
-
- QCOW2
-
-
-
- VNF Type Name
-
- 128T
-
-
-
- Description
-
- 128T Router
-
-
-
- Version
-
- 1.0
-
-
-
- Memory in MB
-
- 8192. More memory can be allocated if required
- (<28672).
-
-
-
- Num. of CPUs
-
- 2. More CPUs can be reserved if required
- (<15).
-
-
-
- Interfaces -> +
-
- Name: mgmt
-
-
-
- Interfaces -> +
-
- Name: wan
-
-
-
- Interfaces -> +
-
- Name: lan
-
-
-
- Cloud Init -> Cloud-Init Datasource
-
- ISO
-
-
-
- Cloud Init -> Cloud-Init Disk Type
-
- cdrom
-
-
-
- Properties -> +
-
- Name: vnfMgmtIpAddress. Value: 10.0.0.2
-
-
-
- Properties -> +
-
- Name: internalMgmtPort. Value: 443
-
-
-
- Properties -> +
-
- Name: externalMgmtPort. Value: 60001
-
-
-
- Onboard
-
- <Wait for message: VNF package onboarded
- successfully>
-
-
-
- Close
-
-
-
-
-
-
-
-
-
-
- HTTPS access (443) can be changed with another type of
- access. Please consult official 128T documentation and make sure
- the 128T VNF is configured to accept another type of connection
- before changing the port number.
-
-
-
- externalMgmtPort (60001) represents the
- external port on which the user can access the VNF management
- interface via HTTPS. Another port can be selected if needed. There
- are no other changes required or components affected by this
- change.
-
-
-
- vnfMgmtIpAddress (10.0.0.2) represents
- the IP address of the management interface of the 128T VNF.
- Changing this value requires an update to the 128T configuration
- to match the new IP address.
-
-
-
-
- Instantiating the VNFs:
-
- Instantiate the 128T VNF by selecting the trgt device, then
- VNF -> Instances -> Add .
-
- Fill in the required fields with the following values:
-
-
- 128T VNF Instantiation
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- Name
-
- 128T_trgt_1
-
-
-
- VNF Type
-
- 128T
-
-
-
- VNFD Version
-
- 1.0
-
-
-
- Flavour
-
- Canonical
-
-
-
- uCPE Device
-
- trgt
-
-
-
- Cloud Init File
-
- centos_128t_internet_ci.iso
-
-
-
- Domain Update Script
-
-
-
-
-
- Interfaces
-
-
-
-
-
- ID
-
- IF Name
-
-
-
- mgmt (dpdk)
-
- Bridge: vnf_mgmt_br
-
-
-
- wan (dpdk)
-
- Bridge: ibm_br
-
-
-
- lan (dpdk)
-
- Bridge: lan_br
-
-
-
- Create
-
-
-
-
-
-
-
-
- To procure the VNF image files and their licenses, please
- contact each respective VNF provider.
-
-
-
-
- Testing the Use-case
-
- In order to access the web interface of the 128T VNF, open a
- browser from a machine connected on the same network with the WAN port
- of the trgt uCPE device and browse to:
- https://<public_trgt_WAN_IP>:60001 . Log in
- using the following credentials:
-
-
-
- Username: admin
-
-
-
- Password: 128Tadmin
-
-
-
- In order to validate the data path, connect a test machine to the
- LAN physical port, assign the static IP and a route:> ifconfig eth3 192.168.64.3 netmask 255.255.255.0
-> ip route add default via 192.168.64.1 dev eth3
-> ping 8.8.8.8
-
-
-
- Use-case Clean-up
-
- In order to remove the setup created previously all components
- need to be deleted in reverse order:
-
-
-
- Select the trgt uCPE device -> VNF -> Instances ->
- 128T -> Delete.
-
-
-
- Select the trgt uCPE device -> Configuration ->
- OpenVSwitch -> Bridges. Select all bridges -> Delete.
-
-
-
- Select the trgt uCPE device -> Configuration -> External
- Interfaces -> Configuration. Select all interfaces ->
- Delete.
-
-
-
- VNF -> Descriptors, select all bundles ->
- Offboard.
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_1.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_1.xml
deleted file mode 100644
index df262af..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_1.xml
+++ /dev/null
@@ -1,63 +0,0 @@
-
-
- How to create a 128T cloud-init iso image (day-0
- configuration)
-
- Prerequisites:
-
- Development host with Linux shell.
-
-
-
- genisoimage tool installed.
-
-
-
- Unpack the 128T/128t-cloud-init-example.tar.gz
- archive and check the README file for more details:
-
- >tar -zxf 128t-cloud-init-example.tar.gz
->cd 128T/cloud-init-example/
->ls ./
-README
-user-data
-meta-data
-t128-running.xml
-
- To generate the cloud-init iso image:
-
- >genisoimage -output centos_128t_ci.iso -volid cidata -joliet \
--rock user-data meta-data t128-running.xml
-
- Notes:
-
- user-data and meta-data
- files must be kept unchanged.
-
-
-
- To update the 128T configuration change the
- t128-runing.xml file.
-
-
-
- XML is the same file downloaded from 128T web access:
- configuration -> Import and Export Configuration ->
- Export Configuration -> Download Configuration . The
- configuration can be updated from a web interface, downloaded onto the
- development host and used in generating a new cloud-init iso
- image.
-
-
-
- By default, t128-running.xml is configured to pass
- all traffic from the LAN to the WAN interface. There is only one change
- required for the 128T VNF to work on the user's network:
-
- <rt:next-hop>172.24.15.254</rt:next-hop>
-
- Please change <172.24.15.254> with the IP address of your
- Gateway in the t128-running.xml file and generate a new
- iso image as described above. For more details about configuring the 128T
- VNF please contact 128 Technologies.
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_2.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_2.xml
deleted file mode 100644
index 2458d99..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_2.xml
+++ /dev/null
@@ -1,326 +0,0 @@
-
-
- How to create the 128T image for NFV Access
-
- The following steps were used by Enea to generate the 128T qcow2 image
- used as the VNF image on NFV Access.
-
-
- Keep in mind a Virtual Machine was used instead of a physical
- host.
-
-
- Prerequisites:
-
- 128T-3.2.7-1.el7.centos.x86_64.iso provided
- by 128 Technologies.
-
-
-
- A Linux development host with internet access.
-
-
-
- A least one of the TAP interfaces connected to a bridge with
- Internet access.
-
- How to create the 128T image for NFV
- Access:
-
- >qemu-img create -f qcow2 128t.qcow2 128G
->qemu-system-x86_64 -enable-kvm -m 8G -cpu host -smp cores=3,sockets=1 \
--M q35 -nographic bios /usr/share/qemu/bios.bin -boot order=d,menu=on \
-cdrom 128T-3.2.7-1.el7.centos.x86_64.iso \
-hdb 128t.qcow2 \
-device e1000,netdev=net1,mac=52:52:01:02:03:01 \
-netdev tap,id=net1,ifname=tap1,script=no,downscript=no
-
-
-
- Press the <ENTER> key to begin the installation
- process.
-
-
-
- Wait for the distribution and the 128T to install:
-
- ------------------------------
-128T Packages Installed
-
-Please Remove Install Media,
-
-then enter <Yes> to reboot and
-continue install process
-
- <Yes> <No>
-------------------------------
-
- Press Yes.
-
-
-
- Wait to reboot and press CTR+ a+c to enter
- the qemu monitor:
-
- (qemu) quit
-
-
-
- Start qemu only with the qcow2 image attached, no installer
- image required:
-
- >qemu-system-x86_64 -enable-kvm -m 8G -cpu host -smp cores=3,sockets=1 \
--M q35 -nographic bios /usr/share/qemu/bios.bin \
--boot order=c,menu=on \
--hda 128t.qcow2 \
--device e1000,netdev=net1,mac=52:52:01:02:03:01 \
--netdev tap,id=net1,ifname=tap1,script=no,downscript=no
-
-------------------------------------------------------------------------------
-Booting from Hard Disk...
-.
-
- * CentOS Linux (3.10.0-514.2.2.el7.x86_64) 7 (Core)
- CentOS Linux (0-rescue-4e73a369e89e466a888c9c77655a1d65) 7 (Core)
-
-
- Use the ^ and v keys to change the selection.
- Press 'e' to edit the selected item, or 'c' for a command prompt.
-------------------------------------------------------------------------------
-
- Select the first option.
-
-
-
- |-------------------128T Installer-------------------|
-| |
-| Configure Linux Networking |
-| |
-| Before 128T SetUp? |
-| |
-| |
-| < Yes > < No > |
-|----------------------------------------------------|
-
- Select NO.
-
-
-
- |----------------------------------------------------|
-| Please select a role for this node: |
-| |----------------------------------------------| |
-| | (*) Router | |
-| | ( ) Conductor | |
-| |----------------------------------------------| |
-| |
-|----------------------------------------------------|
-| < OK > < Back > |
-|----------------------------------------------------| Select
- Router and OK.
-
-
-
- |-------------------Conductor Info-------------------|
-| |
-| |----------------------------------------------| |
-| |1st Conductor Address | |
-| |Conductor Address | |
-| |----------------------------------------------| |
-| |
-|----------------------------------------------------|
-| < OK > < Skip > < Back > < Help > |
-|----------------------------------------------------|
-
- Select SKIP.
-
-
-
- |----------------------HA Setup----------------------|
-| What kind of Router node is this? |
-| |----------------------------------------------| |
-| |(*) Standalone No HA peer | |
-| |( ) 1st HA Node HA peer is not set up | |
-| |( ) 2nd HA Node HA peer is already set up | |
-| |----------------------------------------------| |
-| |
-| |
-|----------------------------------------------------|
-| < OK > < Back > |
-|----------------------------------------------------| Select
- Standalone and OK.
-
-
-
- |---------------------Node Info----------------------|
-| |----------------------------------------------| |
-| | Node Role Router | |
-| | Node Name 128tNode | |
-| | Router Name 128tRouter | |
-| |----------------------------------------------| |
-| |
-|----------------------------------------------------|
-| < OK > < Advanced > < Back > < Help > |
-|----------------------------------------------------|
-
- Enter a name for the router and node, press OK.
-
-
-
- |-------------------Password Setup-------------------|
-| Enter the new password for the 128T 'admin' |
-| user: |
-| |----------------------------------------------| |
-| | 128Tadmin | |
-| |----------------------------------------------| |
-| | |
-|----------------------------------------------------|
-| < OK > < Back > |
-|----------------------------------------------------|
-
- Enter the password for web access: 128Tadmin
- and confirm the password.
-
-
-
- |--------------------------Anonymous Data Collection--------------------------|
-| The 128T Networking Platform comes packaged with a software process |
-|("Roadrunner") that is used to proactively monitor the health and liveliness |
-|of the 128T Router and associated components. This watchdog process collects |
-|anonymous information from the router and sends it to 128 Technology for |
-|storage and analysis. This information helps inform 128 Technology about |
-|software usage, to aid in the support and improvement of the 128 Technology |
-|Networking Platform. |
-| |
-|Disabling this feature will prevent the sending of anonymous usage data to |
-|128 Technology. |
-| |
-| |
-| < Accept > < Back > < Disable > |
-|-----------------------------------------------------------------------------|
-
- Select Accept.
-
-
-
- |-----128T Statistics Table Creator-----|
-| Created table for metric 760/827 |
-| Created table for metric 770/827 |
-| Created table for metric 780/827 |
-| Created table for metric 790/827 |
-| Created table for metric 800/827 |
-| Created table for metric 810/827 |
-| Created table for metric 820/827 |
-| Finished pre-creating stats tables |
-| Creating tables for audit events |
-| Finished creating audit event tables |
-| Completed in 27.001386642456055 s |
-| Shutting down local Cassandra node |
-|---------------------------------------|
-| < OK > |
-|---------------------------------------|
-
- Select OK.
-
-
-
- |--------128T Installer Status----------|
-| |
-| Install SUCCESS |
-| |
-| Start 128T Router |
-| before proceeding to |
-| login prompt? |
-|---------------------------------------|
-| < Yes > < No > |
-|---------------------------------------|
-
- Select: Yes
-
-
-
- localhost login: root
-Password:
-
- The following user accounts and passwords are created during the
- ISO installation process:
-
-
- Accounts Created
-
-
-
-
-
-
- User
-
- Password
-
-
-
-
-
- root
-
- 128tRoutes
-
-
-
- t128
-
- 128tRoutes
-
-
-
-
-
-
-
- GUI login via HTTPS is enabled by default on port 443
-
- [root@localhost ~]# dhclient enp0s2
-[root@localhost ~]# echo "nameserver 8.8.8.8" >>/etc/resolv.conf
-[root@localhost ~]# yum -y install cloud-init
-[root@localhost ~]# reboot
-
-
-
- Wait to reboot and press CTR+ a+c to enter in qemu
- monitor.
-
- (qemu) quit
-> qemu-img info 128t.qcow2
-image: 128t.qcow2
-file format: qcow2
-virtual size: 128G (137438953472 bytes)
-disk size: 5.4G
-cluster_size: 65536
-Format specific information:
- compat: 1.1
- lazy refcounts: false
- refcount bits: 16
- corrupt: false
-
-
-
- Compress the generated 128t.qcow2 image to
- decrease the size of VNF image:
-
- qemu-img convert -O qcow2 -c 128t.qcow2 centos_128t_compressed.qcow2
-
-> qemu-img info centos_128t_compressed.qcow2
-image: centos_128t_compressed.qcow2
-file format: qcow2
-virtual size: 128G (137438953472 bytes)
-disk size: 1.2G
-cluster_size: 65536
-Format specific information:
- compat: 1.1
- lazy refcounts: false
- refcount bits: 16
- corrupt: false
-
-centos_128t_compressed.qcow2 - Resulted image can be used in NFV Access.
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_3.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_3.xml
deleted file mode 100644
index e8bd5ce..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-
-
- How to configure Fortigate VNF (day-0 configuration)
-
- Please check the README file from Fortigate folder for more
- details.
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
deleted file mode 100644
index 0e207ae..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_4.xml
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
- Running Enea Automation Framework and Test Harness
-
- For more detailed information regarding the Automation Framework and
- Test Harness please see the .
-
- The most relevant information from the Automation Framework and Test
- Harness structure is presented below:
-
- |---automation_framework
-| |---unittestSuite
-| | |---128tCleanup.json - Use case 1 - clean up - test.
-| | |---128tDeploy.json - Use case 1 - test.
-| | |---128t_FG_SFCCleanup.json - Use case 2 - clean up - test.
-| | |---128t_FG_SFCDeploy.json - Use case 2 - test.
-| | |---config
-| | | |---cust
- - Folder containing the configuration files used by tests.
-| | |---unittestLoader.py
-| | |---unittestSuite.py
-|---lab_config
-| |---trgt-1
-| | |---ibm_br.json - In-band management definition.
-| | |---lan_br.json - Lan bridge definition.
-| | |---target.json
- - Target definition - the "address", "deviceId", "name" and \
- "version" must be updated.
-| | |---sfc_br.json - Service chain bridge definition.
-| | |---vnf_mgmt_br.json - VNF management bridge definition.
-| | |---lan_nic.json - NIC definition.
-|---vnf_config
-| |---128t
-| | |---128tInstance.json - 128T instantiation - used in use case 1.
-| | |---128t.json - 128T onboarding.
-| | |---128tSFCInstance.json - 128T instantiation - used in use case 2.
-| | |---centos_128t_internet_ci.iso - 128T cloud init (day-0) iso image.
-| |---fortigate
-| | |---fg_basic_fw.conf - Fortigate day-0 configuration.
-| | |---fortigateInstance.json - Fortigate instantiantion.
-| | |---fortigate.json - Fortigate onboarding.
-| | |---fortigateLicense.lic
- - Fortigate license - contact Fortinet to get a VNF image and license file.
-|---vnf_image
-| |---centos_128t_with_ci.qcow2 - Contact 128 Technology to get a \
- VNF image and its license file.
-| |---fortios.qcow2 - Contact Fortinet to get a VNF image \
- and its license file.
-
- Make sure to update the relevant configuration file for your setup.
- The essential files to consider are the uCPE Device configuration
- (target.json ), the license for the Fortigate VNF, and
- the 128T cloud-init iso image matching your network.
-
- For uCPE Device configuration (target.json )
- please change the following information, if needed, in the JSON file:
-
-
-
- address - The IP address of uCPE Device.
-
-
-
- version - The NFVA version.
-
-
-
- deviceId - The device ID of uCPE Device.
-
-
-
- name - The name of uCPE Device.
-
-
-
-
- Before starting the two usecases detailed in the following appendix,
- the uCPE Device needs to be added into Enea Edge Management.
-
-
- To properly set up the Automation Framework and Test Harness please
- see Installation and Initial Setup in the
- for more details.
-
- To run a test:
-
- > cd automation_framework/unittestSuite/
-> python unittestSuite.py -u admin -p admin -H <uCPEManager IP address> -n \
-<uCPE Device name> -s <Test suite> -d <description>
-
- The Test suite must be one from any of the
- following: 128tDeploy.json ,
- 128tCleanup.json ,
- 128t_FG_SFCDeploy.json , or
- 128t_FG_SFCCleanup.json .
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml b/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
deleted file mode 100644
index 67f38e5..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/appendix_5.xml
+++ /dev/null
@@ -1,243 +0,0 @@
-
-
- Example Tests Results using the Automation Framework and Test Harness
-
- In order to run the following example usecases, certain configuration
- file entries need to be modified according to the network setup that it will
- be used, for more details see the previous appendix:
-
-
-
- uCPE Device name: inteld1521-17
-
-
-
- address: 172.24.8.62
-
-
-
- version: 2.2.3
-
-
-
- deviceId: inteld1521-17
-
-
-
- > cat lab_config/trgt-1/target.json
-{
- "name": "inteld1521-17",
- "deviceGroupingTags": " ",
- "description": "trgt",
- "address": "172.24.8.62",
- "port": "830",
- "username": "root",
- "password": "",
- "certificate": null,
- "passphrase": null,
- "callHome": "false",
- "maintMode": "false",
- "version": "2.2.3",
- "deviceId": "inteld1521-17"
-} The IP address of Enea Edge Management that will be used in
- these examples is 172.24.3.92 .
-
- The FortiGate and 128T VNF images need to be copied into the
- vnf_image directory. The names should be the same as
- those described in the previous appendix.
-
- The FortiGate valid license file needs to be copied into the
- vnf_config/fortigate/ directory. The name should be the
- same as that described in the previous appendix.
-
- The cloud init files that match the network, need to be copied into
- the vnf_config/fortigate/ and the
- vnf_config/128t/ directories respectively. The names
- should be the same as those described in the previous appendix.
-
-
- Use-case 1: 128T VNF Router Example Use-case
-
- > cd automation_framework/unittestSuite/
-> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
--s 128tDeploy.json -d "128T Deployment"
-
-Running 128T Deployment...
-
-test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ...
-2020-08-26 10:10:05,517 - INFO: Wait uCPE device
-2020-08-26 10:10:36,650 - INFO: Status: Connected
-2020-08-26 10:10:36,651 - INFO: Done
-ok
-test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ...
-2020-08-26 10:10:36,686 - INFO: Bind NIC
-2020-08-26 10:10:37,788 - INFO: Done
-ok
-test 003: Creating ibm bridge (__main__.UnittestSuite) ...
-2020-08-26 10:10:37,818 - INFO: New OVS network bridge
-2020-08-26 10:10:58,762 - INFO: Done
-ok
-test 004: Creating VNF Management bridge (__main__.UnittestSuite) ...
-2020-08-26 10:10:58,794 - INFO: New OVS network bridge
-2020-08-26 10:10:58,977 - INFO: Done
-ok
-test 005: Creating LAN bridge and attaching lan interface to the bridge \
-(__main__.UnittestSuite) ...
-2020-08-26 10:10:59,003 - INFO: New OVS network bridge
-2020-08-26 10:10:59,334 - INFO: Done
-ok
-test 006: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ...
-2020-08-26 10:10:59,370 - INFO: Onboard wizard
-2020-08-26 10:13:55,775 - INFO: Done
-ok
-test 007: Instantiate 128T VNF (__main__.UnittestSuite) ...
-2020-08-26 10:13:55,813 - INFO: Instantiate VNF
-2020-08-26 10:14:56,583 - INFO: Done
-ok
-
-----------------------------------------------------------------------
-Ran 7 tests in 291.103s
-
-OK
-
-> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
--s 128tCleanup.json -d "128T Cleanup"
-
-Running 128T Cleanup...
-
-test 001: Destroying 128T VNF (__main__.UnittestSuite) ...
-2020-08-26 10:15:28,395 - INFO: Destroy VNF
-2020-08-26 10:15:29,452 - INFO: Done
-ok
-test 002: Deleting network bridge LAN (__main__.UnittestSuite) ...
-2020-08-26 10:15:29,493 - INFO: Delete OVS network bridge
-2020-08-26 10:15:29,734 - INFO: Done
-ok
-test 003: Deleting VNF management bridge (__main__.UnittestSuite) ...
-2020-08-26 10:15:29,765 - INFO: Delete OVS network bridge
-2020-08-26 10:15:30,080 - INFO: Done
-ok
-test 004: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ...
-2020-08-26 10:15:30,110 - INFO: Delete OVS network bridge
-2020-08-26 10:15:46,907 - INFO: Done
-ok
-test 005: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ...
-2020-08-26 10:15:46,967 - INFO: Unbind NIC
-2020-08-26 10:15:48,489 - INFO: Done
-ok
-test 006: Offboarding 128t VNF (__main__.UnittestSuite) ...
-2020-08-26 10:15:48,531 - INFO: Offboard VNF
-2020-08-26 10:15:49,171 - INFO: Done
-ok
-
-----------------------------------------------------------------------
-Ran 6 tests in 20.808s
-
-OK
-
-
-
- Use-case 2: Service Chaining 128T - Fortigate Example
- Use-case
-
- > python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
--s 128t_FG_SFCDeploy.json -d "128T - Fortigate SFC Deployment"
-
-Running 128T - Fortigate SFC Deployment...
-
-test 001: Wait VCPE Agent device be up (__main__.UnittestSuite) ...
-2020-08-26 10:17:29,361 - INFO: Wait uCPE device
-2020-08-26 10:18:00,473 - INFO: Status: Connected
-2020-08-26 10:18:00,474 - INFO: Done
-ok
-test 002: Bind NIC to DPDK for LAN connection (__main__.UnittestSuite) ...
-2020-08-26 10:18:00,634 - INFO: Bind NIC
-2020-08-26 10:18:01,805 - INFO: Done
-ok
-test 003: Creating ibm bridge (__main__.UnittestSuite) ...
-2020-08-26 10:18:01,863 - INFO: New OVS network bridge
-2020-08-26 10:18:30,640 - INFO: Done
-ok
-test 004: Creating VNF Management bridge (__main__.UnittestSuite) ...
-2020-08-26 10:18:30,670 - INFO: New OVS network bridge
-2020-08-26 10:18:30,876 - INFO: Done
-ok
-test 005: Creating LAN bridge and attaching lan interface to the bridge \
-(__main__.UnittestSuite) ...
-2020-08-26 10:18:30,908 - INFO: New OVS network bridge
-2020-08-26 10:18:31,243 - INFO: Done
-ok
-test 006: Creating SFC(service function chaining) bridge (__main__.UnittestSuite) ...
-2020-08-26 10:18:31,273 - INFO: New OVS network bridge
-2020-08-26 10:18:31,416 - INFO: Done
-ok
-test 007: Onboarding 128T VNF (wizard API) (__main__.UnittestSuite) ...
-2020-08-26 10:18:31,448 - INFO: Onboard wizard
-2020-08-26 10:21:21,569 - INFO: Done
-ok
-test 008: Onboarding Fortigate VNF (wizard API) (__main__.UnittestSuite) ...
-2020-08-26 10:21:21,608 - INFO: Onboard wizard
-2020-08-26 10:21:27,199 - INFO: Done
-ok
-test 009: Instantiate 128T VNF (__main__.UnittestSuite) ...
-2020-08-26 10:21:27,226 - INFO: Instantiate VNF
-2020-08-26 10:22:27,067 - INFO: Done
-ok
-test 010: Instantiate Fortigate VNF (__main__.UnittestSuite) ...
-2020-08-26 10:22:27,121 - INFO: Instantiate VNF
-2020-08-26 10:22:31,310 - INFO: Done
-ok
-
-----------------------------------------------------------------------
-Ran 10 tests in 301.989s
-
-OK
-
-> python unittestSuite.py -u admin -p admin -H 172.24.3.92 -n inteld1521-17 \
--s 128t_FG_SFCCleanup.json -d "128T - Fortigate SFC Cleanup"
-
-Running 128T - Fortigate SFC Cleanup...
-
-test 001: Destroying Fortigate VNF (__main__.UnittestSuite) ...
-2020-08-26 10:23:29,308 - INFO: Destroy VNF
-2020-08-26 10:23:30,026 - INFO: Done
-ok
-test 002: Destroying 128T VNF (__main__.UnittestSuite) ...
-2020-08-26 10:23:30,065 - INFO: Destroy VNF
-2020-08-26 10:23:30,917 - INFO: Done
-ok
-test 003: Deleting network bridge SFC (__main__.UnittestSuite) ...
-2020-08-26 10:23:30,960 - INFO: Delete OVS network bridge
-2020-08-26 10:23:31,123 - INFO: Done
-ok
-test 004: Deleting network bridge LAN (__main__.UnittestSuite) ...
-2020-08-26 10:23:31,156 - INFO: Delete OVS network bridge
-2020-08-26 10:23:31,381 - INFO: Done
-ok
-test 005: Deleting VNF management bridge (__main__.UnittestSuite) ...
-2020-08-26 10:23:31,412 - INFO: Delete OVS network bridge
-2020-08-26 10:23:31,596 - INFO: Done
-ok
-test 006: Deleting ibm(In Band Management) bridge (__main__.UnittestSuite) ...
-2020-08-26 10:23:31,621 - INFO: Delete OVS network bridge
-2020-08-26 10:23:47,980 - INFO: Done
-ok
-test 007: Unbind LAN NIC from DPDK target (__main__.UnittestSuite) ...
-2020-08-26 10:23:48,019 - INFO: Unbind NIC
-2020-08-26 10:23:49,547 - INFO: Done
-ok
-test 008: Offboarding 128t VNF (__main__.UnittestSuite) ...
-2020-08-26 10:23:49,575 - INFO: Offboard VNF
-2020-08-26 10:23:50,252 - INFO: Done
-ok
-test 009: Offboarding Fortigate VNF (__main__.UnittestSuite) ...
-2020-08-26 10:23:50,295 - INFO: Offboard VNF
-2020-08-26 10:23:50,589 - INFO: Done
-ok
-
-----------------------------------------------------------------------
-Ran 9 tests in 21.326s
-
-OK
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/book.xml b/doc/book-enea-nfv-access-example-usecases/doc/book.xml
deleted file mode 100644
index 9879c28..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/book.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-]>
-
- Enea Edge Example Use-cases
-
- Release Version
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml
deleted file mode 100644
index 8895c23..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/clav_vnf_examples.xml
+++ /dev/null
@@ -1,396 +0,0 @@
-
-
- Clavister VNF Example Use-cases
-
- The Clavister VNF is a telco-ready, carrier-grade virtual next
- generation firewall.
-
-
- Clavister VNF using an Open vSwitch Bridge
-
- In this use-case, uCPE device 1 runs the Clavister VNF, while uCPE
- device 2 runs two Enea Test VNFs with iPerf client and server
- applications. The uCPE devices are connected using OVS-DPDK
- bridges.
-
-
- Prerequisites
-
- Two uCPE devices will be required for this setup. The system
- requirements for each uCPE device are:
-
-
-
- 1 Network Interface
-
-
-
- 2 GB of RAM memory
-
-
-
- The following files are needed for this example use-case:
-
-
-
- Enea Test VNF image. Please contact Enea to get this image.
-
-
-
- Clavister VNF image. Please contact Clavister to get this
- image.
-
-
- VNF Configuration files. These files are provided with your Enea
- Edge release:
-
-
- clavister-cloudinit.conf .
- enea-vnf-iperf-client.conf .
- enea-vnf-iperf-server.conf .
-
-
-
-
-
-
- Use-case Setup
-
- In this use-case, uCPE device 1 runs the Clavister VNF, while uCPE
- device 2 runs two Enea Test VNFs with iPerf client and server
- applications. The uCPE devices are connected using OVS-DPDK
- bridges.
-
-
- Clavister VNF using an Open vSwitch bridge
-
-
-
-
-
-
-
-
-
- When connecting, the uCPE devices can use a back-to-back or a VPN connection.
- An appropriate interface with the required capabilities needs to be chosen for
- this purpose.
-
-
- Network Configuration:
-
-
-
- Select uCPE device 1, access Configuration ,
- add the network interface that will be used and configure it for
- DPDK.
-
-
-
- Create an OVS bridge and attach the DPDK network
- interface.
-
-
-
- Repeat the steps above for uCPE device 2.
-
-
-
- Onboarding the VNFs:
-
-
-
- Onboard the Clavister VNF by filling the required fields with
- the following values:
-
-
-
- VM Image File : Provide
- the path to the Clavister VNF qcow2 image
-
-
-
- Memory in MB : 1024
-
-
-
- Num of CPUs : 4
-
-
-
- Storage in GB : 20
-
-
-
- Interfaces : Add 2
- interfaces
-
-
-
- Cloud-init Datasource :
- ConfigDrive
-
-
-
- Cloud-init Disk Type :
- disk
-
-
-
-
-
- Onboard the Enea Test VNF by filling the required fields with
- the following values:
-
- VM Image File : Provide
- the path to the Enea Test VNF qcow2 image
-
-
-
- Memory in MB :
- 2048
-
-
-
- Num of CPUs : 2
-
-
-
- Storage in GB :
- 10
-
-
-
- Interfaces : Add 1
- interface
-
-
-
- Cloud-init Datasource :
- NoCloud
-
-
-
- Cloud-init Disk Type :
- disk
-
-
-
-
-
- Instantiating the VNFs:
-
-
-
- Instantiate the Clavister VNF on uCPE device 1 using the
- required fields below:
-
-
-
- Name : clavister
-
-
-
- VNF Type : Select
- Clavister VNF
-
-
-
- uCPE Device : Select
- uCPE device 1
-
-
-
- Cloud Init File :
- Provide the path to the Clavister cloud-init file.
-
-
-
- Interfaces : Set the
- interface type to DPDK and select the OVS
- bridge created above, for both interfaces.
-
-
-
-
-
- Instantiate the Enea iPerf server VNF on uCPE device 2 by
- filling the required fields with the values below:
-
-
-
- Name :
- iperf_server
-
-
-
- VNF Type : Select Enea
- Test VNF
-
-
-
- uCPE Device : Select
- uCPE device 2
-
-
-
- Cloud Init File :
- Provide the path to the Enea VNF IPerf server cloud-init
- file.
-
-
-
- Interfaces : Set the
- interface type to DPDK and select the OVS
- bridge created above.
-
-
-
-
-
- Instantiate the Enea iPerf client VNF on uCPE device 2 by
- filling the required fields with the values below:
-
-
-
- Name :
- iperf_client
-
-
-
- VNF Type : Select Enea
- Test VNF
-
-
-
- uCPE Device : Select
- uCPE device 2
-
-
-
- Cloud Init File :
- Provide the path to the Enea VNF iPerf client cloud-init
- file.
-
-
-
- Interfaces : Set the
- interface type to DPDK and select the OVS
- bridge created above.
-
-
-
-
-
-
-
- Testing the Use-case
-
- SSH to uCPE device 2 (Username: root) and connect to the IPerf
- client VNF console:
-
- virsh list
-virsh console <id of iperf client>
-
- In order to check that traffic is forwarded between the VNFs, run
- the following:
-
- # qemux86-64 login: root
-root@qemux86-64:~# iperf3 -c 192.168.10.10
-
-
-
-
- Clavister VNF using SR-IOV
-
-
- Prerequisites
-
- Two uCPE devices will be required for this setup. The system
- requirements for each uCPE device are:
-
-
-
- 1 Network Interface
-
-
-
- 2 GB of RAM memory
-
-
-
- The following files are needed for this example use-case:
-
-
-
- Enea Test VNF image. Please contact Enea to get this image.
-
-
-
- Clavister VNF image. Please contact Clavister to get this
- image.
-
-
- VNF Configuration files. These files are provided with your Enea
- Edge release:
-
- clavister-cloudinit.conf .
- enea-vnf-iperf-client.conf .
- enea-vnf-iperf-server.conf .
-
-
-
-
-
-
- Use-case Setup
-
- The following use-case is essentially the same as the one detailed
- above, in this scenario however, the uCPE devices are connected using
- SR-IOV, with two virtual functions.
-
-
- Clavister VNF using SR-IOV
-
-
-
-
-
-
-
-
- Network Configuration:
-
-
-
- Select uCPE device 1, access Configuration ,
- add the network interface that will be used and configure it for
- SR-IOV. For sriov-mode select adapter-pool and for
- sriov-num-vfs select "2".
-
-
-
- Repeat the step above for uCPE device 2.
-
-
-
- Onboarding the VNFs:
-
- See the onboarding parameters in the use-case above.
-
- Instantiating the VNFs:
-
- Use the same instantiation parameters as above, but select
- interface type SrIovAdapterPool instead.
-
-
-
- Testing the Use-case
-
- Use the same test instructions as detailed in the use-case
- above.
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/enea_test_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/enea_test_vnf_examples.xml
deleted file mode 100644
index bee5a63..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/enea_test_vnf_examples.xml
+++ /dev/null
@@ -1,308 +0,0 @@
-
-
- Enea Test VNF Example Use-cases
-
- The Enea Test VNF is a simple Enea Linux based VM, which can be used
- for various testing purposes, by using basic DPDK applications (e.g.
- testpmd) as well as non-DPDK tools (e.g. iPerf3). For more information about
- the Testpmd application please see the Testpmd Application User
- Guide .
-
-
- Prerequisites
-
- Two uCPE devices will be required for this setup. The system
- requirements for each uCPE device are:
-
-
-
- 2 Network Interfaces. One for Enea Edge Management and one for data
- traffic.
-
-
-
- 2 GB of RAM memory
-
-
-
- The following files are needed for this example use case:
-
-
-
- VNF image: Enea Test VNF. Please contact Enea to get this
- image.
-
-
- VNF Configuration files. These files are provided with your Enea
- Edge release:
-
-
- enea-vnf-testpmd-fwd.conf .
-
-
-
- enea-vnf-testpmd-term.conf .
-
-
-
-
-
- TestPMD VNF
-
- In this use-case, uCPE device 1 runs the pktgen DPDK application to
- generate traffic and uCPE device 2 runs two Enea Test VNFs. One VNF runs
- the TestPMD DPDK application forwarding traffic, and the other runs the
- TestPMD in order to terminate traffic.
-
-
- TestPMD VNF Overview
-
-
-
-
-
-
-
-
-
- Use-case Setup
-
- Network Configuration:
-
-
-
- Select uCPE device 1, access Configuration ,
- add the network interface that will be used and configure it for
- DPDK. Note the PCI address of the interface, it will be used later
- to run the pktgen application.
-
-
-
- Select uCPE device 2, access Configuration ,
- add the network interface that will be used and configure it for
- DPDK.
-
-
-
- Create an OVS bridge on uCPE device 2 and attach the DPDK
- interface.
-
-
-
- Onboarding the VNF:
-
- Onboard the Enea Test VNF by filling the required fields with the
- following values:
-
-
-
- VM Image File : Provide the
- path to the Enea Test VNF qcow2 image.
-
-
-
- Memory in MB : 2048
-
-
-
- Num of CPUs : 2
-
-
-
- Storage in GB : 10
-
-
-
- Interfaces : Add 1
- interface.
-
-
-
- Cloud-init Datasource :
- NoCloud
-
-
-
- Cloud-init Disk Type :
- disk
-
-
-
- Instantiating the VNFs:
-
-
-
- Instantiate the Enea Edge TestPMD forwarding VNF on uCPE
- Device 2 by filling the required fields with the following
- values:
-
-
-
- Name : testpmd_fwd
-
-
-
- VNF Type : Select Enea
- Test VNF.
-
-
-
- uCPE Device : Select uCPE
- device 2.
-
-
-
- Cloud Init File : Provide
- the path to the Enea VNF TestPMD forwarding cloud-init
- file.
-
-
-
- Interfaces : Set the
- interface type to DPDK and select the OVS
- bridge created above.
-
-
-
-
-
- Instantiate the Enea Edge TestPMD termination VNF on
- uCPE Device 2 by filling the required fields with the following
- values:
-
-
-
- Name : testpmd_term
-
-
-
- VNF Type : Select Enea
- Test VNF.
-
-
-
- uCPE Device : Select uCPE
- device 2.
-
-
-
- Cloud Init File : Provide
- the path to the Enea VNF TestPMD termination cloud-init
- file.
-
-
-
- Interfaces : Set the
- interface type to DPDK and select the OVS
- bridge created above.
-
-
-
-
-
- Creating OVS flow rules:
-
- Select uCPE device 2, access Configuration ,
- open the OVS bridge and add two flow rules:
-
-
-
- Source: DPDK interface, Target:
- testpmd_fwd .
-
-
-
- Source: testpmd_fwd , Target:
- testpmd_term .
-
-
- The flow rules can be described using either the Enea Edge
- Management interface or the configuration files.
-
-
-
-
-
-
- Testing the Use-case
-
-
-
- SSH to uCPE device 1 (Username: root) and start the pktgen
- application:
-
- cd /usr/share/apps/pktgen/
-./pktgen -c 0x7 -n 4 --proc-type auto --socket-mem 256 -w 0000:01:00.0 -- \
- -P -m "[1:2].0"
-
-Pktgen:/> start 0
-
-
- Replace 0000:01:00.0 with the actual PCI address of the
- network interface used on uCPE device 1.
-
-
-
-
- SSH to uCPE device 2 and connect to the TestPMD forwarding VNF
- console:
-
- virsh list
-virsh console <id of testpmd fwd>
-
-
-
- Check the TestPMD traffic forwarding statistics:
-
- # qemux86-64 login: root
-tail -f /var/log/testpmd-out
-
-
-
-
-
- TestPMD VNF using PCI passthrough
-
- In this use case, uCPE device 1 will run the Pktgen and uCPE
- device 2 will run the TestPMD VNF. Both will be using PCI
- passthrough:
-
-
-
- Make sure that neither uCPE device 1 nor uCPE device 2 have
- any configured host interfaces by selcting uCPE device :
- Configuration ->
- OpenVSwitch -> Host
- Interfaces .
-
-
-
- On uCPE device 1 start the Pktgen VNF. Select
- PciPassthrough as the Interface type.
-
- From the drop-down list, select the PCI interface
- corresponding to the NIC which is connected to uCPE device 2:
-
-
-
- On uCPE device 2, start the TestPmdForwarder VNF. Select
- "PciPassthrough" as the Interface type. From the drop-down list,
- select the PCI interface corresponding to the NIC which is connected
- to uCPE device 1:
-
-
-
- To check that traffic is being forwarded from uCPE device 2,
- SSH to the uCPE device and connect to the VNFs console:
-
- Right click on uCPE device 2 and select SSH.
-Run: virsh list
-Run: virsh console [VM NAME]
-Run: tail -f /opt/testpmd-out
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml b/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
deleted file mode 100644
index bb38140..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/forti_vnf_examples.xml
+++ /dev/null
@@ -1,627 +0,0 @@
-
-
- FortiGate VNF Example Use-cases
-
- FortiGate virtual appliances feature all of the security and
- networking services common to traditional hardware-based FortiGate
- appliances. The virtual appliances can be integrated in Firewall or SD-WAN
- solution development.
-
-
- FortiGate VNF as a Firewall
-
- Enea provides an example of a simple basic firewall configuration
- for the FortiGate VNF. FortiGate In-Band Management is a feature used for
- running FortiGate Management traffic over WAN.
-
- Instructions on how to alter the default configuration are provided
- in section FortiGate VNF Web Management in the
-
- Manual.
-
-
- Prerequisites
-
- System requirements for the uCPE device:
-
-
-
- 4 x Network Interfaces
-
-
-
- 4 cores
-
-
-
- 4 GB of RAM memory
-
-
-
- The following file(s) are needed for this example use-case:
-
-
-
- FortiGate VNF image. Please contact Fortinet to get a VNF
- image and its license file.
-
-
-
- VNF Configuration file(s), provided with your Enea Edge
- release: fortigate-basic-fw.conf .
-
-
-
-
-
- Use-case Setup
-
-
- Fortigate VNF as a Firewall
-
-
-
-
-
-
-
-
- Network Configuration :
-
- Since the firewall uses three External Network Interfaces, three
- bridges need to be configured. Each bridge provides the ability to
- connect a physical network interface to the virtual network interface of
- a VM.
-
- Setup of the uCPE device:
-
-
-
- Connect WAN to the Lab Network.
-
-
-
- Connect LAN1 to the Test Machine.
-
-
-
- Leave LAN2 unconnected.
-
-
-
- Connect ETH0 to the Lab Network (for Enea Edge Management
- communications).
-
-
-
- Select the uCPE device, access
- Configuration and bind the three physical network
- interfaces to DPDK.
-
-
-
- Create three OVS bridges, one for each DPDK network interface
- (WAN, LAN1 and LAN2).
-
- Alternatively, the firewall can be setup to use bridges as
- connection points for the FortiGate VNF, by replacing the OVS-DPDK
- bridges with SR-IOV connection points.
-
- Please note that while previously three physical interfaces
- were presumed necessary for VNF connection, in the case of a
- firewall setup only two physical interfaces are required for the
- data path (one for WAN and one for LAN). Only two interfaces will be
- configured as DPDK, with two bridges created, one for each type of
- connection.
-
-
- At VNF instantiation instead of assigning distinct bridges
- for each LAN interface, only one will be used for both LAN1 and
- LAN2, with no changes in WAN interface configuration.
-
-
-
-
- Onboarding the VNF:
-
- Onboard the FortiGate VNF by filling the required fields with the
- following values:
-
-
-
- VM Image File : Provide the
- path to the FortiGate VNF qcow2 image.
-
-
-
- Memory in MB : 1024
-
-
-
- Num of CPUs : 1
-
-
-
- Storage in GB : 20
-
-
-
- Interfaces : Add 3 interfaces
- (wan, lan1 and lan2).
-
-
-
- Cloud-init Datasource :
- ConfigDrive
-
-
-
- Cloud-init Disk Type :
- cdrom
-
-
-
- Cloud-init content file : Add
- a file entry where Path: license.
-
-
-
- Instantiating the VNF:
-
- Instantiate the FortiGate VNF by filling the required fields with
- the following values:
-
-
-
- Name : Name of the VM which
- will be created on the uCPE device.
-
-
-
- VNF Type : Name of the
- onboarded VNF.
-
-
-
- uCPE Device : Select the uCPE
- device where the VNF will be instantiated.
-
-
-
- License file : The FortiGate
- license file provided by Fortinet.
-
-
-
- Configuration file : The
- Firewall example configuration file provided by Enea
- (fortigate-basic-fw.conf ).
-
-
-
- Port1 - WAN : Set the
- External Interface type to
- DPDK and connect it to the
- wan_br ovs bridge.
-
-
-
- Port2 - LAN1 : Set the
- Incoming Interface type to
- DPDK and connect it to the
- lan1_br ovs bridge.
-
-
-
- Port3 - LAN2 : Set the
- Outgoing Interface type to
- DPDK and connect it to the
- lan2_br ovs bridge.
-
-
- The names of the ports used during instantiation need to be
- the same as the ones described above, as the same names will be
- used in the configuration files provided for this example
- use-case.
-
-
-
-
-
-
- Testing the Use-case
-
- Connect the Test Machine on the LAN interface and access the
- internet from the Test Machine to use the firewall on the uCPE
- device.
-
-
- The connected Test Machine can be a laptop or a uCPE device. It
- must have one interface configured to get a dynamic IP from a DHCP
- server. The dhclient <interface> command can
- be used to request an IP address. The received IP must be in the
- 172.16.1.2 - 172.16.1.255 range.
-
-
- The FortiGate VNF management interface is accessible through the
- WAN interface. The WAN IP address can be used from a web browser on the
- Lab Machine to access the FortiGate VNF Management Web UI. See section
- FortiGate VNF web management in the
-
- Manual for more information.
-
-
-
-
- FortiGate VNF as an SD-WAN or a VPN
-
- SD-WAN decouples the network from the management plane, detaching
- traffic management and monitoring functions from hardware. Most forms of
- SD-WAN technology create a virtual overlay that is transport-agnostic,
- i.e. it abstracts underlying private or public WAN connections.
-
- For deployment, the user plugs in WAN links into the device, which
- automatically configures itself with the network.
-
- Example SD-WAN configurations for the FortiGate VNF are provided by
- Enea.
-
-
- Prerequisites
-
- Two uCPE devices will be needed for this setup. The system
- requirements for each uCPE device are:
-
-
-
- 4 x Network Interfaces
-
-
-
- 4 cores
-
-
-
- 4 GB of RAM memory
-
-
-
- The following files are needed for this example use-case:
-
-
-
- FortiGate VNF image. Please contact Fortinet to get a VNF
- image and its license file.
-
-
-
- VNF Configuration file(s), provided with your Enea Edge
- release: fortigate-sdwan<x>.conf .
-
-
-
-
-
- Use-case Setup
-
-
- Fortigate VNF as an SD-WAN or a VPN
-
-
-
-
-
-
-
-
-
- When connecting, the uCPE devices can use a back-to-back or a
- VPN connection. An appropriate interface with the required
- capabilities needs to be chosen for this purpose.
-
-
- Network Configuration:
-
- Since the SD-WAN VNF uses three External Network Interfaces, three
- bridges need to be configured. Each bridge provides the ability to
- connect a physical network interface to the VM's virtual network
- interface.
-
- Each VNF instance will have a virtual interface for VNF
- management, for the WAN network and for LAN communication.
-
- Setup of an Intel Whitebox uCPE
- device :
-
-
-
- Connect the VNF Management interfaces to
- the Lab Network for VNF management access.
-
-
-
- Connect the WAN interfaces back to back or
- via VPN.
-
-
-
- Connect the LAN interfaces to the Test
- Machine.
-
-
-
- Connect the ETH0 interfaces to the Lab
- Network (for Enea Edge Management communications).
-
-
-
- Select uCPE Device 1, access Configuration
- and bind the three physical network interfaces to the DPDK.
-
-
-
- Create three OVS bridges, one for each DPDK network interface
- (VNF management, WAN and LAN).
-
-
-
- Repeat the steps above for uCPE device 2.
-
-
-
- Onboarding the VNF :
-
- Onboard the FortiGate VNF by filling the required fields with the
- following values:
-
-
-
- VM Image File : Provide the
- path to the FortiGate VNF qcow2 image.
-
-
-
- Memory in MB : 1024
-
-
-
- Num of CPUs : 1
-
-
-
- Storage in GB : 20
-
-
-
- Interfaces : Add 3 interfaces
- in the same order as listed below:
-
-
-
- vnfmgr : to connect it to
- the vnfmgmt_br bridge.
-
-
-
- wan: to connect it to the
- wan_br bridge.
-
-
-
- lan: to connect it to the
- lan_br bridge.
-
-
-
-
-
- Cloud-init Datasource :
- ConfigDrive
-
-
-
- Cloud-init Disk Type :
- cdrom
-
-
-
- Cloud-init content file : Add
- a file entry where Path: license.
-
-
-
-
- The order of the interfaces that need to be added must be
- exactly as listed above or else onboarding and in turn instantiation
- will fail.
-
-
- Instantiating the FortiGate
- VNF :
-
- Instantiate the FortiGate VNF by filling the required fields with
- the following values:
-
-
-
- Name : Name of the VM which
- will be created on the uCPE device.
-
-
-
- VNF Type : Name of the
- onboarded VNF.
-
-
-
- uCPE Device : Select the uCPE
- device where the VNF will be instantiated.
-
-
-
- License file : The FortiGate
- license file provided by Fortinet.
-
-
-
- Configuration file : The
- SD-WAN example configuration files provided by Enea:
- fortigate-sdwan1.conf for the FortiGate VNF on
- uCPE device 1 and fortigate-sdwan2.conf for the
- FortiGate VNF on uCPE device 2.
-
-
-
- Port1 - VNF Mgr : Set the type
- to DPDK and connect it to the
- vnfmgmt_br bridge.
-
-
-
- Port2 - WAN : Set the type to
- DPDK and connect it to the
- wan_br bridge.
-
-
-
- Port3 - LAN : Set the type to
- DPDK and connect it to the
- lan_br bridge.
-
-
-
- Instantiate the FortiGate VNF on uCPE device 1 using the
- sdwan1 example configuration file.
-
- To complete the branch-to-branch setup, configure uCPE
- device 2 in the same way as uCPE device
- 1 .
-
-
- The names of the ports used during instantiation need to be the
- same as the ones described above, as the same names will be used in
- the configuration files provided for this example use-case.
-
-
-
-
- Testing the Use-case
-
- Once the full SD-WAN setup is in place a VPN connection needs to
- be established between the two uCPE devices. The Test Machines can be
- connected to the LAN interface on each uCPE device.
-
-
- The connected Test Machine can be a laptop or a uCPE device that
- has one interface configured to get a dynamic IP from a DHCP server.
- The dhclient <interface> command can be used
- to request an IP address.The received IP must be in the 172.16.1.2 -
- 172.16.1.255 range for Test Machine-1 and in the 172.16.2.2 -
- 172.16.2.255 range for Test Machine-2.
-
-
- The Test Machine connected to uCPE device 1
- should be able to ping the Test Machine connected to uCPE
- device 2 in this setup, over the WAN connection. The FortiGate
- VNF management interface can be accessed from a web browser on the Lab
- Machine. For more details please see FortiGate VNF Web Management, .
-
-
- In this SD-WAN VPN setup example, bridges were used as
- connection points for the FortiGate VNF. It is possible to replace
- OVS-DPDK bridges with SR-IOV connection points.
-
-
-
-
-
- FortiGate VNF Web Management
-
- In order to check the IP address assigned to the FortiGate VNF you
- need to connect to the FortiGate CLI.
-
-
-
- SSH to the uCPE Device (Username: root) and connect to the
- FortiGate VNF console:
-
- virsh list
-virsh console <id of FortiGate VNF>
-
-
-
- To access the FortiGate CLI, use admin as the
- user, leaving the password blank/empty, and press enter.
-
- Use the CLI command get system interface to
- get the dynamic interfaces configuration.
-
-
-
- Use the IP address assigned for the management interface in the
- web browser (https://<IP> ), to access the
- FortiGate VNF Web Management Interface. Use the same credentials as
- before to login.
-
-
-
- Browse through the configuration and perform changes according
- to your setup:
-
-
- The FortiGate VNF Web Management Interface
-
-
-
-
-
-
-
-
-
-
- Optionally, alter the default FortiGate example configuration
- provided by Enea, through the following steps:
-
-
-
- Deploy the FortiGate Firewall in its default
- settings.
-
- Maybe more info about how to do it should be added
- here.
-
-
-
- Connect to the FortiGate VNF Web Management interface with a
- web browser.
-
-
-
- Modify the FortiGate configuration in the FortiGate VNF Web
- Management as needed.
-
-
-
- Store the updated configuration in a file, so it may be used
- at the next FortiGate VNF instantiation.
-
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/fortinet_interface.png b/doc/book-enea-nfv-access-example-usecases/doc/images/fortinet_interface.png
deleted file mode 100755
index 9452264..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/fortinet_interface.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.png b/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.png
deleted file mode 100644
index 2977524..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.svg b/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.svg
deleted file mode 100755
index 86f4d12..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt.svg
+++ /dev/null
@@ -1,1231 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- image/svg+xml
-
-
-
-
-
-
-
-
-
-
-
- Guest
-
-
- OVS Bridge
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Legend: - Connection via cloud/internet: - Back to Back: BTB - Flow rules:
-
-
-
-
-
-
- uCPE Device
-
-
-
-
- Internet
-
-
-
- Enea Edge Management
-
-
-
- Web Interface (128T) https://<IP>:60001
-
-
-
- ibm_br
-
-
-
-
- lan_br
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Test Machine
-
-
-
-
-
-
- vnf_mgmt_br
-
-
-
-
-
-
- 128T
-
-
-
- LAN
- WAN
- MGMT
-
-
-
-
-
- .1
- .2
- .1
- .2
- 192.168.64.0/24
- 10.0.0.0/24
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.png b/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.png
deleted file mode 100644
index 7cb5af0..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.svg b/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.svg
deleted file mode 100755
index 4bd6d85..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/trgt_servicechain.svg
+++ /dev/null
@@ -1,1402 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- image/svg+xml
-
-
-
-
-
-
-
-
-
-
-
- Guest
-
-
- OVS Bridge
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Legend: - Connection via cloud/internet: - Back to Back: BTB - Flow rules:
-
-
-
-
-
-
-
-
-
-
- uCPE Device
-
-
-
- Internet
-
-
- Enea Edge Management
-
-
-
-
-
- ibm_br
-
-
-
- lsfc_br
-
-
-
- 128T
-
- LAN
- WAN
- MGMT
-
-
-
-
- .2
- .1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Test Machine
-
- .2
-
- 192.168.64.0/24
-
-
-
- vnf_mgmt_br
-
- .1
- 10.0.0.0/24
-
-
-
- lan_br
-
-
-
- Fortigate
-
-
- LAN
- WAN
- MGMT
-
- .3
- .1
- 172.16.1.0/24
- .2
-
-
-
-
-
-
-
- Web Interface (128T) https://<IP>:60001 (Fortigate) https://<IP>:60002
-
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_bridge.png b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_bridge.png
deleted file mode 100644
index 97492ca..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_bridge.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_bridge.svg b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_bridge.svg
deleted file mode 100755
index 2890881..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_bridge.svg
+++ /dev/null
@@ -1,966 +0,0 @@
-
-
-
-
-
- image/svg+xml
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Legend: - Connection via cloud/internet: - VPN/Back to Back (BTB): - Flow rules:
-
-
-
-
-
-
-
-
-
-
-
-
- Enea Edge Management
-
-
-
-
-
-
-
-
-
- Internet
-
-
-
-
-
-
-
-
-
-
-
-
-
- uCPE Device 2
-
-
- Iperf client
-
-
- Iperf server
-
-
-
-
- 192.168.20.20
- 192.168.10.10
-
-
-
- bridge
-
- dpdk
-
-
-
-
-
-
-
-
-
-
-
- uCPE Device 1
-
-
-
-
-
-
-
- Clavister
- 192.168.10.1
- 192.168.20.1
-
-
-
- bridge
-
- dpdk
-
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_sriov.png b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_sriov.png
deleted file mode 100644
index 2c9ae6b..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_sriov.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_sriov.svg b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_sriov.svg
deleted file mode 100755
index a33c619..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_clavister_sriov.svg
+++ /dev/null
@@ -1,1152 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- image/svg+xml
-
-
-
-
-
-
-
-
-
-
-
-
-
- Legend: - Connection via cloud/internet: - VPN/Back to Back (BTB): - Flow rules:
-
-
-
-
-
-
-
-
-
-
-
-
- Internet
-
-
-
-
-
-
-
-
- Enea Edge Management
-
-
-
-
-
-
-
-
-
-
-
-
- uCPE Device2
-
-
-
-
-
-
-
-
-
-
- Iperf server
- 192.168.10.10
-
-
-
-
-
- SR-IOV
-
- Iperf client
- 192.168.20.20
-
-
-
- uCPE Device1
-
-
- SR-IOV
-
-
-
-
-
-
-
-
-
-
- Clavister
- 192.168.10.1
- 192.168.20.1
-
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_enea_test_vnf.png b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_enea_test_vnf.png
deleted file mode 100644
index be97bc0..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_enea_test_vnf.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_enea_test_vnf.svg b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_enea_test_vnf.svg
deleted file mode 100755
index fc71729..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_enea_test_vnf.svg
+++ /dev/null
@@ -1,1002 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- image/svg+xml
-
-
-
-
-
-
-
-
-
- Guest
-
-
-
-
-
- Enea Edge Management
-
-
-
-
-
-
-
-
-
-
-
-
- Internet
-
-
- BTB
-
-
-
- uCPE Device 1
-
-
-
-
-
-
- pktgen_dpdk
-
-
-
-
-
-
-
-
-
-
-
-
- uCPE Device 2
-
-
- testpmd_fwd
-
-
- testpmd_term
-
-
-
-
-
-
-
-
-
- bridge
- dpdk
-
-
-
-
-
-
-
-
- Legend: - Connection via cloud/internet: - Back to Back: BTB - Flow rules:
-
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_fw.png b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_fw.png
deleted file mode 100644
index f8ae39a..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_fw.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_fw.svg b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_fw.svg
deleted file mode 100755
index 160c8b0..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_fw.svg
+++ /dev/null
@@ -1,940 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- image/svg+xml
-
-
-
-
-
-
-
-
-
-
-
- Test Machine
-
-
-
-
-
-
-
-
- dpdk
-
-
- wan_br
-
-
-
-
- dpdk
-
-
- lan1_br
-
-
-
-
- dpdk
-
-
- lan2_br
-
-
-
- Fortigate
-
-
- uCPE Device
-
-
-
-
-
-
-
- Legend: - Connection via cloud/internet:
-
-
-
-
-
-
-
-
-
- Test
-
-
-
-
-
-
-
- Internet
-
-
-
- Enea Edge Management
-
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_sdwan.png b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_sdwan.png
deleted file mode 100644
index b71b02e..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_sdwan.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_sdwan.svg b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_sdwan.svg
deleted file mode 100755
index 3de54dd..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_fortigate_sdwan.svg
+++ /dev/null
@@ -1,1449 +0,0 @@
-
-
-
-
-
- image/svg+xml
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Cloud
-
-
-
- uCPE Device
-
-
- uCPE Manager
-
-
-
- Internet
-
-
-
- VNF
-
-
-
- Guest
-
-
-
- OVS Bridge
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Internet
-
-
-
- Enea Edge Management
-
-
-
-
- uCPE Device 2
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- vnfmgmt_br
-
- dpdk
-
-
-
- Fortigate
-
-
-
-
- wan_br
- dpdk
-
-
- dpdk
-
-
- lan_br
-
-
-
-
-
-
-
-
-
-
-
-
- Test Machine
-
-
-
-
-
-
- Test Machine
-
-
-
-
-
-
-
-
-
-
-
- uCPE Device 1
-
-
-
-
-
-
-
-
-
- wan_br
-
- dpdk
-
-
-
-
- lan_br
-
- dpdk
-
-
-
-
-
- vnfmgmt_br
-
- dpdk
-
- Fortigate
-
-
-
-
-
-
-
- Legend: - Connection via cloud/internet: - VPN/BTB:
-
-
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_vnf_chaining.png b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_vnf_chaining.png
deleted file mode 100644
index 6aaf4c0..0000000
Binary files a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_vnf_chaining.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_vnf_chaining.svg b/doc/book-enea-nfv-access-example-usecases/doc/images/uc_vnf_chaining.svg
deleted file mode 100755
index 2bb15af..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/images/uc_vnf_chaining.svg
+++ /dev/null
@@ -1,1186 +0,0 @@
-
-
-
-
-
- image/svg+xml
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Cloud
-
-
-
- uCPE Device
-
-
- uCPE Manager
-
-
-
- Internet
-
-
-
- VNF
-
-
-
- Guest
-
-
-
- OVS Bridge
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- sfc_br
-
-
-
-
-
-
- Fortigate
-
- lan
- wan
-
-
-
- LAN2
-
- dpdk
-
- lan_br
-
- Juniper
- lan
- wan
-
- dpdk
-
-
- wan_br
-
-
- uCPE Device 2
-
-
-
-
-
-
-
-
-
-
- sfc_br
-
-
-
- Juniper
- wan
- lan
-
- dpdk
-
- wan_br
-
-
- Fortigate
- wan
- lan
-
- dpdk
-
-
- lan_br
-
-
- uCPE Device 1
-
-
- LAN1
-
-
-
-
-
-
- Legend: - Connection via cloud/internet: - VPN/BTB:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Internet
-
-
-
- Enea Edge Management
-
-
-
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml b/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
deleted file mode 100644
index b502e8b..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/introduction.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
- Introduction
-
- This document describes several example use-cases concerning uCPE
- configuration, onboarding and instantiation of certain VNFs, VNF chaining,
- etc.
-
- Before running any example use case make sure the uCPE device(s) have
- been added to Enea Edge Management and placed on the map. For detailed
- information on how to add a device to Enea Edge Management, how to configure the
- network interfaces to use DPDK, PCI-passthrough or SR-IOV drivers, or VNF
- configuration, please refer to the Manual.
-
-
- Examples presented in this document use 3rd-party VNFs, which are
- not provided by Enea. To procure and use these VNF image files and license
- files, please contact the VNF provider.
-
- Request the VNF prerequisites from the VNF vendors, or alternatively
- obtain the prerequisites based on instructions from each VNF vendor
- respectively.
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml b/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
deleted file mode 100644
index bb05905..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/service_chaining_128t_fortigate.xml
+++ /dev/null
@@ -1,1064 +0,0 @@
-
-
- Service Chaining 128T - Fortigate Example Use-case
-
- The following is an example of how to setup and configure a service
- chain on top of the Enea Edge Runtime, using the
- following commercial VNFs: 128T router and FortiGate.
-
-
- Prerequisites
-
- The 128T router and the Fortinet firewall in a service chain require
- the following prequisites for this example use case:
-
-
-
- 1 in band management port for device management.
-
-
-
- 1 in band management port for the 128T router.
-
-
-
- 1 in band management port for Fortinet.
-
-
-
- 1 WAN interface for Fortinet.
-
-
-
- 1 LAN facing interface for Fortinet.
-
-
-
- 1 WAN facing interface for the 128T router.
-
-
-
- 1 service chain (SFC Bridged interface) to sit between the
- Firewall and vRouter.
-
-
-
- The following files are needed for this example use-case:
-
-
-
- FortiGate VNF image. Please contact Fortinet to get a VNF image
- and its license file.
-
-
-
- 128T router VNF image. Please contact 128 Technology to get a
- VNF image and its license file.
-
-
-
- Cloud-init iso image.
-
-
-
-
- To procure the VNF image files and their licenses, please contact
- each respective VNF provider.
-
-
-
-
- Service Chaining 128T - Fortigate
-
-
- Service Chaining 128T - Fortigate Setup Overview
-
-
-
-
-
-
-
-
-
- Use-case Setup
-
- Configuring Network Interfaces on uCPE
- devices:
-
- Add the trgt uCPE device into Enea Edge Management:
- Devices -> Manage -> Add , and fill in the
- required fields with the following data:
-
-
- Device Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- Type
-
- Enea universal CPE
-
-
-
- Release
-
- 2.2.2
-
-
-
- Name
-
- trgt
-
-
-
- IP/DNS Address
-
- <unspecified>
-
-
-
- Description
-
- Target 1
-
-
-
- SSH Port
-
- 830
-
-
-
- SSH User Name
-
- root
-
-
-
- Password
-
- null
-
-
-
- Device ID
-
- Also configured during installation of the device
- (E.g.: Target-15).
-
-
-
- OK
-
- Green status indicates connection with uCPE device
- was established.
-
-
-
-
-
-
-
- In order to add the device on the map: Right-Click on
- Map -> Place Device -> trgt .
-
-
-
- Configure the infrastructure for the 128T and Fortigate VNFs
- in the service chain by creating four OVS bridges and a host
- interface.
-
- Add the Host Interface by selecting the trgt device, then
- Configuration -> External Interfaces ->
- Configuration -> Add , and fill in the required fields
- with the following data:
-
-
- Host Interface Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- Source
-
- enp4s0f1 . The only interface
- available for LAN connection.
-
-
-
- networking-type
-
- dpdk
-
-
-
- dpdk-type
-
- vfio-pci
-
-
-
- Create
-
- <interface enp4s0f1 ready to be used in a LAN
- bridge.>
-
-
-
-
-
- Add the OVS bridges by selecting the trgt device then:
- Configuration -> OpenVSwitch -> Bridges ->
- Add . Fill in the required fields for each bridge with
- the following data from each table:
-
-
- ibm_br Bridge Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- id
-
- <autogenerated - do not change>
-
-
-
- Name
-
- ibm_br
-
-
-
- ovs-bridge-type
-
- inbandMgmt
-
-
-
- Create
-
-
-
-
-
-
-
-
-
-
- vnf_mgmt_br Bridge Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- id
-
- <autogenerated - do not change>
-
-
-
- Name
-
- vnf_mgmt_br
-
-
-
- ovs-bridge-type
-
- vnfMgmt
-
-
-
- vnf-mgmt-address
-
- 10.0.0.1
-
-
-
- Create
-
-
-
-
-
-
-
-
- lan_br Bridge Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- id
-
- <autogenerated - do not change>
-
-
-
- Name
-
- lan_br
-
-
-
- ovs-bridge-type
-
- dataPlane
-
-
-
- sub-type
-
- communication
-
-
-
- +
-
- Name: enp4s0f1 OK
-
-
-
- Create
-
-
-
-
-
-
-
-
- sfc_br Bridge Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- id
-
- <autogenerated - do not change>
-
-
-
- Name
-
- sfc_br
-
-
-
- ovs-bridge-type
-
- dataPlane
-
-
-
- sub-type
-
- integration
-
-
-
- Create
-
-
-
-
-
-
-
-
-
- Onboarding the VNFs:
-
- Onboard the 128T VNF VM Image through VNF ->
- Descriptors -> On-board , and fill in the required fields
- with the following values:
-
-
- 128T VM Image Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- VM image file
-
- centos_128t_with_ci.qcow2
-
-
-
- Image format
-
- QCOW2
-
-
-
- VNF Type Name
-
- 128T
-
-
-
- Description
-
- 128T Router
-
-
-
- Version
-
- 1.0
-
-
-
- Memory in MB
-
- 8192. More memory can be allocated if required
- (<28672).
-
-
-
- Num. of CPUs
-
- 2. More CPUs can be reserved if required
- (<15).
-
-
-
- Interfaces -> +
-
- Name: mgmt
-
-
-
- Interfaces -> +
-
- Name: wan
-
-
-
- Interfaces -> +
-
- Name: lan
-
-
-
- Cloud Init -> Cloud-Init Datasource
-
- ISO
-
-
-
- Cloud Init -> Cloud-Init Disk Type
-
- cdrom
-
-
-
- Properties -> +
-
- Name: vnfMgmtIpAddress. Value: 10.0.0.2
-
-
-
- Properties -> +
-
- Name: internalMgmtPort. Value: 443
-
-
-
- Properties -> +
-
- Name: externalMgmtPort. Value: 60001
-
-
-
- Onboard
-
- <Wait for message: VNF package onboarded
- successfully>
-
-
-
- Close
-
-
-
-
-
-
-
-
-
-
- HTTPS access (443) can be changed to another type of access.
- Please consult official 128T documentation and make sure the 128T
- VNF is configured to accept another type of connection before
- changing the port number.
-
-
-
- externalMgmtPort(60001) represents the
- external port on which the user can access the VNF management
- interface from the web browser via HTTPS. The user can select
- another port if needed. There are no other changes required or
- components affected by this change.
-
-
-
- vnfMgmtIpAddress (10.0.0.2) represents
- the IP address of the management interface of the 128T VNF.
- Changing this value requires an update to the 128T configuration
- to match the new IP address.
-
-
-
-
- Onboard the Fortigate VNF VM Image through VNF ->
- Descriptors -> On-board , and fill in the required fields
- with the following values:
-
-
- Fortigate VM Image Details
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- VM image file
-
- fortios.qcow2 . Please make sure to
- contact Fortinet for an official FortiGate KVM image.
-
-
-
- Image format
-
- QCOW2
-
-
-
- VNF Type Name
-
- Fortigate
-
-
-
- Description
-
- Fortigate VNF
-
-
-
- Version
-
- 1.0
-
-
-
- Memory in MB
-
- 1024. More memory can be allocated if required
- (<28672).
-
-
-
- Num. of CPUs
-
- 1. More CPUs can be reserved if required
- (<15).
-
-
-
- Interfaces -> +
-
- Name: mgmt
-
-
-
- Interfaces -> +
-
- Name: wan
-
-
-
- Interfaces -> +
-
- Name: lan
-
-
-
- Cloud Init -> Cloud-Init Datasource
-
- ConfigDrive
-
-
-
- Cloud Init -> Cloud-Init Disk Type
-
- cdrom
-
-
-
- Cloud Init -> +
-
- Path: license
-
-
-
- Properties -> +
-
- Name: vnfMgmtIpAddress. Value: 10.0.0.3
-
-
-
- Properties -> +
-
- Name: internalMgmtPort. Value: 443
-
-
-
- Properties -> +
-
- Name: externalMgmtPort. Value: 60002
-
-
-
- Onboard
-
- <Wait for message: VNF package onboarded
- successfully>
-
-
-
- Close
-
-
-
-
-
-
-
-
-
-
- HTTPS access (443) can be changed to another type of access.
- Please consult official Fortigate documentation and make sure the
- Fortigate VNF is configured to accept another type of connection
- before changing the port number.
-
-
-
- externalMgmtPort (60002) represents the
- external port on which the user can access the VNF management
- interface from the web browser via HTTPS. The user can select
- another port if needed. There are no other changes required or
- components affected by this change.
-
-
-
- vnfMgmtIpAddress (10.0.0.3) represents
- the IP address of the management interface of the Fortigate VNF.
- Changing this value requires an update to the Fortigate
- configuration to match with new IP address.
-
-
-
-
- Instantiating the VNFs:
-
- Instantiate the 128T VNF by selecting the trgt device, then
- VNF -> Instances -> Add .
-
- Fill in the required fields with the following values:
-
-
- 128T VNF Instantiation
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- Name
-
- 128T_trgt_1
-
-
-
- VNF Type
-
- 128T
-
-
-
- VNFD Version
-
- 1.0
-
-
-
- Flavour
-
- Canonical
-
-
-
- uCPE Device
-
- trgt
-
-
-
- Cloud Init File
-
- centos_128t_internet_ci.iso .
-
-
-
- Domain Update Script
-
-
-
-
-
- Interfaces
-
-
-
-
-
- ID
-
- IF Name
-
-
-
- mgmt (dpdk)
-
- Bridge: vnf_mgmt_br
-
-
-
- wan (dpdk)
-
- Bridge: ibm_br
-
-
-
- lan (dpdk)
-
- Bridge: sfc_br
-
-
-
- Create
-
-
-
-
-
-
-
-
- To procure the VNF image files and their licenses, please
- contact each respective VNF provider.
-
-
- Instantiate the Fortigate VNF by selecting the trgt device, then
- VNF -> Instances -> Add .
-
- Fill in the required fields with the following values:
-
-
- Fortigate VNF Instantiation
-
-
-
-
-
-
-
-
-
-
- Field
-
- Value
-
-
-
-
-
- Name
-
- fg_trgt_1
-
-
-
- VNF Type
-
- Fortigate
-
-
-
- VNFD Version
-
- 1.0
-
-
-
- Flavour
-
- Canonical
-
-
-
- uCPE Device
-
- trgt
-
-
-
- Cloud Init File
-
- fg_cust_basic_fw.conf
-
-
-
- License File
-
- The FortiGate license file provided by Fortinet.
-
-
-
- Domain Update Script
-
-
-
-
-
- Interfaces
-
-
-
-
-
- ID
-
- IF Name
-
-
-
- mgmt (dpdk)
-
- Bridge: vnf_mgmt_br
-
-
-
- wan (dpdk)
-
- Bridge: sfc_br
-
-
-
- lan (dpdk)
-
- Bridge: lan_br
-
-
-
- Create
-
-
-
-
-
-
-
-
-
- Testing the Use-case
-
- In order to access the web interfaces of the 128T VNF, open a
- browser on a machine connected on the same network with the WAN port of
- the target and connect to:
- https://<publicIP>:60001 using the username:
- admin and the password: 128Tadmin.
-
- In order to access the web interfaces of the Fortigate VNF, open a
- browser on a machine connected on the same network with the WAN port of
- the target and connect to:
- https://<publicIP>:60002 using the username:
- admin, and leaving the password blank.
-
-
- Make sure the WAN interface of the trgt device has access to the
- internet. The Fortigate VNF requires internet access to validate the
- license.
-
-
- In order to validate the data path connect a test machine to the
- LAN physical port and check for a dynamic IP (the Fortigate LAN
- interface is configured with a DHCP server):> dhclient eth1
-> ping 8.8.8.8 For data path validation, a new cloud-init
- image may need to be generated for the 128T VNF to match your network
- configuration.
-
-
-
- Use-case Clean-up
-
- In order to remove the setup created in previously, all components
- need to be deleted in reverse order:
-
-
-
- Select the trgt uCPE device -> VNF -> Instances. Select
- the 128T and Fortigate VNFs -> Delete.
-
-
-
- Select the trgt uCPE device -> Configuration ->
- OpenVSwitch -> Bridges. Select all bridges -> Delete.
-
-
-
- Select the trgt uCPE device -> Configuration -> External
- Interfaces -> Configuration. Select all interfaces ->
- Delete.
-
-
-
- VNF -> Descriptors. Select all bundles ->
- Offboard.
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml b/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
deleted file mode 100644
index 24442af..0000000
--- a/doc/book-enea-nfv-access-example-usecases/doc/vnf_chaining.xml
+++ /dev/null
@@ -1,407 +0,0 @@
-
-
- VNF Chaining Example Use-case
-
- The term service chaining or service function chaining (SFC) is used
- to describe the definition and instantiation of an ordered list of instances
- of such service functions and the subsequent "steering" of traffic flows
- through those service functions. The set of enabled service function chains
- reflects operator service offerings and is designed in conjunction with
- application delivery and service and network policy.
-
- The following is an example of how to setup and configure a
- branch-to-branch service comprised on two commercial VNFs (SD-WAN +
- Firewall). This service will run in a service chain on top of the Enea
- Edge Runtime, deployed through the Enea Edge
- Management.
-
- In the example setup the following commercial VNFs are used: Juniper
- vSRX as the SD-WAN VNF and Fortigate as the Router/Firewall.
-
-
- VNF Chaining with FortiGate
-
-
- Prerequisites
-
- Two uCPE devices will be needed for this setup. The system
- requirements for each uCPE device are:
-
-
-
- 4 x Network Interfaces
-
-
-
- 4 GB of RAM memory
-
-
-
-
- On each uCPE device, 3 interfaces need to be DPDK compliant and
- one of these needs to be connected back-to-back to the other uCPE
- device. This link simulates a WAN/uplink connection. Optionally, one
- additional device (PC/laptop) can be connected on the LAN port of each
- branch to run LAN-to-LAN connectivity tests.
-
-
- The following files are needed for this example use-case:
-
-
-
- Fortigate VNF image file.
-
-
-
- Juniper vSRX VNF image file.
-
-
-
- vSRX-Site<x>.iso Cloud-init files.
-
-
-
- VNF Configuration files, provided with your Enea Edge
- Release:
-
-
-
- vSRX-domain-update-script .
-
-
-
- FortiFW-Site<x>.conf .
-
-
-
-
-
-
- To procure the VNF image files and their licenses, please
- contact each respective VNF provider. To create the
- vSRX-Site<x>.iso file, please follow the documentation provided
- by Juniper.
-
-
-
-
- Use-case Setup
-
-
- VNF Chaining with Fortigate
-
-
-
-
-
-
-
-
- No info about vnf_mgmt_br?
-
- Network Configuration :
-
- Both branches in the example have similar setups, therefore
- necessary step details are presented for only one branch. The second
- branch shall be configured in the same way, adapting as needed the
- corresponding VNFs configuration files.
-
-
-
- Assign three physical interfaces to the DPDK (one for
- management, one WAN and one for LAN). In the example, one of these
- interfaces gets an IP through DHCP and it will be used exclusively
- for the management plane.
-
-
-
- Create the following OVS-DPDK bridges:
-
-
-
- vnf_mgmt_br . Used by VNF management
- ports.
-
-
-
- wan_br . Used by the service uplink
- connection. In our case, Juniper vSRX will have its WAN virtual
- interface in this bridge.
-
-
-
- sfc_br . Used for creating the service
- chain. Each VNF will have a virtual interface in this
- bridge.
-
-
-
- lan_br . Used for the LAN interface of
- the Fortigate FW.
-
-
-
-
-
- Add corresponding DPDK ports (see Step 1) to the management,
- WAN and LAN bridges (sfc_br does not have a
- physical port attached to it).
-
-
- The networking setup (Steps 1-3) can be modeled using the
- Offline Configuration entry, so that it is automatically
- provisioned on the uCPE device, once it gets enrolled into the
- management system (Enea Edge Management).
-
-
-
-
- Onboarding the VNFs :
-
-
-
- Onboard Juniper vSRX using the VNF by filling the required
- fields with the following values:
-
-
-
- The Flavor selected must have at least 2 vCPUs and 4 GB
- RAM since vSRX is quite resource consuming.
-
- Tested in-house with 4 vCPUs/ 6 GB RAM.
-
-
-
- Add three virtual interfaces: management, WAN and
- LAN.
-
-
-
- Select ISO as the Cloud-Init Datasource
- in the Cloud-Init tab.
-
-
-
- Select cdrom as the Cloud-Init Disk
- Type in the Cloud-Init tab.
-
-
-
-
-
- Onboard Fortigate FW using the VNF Onboarding Wizard:
-
-
-
- The Flavor selected can be quite light in resource
- consumption, e.g. 1 CPU and 1 GB RAM.
-
-
-
- Add three virtual interfaces: management, WAN and
- LAN.
-
-
-
- Select ConfigDrive as the Cloud-Init
- Datasource in the Cloud-Init tab.
-
-
-
- Select cdrom as the Cloud-Init Disk
- Type in the Cloud-Init tab.
-
-
-
- In the Cloud-init content files field add an entry where
- Path: license .
-
-
-
-
-
- Instantiating the VNFs:
-
-
-
- Create the vSRX instance:
-
-
-
- Use vSRX-Site1.iso as the Cloud-Init
- file.
-
-
-
- The Domain Update Script field can be
- left empty for the Atom C3000 architecture, while for XeonD the
- vSRX-domain-update-script file will be
- used.
-
-
-
- Add virtual interfaces:
-
-
-
- Management interface added to
- vnf_mgmt_br .
-
-
-
- WAN interface added to
- wan_br .
-
-
-
- LAN interface added to
- sfc_br .
-
-
-
-
-
-
- The login/password values for the vSRX VNF are
- root/vsrx1234 , respectively.
-
-
-
-
- Create the Fortigate FW instance:
-
-
-
- Use FortiFW-Site1.conf as the
- Cloud-Init file.
-
-
-
- Add .lic (not part of the folder) as
- the license file.
-
-
-
- Add virtual interfaces:
-
-
-
- Management interface added to
- vnf_mgmt_br .
-
-
-
- WAN interface added to
- sfc_br .
-
-
-
- LAN interface added to
- lan_br .
-
-
-
-
-
-
- The login/password values for the Fortigate VNF are
- admin/<empty password> ,
- respectively.
-
-
-
-
- At this point the service will be up and running on Site1. Repeat
- the steps to instantiate a VNF for Site2, by changing the configuration
- files accordingly.
-
- After the service is deployed on both branches, the VPN tunnel is
- established and LAN to LAN visibility can be verified by connecting one
- device on each uCPE LAN port.
-
-
-
- Testing the Use-case
-
- Before testing LAN to LAN connectivity, preliminary tests of
- service can be run to ensure everything was set up properly. For
- instance, by connecting to vSRX CLI (any site), one can test IKE
- security associations:
-
- root@Atom-C3000:~ # cli
-root@Atom-C3000> show security ike security-associations
-Index State Initiator cookie Responder cookie Mode Remote Address
-1588673 UP 2f2047b144ebfce4 0000000000000000 Aggressive 10.1.1.2
-...
-root@Atom-C3000> show security ike security-associations index 1588673 detail
-...
-
- Also, from the vSRX CLI, a user can check that the VPN tunnel was
- established and get statistics of the packets passing the tunnel:
-
- root@Atom-C3000> show security ipsec security-associations
-...
-root@Atom-C3000> show security ipsec statistics index <xxxxx>
-...
-
- From the Fortigate Firewall CLI on Site 1, one can check
- connectivity to the remote Fortigate FW (from Site 2):
-
- FGVM080000136187 # execute ping 192.168.168.2
-PING 192.168.168.2 (192.168.168.2): 56 data bytes
-64 bytes from 192.168.168.2: icmp_seq=0 ttl=255 time=0.0 ms
-64 bytes from 192.168.168.2: icmp_seq=1 ttl=255 time=0.0 ms
-64 bytes from 192.168.168.2: icmp_seq=2 ttl=255 time=0.0 ms
-...
-
- Since VNF management ports were configured to get IPs through
- DHCP, the user can use a Web-based management UI to check and modify the
- configuration settings of both vSRX and Fortigate.
-
- For example, in the case of vSRX, from the VNF CLI you can list
- the virtual interfaces as below:
-
- root@Atom-C3000> show interfaces terse
-...
-fxp0.0 up up inet 172.24.15.92/22
-gre up up
-ipip up up
-...
-
- When using provided configurations, the VNF management port for
- Juniper vSRX is always fxp0.0 .
-
- In the case of Fortigate, from the VNF CLI you can list the
- virtual interfaces as such:
-
- FGVM080000136187 # get system interface
-== [ port1 ]
-name: port1 mode: dhcp ip: 172.24.15.94 255.255.252.0 status: up netbios-forward:
-disable type: physical netflow-sampler: disable sflow-sampler: disable...
-...
-
- When using provided configurations, the VNF management port for
- Fortigate is always port1 .
-
- If functionality is as intended, LAN-to-LAN connectivity can be
- checked (through the VPN tunnel) by using two devices (PC/laptop)
- connected to the LAN ports of each uCPE. Optionally, these devices can
- be simulated by using Enea's sample VNF running on both uCPEs and
- connected to the lan_br on each side. Please note
- that instructions for onboarding and instantiating this VNF is not in
- the scope of this document.
-
- Since Fortigate VNF, which is acting as router and firewall, is
- configured to be the DHCP server for the LAN network, the device
- interface connected to the uCPE LAN port has to be configured to get
- dinamically assigned IPs. These IPs are in the 172.0.0.0/24 network for
- Site1 and the 172.10.10.0/24 network for Site2. Therefore, site-to-site
- connectivity can be checked (from Site1) as such:
-
- root@atom-c3000:~# ping 172.10.10.2
-PING 172.10.10.1 (172.10.10.2): 56 data bytes
-...
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-example-usecases/swcomp.mk b/doc/book-enea-nfv-access-example-usecases/swcomp.mk
deleted file mode 100755
index 5f5ab16..0000000
--- a/doc/book-enea-nfv-access-example-usecases/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-example-usecases
-BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Example Use-cases"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml b/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
deleted file mode 100644
index 70a9978..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/advanced_configurations.xml
+++ /dev/null
@@ -1,1042 +0,0 @@
-
-
-
- Advanced Configurations
-
- This chapter describes possible configurations for advanced features
- such as the Hugepage Reservation Service customization, UEFI Secure Boot and
- Bare Metal Provisioning.
-
-
-
-
- UEFI Secure Boot
-
- Secure Boot was designed to enhance security in the pre-boot
- environment. It prevents malicious software and applications from being
- loaded during the system start-up process.
-
- The basic principle of UEFI Secure Boot is that it requires all
- artifacts involved in the boot process (bootloaders, kernel, initramfs) to
- be signed using a set of private keys. On a Secure Boot enabled uCPE
- device these artifacts are checked against a set of public certificates
- which correspond to these keys. If there are any mismatches the boot
- process will fail at the stage(s) they are detected.
-
- For more information about Secure Boot please refer to Secure
- Boot in Modern Computer Security Solutions .
-
-
- Enabling UEFI Secure Boot
-
- All Enea Edge image artifacts delivered with the release are
- signed using the Enea UEFI Secure boot private keys. These artifacts can
- be used on a uCPE device that doesn't have Secure Boot enabled. To use
- the Secure Boot feature, however, the user must make the Enea UEFI
- Secure Boot public certificates available on the uCPE device before
- enabling the feature in BIOS. This process is called
- "Provisioning".
-
-
- Provisioning the Enea UEFI Secure Boot Certificates
-
- The UEFI firmware is normally shipped with factory preloaded
- certificates. If these do not already include Certificates from Enea,
- they will need to be appended or replaced with the Enea
- Certificates.
-
- UEFI Secure Boot certificates provided
- with your release:
-
-
-
- Platform Key (PK) : this key protects the
- next key from uncontrolled modification. Once this key is
- enrolled, Secure Boot enters into User Mode .
- The drivers and loaders signed with the Platform
- Key can then be loaded by the firmware.
-
-
-
- Key Exchange key (KEK) : this key allows
- other certificates which have a connection to the private portion
- of the Platform Key to be used.
-
-
-
- Authorized Signature (DB) : contains the
- trusted keys used for authenticating any
- drivers or applications executed in the UEFI environment.
-
-
-
- The Enea UEFI Secure Boot certificates are installed together
- with the Enea Edge Runtime onto the hard drive. They can be found on
- the EFI partition (usually the first partition of the drive) under
- /uefi_sb_keys .
-
- These certificates need to be manually enrolled in BIOS. The
- exact details on how to proceed may vary depending the version of the
- UEFI firmware.
-
- The UEFI firmware is normally shipped with factory preloaded
- certificates. If these do not already include Certificates from Enea,
- they will need to be appended or replaced with the Enea
- Certificates.
-
-
-
- Enabling Secure Boot in BIOS
-
- Once the certificates are enrolled, Secure Boot needs to be
- enabled in BIOS and the device rebooted.
-
-
-
-
-
- Hugepage Reservation Service
-
- Huge page memory support is a mechanism that allows the Linux kernel
- to support larger page sizes than the default page unit (4KB). Huge pages
- are contiguous blocks of memory that come in 2MB or 1GB sizes. By using
- huge page allocations, less memory is used for page tables and the
- Translation Lookaside Buffer (TLB) miss rate is significantly reduced.
- Enea Edge Runtime uses huge page backed memory in KVM guests in order to
- improve performance.
-
- Enea Edge Runtime implements an automatic hugepage allocation
- service that is triggered at each startup. The service is skipped if
- hugepages have been allocated in the kernel boot command line.
-
- There are two strategies outlined for hugepage allocation:
-
-
-
- If a system has an amount of memory up to 8GB, the allocation
- algorithm will reserve up to 30% (no more than 2GB), for the OS and
- the rest as 2MB hugepages.
-
-
-
- If a system has an amount of memory that's higher than 8GB, the
- allocation algorithm will reserve all but 2GB of memory as 1GB
- hugepages, leaving the rest (2GB) to be used by the OS.
-
-
-
-
- This is a best effort reservation after kernel boot, so the
- results may vary accordingly.
-
-
-
- Customizing Automatic Hugepage Reservation
-
- Configuration of Hugepage reservation is done in
- /etc/enea-nfv-access/hugepages.cfg .
-
- Parameters used by the automatic algorithm:
-
-
-
-
- hugepage_setup : Enables the automatic
- configuration algorithm. It has only one value,
- auto . For manual configuration comment or remove
- this parameter. Use the other parameter descriptions as a
- template/example.
-
-
-
- threshold_to_use_1g : Decides the threshold
- which instructs the algorithm to use 1GB hugepages. If a system's
- memory is higher than threshold_to_use_1g , then
- the algorithm will use 1GB hugepages, otherwise it will use 2MB
- hugepages.
-
-
-
- percent_os_alloc : Decides how much memory
- to try to reserve for userspace applications. The algorithm will try
- to reserve at least the value of percent_os_alloc
- of the total system memory for userspace applications.
-
-
-
- maximum_os_alloc_mb : Maximum amount of
- memory to allocate for userspace applications. If
- percent_os_alloc of the total system memory
- exceeds maximum_os_alloc_mb then the maximum
- allocated memory for userspace applications is
- maximum_os_alloc_mb .
-
-
-
- Example of automatic Hugepage
- Configuration:
-
- hugepage_setup = auto
-threshold_to_use_1g = 8192
-percent_os_alloc = 30
-maximum_os_alloc_mb = 2048
-
- The following possible allocations can result (based on total
- system memory available):
-
-
-
- 2GB of memory: approximately 30% will be allocated for the OS
- and the rest will be allocated as 2MB hugepages.
-
-
-
- 4GB of memory: approximately 30% will be allocated for the OS
- and the rest will be allocated as 2MB hugepages.
-
-
-
- 16GB of memory: approximately 2GB will be allocated for the OS
- and the rest as 1GB hugepages.
-
-
-
-
- The memory allocated for the kernel and hugepages might vary
- slightly depending on how much memory is available.
-
-
-
-
- Customizing Manual Hugepage Reservation
-
- The automatic algorithm can be disabled and hugepages in turn,
- configured manually. To do this, comment the line which defines
- hugepage_setup as auto and
- configure memory for each CPU socket in the following manner:
-
- <NUMA node>.<hugepage size> = <number of pages>
-
- Where <NUMA node> refers to a node which
- is part of the system's NUMA topology, <hugepage
- size> decides what type of hugepages should be set and
- <number of hugepages> is how many hugepages of
- <hugepage size> should be allocated.
-
- To list the available system nodes, run:
-
- ls -d /sys/devices/system/node/node*
-
- To list available hugepage sizes, per node, run:
-
- ls -d /sys/devices/system/node/node*/hugepages/hugepages-*
-
- Example of Manual Hugepage Configuration, configuring the system
- to allocate three 1GB hugepages and 512 of 2MB hugepages on node:
-
- node0.2048kB = 512
-node0.1048576kB = 3
-
-
- Make sure there are no hugepages reserved in the kernel boot
- command line, these will override any manual configuration done in the
- service.
-
-
-
-
-
- Installing the Enea Edge Management in High Availability
- Mode
-
- The following describes the setup needed for running the Enea Edge
- Management in High Availabilty (HA) mode, with a MariaDB database cluster.
- A setup example is illustrated in the diagram below.
-
-
- The High Availability setup
-
-
-
-
-
-
-
-
- The setup consists of two sub-clusters, placed in different
- geographical locations, each consisting of three MariaDB servers. In this
- example, two of the machines are running only MariaDB, while the rest are
- hosting a MariaDB server and an Enea Edge Management instance. The entire
- network is hidden behind a firewall that performs NAT. While in protection
- (cluster) mode, the Enea Edge Management instances promote a Virtual IP
- (VIP) that represents the IP address of the entire cluster. The firewall
- in this case will allocate a public IP for the outside world that will be
- translated into the VIP. Also in this example, the traffic towards the
- cluster from outside the firewall is done through HTTPS, which will be
- translated to HTTP inside the private network.
-
-
- By default, communication to the Enea Edge Management is done with
- HTTPS. To enable HTTP, go to System ,
- Configuration , click on the Web Access tab and check the Enable HTTP checkbox.
-
-
-
- Requirements for High Availability
-
- The following hardware is needed for deploying the base
- configuration:
-
-
-
- Machines running the Enea Edge Management and MariaDB:
-
-
-
- 4 CPU cores
-
-
-
- 12 - 16 GB memory
-
-
-
- 256 - 512 GB hard disk
-
-
-
-
-
- Machines running only MariaDB:
-
-
-
- 2 CPU cores
-
-
-
- 8 GB memory
-
-
-
- 256 - 512 GB hard disk
-
-
-
-
-
-
-
- Firewall Rules
-
- Please refer to Firewall Configuration in the
- Manual. In addition, the following configuration is needed:
-
-
-
- Disable SELINUX on all database servers by
- editing /etc/sysconfig/selinux and changing the
- following:
-
- SELINUX=disabled
-SELINUXTYPE=targeted
-
-
-
- Reboot the server:
-
- [root@localhost ~]# sudo shutdown -r now
-
-
-
- The following ports should be opened in the local firewall (not
- the one doing NAT), for each Enea Edge Management machine:
-
-
- Ports for Enea Edge Management Machines
-
-
-
-
-
-
- Port (Protocol)
-
- Usage
-
-
-
-
-
- 80 (TCP)
-
- HTTP
-
-
-
- 443 (TCP)
-
- HTTPS
-
-
-
- 54327 (UDP)
-
- Cluster multicasting (Hazelcast)
-
-
-
- 5701 - 5708 (TCP)
-
- Hazelcast communications
-
-
-
- 4334 (TCP)
-
- NETCONF call-home
-
-
-
- 7000 - 7009 (TCP)
-
- Reverse SSH connection pool
-
-
-
-
-
- For MariaDB, the following ports must be opened (on each MariaDB
- server, including the ones hosting the Enea Edge Management):
-
-
- Ports for MariaDB Machines
-
-
-
-
-
-
- Port (Protocol)
-
- Usage
-
-
-
-
-
- 3306 (TCP)
-
- Client connections
-
-
-
- 4567 (UDP/TCP)
-
- Galera cluster replication with multicasting
-
-
-
- 4568 (TCP)
-
- Incremental state transfer
-
-
-
- 4444 (TCP)
-
- State snapshot transfer
-
-
-
-
-
- The following ports should be accessible externally and translated
- to the Virtual IP side as shown below:
-
-
- Ports for Virtual IP
-
-
-
-
-
-
- External Port (Protocol)
-
- Usage
-
- Local Port (Protocol)
-
-
-
-
-
- 443 (TCP)
-
- HTTPS to/back HTTP
-
- 80 (TCP)
-
-
-
- 4334 (TCP)
-
- NETCONF call-home
-
- 4334 (TCP)
-
-
-
- 7000 - 7009 (TCP)
-
- Reverse SSH connection pool
-
- 7000 - 7009 (TCP)
-
-
-
-
-
-
-
- Installing High Availability
-
- The Enea Edge Management can be installed in High Availability
- mode with a MariaDB database cluster by performing the following steps.
- The mandatory Java configuration is also detailed.
-
-
- Installing and configuring the MariaDB cluster
-
- Install the latest MariaDB packages on all servers.
-
-
- The setup was tested using MariaDB 10.5.8, built for CentOS
- 7.
-
-
- How to install MariaDB
-
-
-
- Install the MariaDB official yum repository. Create a file
- named mariadb.repo in
- /etc/yum.repos.d/ with the following
- content:# MariaDB 10.5 CentOS repository list - created 2021-02-16 08:46 UTC
-# http://downloads.mariadb.org/mariadb/repositories/
-[mariadb]
-name = MariaDB
-baseurl = http://yum.mariadb.org/10.5/centos7-amd64
-gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
-gpgcheck=1
-
-
-
- For more information about setting the repository, consult
- Downloads
- - Setting up MariaDB Repositories .
-
-
-
-
- Make sure the following packages are installed:
-
- MariaDB-compat-10.5.8-1.el7.centos.x86_64
-MariaDB-common-10.5.8-1.el7.centos.x86_64
-MariaDB-server-10.5.8-1.el7.centos.x86_64
-MariaDB-client-10.5.8-1.el7.centos.x86_64
-galera-4-26.4.6-1.el7.centos.x86_64
-
- These provide the MariaDB server, client and the Galera
- wsrep provider library.
-
-
-
- Copy the wsrep template:
-
- [root@localhost ~]# cp /usr/share/mysql/wsrep.cnf /etc/my.cnf.d
-
-
-
-
- Change the following configuration in
- /etc/my.cnf.d/wsrep.cnf :
-
- # Full path to wsrep provider library or 'none'
-wsrep_provider=/usr/lib64/galera-4/libgalera_smm.so
-
-# Provider specific configuration options
-#wsrep_provider_options=
-
-# Logical cluster name. Should be the same for all nodes.
-wsrep_cluster_name="ucpemanager"
-
-# Group communication system handle
-wsrep_cluster_address="gcomm://192.168.10.11,192.168.10.12,..,192.168.10.16"
-
-# Human-readable node name (non-unique). Hostname by default.
-wsrep_node_name=Node1 # current node's name. set node name for each server in \
-the cluster
-
-# Base replication <address|hostname>[:port] of the node.
-# The values supplied will be used as defaults for state transfer receiving,
-# listening ports and so on. Default: address of the first network interface.\
-wsrep_node_address=192.168.10.11
-#current node's interface IP . must be set for each node in the cluster
-
-
- Steps 2, 3 and 4 must be performed for each MariaDB node
- in the cluster.
-
-
-
-
- Bootstrap the first node in the cluster (referred to as
- Node1 in this example), by running:
-
- [root@localhost ~]# galera_new_cluster
-
- This script passes the
- --wsrep-new-cluster to
- mysqld which tells the node that there is no
- pre-existing cluster to connect to. The node will create a new
- UUID to identify the new cluster.
-
-
- Do not execute this script when connecting to an existing
- cluster. It will create a new UUID to identify the cluster
- again, and the node won't reconnect to the old cluster.
-
-
-
-
- Go to Node1 and start the service:
-
- [root@localhost ~]# systemctl start mariadb
-
- Subsequently, start the service on the other servers.
-
-
-
- Verify that the nodes have entered the cluster:
-
- [root@localhost ~]# mysql --host=localhost --user=root -p
-MariaDB [(none)]> show status like 'wsrep_cluster_conf_%';
-+-----------------------+-------+
-| Variable_name | Value |
-+-----------------------+-------+
-| wsrep_cluster_conf_id | 3 |
-+-----------------------+-------+
-1 row in set (0.001 sec)
-
-
-
- Run the initial configuration script (only once, on one of
- the machines in the cluster):
-
- [root@localhost ~]# mysql_secure_installation
-
-Switch to unix_socket authentication [Y/n] Y
-Enabled successfully!
-Reloading privilege tables..
- ... Success!
-…
-Change the root password? [Y/n] Y
-New password:
-Re-enter new password:
-Password updated successfully!
-Reloading privilege tables..
- ... Success!
-…
-Remove anonymous users? [Y/n] Y
- ... Success!
-…
-Disallow root login remotely? [Y/n] Y
- ... Success!
-…
-Remove test database and access to it? [Y/n] Y (optional)
- - Dropping test database...
- ... Success!
- - Removing privileges on test database...
- ... Success!
-Reload privilege tables now? [Y/n] Y
- ... Success!
-
-Cleaning up...
-
-All done! If you've completed all of the above steps, your MariaDB
-installation should now be secure.
-
-Thanks for using MariaDB!
-
-
-
- Create the initial database and grant access to it:
-
- [root@localhost application]# mysql --host=localhost --user=root -p
-MariaDB [(none)]> CREATE DATABASE ucpemanager CHARACTER SET='utf8' \
-COLLATE='utf8_bin';
-Query OK, 1 row affected (0.004 sec)
-
-MariaDB [(none)]> GRANT ALL PRIVILEGES ON ucpemanager.* \
-TO 'enea'@'%' IDENTIFIED BY 'somepassword' WITH GRANT OPTION;
-
-
-
-
-
- Installing the Java SDK
-
- Please refer to Configuring OpenJDK and
- PostgreSQL in the
- Manual, for details on how to install and configure Java
- OpenJDK.
-
- Make sure the JAVA_HOME variable points to
- the OpenJDK 11 installation:
-
- [root@localhost ~]# echo $JAVA_HOME
-/usr/lib/jvm/java-11-openjdk-11.0.10.0.9-0.el7_9.x86_64
-
-
-
-
- Installing the Enea Edge Management in High Availabilty
- mode
-
- These steps must be taken on each of the CentOS 7 machines that
- will host the Enea Edge Management. The Enea Edge Management will be
- installed and the setup for the external database cluster will be
- prepared.
-
- As the root user, go to the distribution folder of the Enea Edge
- Management, and run:
-
- [root@localhost distro]#./install.sh /opt/ \
-Enea_NFV_Access_uCPEManager_2.3.0-build23.tar.gz
-This will install uCPEManager into /opt/ucpemanager folder.
-Select the following options, while asked by the installation script:
-Are you using the embedded PostgreSQL database? [Y/N]: N
-External database selected, getting user information ...
-Press 1 for PostgreSQL, 2 for MariaDB, 3 for SQL Server, 4 for Oracle and 5 \
-for MySQL: 2
-Specify database server name(s) or IP Address(es): \
-192.168.10.11,192.168.10.12,…,192.168.10.16 *(see note)
-Specify database ID (or name) [ucpemanager]:
-Specify database server port [3306]:
-Specify database user name [root]: enea
-Specify database password [root]: somepassword
-Specify database startup thread pool size [1]:
-Creating database configuration file \
-/opt//ucpemanager/application/config/databaseConfig.xml ...
-Done .
-…
-Installing ucpemanager service ..
-Specify service username [ucpemanager]:
-Specify service password [ucpemanager]: somepassword
-…
-Specify the IP address of the local interface: 192.168.10.11
-Is this server part of a cluster? [Y/N]: Y
-Specify the name of the cluster [ucpemanager]:
-Specify the shared (virtual) cluster IP address: 192.168.10.10
-Specify the netmask for the cluster IP address [255.255.255.0]:
-HA Configuration files modified successfully.
-Configuration complete.
-
-
- For each Enea Edge Management installation, place the local
- interface IP first in the list of IPs. This will optimize database
- communication, since the Enea Edge Management uses the list of IPs
- sequentially, therefore using the internal loopback interface for
- communicating with the database.
-
-
- Once the servers are up and running, log into the Primary and go to System and select Cluster
- View . The list of Enea Edge Management servers should be
- displayed, with one listed as Primary and the rest as Backup.
-
-
-
-
- Upgrading a High Availability Deployment
-
- Upgrading a High Availabilty deployment is a highly complex,
- multi-step process that requires care to ensure both consistency and
- high-availability. Some steps need to be done manually.
-
-
-
- We start with the assumption that ucpeManager-1
- is the "PRIMARY" server.
-
-
-
- Shut down database services on one side of the network, for
- example: MariaDB-4, MariaDB-5 and MariaDB-6.
-
-
-
- Disconnect the network interfaces towards the VPN for machines
- MariaDB-4, MariaDB-5 and MariaDB-6. This will prevent any attempts
- at failover/synchronization.
-
-
-
- Run the upgrade process on ucpeManager-3
- and ucpeManager-4 . This will upgrade the service
- to the current release. Once the upgrade process completes, shutdown
- the Enea Edge Management service on both machines.
-
-
-
- Disconnect the ucpeManager-2 machine from
- the network (which will take MariaDB-2 offline as well). At this
- point, only the "PRIMARY" server is running, this is the start of
- the interval when we are susceptible to single-server
- failure.
-
-
-
- Shutdown the MariaDB-2 process and run the Enea Edge
- Management upgrade process on ucpeManager-2 . This
- will upgrade the service to the current release. Once the upgrade
- process completes, shutdown the Enea Edge Management service on the
- machine.
-
-
-
- Reconnect the network interfaces towards the VPN for MariaDB-4
- (ucpeManager-3 ), MariaDB-5
- (ucpeManager-4 ) and MariaDB-6
- (ucpeManager-2 ). Restart database services on
- MariaDB-2, MariaDB-4, MariaDB-5 and MariaDB-6. This will allow
- database services on all machines to synchronize, any data that has
- been modified during the upgrade process will be made
- consistent.
-
-
-
- Shutdown the "Primary" server
- (ucpeManager-1 ). At this point, the service is no
- longer available.
-
-
-
- Start the Enea Edge Management services on
- ucpeManager-2 . This machine will come up as the
- new "PRIMARY" with the upgraded software. As part of the startup
- process, it will upgrade the database and perform any other
- upgrade-related functionality.
-
-
-
- At this point (once startup completes), service is available.
- However, we are still susceptible to single-server failure.
-
-
-
- Start the Enea Edge Management services on
- ucpeManager-3 and
- ucpeManager-4 . At this point, we are in
- highly-available mode.
-
-
-
- Upgrade the Enea Edge Management on
- ucpeManager-1 (the one that has been shut down).
- Once that upgrade is complete and the service restarts, the entire
- setup has been upgraded to the new version.
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-getting-started/doc/book.xml b/doc/book-enea-nfv-access-getting-started/doc/book.xml
deleted file mode 100644
index 0704dd0..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/book.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-]>
-
- Enea Edge Getting Started
-
- Release Version
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-getting-started/doc/grafana.xml b/doc/book-enea-nfv-access-getting-started/doc/grafana.xml
deleted file mode 100644
index 05276ed..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/grafana.xml
+++ /dev/null
@@ -1,266 +0,0 @@
-
-
- Using Grafana and InfluxDB
-
- InfluxDB is essentially a time series database process that runs on a
- server, while Grafana is a visualization tool for time series data. Grafana
- is a very lightweight server-side application, and most of the monitoring
- runs in a browser.
-
-
- Deploying Grafana and InfluxDB
-
- Grafana and InfluxDB can be deployed using images for Docker on
- linux. These images are provided by Enea along with a deploy script and
- predefined dashboards.
-
- The Grafana and InfluxDB images can be deployed on the same machine
- or on separate machines.
-
-
- Prerequisites for Deploying an Image
-
- The following must be present in order to deploy an image:
-
-
-
- CentOS 7 Linux.
-
-
-
- Docker for CentOS 7 installed on the machine and set to
- autostart as a service.
-
-
-
- Superuser rights on the CentOS 7 machine.
-
-
-
-
-
- Deploying Grafana and InfluxDB
-
- On the CentOS 7 server open a terminal, log into a bash shell with
- the root account and perform the following:
-
-
-
- Extract
- Enea_Edge_Telemetry_Deploy_<version>-build<build_number>.tar.gz .
-
- The directory in which the archive will be unpacked will be
- denoted as: <Telemetry-installdir> .
-
-
-
- Enter <Telemetry-installdir> .
-
-
-
- Run the provided telemetry_deploy.sh
- script.
-
-
-
- When prompted, select what images you want to deploy.
-
- If an image is already deployed, you will be prompted to
- replace it.
-
-
-
- During the InfluxDB deployment, you will be prompted to
- provide a username and password. These must match the ones
- configured in the Enea Edge Management for Telemetry.
-
-
- Changing the InfluxDB username and password requires
- redeploying the InfluxDB image.
-
-
-
-
- Verify the installation by running the command docker
- ps -a . The Grafana and InfluxDB containers should be
- present and have the status Up .
-
-
-
-
-
-
- Setting Grafana and InfluxDB parameters
-
- Customizing InfluxDB and Grafana parameters can be done by selecting
- System , then the Configuration menu, accessing the Properties tab, and clicking on the Telemetry tab. The settings that can be changed are
- listed in the table below:
-
-
- Telemetry settings
-
-
-
-
-
-
-
-
-
-
- Field name
-
- Description
-
- Default value
-
-
-
- Grafana Hostname or IP Address
-
- The hostname or IP address where the Grafana instance is
- installed.
-
- no default
-
-
-
- Grafana Port
-
- The port Grafana uses.
-
- 3000
-
-
-
- Grafana Dashboard
-
- The dashboard that should be used when opening Grafana
- using the Enea Edge Management.
-
- host
-
-
-
- InfluxDB Hostname or IP Address
-
- The hostname or IP address where the InfluxDB database is
- installed.
-
- no default
-
-
-
- InfluxDB Port
-
- The port used for communication between InfluxDB and the
- Telemetry server.
-
- 25826
-
-
-
- InfluxDB Username
-
- The username used for encrypting communication between
- InfluxDB and the Telemetry server.
-
- admin0
-
-
-
- InfluxDB Password
-
- The password used for encrypting communication between
- InfluxDB and the Telemetry server.
-
- admin
-
-
-
-
-
- When changing any of the settings in the Telemetry tab, the Enea Edge Management will inform
- all uCPE devices of the change if they have telemetry running.
-
-
- Telemetry Properties
-
-
-
-
-
-
-
-
-
-
- Starting and stopping Telemetry
-
- When a uCPE Device is selected, in the Operations menu, the Start
- Telemetry and Stop Telemetry
- options are available.
-
- When starting Telemetry for a uCPE device, the Enea Edge Management
- sends the following information about the InfluxDB:
-
-
-
- The IP address and hostname where InfluxDB is installed.
-
-
-
- The port used for communication between InfluxDB and the
- Telemetry server.
-
-
-
- The credentials used for encrypting communication between
- InfluxDB and the Telemetry server.
-
-
-
- These fields are read-only and are populated with the values already
- set in the System Configuration . If one
- of the fields is not set or if it does not have the desired value, modify
- it in the System Configuration . The
- password is sent encrypted using the Base64 scheme.
-
-
- Telemetry Start Dialog
-
-
-
-
-
-
-
-
- When the Telemetry status is changed on a uCPE device, a
- notification is sent to the Enea Edge Management. These notifications can
- be inspected under Fault found in the
- Event menu.
-
-
-
- Launching Grafana
-
- When a uCPE Device is selected, the Telemetry button is available. Pressing this button
- will open a new window pointing to Grafana. The current uCPE device will
- be selected in Grafana.
-
- The hostname or IP Address and the port of the Grafana installation
- can be customized by selecting System ,
- then the Configuration menu, accessing
- the Properties tab, and clicking on the
- Telemetry tab. The default dashboard
- available when launching Grafana can be customized as well.
-
-
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/archive_list.png b/doc/book-enea-nfv-access-getting-started/doc/images/archive_list.png
deleted file mode 100755
index 302f32d..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/archive_list.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/collect_debug_logs.png b/doc/book-enea-nfv-access-getting-started/doc/images/collect_debug_logs.png
deleted file mode 100755
index 6582737..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/collect_debug_logs.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/debug_settings.png b/doc/book-enea-nfv-access-getting-started/doc/images/debug_settings.png
deleted file mode 100755
index 2c97b2c..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/debug_settings.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/dev_file_mg.png b/doc/book-enea-nfv-access-getting-started/doc/images/dev_file_mg.png
deleted file mode 100755
index a4a4f5c..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/dev_file_mg.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/download_files.png b/doc/book-enea-nfv-access-getting-started/doc/images/download_files.png
deleted file mode 100755
index cb686e4..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/download_files.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/edit_inter.png b/doc/book-enea-nfv-access-getting-started/doc/images/edit_inter.png
deleted file mode 100755
index fddde37..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/edit_inter.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/edit_inter_config.png b/doc/book-enea-nfv-access-getting-started/doc/images/edit_inter_config.png
deleted file mode 100755
index f9ab8aa..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/edit_inter_config.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/fault_events.png b/doc/book-enea-nfv-access-getting-started/doc/images/fault_events.png
deleted file mode 100755
index aeec955..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/fault_events.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/high_av_setup.png b/doc/book-enea-nfv-access-getting-started/doc/images/high_av_setup.png
deleted file mode 100644
index d119ecb..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/high_av_setup.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png b/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png
deleted file mode 100755
index da52202..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/ovs_bridges_tab.png b/doc/book-enea-nfv-access-getting-started/doc/images/ovs_bridges_tab.png
deleted file mode 100755
index 0b3ec54..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/ovs_bridges_tab.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png b/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png
deleted file mode 100755
index 2db2487..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/prep_deploy.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png b/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png
deleted file mode 100755
index 404760b..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/prep_execution.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/telemetry_settings.png b/doc/book-enea-nfv-access-getting-started/doc/images/telemetry_settings.png
deleted file mode 100644
index 276b716..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/telemetry_settings.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/telemetry_start.png b/doc/book-enea-nfv-access-getting-started/doc/images/telemetry_start.png
deleted file mode 100644
index 81510b5..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/telemetry_start.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/vnf_space.png b/doc/book-enea-nfv-access-getting-started/doc/images/vnf_space.png
deleted file mode 100755
index 57ed581..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/vnf_space.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/wap_external_interface.png b/doc/book-enea-nfv-access-getting-started/doc/images/wap_external_interface.png
deleted file mode 100644
index ee49fc1..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/wap_external_interface.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/wap_wireless_ap.png b/doc/book-enea-nfv-access-getting-started/doc/images/wap_wireless_ap.png
deleted file mode 100644
index b7c77bf..0000000
Binary files a/doc/book-enea-nfv-access-getting-started/doc/images/wap_wireless_ap.png and /dev/null differ
diff --git a/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml b/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
deleted file mode 100644
index d9784a0..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/installation_guide.xml
+++ /dev/null
@@ -1,1193 +0,0 @@
-
-
- Setting up and Installing the Enea Edge Base Configuration
-
- The setup and installation steps detailed below will deploy a base
- configuration which will be used as a reference for more complex deployment
- scenarios.
-
-
- Hardware Requirements
-
- The following hardware is needed for deploying the base
- configuration:
-
-
-
- One server running the CentOS 7 distribution
-
-
- The CentOS 7 server must be updated to the latest revision
- before installing Enea Edge.
-
-
- The following will detail CPU, RAM and storage requirements for
- the Enea Edge Management.
-
-
-
- For small-sized deployments (tens of devices):
-
-
-
- 4 cores
-
-
-
- 16 GB RAM
-
-
-
- 300 GB single disk storage
-
-
-
-
-
- For mid-sized deployments (hundreds of devices):
-
-
-
- 8 cores
-
-
-
- 32 GB RAM
-
-
-
- 300 GB single disk storage
-
-
-
-
-
- For large deployments (thousands of devices):
-
-
-
- 16 cores
-
-
-
- 64-256 GB RAM
-
-
-
- 1-2 TB single disk storage
-
-
-
-
-
- The purpose of the CentOS 7 server is to host the Enea Edge
- Management. Network access between the CentOS 7 server and the uCPE
- devices is required. The Enea Edge Management and the uCPE devices
- will be connected on separate subnets to avoid inconsistencies.
-
-
-
- One or more uCPE devices.
-
- Whitebox devices where the Enea Edge Runtime will be installed,
- containing a minimum of 2 cores and 4 GB RAM and at least two ethernet
- ports that will be configured as WAN and LAN during deployment.
-
- When hosting an entire solution including one or several network
- services, the hardware must also have the resources to host one or
- more VNFs. During a typical evaluation, a dual VNF service on the Enea
- Edge Runtime needs a CPU with 4-8 cores and at least 8 GB RAM. The
- supported Intel CPUs of Enea Edge are documented in the
- manual.
-
- Enea Edge Runtime needs EFI support in BIOS to boot. When
- configuring the uCPE device BIOS a serial connection is
- required.
-
-
-
- A laptop.
-
- The laptop is used for 2 scenarios:
-
-
-
- Installing the Enea Edge Runtime on uCPE Devices.
-
-
-
- Connecting to the GUI of the Enea Edge Management for
- management and configuration. Network access between the CentOS 7
- server and the laptop is required. Please see the manual
- available with your release, for recommended browsers.
-
-
-
-
-
- A 16 GB USB stick used for the uCPE Device Installation.
-
-
-
-
-
- Software Configuration
-
- The CentOS 7 server requires a specific configuration for the setup
- to work.
-
-
- Firewall Configuration
-
- Any firewall running on the CentOS 7 server may block the
- management protocols required to communicate between the uCPE device and
- the Enea Edge Management as well as between the Enea Edge Management and
- its northbound clients. Quick handling of a blocking firewall would be
- to disable it, typical for a lab environment, through:
-
- sudo systemctl stop firewalld
-sudo systemctl disable firewalld
-sudo systemctl mask now firewalld
-
- For an advanced firewall configuration, the following ports need
- to be opened:
-
-
- Ports to be Activated
-
-
-
-
-
-
- 80
-
- TCP
-
- Required for GUI Access.
-
-
-
- 443
-
- TCP
-
- Required for GUI Access and Device Connectivity.
-
-
-
- 54327
-
- UDP
-
- Required for the Enea Edge Management High Availability
- Configuration.
-
-
-
- 5701:5708
-
- TCP
-
- Required for the Enea Edge Management High Availability
- Configuration.
-
-
-
- 4334
-
- TCP
-
- Required for Call Home.
-
-
-
- 2021:2040
-
- TCP
-
- Required for Call Home when connecting uCPE Devices using
- Enea NFV Access 2.3.0 or older.
-
-
-
-
-
- Use the following command sequence to enable the required ports
- for deployment of the Enea Edge Management:
-
- sudo firewall-cmd --permanent --add-port=80/tcp
-sudo firewall-cmd --permanent --add-port=443/tcp
-sudo firewall-cmd --permanent --add-port=54327/udp
-sudo firewall-cmd --permanent --add-port=5701-5708/tcp
-sudo firewall-cmd --permanent --add-port=4334/tcp
-sudo firewall-cmd --permanent --add-port=2021-2040/tcp
-sudo firewall-cmd --reload
-
-
- If the Enea Edge Management host resides behind a corporate
- port-filtering firewall, then all the aforementioned ports need to
- also be enabled on the respective firewall. As an additional
- requirement, port 22/TCP also needs to be enabled for reverse SSH to
- the Enea Edge Management.
-
- No enabling and no forwarding rules are necessary for ports
- 2021-2040 if using Enea Edge 2.4.0 or newer.
-
-
-
-
- Configuring OpenJDK and PostgreSQL
-
- The Enea Edge Management requires a specific Java version (OpenJDK
- 11) and a PostgreSQL version to operate correctly.
-
- Installing OpenJDK
-
-
-
- Install OpenJDK 11 using the root account:
-
- yum install java-11-openjdk-devel
-
-
-
- Verify the installation:
-
- java -version
-openjdk version "11.0.3" 2019-04-16 LTS
-OpenJDK Run Time Environment 18.9 (build 11.0.3+7-LTS)
-OpenJDK 64-Bit Server VM 18.9 (build 11.0.3+7-LTS, mixed mode, sharing)
-
-
- If there are multiple java versions installed, switch
- between them using the following command:
-
- alternatives --config java
-
- Optionally, the user can switch between the
- javac versions using:
-
- alternatives --config javac
-
-
-
-
- The following system variables need to point to the OpenJDK 11
- installation:
-
- export JAVA_HOME=$(dirname $(dirname $(readlink $(readlink $(which java)))))
-export PATH=$PATH:$JAVA_HOME/bin
-export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
-
-
- In order to make these system variables persistent, the
- commands given above should be added to a script in the
- /etc/profile.d/ folder. Sudo access is needed for this
- operation.
-
-
-
-
- The Enea Edge Management requires a specific PostgreeSQL version.
- This is embedded in the Enea Edge Management installation. In order to
- avoid conflicts, any existing PostgreeSQL installation needs to be
- uninstalled.
-
- Uninstalling PostgreSQL
-
-
-
- Open a terminal with administrative rights, i.e. log into a
- bash shell with root privileges.
-
-
-
- Execute the following command to check if you have a currently
- running PostgreSQL database server:
-
- ps -ef | grep post
-
-
-
- Remove the installed PostgreSQL server (including the existing
- postgres user):
-
-
- This step is not necessary if the Enea Edge Management will
- be using an external database (like MariaDB).
-
-
- yum remove postgres\*
-rm -rf /var/lib/pgsql
-rm -f /etc/postgres-reg.ini
-userdel postgres
-
-
-
- If you have multiple spindles, it is recommended to let the
- application run off one and the database off the other. This will result
- in optimum performance. It is also recommended that the swap disk be the
- same as the one used for the application.
-
- Assuming another spindle is used (/drive2 ) do
- the following:
-
-
-
- Create a folder which will host the database (e.g.
- emsDatabase ).
-
-
-
- Create a soft-link that will point to this folder:
-
- ln -s /opt/ems/elementcenter/database /drive2/emsDatabase
-
-
-
- Follow the installation steps for the Enea Edge Management
- available in Installing the Enea Edge Management in
- the
- Manual.
-
-
-
-
-
-
- uCPE Device Configuration
-
-
- Determining the WAN and LAN ports
-
- A typical whitebox comes with multiple physical network ports,
- ready to be used. The user must determine the purpose and allocation of
- each port. The allocation is later aligned with the software
- configuration within the Web-installer.
-
- A common way is to allocate the left ports to WANs and the right
- ports to LANs. At least one port must be allocated to WAN and one to
- LAN.
-
-
-
- Determining the Device ID
-
- Each uCPE device needs a unique identifier. This identifier is
- used to match the registration in the Enea Edge Management and the
- offline configuration of the uCPE device during ZTP (Zero Touch
- Provisioning).
-
- Select a text string to represent the uCPE device, e.g.
- uCPE-1 or fwa-t1012vc_boston_1234 .
- It can have any length and any type of characters with the exception of
- quotation characters (' or ") or line terminators (\n or \r) which can
- interfere with the JSON format of the
- install_data.json file.
-
-
-
- Configuring the BIOS
-
- The factory configuration of the BIOS may not match the
- requirements of Enea Edge Runtime. The BIOS configuration needs to be
- reviewed and potentially reconfigured to prepare for a successful
- installation.
-
- Access the BIOS using a serial cable between the uCPE device and
- the laptop, to review and configure the BIOS correctly. The whitebox
- vendor is expected to provide the right serial cable for the box. A
- terminal emulator (such as putty) is needed on the laptop.
-
- Enable the following BIOS features/configurations:
-
-
-
- EFI
-
-
-
- Intel Virtualization Technology (VT-x)
-
-
-
- Intel Virtualization Technology for Directed I/O (VT-d)
-
-
-
- SR-IOV
-
-
-
- The boot order may also need to be modified to support
- installation and execution of the Enea Edge Runtime on the uCPE
- device.
-
- The following boot order is recommended for a base
- configuration:
-
-
-
- Boot from USB
-
-
-
- Boot from Disk
-
-
-
- By arranging the above boot order there is no need for a further
- configuration of the BIOS during installation and deployment.
-
-
-
-
- Preparing the Deployment
-
-
- Installing the Enea Edge Management
-
- The Enea Edge Management can be installed using a fresh
- (first-time) configuration or using a backup file of a previous
- installation, created within the Enea Edge Management GUI.
-
-
- Fresh Installation of the Enea Edge Management
-
- On the CentOS 7 server open a terminal, log into a bash shell
- with the root account and perform the following:
-
-
-
- Extract
- Enea_Edge_Management_<version>-build<build_number>.tar.gz
-
- The directory in which the archive has been unpacked will be
- denoted as: <uCPEM-installdir> .
-
-
-
- Enter <uCPEM-installdir>/dist .
-
-
-
- Choose the target installation folder, e.g.
- /opt/ems . Everything will be installed under a
- folder called /ucpemanager within the target
- installation folder.
-
- The application files will be installed in
- /opt/ems/ucpemanager/application . The database
- will be installed in
- /opt/ems/ucpemanager/database .
-
-
-
- Run the following interactive command:
-
- ./install.sh /opt/ems \
-Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
-
- The default configuration values are specified in brackets.
- If no other value is preferred and typed in, pressing
- ENTER will keep the default values. When there
- is an option within parentheses (i.e.Y/N), a value must be
- specified.
-
-
- The same configuration values set now will need to be
- provided when upgrading or uninstalling the Enea Edge
- Management.
-
-
-
-
- Database Configurations:
-
-
-
- Are you using the embedded PostgreSQL database?
- [Y/N]: Y .
-
-
-
- Specify the database process password
- [postgres]:
-
-
-
- Specify the database ID (or name)
- [ucpemanager]:
-
-
-
- Specify the database server port
- [5432]:
-
-
-
- Specify a database user name
- [postgres]:
-
-
-
- Specify a database password
- [postgres]:
-
-
-
- Specify the database startup thread pool size
- [1]:
-
-
-
-
-
- Service Configurations:
-
-
-
- Specify a service username
- [ucpemanager ]:
-
-
-
- Specify a service password
- [ucpemanager ]:
-
-
-
-
-
- High Availability Configurations:
-
-
-
- Specify the IP address of the local interface: The
- CentOS 7 Server loopback address:
- 127.0.0.1 .
-
-
-
- Is this server part of a cluster? [Y/N]:
- N .
-
-
-
-
-
- Heap Configuration: Please enter the new
- Maximum Heap Size [4g] :
-
-
-
- Create the self-signed certificate: Specify IP
- or domain name:
-
-
- The certificate can be generated again by running the
- createCertificate script from the
- distribution folder.
-
-
-
-
- This command will:
-
-
-
- Extract the application files from the compressed
- installation kit.
-
-
-
- Install the bundled database.
-
-
-
- Install the Enea Edge Management as a service with the
- name ucpemanager .
-
-
-
- Start the ucpemanager service
-
-
-
-
-
- Using the IPv4 address of the CentOS 7 Server in a web
- browser, running on the laptop, log into the Enea Edge Management
- GUI using the default username and password:
- admin/admin .
-
-
-
-
- The IPv4 address of the CentOS 7 Server, connected to the same
- network as the uCPE Devices, will be used as a configuration
- parameter when setting up the uCPE devices.
-
- If the CentOS 7 Server is installed behind NAT, the IPv4
- address used will be the public IP of the NAT device and port
- forwarding rules must be created to ensure the uCPE device can
- access the Enea Edge Management. For more details, please see Firewall Configuration.
-
-
-
-
- Installation of the Enea Edge Management using a System
- Back-up
-
- The Enea Edge Management can be restored if a backup file has
- been previously created.
-
- A backup file can be created by accessing the System menu, and clicking System Backup , from the Enea Edge Management
- GUI. The resulting zip archive will be located in the
- /opt/ems/ucpemanager/application/backup folder
- and will be named
- SystemBackup_MMMDD_YYYY_HHMM_SS.zip (e.g
- System-Backup_Feb19_2013_2257_42.zip). Save the archive to another
- location outside the Enea Edge Management installation folder for
- future use.
-
-
- The System Back-up file obtained from the Enea Edge Management
- GUI (SystemBackup_MMMDD_YYYY_HHMM_SS.zip ) is
- different from the snapshot obtained during a Enea Edge Management
- Upgrade or Uninstall operation
- (ucpemanager-Backup-YYYYddMMHHmm.tar.gz ) needed
- for recovery of the Enea Edge Management. For more details, see
- Restoring a previous Enea Edge
- Management installation in the
- Manual.
-
-
- To install the Enea Edge Management with the restore option
- provide an additional argument as shown below during
- installation:
-
- ./install.sh \
-/opt/ems Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz \
-SystemBackup_MMMDD_YYYY_HHMM_SS.zip
-
-
-
-
- Preparing the USB stick for installation of the Enea Edge
- Runtime
-
- To install the Enea Edge Runtime, create a bootable USB stick with
- the image you intend to install.
-
- In the example below, step by step instructions are provided for
- the CentOS 7 distribution. It's possible with the appropriate tools to
- also use Windows OS or MacOS.
-
-
- The .hddimg image is available in the
- Enea_Edge_Runtime_Platform_
- <processor>_<version>-build<build_number>.tar.gz
- file you downloaded with your release.
-
-
- Create a bootable USB stick
- image
-
-
-
- Copy the .hddimg image file provided by
- Enea, into the CentOS 7 server.
-
-
-
- Connect the USB stick to the CentOS 7 Server and identify the
- USB device name given by the system with
- lsblk :
-
- NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 1 28.7G 0 disk
-sdb 8:0 0 111.8G 0 disk
-|-sdb1 8:1 0 111.8G 0 part
-
-
-
- Copy the .hddimg image onto the USB
- stick, e.g:
-
- sudo dd if=./enea-nfv-access-<machine>.hddimg \
-of=/dev/sdb bs=4M conv=fsync
-
- Where
- enea-nfv-access-<machine>.hddimg is the
- .hddimg file and sdb is the
- assigned USB device name.
-
-
-
-
-
- Preparing Physical Deployment for Installation
-
-
- Preparing for Hardware Installation
-
-
-
-
-
-
-
-
- While the uCPE device is powered off, in order to install and
- configure the Enea Edge Runtime (using the prepared USB stick), connect
- the laptop to a uCPE device LAN port. For this purpose, a Layer 2 switch
- or direct cable connection can be used.
-
-
-
- Installing Enea Edge - uCPE Device Installation
-
- To initiate the installation of the Enea Edge Runtime do the
- following:
-
-
-
- Plug the USB stick into the uCPE device.
-
-
-
- Power up the uCPE device and boot the USB stick.
-
-
-
- The Web-installer application will start automatically and can
- be accessed in a web browser on the laptop at
- http://172.16.1.1 (port 80).
-
-
-
- On the Requirements page of
- the Web-installer, the user must confirm the current state of
- installation prerequisites is inline with the desired state:
-
-
-
- Requirements table. Minimum values apply to the
- installation process only. For runtime operations, additional
- resources should be available depending on the specific
- workload. Requirements are color coded (green when met, red when
- mandatory and not met, orange when optional and not met). The
- Requirements table has the following fields:
-
-
-
- Disk size (mandatory). 2GB or more are required for
- the installation.
-
-
-
- CPU cores (mandatory). 2 cores or more are required
- for the installation.
-
-
-
- RAM (mandatory). 2GB or more are required for the
- installation.
-
-
-
- VT-x (mandatory). Intel Virtualization Technology must
- be enabled.
-
-
-
- VT-d (optional, recommended). Intel Virtualization
- Technology for Directed I/O should be enabled.
-
-
-
- IOMMU Group separation (optional). If the hardware
- does not support IOMMU Group separation, there are certain
- limitations regarding how the vfio-pci
- driver can be used. For more details, see the Known Issues and Limitations in
- this Release in the
- Manual.
-
-
-
-
-
- Force installation checkbox. When enabled, the
- installation can be performed even if some of the mandatory
- requirements are not met or if non-fatal problems are detected
- during the process.
-
-
-
-
-
- On the Enea Edge Management
- settings page of the Web-installer, the user must fill
- in:
-
-
-
- The static Enea Edge Management IP Address or FQDN. This can be
- either:
-
-
-
- The IP address of the Enea Edge Management host
- machine, if the device can directly access it.
-
-
-
- The IP address of the NAT device, if the Enea Edge
- Management host is located behind a NAT. For more details,
- please see Firewall
- Configuration.
-
-
-
- The Fully Qualified Domain Name (FQDN) of the Enea
- uCPE Manager host machine.
-
-
-
-
-
- The unique identifier of the uCPE device (called
- "DeviceId" in this guide).
-
-
-
- Customer Tags. They are used for Zero Touch Provisioning
- (ZTP) and can be left empty for a base configuration. What can
- be entered here (if needed), are the tag(s) specified when
- creating an offline configuration in the Enea Edge Management. A
- later addition of customer tags can only be done by reinstalling
- the uCPE devices.
-
-
-
-
-
- Connect the WAN cable to the uCPE device (see Figure 2). This
- will be used as the uCPE management network interface, as described
- below.
-
-
-
- On the Network Setup page of
- the Web-installer, the user must do the following:
-
-
-
- Select a WAN interface to use as the management network
- interface. This interface is used by the Enea Edge Management to
- communicate with the uCPE device.
-
-
-
- Plug-in additional WAN interfaces (if applicable) and
- provide their Layer 3 configuration.
-
-
-
-
-
- When the user has completed the configuration steps in the
- Web-installer, Enea Edge Runtime is installed on the hard drive. At this
- stage, the user should remove the USB stick and the LAN cable, and
- shutdown the uCPE device. It will be started after necessary
- configurations are done in the Enea Edge Management, as described
- below.
-
-
- If errors are detected during installation, full logs will be
- available on the last page of the Web-installer. Please contact Enea
- for log analysis. The system is not expected to be usable if errors are
- reported during installation.
-
- If the USB stick was booted in UEFI mode, a UEFI boot entry is
- automatically created and the system will start booting from the hard
- drive without further user configuration.
-
-
-
-
- Preparing Physical Deployment for Execution
-
-
- Preparing for Deployment Execution
-
-
-
-
-
-
-
-
- The following network configuration is needed for managing the
- uCPE device and service deployment:
-
-
-
- Network connection between the server running the Enea Edge
- Management and the laptop.
-
-
-
- Network connection between the server running the Enea Edge
- Management and the uCPE device.
-
-
-
-
-
-
- Management of uCPE Devices
-
- When the installation is complete the uCPE device can be managed in
- the Enea Edge Management.
-
-
- Add a default Offline Configuration
-
- Zero Touch Provisioning is always turned on when a uCPE device
- connects to the Enea Edge Management. To enable it in the Enea Edge
- Management, an offline configuration needs to be registered for Day-0
- configuration.
-
-
- Day-0 configuration is a software lifecycle term referring to
- early configurations used to put the uCPE device in an active state.
- Day-1 Configurations are applied after Day-0 and set the uCPE device
- and its service in an active state. Day-2 Configurations are live
- configurations on the uCPE device and its service, applied after they
- have been activated.
-
-
- The offline configuration consists of data and parameters that are
- meant to be automatically set when a uCPE device connects to the Enea
- Edge Management for the first time. The configuration is typically
- focused on setting up the network management of the uCPE device, e.g.
- configuring network interfaces, WAN and LAN networking and service
- chains.
-
- For this base configuration, the offline configuration will be
- left blank. The blank offline configuration can be filled with
- user-specific values and data once the service is created, which is done
- after the installation is complete.
-
-
- If the offline configuration is not configured, an alarm will be
- raised: Day-0 Config:ZTP:Major when the uCPE device
- tries to connect to the Enea Edge Management, informing the user that
- the ZTP setup failed for the uCPE device.
-
-
- To create an offline
- configuration
-
- In a browser access the Enea Edge Management, open Applications and select Offline Config .
-
-
-
- Create a new offline configuration in the GUI by selecting
- the Add button and filling in the
- mandatory fields: name ,
- deviceVersion and
- deviceId .
-
- The name is user defined and can be set to any unique text
- string identifying the configuration. The
- deviceVersion must match the Enea Edge Runtime
- version of the uCPE device and the deviceId
- must be the previously set identifier of the uCPE device
- (DeviceId).
-
-
-
-
-
- Add a uCPE device to the Management System
-
- In order to enroll a uCPE device in the management system and
- establish a management connection, the user will add uCPE device
- information in the Enea Edge Management. This is accomplished by going
- to Devices , selecting Manage and then clicking the Add button.
-
- The relevant parameters are:
-
-
-
- Type. The type of device to
- be added, i.e Enea universal CPE.
-
-
-
- Name. The name by which the
- uCPE device is referred to in the Enea Edge Management.
- (Mandatory).
-
-
-
- SSH Port. The NETCONF Port
- used for communications. Default is set to 830.
-
-
-
- SSH User Name. The user name
- for SSH connectivity. Default user is root.
-
-
-
- SSH Password. Leave this
- blank.
-
-
-
- Device Calls Home. This
- checkbox indicates the direction of uCPE device communications. For
- a base configuration, leave this flag unchecked.
-
-
-
- Device ID. The unique
- identifier of the uCPE device. (Mandatory).
-
-
-
- For more details concerning Device Calls Home, please see Device Call Home Connection for
- Deployment behind NAT in the
- Manual.
-
-
-
- Booting the uCPE device and adding it to the Map
-
- When connectivity is established with the Enea Edge Management and
- a uCPE device is already registered with a matching Device
- ID , the installation is complete, and the connection is
- established.
-
- When a uCPE device is registered it can be manually added to the
- map for overview. Right-click on the
- map and select Place Device to put the
- uCPE device on the map.
-
- In case of management connection failure (e.g. due to a
- misconfiguration), the uCPE device status will be seen as RED
- (disconnected) in the Enea Edge Management. The uCPE device
- configuration can be corrected by removing the WAN cable(s),
- reconnecting the laptop to the LAN interface of the uCPE device and
- rebooting it. At this point, the Web-installer can be accessed from the
- laptop as described in Installing Enea Edge - uCPE Device
- installation in the
- Manual.
-
-
-
-
- uCPE Device Monitorization and Control
-
- Once the uCPE device is connected to the Enea Edge Management, it is
- ready for central management. Two important functions available in the
- Enea Edge Management GUI are alarm checking and resource
- allocation.
-
-
- Checking Alarms
-
- The Enea Edge Management dashboard presents alarms in a specific
- window on the front page.
-
- An alarm can be easily triggered by disconnecting and reconnecting
- the WAN ethernet cable from the uCPE device. The management system will
- detect the broken link and raise an alarm: Device
- Disconnected::Critical .
-
- A separate Alarm Management window can be accessed from the Enea
- Edge Management menu for in-depth access and programming of Alarms and
- Events.
-
-
-
- Checking uCPE device Resource Allocation
-
- When the uCPE device is connected to the Enea Edge Management it
- is of interest to check the amount of hardware resources in use.
-
- To check CPU, RAM and disk utilization simply select the uCPE
- device and go to the Virtual Machines
- tab in the map view. The same view will show active VNFs running on the
- uCPE device once instantiated.
-
-
-
- Accessing the uCPE device CLI
-
- As a final check to make sure the uCPE device was installed and
- configured correctly, access the uCPE device Linux CLI by selecting the
- uCPE device on the map and using the SSH
- button from the panel. A new window will appear for CLI
- access. The default user and password are root and
- blank, respectively.
-
- This is a pure Linux CLI providing access to standard Linux CLI
- commands. The CLI is a central feature for running custom
- scripting.
-
-
- In case the uCPE device was installed behind a NAT device, the
- reverse SSH connection will be used. For more details, please see
- Device Call Home Connection for
- deployment behind NAT in the
- Manual.
-
-
-
-
diff --git a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
deleted file mode 100644
index 4dec1e1..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
+++ /dev/null
@@ -1,264 +0,0 @@
-
-
-
- Overview
-
- This document describes the Enea Edge and provides installation
- steps for deploying a base configuration in order to create:
-
-
-
- A functional Enea Edge Management installation ready to manage uCPE
- devices.
-
-
-
- One or several managed uCPE devices, ready to host network
- services, using one wired WAN and one wired LAN connection.
-
-
-
- Extended deployment and configuration options are also detailed in the
- following chapters.
-
-
- Enea Edge
-
- Enea Edge for universal Customer Premise Equipment (uCPE) is a
- virtualization and management platform, which allows end-users to onboard,
- instantiate, and run third-party VNFs onto their systems. It is comprised
- of two major components working in close cooperation:
-
-
-
- The Enea Edge Runtime, which acts as the host
- for Virtualized Network Functions (VNFs) and provides management over
- NETCONF.
-
-
-
- The Enea Edge Management, a solution that runs on an external
- server, used for VNF Management and managing large numbers of uCPE
- devices.
-
-
-
- In addition, Enea Edge includes a framework for
- automation and testing. More information can be found in
- .
-
- Details concerning release content, including documentation
- structure, are provided in the manual included
- with your release.
-
-
- Enea Edge Runtime
-
- Enea Edge Runtime is a lightweight,
- multi-architecture virtualization platform built on de-facto standards
- in an SDN/NFV ecosystem. It is designed for a high networking
- performance with minimal hardware footprint, by only providing relevant
- functionalties and technologies.
-
- Virtualization methods include Virtual Machines (KVM / QEMU) and
- container(s) (Docker). High networking throughput and low latency are
- ensured by accelerated data plane relying on technologies like DPDK,
- OVS-DPDK and SR-IOV/PCI-Passthrough. Key functionalities, such as
- platform software management, virtualized networking, VNFs life-cycle
- management and FCAPS are provided through the YANG-modelled NETCONF
- protocol.
-
-
- VNF Space
-
-
-
-
-
-
-
-
-
-
- Enea Edge Management
-
- The Enea Edge Management is centralized control system providing
- uCPEs domain management capabilities through a GUI and REST API. It can
- be deployed on a host or a virtual machine running 64-bit CentOS 7 on an
- x86 platform. The Enea Edge Management uses a southbound NETCONF protocol
- to connect and manage uCPE devices.
-
- The Enea Edge Management provides the following key features:
-
-
-
- Enea Edge Runtime Software Management
-
-
-
- VNF Onboarding
-
-
-
- VNF Management
-
-
-
- FCAPS
-
-
-
- Zero Touch Provisioning
-
-
-
- Alarms / Events management and monitoring
-
-
-
-
-
-
- Definitions and Acronyms
-
-
- Definitions
-
-
- Definitions
-
-
-
-
-
-
-
-
- Enea Edge
-
- The Enea Edge Runtime and the Enea Edge
- Management.
-
-
-
- Enea Edge Runtime
-
- A lightweight, multi-architecture virtualization
- platform, supporting Virtual Machines.
-
-
-
- Enea Edge Management
-
- Enea Universal Customer Premises Equipment
- Manager.
-
-
-
- uCPE device
-
- A whitebox running the Enea Edge
- Runtime.
-
-
-
-
-
-
-
- Acronyms
-
-
- Acronyms
-
-
-
-
-
-
-
-
- API
-
- Application Programming Interface.
-
-
-
- DPDK
-
- Data Plane Development Kit.
-
-
-
- EFI
-
- Extensible Firmware Interface.
-
-
-
- FCAPS
-
- Fault-management, Configuration, Accounting, Performance
- and Security.
-
-
-
- NETCONF
-
- Network Configuration Protocol.
-
-
-
- NFV
-
- Network Functions Virtualization.
-
-
-
- OVS
-
- Open vSwitch.
-
-
-
- UEFI
-
- Unified Extensible Firmware Interface.
-
-
-
- SR-IOV
-
- Single Root Input/Output Virtualization.
-
-
-
- PCI
-
- Peripheral Component Interconnect.
-
-
-
- REST
-
- Representational State Transfer.
-
-
-
- VNF
-
- Virtual Network Function.
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml b/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
deleted file mode 100644
index baa1340..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/log_collector.xml
+++ /dev/null
@@ -1,401 +0,0 @@
-
-
- Using the Log Collector
-
- Troubleshooting problems on the uCPE device require an analysis of a
- set of information i.e. logs collected from the uCPE device and/or the Enea
- Edge Management. The following information describes how the log collection
- mechanism works.
-
-
- Log collecting using the Enea Edge Management
-
- The Enea Edge Management allows for collecting a set of logs and state
- information from a uCPE device.
-
-
- Collecting the Logs
-
- Collect the necessary log files and system details, then create an
- archive (a tar file) on the uCPE device in the
- /var/odm/log/archives folder:
-
-
-
- Access Operations and then
- select Collect Debug Logs .
-
-
-
- Provide a file name in the new window.
-
-
-
- Press the Execute button.
-
- A success message is shown in the same window as shown below.
- At this moment, the process of collecting logs on the uCPE device
- starts.
-
-
-
- Collecting Debug Logs
-
-
-
-
-
-
-
-
-
-
- It might take some time for the archive to be created. When the
- operation completes, a "CollectLogsComplete" notification is sent from
- the uCPE device to the Enea Edge Management. This can be viewed in the
- GUI in the Faults menu, after selecting
-Events .
-
-
- Collecting Debug Logs
-
-
-
-
-
-
-
-
-
-
-
- View collected Logs
-
- A list with the archives containing already collected logs will be
- shown in the Device File Listing table:
-
-
-
- Access Files and then the
-Download button.
-
-
-
- Press the List button.
-
-
- Device File Listing Table
-
-
-
-
-
-
-
-
-
-
-
- If the filename you specified does not appear, it might still be
- in the process of creation. Click on the Refresh
- icon at the bottom of the table until you can see the desired file
- listing.
-
-
-
-
- Downloading Logs from the uCPE Device
-
- This option transfers a debug file archive from the uCPE device to
- Enea Edge Management.
-
-
-
- Access Files and choose the
- Download button.
-
-
-
- Press the List button.
-
-
-
- In the Device File Listing table, select
- the archive you want to download from the uCPE device to Enea Edge
- Management.
-
-
-
- Press the Download from Device
- button.
-
- The archive will be downloaded from the uCPE device and stored
- on the Enea Edge Management.
-
-
-
-
- The archive will not be deleted from the uCPE device after
- download.
-
-
-
-
- Downloading collected Logs locally
-
- This option downloads a logs archive from the Enea Edge Management to
- a local (user) machine for analysis. The archive must first be available
- in the Enea Edge Management in order to be downloaded.
-
-
-
- Access the Devices menu and select
-Files .
-
-
-
- Select the Downloaded Files tab.
-
-
-
- Select an archive from the Downloaded Files
- table.
-
-
-
- Click the Download button.
-
- The file will be downloaded in browser's download
- folder.
-
-
- Downloaded Files Table
-
-
-
-
-
-
-
-
-
-
-
-
- Deleting a Logs Archive from a uCPE device
-
- Use this option when you want to delete unnecessary collected logs
- on the uCPE device.
-
-
-
- Access Files and then click the
- Download button.
-
-
-
- Press the List button.
-
-
-
- In the Device File Listing table, select
- the archive you want to delete from the uCPE device.
-
-
-
- Press the Delete button.
-
- The archive will be deleted from the uCPE device and the table
- will be updated.
-
-
-
- The same can be achieved using these alternative options:
-
-
-
- Access the Operations menu and
-select Delete Debug Log Archive .
-
-
-
- Provide a file name in the new window.
-
-
-
- Press the Execute button.
-
- A success message is displayed if the file is deleted from the
- uCPE device correctly.
-
-
-
-
-
- Deleting a Logs Archive from the Enea Edge Management
-
- This option deletes a logs archive from the Enea Edge
- Management.
-
-
-
- Access the Devices menu, then select
- Files .
-
-
-
- Select the Downloaded Files tab.
-
-
-
- Select an archive from the Downloaded Files
-table.
-
-
-
- Click the Delete button.
-
- The file will be deleted from the Enea Edge Management and the
- table will be updated.
-
-
-
-
- Deleting the logs file from the Enea Edge Management does not
- affect the file located on the uCPE device.
-
-
-
-
- Enabling/Disabling of the Log Collector via Permissions
-
- To disable the ability to access/download the uCPE device's
- debug-log files from the Enea Edge Management, the appropriate permissions
- must be changed:
-
-
-
- Access the Security menu,
-then select Configuration .
-
-
-
- Click the Security Groups tab.
-
-
-
- Click the desired group.
-
-
-
- Click the Permissions tab on the right
- side.
-
-
-
- Click the Devices tab like in the image
- below.
-
-
-
- Change the Device File Management option to
- none to disable the feature.
-
-
-
-
- Device File Management
-
-
-
-
-
-
-
-
-
-
- Downloading Enea Edge Management Logs
-
- Often, sending the Enea Edge Management logs together with collected
- uCPE device logs to the support team provides important information for
- troubleshooting (especially in cases of connectivity issues with the
- uCPE device and error popups).
-
- Enea Edge Management log files are located in
- application/logs/ in the Enea Edge Management's
- installation folder
- (e.g./opt/ems/ucpemanager/application/logs ). They
- can be copied from that location, or they can be downloaded using the
- Enea Edge Management GUI by performing the following:
-
-
-
- Access Test , then Debug
- Settings and select the Log Files tab.
-
-
-
- Select the desired log file
- (ucpemanager.log or
- watchdog.log ) and press the
- Download button.
-
-
-
- A new (blank) popup window opens and the file is downloaded
- locally. This popup can be closed after the download.
-
-
-
- Repeat steps 2. And 3. Until all the desired log files have
- been downloaded
-
-
-
-
- Debug Settings
-
-
-
-
-
-
-
-
-
-
-
- Log collecting without using the Enea Edge Management
-
- Log collection from uCPE Devices can also be done when there is no
- Enea Edge Management connection. A SSH connection to uCPE Device is needed
- for use of the log collector script, which can be found in the uCPE Device
- file system in /usr/local/enea/ .
-
- The Log collector script takes relevant information about the system
- and collects it in an archive:
-
- ./log-collector.sh -p <LOG_PATHh> -n <ARCHIVE_NAME>
-
- Where -p is the path where the log archive will
- be saved, -n is the archive name.
-
-
- If -p is not provided, the default path will be
- used: /var/logcollector . If -n is
- not provided, the default name will be used:
- log_archive_<timestamp>.tar.gz .
-
-
- To access the help menu of the script:
-
- ./log-collector.sh -h
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml b/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
deleted file mode 100644
index dae5b36..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/net_config_options.xml
+++ /dev/null
@@ -1,886 +0,0 @@
-
-
- Network Configuration Options
-
- Various Advanced Network Configuration options can be done from Enea
- Edge Management GUI.
-
-
- Device Call Home Connection for Deployment behind NAT
-
- The Device Call Home option enables the initiation of the connection
- between the uCPE Device and the Enea Edge Management, from the uCPE
- device. The Device Call Home option is required when deploying a uCPE
- device behind NAT since the IP address of the uCPE device is hidden for
- the Enea Edge Management.
-
- Enable Device Call Home by marking the Device Call Home checkbox
- when registering the uCPE device in Enea Edge Management. When using this
- mechanism, the device will initiate a connection to the Enea Edge
- Management for NETCONF traffic (over SSH), while the Enea Edge Management
- waits for a device connection.
-
-
-
- uCPE Device Network Configuration
-
- The following describes the steps required for setting up the
- virtualization infrastructure, ensuring that a uCPE device has networking
- setup for virtualized service deployment. Networking is enabled by
- selecting physical interfaces to be used by virtualized networking and
- creating different types of bridges to enable VNF communication.
-
- The Zero Touch Provisioning mechanism is also touched upon, as
- alternative to manual configuration of the virtualization
- infrastructure.
-
-
- Configure DPDK
-
- DPDK is an important functionality for accelerating networking
- performance. The DPDK is enabled by default and should be utilized in
- most configurations.
-
- In use cases where CPU capacity is very limited, disabling DPDK
- can free up CPU capacity and overall performance can improve. Navigate
- to Configuration , then DPDK and deselect Enable
- DPDK to disable the DPDK.
-
-
- Disabling the DPDK cannot be done after other network
- configurations have been made.
-
-
- In Configuration , select
- DPDK where DPDK resources can also be
- configured such as:
-
-
-
- LCore Mask . Allocated cores
- for non-datapath OVS-DPDK threads (CPU core bitmask). Default:
- 0x2.
-
-
-
- PMD CPU Mask . Allocated cores
- for datapath processing (CPU core bitmask). Default: 0x4.
-
-
-
- Socket Memory . Hugepage
- memory allocated for DPDK. Default: 1494.
-
-
-
-
-
- Configure External Interfaces
-
- Once a management connection with the uCPE device has been
- established by using any of the supported methods, the virtualization
- networking infrastructure can be configured either manually or by using
- Zero Touch Provisioning.
-
- Available network interfaces can be added to the management
- system, for use by the networking virtualization infrastructure.
-
- In order to make physical network interfaces available to the
- virtualization infrastructure and VNFs, they must be configured into the
- management system.
-
- To add an interface into the Enea Edge Management, select the uCPE
- device, then from the top toolbar select Configuration , then External Interfaces , Configuration , and click the Add button. The available Interface types are
- detailed below.
-
-
- DPDK Interface Type
-
- Configuring a physical interface in DPDK mode will require a
- DPDK-based application (e.g. OVS-DPDK) in order to access and use the
- interface. An interface set as DPDK can be attached to an OVS-DPDK
- bridge.
-
-
- Make sure the Enable DPDK
- checkbox is selected by accessing Device , Configuration and choosing DPDK , otherwise no interface can be assigned
- as DPDK.
-
-
- To add a DPDK interface under the management system, set
- appropriate values for the following fields:
-
-
-
- Source: name of the physical interface.
-
-
-
- Networking-type: dpdk
-
-
-
- Dpdk-type: the kernel module that allows user space access
- to the physical interface. Either the vfio-pci
- (most commonly used type) or the igb_uio driver
- can be used.
-
-
-
-
-
- SR-IOV Interface Type
-
- SR-IOV technology allows for the creation of a number of virtual
- functions on the host interface, which can be used by VNFs running on
- the uCPE device.
-
- For SR-IOV mode configuration, the user must set values for the
- following fields:
-
-
-
- Source: name of the physical interface.
-
-
-
- Networking-type: srIov
-
-
-
- sriov-mode: adapter-pool
-
-
-
- sriov-num-vfs: the number of virtual functions to
- create.
-
-
-
-
-
- Standard Interface Type
-
- Some of the physical network interfaces available on a uCPE
- device, including Ethernet interfaces, do not have DPDK or SR-IOV
- support. Instead, the Linux kernel driver has to be used.
-
- To add Standard Interfaces under the management system, the user
- must set values for the following fields:
-
-
-
- Source: the name of physical interface.
-
-
-
- Networking-type: standard.
-
-
-
-
-
- Wan Interface Type
-
- WAN interfaces configured during the installation of the uCPE
- device are automatically added in the Enea Edge Management as type
- wan . The WAN interface used for management of the
- uCPE device is marked with the Management property
- set to True .
-
- If a WAN interface is to be assigned for use by a VNF, it must
- be changed into another interface type depending on the type of
- connection that will be used. The management WAN interface cannot be
- changed to a different type. It is automatically used when an In-band
- management bridge is created.
-
- How to Edit the Configuration of a Wan
- Interface
-
-
-
- To edit an interface configuration type from the Enea Edge
- Management, select the uCPE device, then from the top toolbar
- select the Configuration menu,
- then External Interfaces and
- Configuration . The already
- configured interfaces are displayed here, as seen in the figure
- above.
-
-
-
- In order to edit an already configured interface, (as in the
- example popup shown below, a WAN interface) double click on the
- desired one and a popup will appear. A different popup appears for
- each type of interface. From the Host
- Interface window, a user can change the networking type
- and the IP address assignment:
-
-
- Editing an Interface
-
-
-
-
-
-
-
-
-
-
-
- When changing the address-assignment from
- static to DHCP, if any of the ip-address ,
- netmask or gateway fields have
- invalid values a validation error will be triggered. These fields
- must be empty or have the valid values for their respective address
- assignment.
-
-
-
-
- Wap Interface Type
-
- Wireless Access Point (Wap) interfaces are used to create
- Wireless Access Points. Only interfaces with
- wap-capable capabilities can be added as WAP
- interfaces.
-
- How to edit the Configuration of a Wap
- Interface
-
-
-
- To edit an interface configuration from the Enea Edge
- Management, select the uCPE device, then from the top toolbar
- select the Configuration menu
- then External Interfaces and
- select Configuration . The already
- configured interfaces will be displayed here.
-
-
-
- In order to edit an already configured interface, (as in the
- example popup shown below, a WAP interface) double click on the
- desired one and a pop-up will appear. A different pop-up appears
- for each type of interface. From the Host
- Interface window, the following parameters are
- configurable:
-
-
-
- Country Code: the country code, a 2 letter
- ISO3166-alpha2 identifier.
-
-
-
- Wireless Band: 2.4 GHz or 5 GHz. Depending on the band
- selection, the correct Wireless Mode and
- Radio Channel must be provided.
-
-
-
-
- Editing an Interface
-
-
-
-
-
-
-
-
-
-
-
- Correct Country Code
- selection is mandatory. All configuration options are available in
- the Enea Edge Management GUI but only the Radio Settings that
- conform with the selected country's official regulatory laws will be
- applied when the Wireless AP is started on the uCPE Device.
-
-
-
-
- Manual Configuration
-
- For Manual Configuration of uCPE networking, select the uCPE
- device first, then access the Configuration menu, and choose External Interfaces , where a list of available
- network interfaces and their capabilities can be found.
-
- After networking interfaces have been added to the Enea Edge
- Management, the user can change the interface type (DPDK, SR-IOV,
- Standard, WAN, WAP).
-
-
- Configuration of External Interfaces
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Zero Touch Provisioning - Creating an Offline Configuration
-
- Zero-Touch Provisioning (ZTP) refers to the process of when a device
- starts up for the first time and its initial configuration is pushed down
- by an external management system, so that it is setup for proper operation
- without additional manual intervention by an operator. ZTP is an
- alternative to Manual configuration.
-
- A variety of operations can occur as part of ZTP such as initial
- device setup, configuration of managed objects, etc. The goal is to set up
- a device to the maximum possible extent without forcing an operator to be
- physically present (initially) to manage the device.
-
- An offline configuration is usually prepared in advance for the Enea
- Edge Management to setup the virtualization infrastructure on the uCPE
- device, as soon as a device enrolls into the management system.
-
-
- Offline Configuration
-
- The Offline Configuration subsystem is used to pre-populate a
- configuration for a device that will be brought under management at a
- future point in time. When creating an offline configuration store a
- Device ID can be specified. This ID uniquely
- identifies the device to be initialized.
-
- Alternatively, a wildcard can be used in the Device
- ID field, which results in a configuration being pushed on all
- uCPE devices upon their initial connection towards the Enea Edge
- Management.
-
- If the offline configuration is not configured for a uCPE device,
- an alarm will be raised: Day-0 Config:ZTP:Major ,
- which occurs when the uCPE device connects to the Enea Edge Management
- informing that the ZTP setup failed for the specific uCPE device.
-
- To create an offline configuration, select from the top toolbar
- the Applications menu, then Offline Config and choose Add . The following fields should be
- filled:
-
-
-
- Name: name of the device.
-
-
-
- Device type: Enea universal CPE.
-
-
-
- DeviceVersion:
-
-
-
- Config Set: uCPE Config
-
-
-
- Device ID: device ID or a wildcard(*).
-
-
-
- Device Grouping Tags: a tag to group devices. These tags match
- the customer tags provided during the installation of the
- device.
-
-
-
- The Name is user defined and can be set to any unique text string
- identifying the configuration. The Device Version will match the Enea
- Edge version of the uCPE device and the Device ID will be set to the
- previously set identifier of the uCPE device.
-
- When a device connects to the Enea Edge Management for the first
- time, it checks the device to see if it has been Zero Touch Provisioned
- (ZTP). If not, it looks for an offline configuration that matches these
- values, in the following order:
-
-
-
- The Device ID.
-
-
-
- The set of tags.
-
-
-
- A "*" for Device ID (wildcard).
-
-
-
- If a match is found, the offline configuration is sent to the
- device as part of Zero-Touch-Provisioning.
-
- After creating the Offline Config Store, access the device by
- selecting Applications , then offline config and clicking Config App , to provision it with the required
- initial configuration. This operation mirrors what happens during manual
- configuration described previously.
-
-
- The ZTP will only be triggered the first time a uCPE device
- connects to the Enea Edge Management. Just changing an offline
- configuration will not push the new changes to the device. If an
- offline configuration is changed after uCPE device registration, a
- factory reset can be executed to force a new ZTP to execute. Select
- the device, then access the Operations menu and select factory reset .
-
-
-
-
-
- Custom Scripts for Custom Networking Configurations
-
- The custom scripts feature allows users to execute user-defined
- scripts on the uCPE device at various times.This allows for more flexible
- and advanced configurations such as a LTE modem configuration, advanced
- network configurations or OVS flow rule programming at any time.
-
-
- Uploading Scripts
-
- The scripts need to be uploaded to the Enea Edge Management prior
- to use. When uploading scripts to the Enea Edge Management make sure to
- select the right script type.
-
- The following script types are supported:
-
-
-
- Once-before-startup . This script will only
- execute once after the system has rebooted, prior to processing any
- device configuration.
-
-
-
- Always-before-startup . This script will
- always execute after the system has rebooted, prior to processing
- any device configuration.
-
-
-
- Once-after-startup . The script will always
- execute after the system has rebooted, after all device
- configuration processes have completed.
-
-
-
- Always-after-startup . This script will
- always execute after all device configuration processes have
- completed after the system has rebooted.
-
-
-
-
- After a factory reset, any of the
- Once-before-* or Once-after-*
- scripts will be re-run as described above.
-
-
- Follow the instruction below to upload scripts:
-
-
-
- Access the Devices menu, then
- Custom Scripts and choose Configure .
-
-
-
- Select Upload to EMS .
-
-
-
- In the Script Type menu,
- select the type the uploaded script should have.
-
-
-
- Press Choose File to select
- the scripts needed, and then click Send .
-
-
-
-
-
- Removing Scripts
-
- Follow the instruction below to remove scripts:
-
-
-
- Access the Devices menu, then
- Custom Scripts and select Configure .
-
-
-
- Select the script you want to delete from the Uploaded Scripts tab and then click Delete , which will remove the script
- immediately from the Enea Edge Management.
-
-
-
-
-
-
-
- Running the Scripts
-
- How to run Custom Scripts
-
-
-
- Access the Devices menu,
- choose Custom Scripts and select
- Apply Scripts .
-
-
-
- In the Script Config Screen
- pop up, select the devices from the device(s) chooser list on which
- to run the scripts. Press the >
- button to move the devices to the right side of the chooser, which
- is the list of devices that will execute the selected
- scripts.
-
-
-
- Select the scripts from the list under the device(s) chooser
- by pressing the + button.
-
-
-
- In the pop-up window, select the scripts from the list. If
- there are no scripts to select, then there is no script uploaded
- with that particular type. Upload the script(s) needed and try
- again.
-
-
-
- Check the Reboot devices
- checkbox if you want to reboot and execute the scripts at once and
- then select ok .
-
-
- The status of execution for the scripts can be seen by
- accessing Fault , opening the
- Events screen and filtering by
- device and/or the event name
- CustomScriptExecuted .
-
-
-
-
-
-
-
- Wireless Access Point
-
- The Wireless AP Screen from the Enea Edge Management Configuration
- menu allows users to configure a Wireless Access Point .
- A wap-capable interface and a LAN bridge must be added
- before doing the Wireless AP configuration. For more details see sections
- Wap interface Type and Data-plane bridge.
-
- The following parameters are configurable:
-
-
-
- SSID: the Wireless network name - any string with a max. length
- of 32 octets.
-
-
-
- Interface Name: the wap-capable external
- interface.
-
-
-
- Lan Bridge: the LAN bridge where wireless clients will be
- hosted.
-
-
-
- WAP Security Mode: open or
- wpa2Psk . When choosing wpa2Psk ,
- a password and an encryption
- must be provided. The password can be any string
- with a minimum length of 8 and a maximum length of 63
- characters.
-
-
-
- DHCP Server: disabled or
- enabled . When enabled is
- selected, the range of IPs (IP Address Start -
- IP Address End ), Netmask and
- Gateway values must be provided.
-
-
-
-
- Wireless AP
-
-
-
-
-
-
-
-
-
- Only a single Wireless AP is allowed on a physical interface. The
- validation of the wap-capable interface is done when
- adding the Wireless AP, so, in case of an error, the parameters of the
- wap-capable interface must be rechecked. This can be
- done by accessing the Configuration
- menu and selecting External
- Interfaces .
-
-
-
diff --git a/doc/book-enea-nfv-access-getting-started/doc/troubleshooting.xml b/doc/book-enea-nfv-access-getting-started/doc/troubleshooting.xml
deleted file mode 100644
index 4984a35..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/troubleshooting.xml
+++ /dev/null
@@ -1,226 +0,0 @@
-
-
- Troubleshooting and Recovery
-
- In all scenarios where possible, collect the logs for debugging. More
- information on log collecting can be found in Using the Log Collector in the
- Manual.
-
- The following is a small list of possible Enea Edge problems, and
- their solutions. If you encounter other issues or can't get Enea Edge to
- work successfully after consulting the information below, please use the
- Enea Support Team Form, available in the
- Manual
- downloaded with your release.
-
-
- Troubleshooting and Recovery
-
-
-
-
-
-
- Enea Edge Problem
-
- Solution
-
-
-
-
-
- A uCPE device fails to connect to the Enea Edge Management
- after installation.
-
- If the uCPE device is not able to connect to the Enea Edge
- Management after an installation, the Web-installer application is
- started automatically on the uCPE device to change the configuration
- via a web browser. Please see Booting the uCPE device and adding
- it to the Map in the
- Manual.
-
-
-
- The uCPE Device cannot boot after an upgrade.
-
-
-
- Perform a hardware reboot of the uCPE Device and select
- the previous Enea Edge Runtime image from the GRUB menu. This
- action assumes physical access to the uCPE device.
-
-
-
- Reinitiate the Upgrade procedure according to the steps
- in section uCPE device upgrades in the
-
- Manual.
-
-
-
-
-
- After a failed uCPE device upgrade the previous Enea Edge
- image (from the GRUB menu) does not boot.
-
- Reinstall Enea Edge on the uCPE device and redeploy the
- initial configuration and virtualized services, by following the
- steps in Installing Enea Edge - uCPE Device
- installation in the
- Manual.
-
-
-
- The Enea Edge Management upgrade fails and a working snapshot
- is available.
-
- If a working snapshot obtained during a previous Upgrade or
- Uninstall is available
- (ucpemanager-Backup-YYYYddMMHHmm.tar.gz ):
-
-
- Cleanup the current upgrade attempt with:
-
- ./cleanup.sh /opt/ems
-
-
-
- Restore the previous installation as described in Restoring a previous
- Enea Edge Management installation in the
- Manual.
-
-
-
-
-
- The Enea Edge Management upgrade fails and no working
- snapshot is available, but a System Back-up file exists.
-
-
-
- Cleanup the current upgrade attempt with:
-
- ./cleanup.sh /opt/ems
-
-
-
- Perform an installation with the restore option of a
- previous Enea Edge Management configuration as described in
- Installation of the
- Enea Edge Management using a System Back-up in the
- Manual.
-
-
-
-
-
- The uCPE device is booted, the ssh connection is available
- but the device is not connected to the Enea Edge Management.
-
-
-
- Perform a hardware reboot on the uCPE device to
- reinitiate the connection mechanism.
-
-
-
- Use the Reconnect
- button from the Enea Edge Management's GUI.
-
-
-
- Connect to uCPE Device console and run the factory reset
- script:
-
- /usr/local/odm/bin/factory_reset.sh
-
-
-
- If the above actions do not work, reinstall and
- reconfigure the device using the steps provided in Installing Enea Edge - uCPE
- Device installation in the
- Manual.
-
-
-
-
-
- The SSH connection to the device cannot be
- established.
-
- Perform a hardware reboot on the uCPE device. If the problem
- is not fixed, reinstall and reconfigure the device using the steps
- provided in Installing Enea Edge - uCPE Device
- installation in the
- Manual.
-
-
-
- The VNF Service is not working as expected after
- reconfiguration (e.g. a VNF chain is malfunctioning).
-
-
-
- Undo all flows and/or configuration changes in order to
- move the system to a previously working configuration.
-
-
-
- Reboot the device by accessing Operations and then selecting Reboot from within the Enea Edge
- Management.
-
-
-
- If the above actions do not work, redeploy all services.
- This is done by cleaning up the existing configuration by
- accessing Operations , then
- selecting Factory Reset for a
- specific device and redeploying the VNF services.
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml b/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
deleted file mode 100644
index 641775d..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/upgrade_ena.xml
+++ /dev/null
@@ -1,588 +0,0 @@
-
-
- Upgrading Enea Edge
-
- Enea provides regular releases that will require the upgrading of Enea
- Edge components. The Enea Edge Management must be upgraded first, followed
- by upgrading the Enea Edge Runtime on the uCPE devices.
-
-
- Upgrading the Enea Edge Management
-
-
- It is recommended to create a system backup by accessing System and selecting System
- Backup from the Enea Edge Management GUI, for recovery in
- case of an upgrade failure.
-
-
-
-
- Extract the
- Enea_Edge_Management_<version>-build<build_number>.tar.gz
- folder.
-
- The directory in which the archive has been unpacked will be
- denoted as <uCPEM-installdir> .
-
-
-
- Enter <uCPEM-installdir>/dist .
-
-
-
- Run the following command with the root account and change
- /opt/ems to the correct location of the Enea Edge
- Management installation:
-
- ./upgrade.sh /opt/ems \
-Enea_NFV_Access_uCPEManager_<version>-build<build_number>.tar.gz
-
-
-
- Running this command will:
-
-
-
- Stop the currently running ucpemanager
- service.
-
-
-
- Create a compressed file of the ucpemanager
- application folder
- (ucpemanager-Back-up-YYYYddMMHHmm.tar.gz ), which
- contains a snapshot of the existing installation in the
- <uCPEM-installdir>/dist directory.
-
-
- The snapshot file created during the upgrade can be used for
- restoring the Enea Edge Management.
-
-
-
-
- Extract the application files from the specified compressed
- install kit.
-
-
-
- Start the ucpemanager service.
-
-
-
- Fresh Installation of the Enea Edge Management
- in the
- Manual contains information about the input required to be entered during
- the execution of the upgrade script.
-
- For an example on how to upgrade an Enea Edge Management installation
- in a High Availability setup, consult Upgrading a High Availability Deployment in the
-
- Manual.
-
-
- Restoring a previous Enea Edge Management Installation
-
- How to restore a previous Enea Edge
- Management installation
-
-
-
- Extract
- Enea_Edge_Management_<version>-build<build_number>.tar.gz
-
-
-
- The directory in which the archive has been unpacked will be
- denoted as <uCPEM-installdir> .
-
-
-
- Copy the snapshot file
- (ucpemanager-Backup-YYYYddMMHHmm.tar.gz )
- created during a previous Enea Edge Management Upgrade or Enea Edge
- Management Uninstall Operation into the
- <uCPEM-installdir> directory.
-
-
-
- Enter <uCPEM-installdir>/dist .
-
-
-
- Run the following command with the root user and change
- /opt/ems to the correct location of the Enea Edge
- Management installation:
-
- ./restore.sh /opt/ems ucpemanager-Backup-YYYYddMMHHmm.tar.gz
-
-
-
- Running this command will:
-
-
-
- Remove any vestiges of the existing
- ucpemanager service, if they exist.
-
-
-
- Reinstall the Enea Edge Management application on the
- specified target location, restoring the data in the database and
- files in the process.
-
-
-
- The ucpemanager service will then start with
- the older version now running on the system.
-
-
-
- Uninstalling an existing Enea Edge Management
- Installation
-
- How to uninstall an existing Enea Edge
- Management installation
-
-
-
- Navigate to the folder where the Enea Edge Management is
- installed: <uCPEM-installdir> .
-
-
-
- Run the following command with the root user and change
- /opt/ems to the correct location of the Enea Edge
- Management installation:
-
- ./uninstall.sh /opt/ems
-
-
-
- Running this command will:
-
-
-
- Stop the currently running ucpemanager
- service.
-
-
-
- Create a compressed file of the ucpemanager
- application folder:
- ucpemanager-Back-up-YYYYddMMHHmm.tar.gz , which
- contains a snapshot of the existing installation and functions as a
- restore point.
-
-
- The snapshot file created during the uninstall can be used
- for restoring Enea Edge Management.
-
-
-
-
- Uninstall the ucpemanager service, so that
- it will not start up on reboot.
-
-
-
- Uninstall the database service.
-
-
-
- Completely remove the contents of the application and database
- folders.
-
-
-
- After these steps, the Enea Edge Management is completely removed
- from the system.
-
-
-
-
- uCPE device Upgrades
-
- A uCPE device can be upgraded using the Enea Edge Management
- GUI.
-
-
- The uCPE device Upgrade Process
-
- The Device Upgrade/Install option performs the following
- operations to the uCPE device:
-
-
-
- Prepare for upgrade. This
- stage prepares the files needed for an upgrade.
-
-
-
- Install file on device. This
- stage copies the file to the uCPE device.
-
-
-
- Upgrade Device. This stage
- upgrades the uCPE device to a newer version.
-
-
-
-
- Upgrading from Enea NFV Access 2.3.0 is not possible when using
- the Enea uCPE Manager in HTTPS mode. Either switch to HTTP by accessing
- System , Configuration , Web
- Access and checking the Enable
- HTTP box, or installing it manually.
-
-
-
-
- Managing the uCPE device Upgrade
-
- Before an installation or upgrade can be completed, certain
- configuration data must be set. Files also need to be uploaded to the
- Device Upgrade image repository in order to be uploaded to the
- device.
-
- Launch the Device Upgrade management console by selecting
- Devices and then the Upgrade button from the top tool-bar. The console
- will contain the following tabs:
-
-
-
- Image Library . To add/delete
- an image.
-
-
-
- Upgrade Operations . See
- upgrades that are currently running, cancel any upgrades in
- progress, or start a uCPE device upgrade.
-
-
-
- Configuration . Upgrade
- configuration parameters.
-
-
-
-
- The uCPE Device upgrade is done with image files of the type
- rootfs.ostree.tar.bz2 , which are available in the
- Enea_Edge_Runtime_<processor>_<version>-build<build_number>.tar.gz
- file you downloaded with your release.
-
-
-
- Image Library
-
- Adding an image to the image
- repository/library
-
- Select Devices and then
- the Upgrade button.
-
-
-
- Select Add from the
- Image Library tab to add a new
- image file.
-
-
-
- Select Choose File to
- provide the path to the image file (must be of type
- rootfs.os-tree.tar.bz2 ).
-
-
-
- Select the target hardware platform corresponding to the
- image being uploaded (xeon-d or
- atom-c3000 ).
-
-
-
- Click Send to upload the
- image to the image repository.
-
-
-
- Deleting an image from the image
- repository
-
-
-
- Select Devices and then the
- Upgrade button.
-
-
-
- Select the image you want to delete from the Image Library tab and then click Delete .
-
-
-
-
-
- Upgrade Operations
-
- The Upgrade Operations tab
- allows a user to manage uCPE device upgrades in the system. It allows
- the user to see all the upgrades that are currently in progress, as
- well as listing the completed ones. If an upgrade succeeds or fails,
- then a row will be added to the completed upgrades table. If one
- fails, the failure message will be visible in the table.
-
-
- The list of completed upgrade tasks resides in the cache
- memory and will not persist across reboots of the server.
-
-
- How to Install/Upgrade a device
- immediately or schedule the process for later
-
- Select Devices and then
- the Upgrade button.
-
-
-
- Select Upgrade Devices
- from the Upgrade Operations
- tab. This will launch a Multi Device Install
- Image screen that will allow the user to install and
- upgrade more than one uCPE device at a time or upgrade
- later.
-
-
-
- The configurable parameters are:
-
-
-
- Scheduling . Click this checkbox if the
- upgrade will be done later. Schedule the day, hour and minute for
- when to run the upgrade.
-
-
- The hour represents the local Enea Edge Management server
- hour.
-
-
-
-
- Description . An optional description of
- the operation. It is recommended to add a description so that
- different upgrades happening simultaneously can be
- distinguished.
-
-
-
- Image File . Click on Choose Image File to select the image
- file.
-
-
-
- Devices . The list of uCPE Devices that
- can accept an image file is populated when the image file is
- chosen.
-
- Mark the uCPE devices that you wish to upgrade and press the
- > button to move the uCPE
- devices to the right side of the selector. Those chosen form the
- list of uCPE devices that will be upgraded.
-
-
-
- Upgrade Operation . The available options
- are:
-
-
-
- Install and Activate . This will do an
- image installation as well as an upgrade.
-
-
-
- Install Only . This will do an image
- installation only. The image is copied to the uCPE device, and
- an upgrade will be done later either at a scheduled time or
- when the option Activate Only is
- selected.
-
-
-
- Activate Only . This will activate an
- already installed image on the uCPE device.
-
-
-
-
-
- To start the upgrade, click ok .
-
-
-
-
- When the uCPE device activates the upgrade, it will be
- rebooted automatically.
-
-
-
-
- Releases installed on a uCPE device
-
- The installed releases on a uCPE device can be viewed by
- selecting the uCPE device first, then from the top toolbar selecting
- Configuration and then the Upgrade button.
-
- The installed releases on the uCPE device, the release status,
- release state, commit-id and release version will
- be listed in a table.
-
-
-
- uCPE device Upgrade Status
-
- The status of the installation and upgrade can be viewed in the
- Upgrade Operations tab. Ongoing or
- scheduled upgrade operations can be viewed or cancelled.
-
- To view the status of an installation or
- upgrade operations
-
-
-
- Select Devices and then the
- Upgrade button.
-
-
-
- Select Upgrade Operations .
- The ongoing operations are listed at the top and a history of
- failed or successful operations are listed at the bottom.
-
-
-
- Select an Active or
- Completed Upgrade Operation and
- then the Device Status button to
- see detailed information regarding the upgrade operation,
- including the uCPE devices involved and information per uCPE
- device.
-
-
-
- To cancel an upgrade
- operation
-
-
-
- Select Devices , then the
- Upgrade button and choose
- Upgrade Operations .
-
-
-
- Select an operation from the list and choose Cancel Upgrade and Confirm . The operation will then be deleted
- from the list.
-
-
-
-
-
- Configuration
-
-
- The default values present in the configuration of each uCPE
- device are recommended for use. Modifying them is for an Advanced User only.
-
-
- How to Configure the uCPE device
- Upgrade
-
- Select Devices and then
- the Upgrade button.
-
-
-
- Select Configuration .
-
-
-
- The configurable parameters are:
-
-
-
- deviceImageDir . This is the disk
- location of the device image repository.
-
-
- If no absolute path name is given it is assumed to
- be relative to the installation directory.
-
-
-
-
- maxThreads . This number dictates
- how many upgrades the system can manage at one time, either
- individually launched or launched from the multi-device
- screens. This value defaults to 20, which means that 20 uCPE
- devices may be updated at one time.
-
-
-
- KeepAlive . This number represents
- the number of seconds that a thread will be kept alive
- before it is collected. If multiple installations are
- occurring, this will keep the thread alive for X seconds
- before it is released. If not released, it can be used by
- the internal scheduling system as soon as it has completed
- an upgrade.
-
-
-
-
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml b/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
deleted file mode 100644
index bd2fb0b..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/vnf_mg.xml
+++ /dev/null
@@ -1,477 +0,0 @@
-
-
- VNF Management
-
- The Enea Edge Management is responsible for onboarding, configuring
- (e.g. CloudInit) and ensuring life cycle management of VNFs that are
- instantiated and run on the various uCPE devices.
-
-
- Onboarding a VNF
-
- The onboarding of a VNF means adding it to the Enea Edge Management
- VNF Catalogue and preparing it for instantiation (deployment on connected
- uCPE devices). This is accomplished using the Enea Edge Management
- Onboarding graphical user interface.
-
- Typically, the Getting Started Guide of a VNF, provided by the VNF
- vendor, contains all necessary information needed to onboard a VNF.
-
-
- Retrieving Artifacts
-
- The user must first retrieve the necessary artifacts from the VNF
- vendor:
-
-
-
- Download the VNF from the commercial vendor.
-
-
-
- Procure any VNF-specific files from the VNF vendor, e.g.
- license file.
-
-
- There are no standard ways of managing VNF licenses,
- therefore no general guidelines can be provided. One example of
- license handling that can be employed in the Enea Edge Management
- is the adding of a license during the Cloud-Init setup.
-
-
-
-
- Optionally, get access to the VNF specific VNF Manager for day
- 1 and 2 configuration (in cloud or for local deployment).
-
-
-
- Procure the Getting Started Guide from the VNF vendor,
- preferably for KVM deployment for VNF specific configuration
- information.
-
-
-
-
-
- Preparation
-
- Once all needed downloadables, documentation and more have been
- attained, preparation for onboarding must be completed:
-
-
-
- Determine the use-case and performance requirements of the VNF
- you wish to deploy:
-
-
-
- This decides what resources the VNF is configured for,
- along with networking and day zero configurations.
-
-
- Generally, the Getting Started Guide for the VNF
- provides guidelines for resource allocation, but since
- performance is dependent on hardware capacity, the right
- resource allocation for deployment is determined through
- benchmarking.
-
-
-
-
- Determine the amount of hardware resources needed for the
- VNF (RAM, number of CPUs and storage size).
-
-
-
- Determine how many Virtual Network Interfaces the VNF will
- use.
-
-
-
-
-
- Determine the Day-0 configuration method from the VNF Getting
- Started guidelines.
-
-
- For many VNFs, day zero configuration can be skipped in
- early onboarding efforts when automation is not of
- importance.
-
-
-
-
- Determine any requirements needed by the Cloud-Init file
- structure and the content needed when this structure is used.
-
-
-
-
-
- Onboarding into the Enea Edge Management
-
- How to onboard a VNF into the Enea Edge
- Management
-
-
-
- Select from the top toolbar VNF and then Descriptors .
-
-
-
- Click the On-board
- button.
-
-
-
- This window contains data fields where both necessary and optional
- information about the VNF can be supplied. After doing so, press the
- Onboard button, the Enea Edge Management will create the VNF descriptor
- and add it to its VNF Catalog.
-
-
- Onboard a VNF
-
-
-
-
-
-
-
-
- Main fields
-
-
-
- VM Image File . This is the
- Virtual Machine image file for the VNF. Typically, it is a QCOW
- image. Press Choose File and select
- the image you wish to upload.
-
-
-
- Image Format . Select the
- format which matches the image file format.
-
-
-
- VNF Type Name . This is the
- name that will be used to identify this VNF. It will be shown in the
- VNFs list.
-
-
-
- Description . This field
- contains any description provided and is only displayed in the GUI
- tables in the Enea Edge Management.
-
-
-
- Version . This is the version
- of the current VNF that you are hosting. It's used to distinguish
- this VNF from other versions of the same type.
-
-
-
- Memory in MB . This is the
- amount of memory (in megabytes) that will be provided to this type
- of VNF when it is instantiated. To determine the value for this
- field, consult the VNF vendor.
-
-
-
- Num of CPUs . The number of
- CPUs that will be dedicated to an instance of this VNF when created.
- To determine the value for this field, consult the VNF
- vendor.
-
-
-
- Storage in GB . How much disk
- space to provide an instance of this VNF. To determine the value for
- this field, consult the VNF vendor.
-
-
-
- Interfaces Tab
-
- Click on the Interfaces tab to
- show the Interfaces table.
-
- This table will contain the interfaces required by this VNF to be
- configured, when creating an instance. Consult the VNF vendor to
- determine which and how many are required. Each interface requires a
- name, and optionally a description, used only by the Enea Edge
- Management.
-
-
- CAUTION: The user MUST conserve the same order for the virtual
- interfaces during both onboarding and instantiation phases.
-
-
- Cloud Init Tab
-
- Click the Cloud Init tab to
- provide the Cloud-Init configuration. There are three fields that need
- to be populated:
-
-
-
- Cloud-Init Datasource
-
- To onboard a VNF you must specify the Cloud-Init
- Datasource that the VNF uses. This information is procured
- from the VNF Vendor. Choose one of the following methods to specify
- the datasource:
-
-
-
- None . If there is no
- datasource.
-
-
-
- ConfigDrive . This method
- allows you to provide any number of content-data files
- containing Cloud-Init data.
-
-
-
- NoCloud . This is a
- simpler method that uses only one cloud init file
- (User-Data).
-
-
-
- ISO . Pre-cooked
- cloud-init image. This image must be created by the user
- according to VNF requirements.
-
-
-
-
-
- Cloud-Init Disk Type
-
- The Cloud-Init Disk Type field must be set
- to either Disk , or CD-ROM ,
- depending on what the VNF requires. You can get this information
- from the VNF Vendor.
-
-
-
- Content Files Table
-
- The Content Files Table is ONLY used if
- ConfigDrive is chosen as the Cloud-Init
- Datasource. For each content file added, a Path
- must be provided. When the Enea Edge Management is used to create an
- instance for multiple VNFs, the user will be prompted to provide a
- data file for each entry in this table. Each type of VNF will
- require different cloud-init files, e.g.: a license file. The data
- files will be added to the cloud-init image that the user provides
- at the instantiation of the VNF. If the cloud-init image is not
- provided, no Cloud-Init Data Source will be created for that VNF and
- there will be no warning.
-
-
-
- Consult with the VNF vendor to determine what is required for the
- VNF you are onboarding.
-
- Properties Tab
-
- In this table, you can enter values for properties that will be
- used during instantiation of the VNF. The values will augment the
- default values in the domain.xml file used by
- libvirt/virsh (running in Enea Edge) when creating an
- instance of the VNF. Consult with the VNF Vendor or ENEA support for
- values needed by specific VNFs.
-
- Property Values
-
-
-
- numHugePages defines the number of huge
- memory pages the VNF uses (for DPDK).
-
-
-
- vnfMgmtIpAddress : the IP address of the
- VNF's management interface, connected to a
- vnfMgmt bridge (e.g. 10.0.0.2).
-
-
-
- internalMgmtPort : the VNF's TCP/UDP port
- used for management (e.g. 443).
-
-
-
- externalMgmtPort : the Management port used
- for external access (e.g. 60001).
-
-
-
-
- The last three properties are useful in conjuction with the
- vnfMgmt bridge type. They allow the user to map the
- internal VNF management port to an external port, useful for VNF
- configuration from WAN.
-
- In the previous example, the internal TCP port 443 (HTTPS) was
- mapped to the external port 60001, which allows the user to access the
- VNF management port from a web browser e.g.
- https://<WAN_IP>:60001 .
-
-
-
-
-
- Instantiating a VNF
-
- When a VNF is onboarded and available in the VNF catalog, it can be
- instantiated on connected uCPE devices. The configurations provided when
- the VNF is onboarded, serve as a template for instantiation. Before
- instantiating any VNF, please make sure the available storage space on the
- uCPE device is big enough to accommodate the VNF you need to
- instantiate.
-
- Follow the instructions below to instantiate a VNF:
-
-
-
- Select from the top toolbar VNF
- and choose Instances .
-
-
-
- Click the Add button.
-
-
-
- Fill out the following mandatory fields:
-
-
-
- Name: a descriptive name.
-
-
-
- VNF Type: a list of onboarded VNFs.
-
-
-
- uCPE Device: the uCPE device to instantiate the VNF
- on.
-
-
-
- Networking Configuration:
-
-
-
- Connect each configured NIC with a bridge, SR-IOV or PCI
- Passthrough.
-
-
-
- Set up each NIC with a driver method.
-
-
-
-
- All configured NICs must be set up before instantiating a
- VNF. Failure to do so will end in a failed instantiation.
-
-
-
-
-
-
- Add VNF-specific configuration data by uploading a Cloud-Init
- file (when the Cloud-Init is used).
-
-
-
- Add any VNF-specific files (e.g license files).
-
-
-
- Hit the Create button to deploy
- the VNF and run it on the specified uCPE device.
-
-
-
- Selecting the VNF menu then
- choosing Events will show that the VNF
- was created and a connection was established.
-
-
-
- Accessing the VNF console
-
- Once the VNF is deployed, the VNF console can be entered using SSH
- and virsh commands. The VNF Console is a typical starting point for
- determining a successful deployment and configuring a VNF beyond Day
- Zero.
-
-
-
- SSH to the uCPE device from the Enea Edge Management (Access the
- Device menu and select SSH ) using:
-
-
-
- For normal connections: the Username
- (default: root), the Password (default: no
- password), the Port (default: 22) and the
- Reverse ssh checkbox: unchecked.
-
-
-
- For reverse ssh connections (ssh to a uCPE device behind
- NAT): the Username (default: root) and the
- Reverse ssh checkbox checked. The port will be
- automatically chosen by the Enea Edge Management in the range
- defined in the SSH configuration
- panel, available when accessing System , then Configuration and choosing Reverse SSH . By default, the start port
- will be 7000 and the maximum number of ports
- allocated to all devices is 10. Only one port per device is
- allowed.
-
- When the SSH window is closed, the tunnel configuration is
- deleted on the uCPE device and the tunnel is destroyed, so that
- the port can be reused to establish a new tunnel when
- needed.
-
-
-
-
-
- In SSH:
-
-
-
- Use the virsh list command to list all
- running VNFs and to determine the VNF's instance number.
-
-
-
- Use the virsh console <instance
- number> command to enter the VNF-specific
- console.
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-getting-started/swcomp.mk b/doc/book-enea-nfv-access-getting-started/swcomp.mk
deleted file mode 100755
index 52b433e..0000000
--- a/doc/book-enea-nfv-access-getting-started/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-getting-started
-BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Getting Started"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/README b/doc/book-enea-nfv-access-platform-open-source/doc/README
deleted file mode 100644
index 607ce67..0000000
--- a/doc/book-enea-nfv-access-platform-open-source/doc/README
+++ /dev/null
@@ -1,4 +0,0 @@
-The licenses.xml in the git repository of Enea NFV Access Runtime Platform Open Source Report
-is the frozen version belonging to the last official release of Enea NFV Access.
-The contents must be generated from the release script to obtain the latest
-lists of packages and licenses.
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/about.xml b/doc/book-enea-nfv-access-platform-open-source/doc/about.xml
deleted file mode 100644
index 2a8bf01..0000000
--- a/doc/book-enea-nfv-access-platform-open-source/doc/about.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
- About this Report
-
- This document contains the open source and license information pertaining to packages provided with this release of the Enea Edge Runtime and the Installer.
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/book.xml b/doc/book-enea-nfv-access-platform-open-source/doc/book.xml
deleted file mode 100644
index 1150b11..0000000
--- a/doc/book-enea-nfv-access-platform-open-source/doc/book.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-]>
-
- Enea Edge Runtime Open Source Report
- Release Version
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
deleted file mode 100644
index 6f9aa06..0000000
--- a/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
+++ /dev/null
@@ -1,9936 +0,0 @@
-
-
-
- Packages and Licenses
-
-
- Packages
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Package Name
- Version
- Description
- License
-
-
-
-
-
-
- 4g-sierra
- 1.0
- Scripts to setup 4G modems from Sierra
- Enea
-
-
- acl
- 2.2.52
- Utilities for managing POSIX Access Control Lists.
- LGPL-2.1, GPL-2.0
-
-
- acpid
- 2.0.28
- A daemon for delivering ACPI events.
- GPL-2.0
-
-
- alsa-lib
- 1.1.4.1
- ALSA sound library.
- LGPL-2.1, GPL-2.0
-
-
- ant
- 1.8.1
- Another Neat Tool - build system for Java
- Apache-2.0
-
-
- antlr
- 2.7.7
- Framework for constructing recognizers interpreters compilers and translators
- PD
-
-
- apache2
- 2.4.27
- The Apache HTTP Server is a powerful efficient and extensible web server.
- Apache-2.0
-
-
- apr-util
- 1.6.0
- Apache Portable Runtime (APR) companion library.
- Apache-2.0
-
-
- apr
- 1.6.2
- Apache Portable Runtime (APR) library.
- Apache-2.0
-
-
- apt
- 1.2.24
- Advanced front-end for dpkg.
- GPL-2.0
-
-
- attr
- 2.4.47
- Utilities for manipulating filesystem extended attributes.
- LGPL-2.1, GPL-2.0
-
-
- aufs-util
- 4.4
- Tools for managing AUFS mounts.
- GPL-2.0
-
-
- augeas
- 1.5.0
- Augeas configuration API.
- LGPL-2.1
-
-
- autoconf-archive
- 2016.09.16
- a collection of freely re-usable Autoconf macros.
- GPL-3.0-with-autoconf-exception
-
-
- autoconf
- 2.69
- Autoconf is an extensible package of M4 macros that produce shell scripts to automatically configure software source code packages. Autoconf creates a configuration script for a package from a template file that lists the operating system features that the package can use in the form of M4 macro calls.
- GPL-2.0, GPL-3.0
-
-
- automake
- 1.15.1
- Automake is a tool for automatically generating `Makefile.in' files compliant with the GNU Coding Standards. Automake requires the use of Autoconf.
- GPL-2.0
-
-
- avahi
- 0.6.32
- "Avahi is a fully LGPL framework for Multicast DNS Service Discovery. It allows programs to publish and discover services and hosts running on a local network with no specific configuration. This tool implements IPv4LL ""Dynamic Configuration of IPv4 Link-Local Addresses"" (IETF RFC3927) a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server."
- GPL-2.0, LGPL-2.1
-
-
- avalon-framework-api
- 4.3
- Common way for components to be created initialized configured started. (API-only)
- Apache-2.0
-
-
- base-files
- 3.0.14
- The base-files package creates the basic system directory structure and provides a small set of key configuration files for the system.
- GPL-2.0
-
-
- base-passwd
- 3.5.29
- The master copies of the user database files (/etc/passwd and /etc/group). The update-passwd tool is also provided to keep the system databases synchronized with these master files.
- GPL-2.0
-
-
- bash-completion
- 2.7
- Programmable Completion for Bash 4.
- GPL-2.0
-
-
- bash
- 4.4
- An sh-compatible command language interpreter.
- GPL-3.0
-
-
- bc
- 1.06
- Arbitrary precision calculator language.
- GPL-2.0, LGPL-2.1
-
-
- bcel
- 5.2
- Java Bytecode manipulation library
- Apache-2.0
-
-
- bind
- 9.10.5-P3
- ISC Internet Domain Name Server.
- ISC, BSD
-
-
- binutils-cross-x86_64
- 2.29.1
- The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
- GPL-3.0
-
-
- binutils
- 2.29.1
- The GNU Binutils are a collection of binary tools. The main ones are ld (GNU Linker) and as (GNU Assembler). This package also includes addition tools such as addr2line (Converts addresses into filenames and line numbers) ar (utility for creating modifying and extracting archives) nm (list symbols in object files) objcopy (copy and translate object files) objdump (Display object information) and other tools and related libraries.
- GPL-3.0
-
-
- bison
- 3.0.4
- Bison is a general-purpose parser generator that converts an annotated context-free grammar into an LALR(1) or GLR parser for that grammar. Bison is upward compatible with Yacc: all properly-written Yacc grammars ought to work with Bison with no change. Anyone familiar with Yacc should be able to use Bison with little trouble.
- GPL-3.0
-
-
- bjam
- 1.64.0
- Portable Boost.Jam build tool for boost.
- BSL-1.0, MIT, Python-2.0
-
-
- bmap-tools
- 3.4
- "Bmap-tools - tools to generate block map (AKA bmap) and flash images using bmap. Bmaptool is a generic tool for creating the block map (bmap) for a file and copying files using the block map. The idea is that large file containing unused blocks like raw system image files can be copied or flashed a lot faster with bmaptool than with traditional tools like ""dd"" or ""cp""."
- GPL-2.0
-
-
- boost
- 1.64.0
- Free peer-reviewed portable C++ source libraries.
- BSL-1.0, MIT, Python-2.0
-
-
- bridge-utils
- 1.5
- Tools for ethernet bridging.
- GPL-2.0
-
-
- bsf
- 2.4.0
- Bean Scripting Framework package
- Apache-2.0
-
-
- btrfs-tools
- 4.12
- Btrfs is a new copy on write filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance repair and easy administration. This package contains utilities (mkfs fsck btrfsctl) used to work with btrfs and an utility (btrfs-convert) to make a btrfs filesystem from an ext3.
- GPL-2.0
-
-
- busybox
- 1.24.1
- BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for most of the utilities you usually find in GNU fileutils shellutils etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete POSIX environment for any small or embedded system.
- GPL-2.0, BSD-4-Clause
-
-
- bzip2
- 1.0.6
- bzip2 compresses files using the Burrows-Wheeler block-sorting text compression algorithm and Huffman coding. Compression is generally considerably better than that achieved by more conventional LZ77/LZ78-based compressors and approaches the performance of the PPM family of statistical compressors.
- BSD-4-Clause
-
-
- ca-certificates
- 20170717
- This package includes PEM files of CA certificates to allow SSL-based applications to check for the authenticity of SSL connections. This derived from Debian's CA Certificates.
- GPL-2.0, MPL-2.0
-
-
- cacao-initial
- 0.98
- CacaoVM for use as OpenEmbedded's Java VM
- GPL-2.0
-
-
- cairo
- 1.14.10
- Cairo is a multi-platform library providing anti-aliased vector-based rendering for multiple target backends. Paths consist of line segments and cubic splines and can be rendered at any width with various join and cap styles. All colors may be specified with optional translucence (opacity/alpha) and combined using the extended Porter/Duff compositing algebra as found in the X Render Extension.
- MPL-1.0, LGPL-2.1, GPL-3.0
-
-
- cantarell-fonts
- 0.0.24
- The Cantarell font typeface is designed as a contemporary Humanist sans serif and was developed for on-screen reading; in particular reading web pages on an HTC Dream mobile phone.
- OFL-1.1
-
-
- cdrkit
- 1.1.11
- CD/DVD command line tools.
- GPL-2.0
-
-
- cdrtools
- 3.01a31
- A set of tools for CD recording including cdrecord.
- GPL-2.0, CDDL-1.0, LGPL-2.1
-
-
- classpath-initial
- 0.93
- Java1.4-compatible GNU Classpath variant that is used as bootclasspath for jikes-native.
- GPL-2.0, SAX-PD
-
-
- classpath
- 0.99
- GNU Classpath standard Java libraries - For native Java-dependent programs
- GPL-2.0, SAX-PD
-
-
- cloud-init
- 0.7.6
- Init scripts for use on cloud images
- GPL-3.0
-
-
- cmake
- 3.8.2
- Cross-platform open-source make system.
- BSD
-
-
- collectd
- 5.12.0
- collectd is a daemon which collects system performance statistics periodically and provides mechanisms to store the values in a variety of ways for example in RRD files.
- GPL-2.0, MIT
-
-
- commons-logging
- 1.1.1
- Java Internet protocol suite library
- Apache-2.0
-
-
- commons-net
- 1.4.1
- Java Internet protocol suite library
- Apache-2.0
-
-
- compose-file
- 3.0
- Parser for the Compose file format (version 3)
- Apache-2.0
-
-
- containerd-docker
- v0.2.x
- containerd is a daemon to control runC built for performance and density. containerd leverages runC's advanced features such as seccomp and user namespace support as well as checkpoint and restore for cloning and live migration of containers.
- Apache-2.0
-
-
- core-image-minimal-initramfs
- 1.0
- Small image capable of booting a device. The kernel includes the Minimal RAM-based Initial Root Filesystem (initramfs) which finds the first 'init' program more efficiently.
- MIT
-
-
- coreutils
- 8.27
- The GNU Core Utilities provide the basic file shell and text manipulation utilities. These are the core utilities which are expected to exist on every system.
- GPL-3.0
-
-
- crda
- 3.18
- Wireless Central Regulatory Domain Agent.
- copyleft-next-0.3.0
-
-
- cross-localedef
- 2.26
- Cross locale generation tool for glibc.
- LGPL-2.1
-
-
- cryptodev-linux
- 1.9
- A /dev/crypto device driver header file.
- GPL-2.0
-
-
- cup
- 0.10k
- Lexical analyzer generator for Java
- CUP
-
-
- curl
- 7.58.0
- Command line tool and library for client-side URL transfers.
- MIT
-
-
- cwautomacros
- 20110201
- Collection of autoconf m4 macros.
- GPL-2.0
-
-
- db
- 5.3.28
- Berkeley Database v5.
- Sleepycat
-
-
- dbus-glib
- 0.108
- GLib bindings for the D-Bus message bus that integrate the D-Bus library with the GLib thread abstraction and main loop.
- AFL-2.0, GPL-2.0
-
-
- dbus-test
- 1.10.20
- D-Bus test package (for D-bus functionality testing only).
- AFL-2.0, GPL-2.0
-
-
- dbus
- 1.10.20
- "D-Bus is a message bus system a simple way for applications to talk to one another. In addition to interprocess communication D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a \""single instance\"" application or daemon and to launch applications and daemons on demand when their services are needed."
- AFL-2.0, GPL-2.0
-
-
- debianutils
- 4.8.1.1
- Miscellaneous utilities specific to Debian.
- GPL-2.0, SMAIL_GPL
-
-
- depmodwrapper
- 1.0
- Wrapper script for the Linux kernel module dependency indexer.
- MIT
-
-
- dhcp
- 4.3.6
- DHCP (Dynamic Host Configuration Protocol) is a protocol which allows individual devices on an IP network to get their own network configuration information from a server. DHCP helps make it easier to administer devices.
- ISC
-
-
- diffutils
- 3.6
- Diffutils contains the GNU diff diff3 sdiff and cmp utilities. These programs are usually used for creating patch files.
- GPL-3.0
-
-
- dmidecode
- 3.1
- DMI (Desktop Management Interface) table related utilities.
- GPL-2.0
-
-
- dnsmasq
- 2.78
- Lightweight easy to configure DNS forwarder and DHCP server.
- GPL-2.0, GPL-3.0
-
-
- docker
- 17.06.0
- Linux container runtime Docker complements kernel namespacing with a high-level API which operates at the process level. It runs unix processes with strong guarantees of isolation and repeatability across servers. . Docker is a great building block for automating distributed systems: large-scale web deployments database clusters continuous deployment systems private PaaS service-oriented architectures etc. . This package contains the daemon and client. Using docker.io is officially supported on x86_64 and arm (32-bit) hosts. Other architectures are considered experimental. . Also note that kernel version 3.10 or above is required for proper operation of the daemon process and that any lower versions may have subtle and/or glaring issues.
- Apache-2.0
-
-
- dosfstools
- 4.1
- DOS FAT Filesystem Utilities.
- GPL-3.0
-
-
- dpdk-dev-libibverbs
- 1.2.1-3.4-2.0.0.0
- libibverbs library to support Mellanox config
- GPL-2.0
-
-
- dpdk
- 18.02
- Intel(r) Data Plane Development Kit
- BSD, LGPL-2.0, GPL-2.0
-
-
- dpkg
- 1.18.24
- Package maintenance system from Debian.
- GPL-2.0
-
-
- dtc
- 1.4.4
- The Device Tree Compiler is a tool used to manipulate the Open-Firmware-like device tree used by PowerPC kernels.
- GPL-2.0, BSD
-
-
- e2fsprogs
- 1.43.5
- The Ext2 Filesystem Utilities (e2fsprogs) contain all of the standard utilities for creating fixing configuring and debugging ext2 filesystems.
- GPL-2.0, LGPL-2.0, BSD, MIT
-
-
- ebtables
- 2.0.10-4
- Utility for basic Ethernet frame filtering on a Linux bridge advanced logging MAC DNAT/SNAT and brouting.
- GPL-2.0
-
-
- ecj-bootstrap
- 1.0
- JDT Core Batch Compiler - Bootstrap variant
- MIT
-
-
- ecj-initial
- 1.0
- JDT Core Batch Compiler - Bootstrap variant
- MIT
-
-
- efibootmgr
- 0.15
- Linux user-space application to modify the EFI Boot Manager.
- GPL-2.0
-
-
- efitools
- 1.7.0
- From the EFI Tools package in the Linux user-space it's now possible to read and manipulate the UEFI signatures database via the new efi-readvar and efi-updatevar commands. Aside from needing efitools 1.4 the EFIVARFS file-system is also needed which was only introduced in the Linux 3.8 kernel.
- GPL-2.0
-
-
- efivar
- 0.31
- efivar provides a simple command line interface to the UEFI variable facility
- LGPL-2.1
-
-
- element-vcpe
- 4.1.3
- vCPE(based on Element-ODM)
- Enea, BSD, BSD-2-Clause, GPL-3.0, ISC, LGPL-2.1
-
-
- elfutils
- 0.170
- Utilities and libraries for handling compiled object files.
- GPL-3.0, Elfutils-Exception
-
-
- enea-nfv-access-vnf
- 1.0
- VNF image of the Enea Edge Runtime includes kernel rootfs and boot parameters
- MIT
-
-
- enea-nfv-access
- 1.0
- Image for the host side of the Enea Edge Runtime with ODM and NETCONF Edgelink customizations
- MIT
-
-
- ethtool
- 4.11
- A small utility for examining and tuning the settings of your ethernet-based network interfaces.
- GPL-2.0
-
-
- expat
- 2.2.3
- Expat is an XML parser library written in C. It is a stream-oriented parser in which an application registers handlers for things the parser might find in the XML document (like start tags)
- MIT
-
-
- fastjar
- 0.98
- jar replacement written in C.
- GPL-2.0
-
-
- file
- 5.31
- File attempts to classify files depending on their contents and prints a description if a match is found.
- BSD
-
-
- findutils
- 4.6.0
- The GNU Find Utilities are the basic directory searching utilities of the GNU operating system. These programs are typically used in conjunction with other programs to provide modular and powerful directory search and file locating capabilities to other commands.
- GPL-3.0
-
-
- flex
- 2.6.0
- Flex is a fast lexical analyser generator. Flex is a tool for generating programs that recognize lexical patterns in text.
- BSD
-
-
- fontconfig
- 2.12.4
- Fontconfig is a font configuration and customization library which does not depend on the X Window System. It is designed to locate fonts within the system and select them according to requirements specified by applications. Fontconfig is not a rasterization library nor does it impose a particular rasterization library on the application. The X-specific library 'Xft' uses fontconfig along with freetype to specify and rasterize fonts.
- MIT, PD
-
-
- freetype
- 2.8
- FreeType is a software font engine that is designed to be small efficient highly customizable and portable while capable of producing high-quality output (glyph images). It can be used in graphics libraries display servers font conversion tools text image generation tools and many other products as well.
- FreeType, GPL-2.0
-
-
- fuse
- 2.9.7
- FUSE (Filesystem in Userspace) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel. FUSE also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations.
- GPL-2.0, LGPL-2.0
-
-
- gawk
- 4.1.4
- The GNU version of awk a text processing utility. Awk interprets a special-purpose programming language to do quick and easy text pattern matching and reformatting jobs.
- GPL-3.0
-
-
- gcc-cross-initial-x86_64
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc-cross-x86_64
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc-runtime
- 7.3.0
- Runtime libraries from GCC.
- GPL-3.0-with-GCC-exception
-
-
- gcc-source-7.3.0
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gcc
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- gdbm
- 1.13
- Key/value database library with extensible hashing.
- GPL-3.0
-
-
- gettext-minimal
- 0.19.8.1
- Contains the m4 macros sufficient to support building autoconf/automake. This provides a significant build time speedup by the removal of gettext-native from most dependency chains (now only needed for gettext for the target).
- FSF-Unlimited
-
-
- gettext
- 0.19.8.1
- GNU gettext is a set of tools that provides a framework to help other programs produce multi-lingual messages. These tools include a set of conventions about how programs should be written to support message catalogs a directory and file naming organization for the message catalogs themselves a runtime library supporting the retrieval of translated messages and a few stand-alone programs to massage in various ways the sets of translatable and already translated strings.
- GPL-3.0, LGPL-2.1
-
-
- giflib
- 5.1.4
- shared library for GIF images.
- MIT
-
-
- git
- 2.13.3
- Distributed version control system.
- GPL-2.0
-
-
- glib-2.0
- 2.52.3
- GLib is a general-purpose utility library which provides many useful data types macros type conversions string utilities file utilities a main loop abstraction and so on.
- LGPL-2.0, BSD, PD
-
-
- glibc-locale
- 2.26
- Locale data from glibc.
- GPL-2.0, LGPL-2.1
-
-
- glibc
- 2.26
- The GNU C Library is used as the system C library in most systems with the Linux kernel.
- GPL-2.0, LGPL-2.1
-
-
- gmp
- 6.1.2
- GMP is a free library for arbitrary precision arithmetic operating on signed integers rational numbers and floating point numbers
- GPL-2.0, LGPL-3.0
-
-
- gnome-desktop-testing
- 2014.1
- Test runner for GNOME-style installed tests.
- LGPL-2.0
-
-
- gnu-config
- 20150728
- Tool that installs the GNU config.guess / config.sub into a directory tree
- GPL-3.0-with-autoconf-exception
-
-
- gnu-efi
- 3.0.6
- Libraries for producing EFI binaries.
- GPL-2.0, BSD-2-Clause
-
-
- gnujaf
- 1.1.1
- Provides a mean to type data and locate components suitable for performing various kinds of action on it.
- GPL-2.0-with-GCC-exception
-
-
- gnulib
- 2017-08-20.18
- A collection of software subroutines which are designed to be usable on many operating systems. The goal of the project is to make it easy for free software authors to make their software run on many operating systems. Since source is designed to be copied from gnulib it is not a library per-se as much as a collection of portable idioms to be used in other projects.
- LGPL-2.0
-
-
- gnumail
- 1.1.2
- GNU's free implementation of the JavaMail API specification
- GPL-2.0-with-GCC-exception
-
-
- gnutls
- 3.5.13
- GNU Transport Layer Security Library.
- GPL-3.0, LGPL-2.1
-
-
- go-capability
- 0.0
- Utilities for manipulating POSIX capabilities in Go.
- BSD-2-Clause
-
-
- go-cli
- 1.1.0
- A small package for building command line apps in Go
- MIT
-
-
- go-connections
- 0.2.1
- Utility package to work with network connections
- Apache-2.0
-
-
- go-context
- git
- A golang registry for global request variables.
- BSD-3-Clause
-
-
- go-cross-x86_64
- 1.9.4
- The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
- BSD-3-Clause
-
-
- go-dbus
- 4.0.0
- Native Go bindings for D-Bus
- BSD-2-Clause
-
-
- go-distribution
- 2.6.0
- The Docker toolset to pack ship store and deliver content
- Apache-2.0
-
-
- go-fsnotify
- 1.2.11
- A golang registry for global request variables.
- BSD-3-Clause
-
-
- go-libtrust
- 0.0
- Primitives for identity and authorization
- Apache-2.0
-
-
- go-logrus
- 0.11.0
- A golang registry for global request variables.
- MIT
-
-
- go-mux
- git
- A powerful URL router and dispatcher for golang.
- BSD-3-Clause
-
-
- go-patricia
- 2.2.6
- A generic patricia trie (also called radix tree) implemented in Go (Golang)
- MIT
-
-
- go-pty
- git
- PTY interface for Go
- MIT
-
-
- go-systemd
- 4
- Go bindings to systemd socket activation journal D-Bus and unit files
- Apache-2.0
-
-
- go
- 1.9.4
- The Go programming language is an open source project to make programmers more productive. Go is expressive concise clean and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast statically typed compiled language that feels like a dynamically typed interpreted language.
- BSD-3-Clause
-
-
- gobject-introspection
- 1.52.1
- Middleware layer between GObject-using C libraries and language bindings.
- LGPL-2.0, GPL-2.0
-
-
- gotty
- 1.0
- Run a terminal application as a web service
- MIT
-
-
- gperf
- 3.1
- GNU gperf is a perfect hash function generator
- GPL-3.0
-
-
- gpgme
- 1.9.0
- GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a High-Level Crypto API for encryption decryption signing signature verification and key management
- GPL-2.0, LGPL-2.1
-
-
- gptfdisk
- 1.0.3
- GPT fdisk is a disk partitioning tool loosely modeled on Linux fdisk but used for modifying GUID Partition Table (GPT) disks. The related FixParts utility fixes some common problems on Master Boot Record (MBR) disks.
- GPL-2.0
-
-
- grep
- 3.1
- GNU grep utility.
- GPL-3.0
-
-
- groff
- 1.22.3
- The groff (GNU troff) software is a typesetting package which reads plain text mixed with formatting commands and produces formatted output.
- GPL-3.0
-
-
- grpc-go
- 1.4.0
- The Go language implementation of gRPC. HTTP/2 based RPC
- BSD
-
-
- grub-disable-fallback
- 1.0
- Enea service to disable grub fallback when boot is successful
- Enea
-
-
- grub-efi
- 2.02
- GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
- GPL-3.0
-
-
- grub
- 2.02
- GRUB2 is the next generaion of a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel it implements the Multiboot standard which allows for flexible loading of multiple boot images.
- GPL-3.0
-
-
- gtk-doc
- 1.25
- Gtk-doc is a set of scripts that extract specially formatted comments from glib-based software and produce a set of html documentation files from them
- GPL-2.0
-
-
- gzip
- 1.8
- GNU Gzip is a popular data compression program originally written by Jean-loup Gailly for the GNU project. Mark Adler wrote the decompression part
- GPL-3.0
-
-
- harfbuzz
- 1.4.8
- HarfBuzz is an OpenType text shaping engine.
- MIT
-
-
- haveged
- 1.9.1
- The haveged project is an attempt to provide an easy-to-use unpredictable random number generator based upon an adaptation of the HAVEGE algorithm. Haveged was created to remedy low-entropy conditions in the Linux random device that can occur under some workloads especially on headless servers.
- GPL-3.0
-
-
- help2man
- 1.47.4
- Program for creating simple man pages.
- GPL-3.0
-
-
- hostapd
- 2.9
- User space daemon for extended IEEE 802.11 management.
- BSD-3-Clause
-
-
- htop
- 1.0.3
- htop process monitor.
- GPL-2.0
-
-
- hugepage-reservation
- 1.0
- Reserve hugepages on system startup.
- Enea
-
-
- icedtea7
- 2.1.3
- Harness to build the source code from OpenJDK using Free Software build tools
- GPL-2.0-with-classpath-exception
-
-
- icu
- 59.1
- The International Component for Unicode (ICU) is a mature portable set of C/C++ and Java libraries for Unicode support software internationalization (I18N) and globalization (G11N) giving applications the same results on all platforms.
- ICU
-
-
- inetlib
- 1.1.1
- GNU Classpath inetlib is an extension library to provide extra network protocol support for GNU Classpath and ClasspathX project but it can also used standalone to add http imap pop3 and smtp client support applications.
- GPL-2.0-with-GCC-exception
-
-
- initramfs-framework
- 1.0
- Modular initramfs system.
- MIT
-
-
- initramfs-module-install-efi
- 1.0
- initramfs-framework module for EFI installation option.
- MIT
-
-
- initramfs-module-install
- 1.0
- initramfs-framework module for installation option.
- MIT
-
-
- initramfs-module-setup-live
- 1.0
- initramfs-framework module for live booting.
- MIT
-
-
- initramfs-ostree-image
- 1.0
- OSTree initramfs image
- MIT
-
-
- inputproto
- 2.3.2
- This package provides the wire protocol for the X Input extension. The extension supports input devices other then the core X keyboard and pointer.
- MIT
-
-
- intltool
- 0.51.0
- Utility scripts for internationalizing XML.
- GPL-2.0
-
-
- iperf3
- 3.2
- iperf is a tool for active measurements of the maximum achievable bandwidth on IP networks. It supports tuning of various parameters related to timing protocols and buffers. For each test it reports the bandwidth loss and other parameters.
- BSD
-
-
- iproute2
- 4.11.0
- Iproute2 is a collection of utilities for controlling TCP / IP networking and traffic control in Linux. Of the utilities ip and tc are the most important. ip controls IPv4 and IPv6 configuration and tc stands for traffic control.
- GPL-2.0
-
-
- iptables
- 1.6.1
- iptables is the userspace command line program used to configure and control network packet filtering code in Linux.
- GPL-2.0
-
-
- iw
- 4.9
- iw is a new nl80211 based CLI configuration utility for wireless devices. It supports almost all new drivers that have been added to the kernel recently.
- BSD
-
-
- ixgbe
- 5.10.2
- The ixgbe driver supports 82598- and 82599-based PCI Express* 10 Gigabit Network Connections.
- GPL-2.0
-
-
- ixgbevf
- 4.10.2
- This virtual function driver supports kernel versions 2.6.x and newer This driver supports 82599 X540 X550 and X552-based virtual function devices that can only be activated on kernels that support SR-IOV. SR-IOV requires the correct platform and OS support. The guest OS loading this driver must support MSI-X interrupts.
- GPL-2.0
-
-
- jacl
- 1.4.1
- Tcl interpreter for Java
- UCB, SUN, AMD, CDS
-
-
- jamvm
- 2.0.0-devel
- A compact Java Virtual Machine which conforms to the JVM specification version 2.
- GPL-2.0
-
-
- jansson
- 2.9
- Jansson is a C library for encoding decoding and manipulating JSON data.
- MIT
-
-
- jaxp1.3
- 1.4.01
- Java XML parser and transformer APIs (DOM SAX JAXP TrAX)
- Apache-2.0, W3C, PD
-
-
- jdepend
- 2.9.1
- Design quality metrics generator for each Java
- BSD
-
-
- jikes-initial
- 1.0
- Initial Java 1.4-compatible (and not higher) compiler.
- MIT
-
-
- jikes
- 1.22
- Java compiler adhering to language and VM specifications
- IPL-1.0
-
-
- jlex
- 1.2.6
- Lexical analyzer generator for Java
- JLEX
-
-
- jq
- 1.5
- jq is like sed for JSON data you can use it to slice and filter and map and transform structured data with the same ease that sed awk grep and friends let you play with text.
- MIT
-
-
- jsch
- 0.1.40
- SSH implementation in Java
- BSD
-
-
- junit
- 3.8.2
- JUnit is a testing framework for Java
- CPL-1.0
-
-
- jzlib
- 1.0.7
- zlib implementation in Java
- BSD
-
-
- kbd
- 2.0.4
- Keytable files and keyboard utilities.
- GPL-2.0
-
-
- kbproto
- 1.0.7
- This package provides the wire protocol for the X Keyboard extension. This extension is used to control options related to keyboard handling and layout.
- MIT
-
-
- kern-tools
- 0.2
- Tools for managing Yocto Project style branched kernels.
- GPL-2.0
-
-
- keymaps
- 1.0
- Keymaps and initscript to set the keymap on bootup.
- GPL-2.0
-
-
- keyutils
- 1.5.10
- Utilities to control the kernel key management facility and to provide a mechanism by which the kernel call back to userspace to get a key instantiated.
- LGPL-2.1, GPL-2.0
-
-
- kmod
- 24
- kmod is a set of tools to handle common tasks with Linux kernel modules like insert remove list check properties resolve dependencies and aliases.
- GPL-2.0, LGPL-2.1
-
-
- krb5
- 1.15.1
- "Kerberos is a system for authenticating users and services on a network. Kerberos is a trusted third-party service. That means that there is a third party (the Kerberos server) that is trusted by all the entities on the network (users and services usually called ""principals""). . This is the MIT reference implementation of Kerberos V5. . This package contains the Kerberos key server (KDC). The KDC manages all authentication credentials for a Kerberos realm holds the master keys for the realm and responds to authentication requests. This package should be installed on both master and slave KDCs."
- MIT
-
-
- ldconfig
- 2.12.1
- A standalone native ldconfig build.
- GPL-2.0
-
-
- less
- 487
- Less is a program similar to more i.e. a terminal based program for viewing text files and the output from other programs. Less offers many features beyond those that more does.
- GPL-3.0, BSD-2-Clause
-
-
- libaio
- 0.3.110
- Asynchronous input/output library that uses the kernels native interface
- LGPL-2.1
-
-
- libarchive
- 3.3.2
- C library and command-line tools for reading and writing tar cpio zip ISO and other archive formats
- BSD
-
-
- libassuan
- 2.4.3
- IPC library used by GnuPG and GPGME.
- GPL-3.0, LGPL-2.1
-
-
- libbsd
- 0.8.6
- This library provides useful functions commonly found on BSD systems and lacking on others like GNU systems thus making it easier to port projects with strong BSD origins without needing to embed the same code over and over again on each project.
- BSD-4-Clause, ISC, PD
-
-
- libcap
- 2.25
- Library for getting/setting POSIX.1e capabilities.
- BSD, GPL-2.0
-
-
- libcgroup
- 0.41
- libcgroup is a library that abstracts the control group file system in Linux. Control groups allow you to limit account and isolate resource usage (CPU memory disk I/O etc.) of groups of processes.
- LGPL-2.1
-
-
- libcheck
- 0.10.0
- Check - unit testing framework for C code.
- LGPL-2.1
-
-
- libdaemon
- 0.14
- Lightweight C library which eases the writing of UNIX daemons.
- LGPL-2.1
-
-
- libdevmapper
- 2.02.171
- LVM2 is a set of utilities to manage logical volumes in Linux.
- GPL-2.0, LGPL-2.0
-
-
- libecj-bootstrap
- 3.6.2
- JDT Core Batch Compiler - Jar only
- EPL-1.0
-
-
- liberation-fonts
- 2.00.1
- The Liberation(tm) Fonts is a font family originally created by Ascender(c) which aims at metric compatibility with Arial Times New Roman Courier New.
- OFL-1.1
-
-
- libffi
- 3.2.1
- The `libffi' library provides a portable high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. FFI stands for Foreign Function Interface. A foreign function interface is the popular name for the interface that allows code written in one language to call code written in another language. The `libffi' library really only provides the lowest machine dependent layer of a fully featured foreign function interface. A layer must exist above `libffi' that handles type conversions for values passed between the two languages.
- MIT
-
-
- libfile-slurp-perl
- 9999.19
- This module provides subroutines to read or write entire files with a simple call. It also has a subroutine for reading the list of filenames in a directory.
- Artistic-1.0, GPL-1.0
-
-
- libgcc-initial
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception
-
-
- libgcc
- 7.3.0
- GNU cc and gcc C compilers.
- GPL-3.0-with-GCC-exception, GPL-3.0
-
-
- libgcrypt
- 1.8.0
- General purpose cryptographic library based on the code from GnuPG.
- GPL-2.0, LGPL-2.1, GPL-3.0
-
-
- libgpg-error
- 1.27
- Small library that defines common error values for all GnuPG components.
- GPL-2.0, LGPL-2.1
-
-
- libgudev
- 231
- GObject wrapper for libudev.
- LGPL-2.1
-
-
- libice
- 1.0.9
- The Inter-Client Exchange (ICE) protocol provides a generic framework for building protocols on top of reliable byte-stream transport connections. It provides basic mechanisms for setting up and shutting down connections for performing authentication for negotiating versions and for reporting errors.
- MIT
-
-
- libidn
- 1.33
- Implementation of the Stringprep Punycode and IDNA specifications defined by the IETF Internationalized Domain Names (IDN) working group.
- LGPL-2.1, LGPL-3.0, GPL-3.0
-
-
- libjpeg-turbo
- 1.5.2
- libjpeg-turbo is a derivative of libjpeg that uses SIMD instructions (MMX SSE2 NEON) to accelerate baseline JPEG compression and decompression
- BSD-3-Clause
-
-
- libmbim
- 1.16.0
- libmbim is a glib-based library for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol
- GPL-2.0, LGPL-2.1
-
-
- libmnl
- 1.0.4
- Minimalistic user-space library oriented to Netlink developers providing functions for common tasks in parsing validating and constructing both the Netlink header and TLVs.
- LGPL-2.1
-
-
- libmpc
- 1.0.3
- Mpc is a C library for the arithmetic of complex numbers with arbitrarily high precision and correct rounding of the result. It is built upon and follows the same principles as Mpfr
- LGPL-3.0
-
-
- libndp
- 1.6
- Library for IPv6 Neighbor Discovery Protocol.
- LGPL-2.1
-
-
- libnewt
- 0.52.20
- Newt is a programming library for color text mode widget based user interfaces. Newt can be used to add stacked windows entry widgets checkboxes radio buttons labels plain text fields scrollbars etc. to text mode user interfaces. This package also contains the shared library needed by programs built with newt as well as a /usr/bin/dialog replacement called whiptail. Newt is based on the slang library.
- LGPL-2.0
-
-
- libnl
- 3.4.0
- A library for applications dealing with netlink sockets.
- LGPL-2.1
-
-
- libnss-mdns
- 0.10
- Name Service Switch module for Multicast DNS (zeroconf) name resolution.
- LGPL-2.1
-
-
- libpcap
- 1.8.1
- Libpcap provides a portable framework for low-level network monitoring. Libpcap can provide network statistics collection security monitoring and network debugging.
- BSD
-
-
- libpciaccess
- 0.13.5
- libpciaccess provides functionality for X to access the PCI bus and devices in a platform-independent way.
- MIT
-
-
- libpcre
- 8.41
- The PCRE library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. PCRE has its own native API as well as a set of wrapper functions that correspond to the POSIX regular expression API.
- BSD
-
-
- libpng
- 1.6.31
- PNG image format decoding library.
- Libpng
-
-
- libpthread-stubs
- 0.4
- This library provides weak aliases for pthread functions not provided in libc or otherwise available by default.
- MIT
-
-
- libqmi
- 1.20.2
- libqmi is a glib-based library for talking to WWAN modems and devices which speak the Qualcomm MSM Interface (QMI) protocol
- GPL-2.0, LGPL-2.1
-
-
- libsdl
- 1.2.15
- Simple DirectMedia Layer is a cross-platform multimedia library designed to provide low level access to audio keyboard mouse joystick 3D hardware via OpenGL and 2D video framebuffer.
- LGPL-2.1
-
-
- libsign
- 0.3.2
- This project targets to provide a generic signing framework. This framework separates the signing request and signing process and correspondingly forms the so-called signlet and signaturelet. Each signaturelet only concerns about the details about how to construct the layout of a signature format and signlet only cares how to construct the signing request.
- BSD-3-Clause
-
-
- libsm
- 1.2.2
- "The Session Management Library (SMlib) is a low-level \""C\"" language interface to XSMP. The purpose of the X Session Management Protocol (XSMP) is to provide a uniform mechanism for users to save and restore their sessions. A session is a group of clients each of which has a particular state."
- MIT
-
-
- libtasn1
- 4.12
- Library for ASN.1 and DER manipulation.
- GPL-3.0, LGPL-2.1
-
-
- libtool
- 2.4.6
- This is GNU libtool a generic library support script. Libtool hides the complexity of generating special library types (such as shared libraries) behind a consistent interface.
- GPL-2.0, LGPL-2.1
-
-
- libunistring
- 0.9.7
- Text files are nowadays usually encoded in Unicode and may consist of very different scripts from Latin letters to Chinese Hanzi with many kinds of special characters accents right-to-left writing marks hyphens Roman numbers and much more. But the POSIX platform APIs for text do not contain adequate functions for dealing with particular properties of many Unicode characters. In fact the POSIX APIs for text have several assumptions at their base which don't hold for Unicode text. This library provides functions for manipulating Unicode strings and for manipulating C strings according to the Unicode standard. This package contains documentation.
- LGPL-3.0, GPL-2.0
-
-
- libusb1
- 1.0.21
- Userspace library to access USB (version 1.0).
- LGPL-2.1
-
-
- libvirt
- 4.2.0
- A toolkit to interact with the virtualization capabilities of recent versions of Linux.
- LGPL-2.1, GPL-2.0
-
-
- libx11
- 1.6.5
- This package provides a client interface to the X Window System otherwise known as 'Xlib'. It provides a complete API for the basic functions of the window system.
- MIT, BSD
-
-
- libxau
- 1.0.8
- libxau provides the main interfaces to the X11 authorisation handling which controls authorisation for X connections both client-side and server-side.
- MIT
-
-
- libxcb
- 1.12
- The X protocol C-language Binding (XCB) is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
- MIT
-
-
- libxdmcp
- 1.1.2
- The purpose of the X Display Manager Control Protocol (XDMCP) is to provide a uniform mechanism for an autonomous display to request login service from a remote host. An X terminal (screen keyboard mouse processor network interface) is a prime example of an autonomous display.
- MIT
-
-
- libxext
- 1.3.3
- libXext provides an X Window System client interface to several extensions to the X protocol. The supported protocol extensions are DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. libXext also provides a small set of utility functions to aid authors of client APIs for X protocol extensions.
- MIT
-
-
- libxft
- 2.3.2
- Xft was designed to provide good support for scalable fonts and to do so efficiently. Unlike the core fonts system it supports features such as anti-aliasing and sub-pixel rasterisation. Perhaps more importantly it gives applications full control over the way glyphs are rendered making fine typesetting and WYSIWIG display possible. Finally it allows applications to use fonts that are not installed system-wide for displaying documents with embedded fonts. Xft is not compatible with the core fonts system: usage of Xft requires fairly extensive changes to toolkits (user-interface libraries).
- MIT
-
-
- libxkbcommon
- 0.7.1
- libxkbcommon is a keymap compiler and support library which processes a reduced subset of keymaps as defined by the XKB specification.
- MIT
-
-
- libxml-parser-perl
- 2.44
- XML::Parser - A perl module for parsing XML documents.
- Artistic-1.0, GPL-1.0
-
-
- libxml2
- 2.9.5
- The XML Parser Library allows for manipulation of XML files. Libxml2 exports Push and Pull type parser interfaces for both XML and HTML. It can do DTD validation at parse time on a parsed document instance or with an arbitrary DTD. Libxml2 includes complete XPath XPointer and Xinclude implementations. It also has a SAX like interface which is designed to be compatible with Expat.
- MIT
-
-
- libxrandr
- 1.5.1
- The X Resize Rotate and Reflect Extension called RandR for short brings the ability to resize rotate and reflect the root window of a screen. It is based on the X Resize and Rotate Extension as specified in the Proceedings of the 2001 Usenix Technical Conference [RANDR].
- MIT
-
-
- libxrender
- 0.9.10
- The X Rendering Extension (Render) introduces digital image composition as the foundation of a new rendering model within the X Window System. Rendering geometric figures is accomplished by client-side tessellation into either triangles or trapezoids. Text is drawn by loading glyphs into the server and rendering sets of them.
- MIT
-
-
- libxslt
- 1.1.29
- GNOME XSLT library.
- MIT
-
-
- libyaml
- 0.1.7
- LibYAML is a C library for parsing and emitting data in YAML 1.1 a human-readable data serialization format.
- MIT
-
-
- lighttpd
- 1.4.45
- Lightweight high-performance web server.
- BSD
-
-
- linux-firmware
- 0.0
- Firmware files for use with Linux kernel.
- Redistributable binaries
-
-
- linux-intel-guest
- 4.14.123
- Linux kernel.
- GPL-2.0
-
-
- linux-intel-host
- 4.14.123
- Linux kernel.
- GPL-2.0
-
-
- linux-libc-headers
- 4.12
- Sanitized set of kernel headers for the C library's use.
- GPL-2.0
-
-
- lmsensors-config
- 1.0
- Hardware health monitoring configuration files
- MIT
-
-
- lmsensors
- 3.6.0
- Hardware health monitoring applications.
- GPL-2.0, LGPL-2.1
-
-
- log-collector
- 1.0
- Service that collects platform logs
- Enea
-
-
- log4j1.2
- 1.2.17
- Java library to help the programmer output log statements to a variety of output targets
- Apache-2.0
-
-
- logkit
- 1.2.2
- Logging toolkit designed for secure performance orientated logging in Java applications
- Apache-2.0
-
-
- logrotate
- 3.12.3
- Rotates compresses removes and mails system log files.
- GPL-2.0
-
-
- lsb
- 4.1
- LSB support for OpenEmbedded.
- GPL-2.0
-
-
- lsbinitscripts
- 9.72
- SysV init scripts which are only used in an LSB image.
- GPL-2.0
-
-
- lshw
- 02.17
- A small tool to provide detailed information on the hardware configuration of the machine. It can report exact memory configuration firmware version mainboard configuration CPU version and speed cache configuration bus speed etc. on DMI-capable or EFI systems.
- GPL-2.0
-
-
- lsof
- 4.89
- Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open Files and it does just that.
- BSD
-
-
- lvm2
- 2.02.171
- LVM2 is a set of utilities to manage logical volumes in Linux.
- GPL-2.0, LGPL-2.0
-
-
- lxc
- 2.0.8
- lxc aims to use these new functionnalities to provide an userspace container object
- GPL-2.0
-
-
- lxd
- git
- "LXD is a container ""hypervisor"" and a new user experience for LXC Specifically it's made of three components: - A system-wide daemon (lxd) - A command line client (lxc) - An OpenStack Nova plugin (nova-compute-lxd)"
- Apache-2.0
-
-
- lz4
- 1.7.4
- LZ4 is a very fast lossless compression algorithm providing compression speed at 400 MB/s per core scalable with multi-cores CPU. It also features an extremely fast decoder with speed in multiple GB/s per core typically reaching RAM speed limits on multi-core systems.
- BSD, BSD-2-Clause, GPL-2.0
-
-
- lzo
- 2.10
- Lossless data compression library.
- GPL-2.0
-
-
- lzop
- 1.03
- lzop is a compression utility which is designed to be a companion to gzip. \nIt is based on the LZO data compression library and its main advantages over \ngzip are much higher compression and decompression speed at the cost of some \ncompression ratio. The lzop compression utility was designed with the goals \nof reliability speed portability and with reasonable drop-in compatibility \nto gzip.
- GPL-2.0
-
-
- m4
- 1.4.18
- GNU m4 is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible although it has some extensions (for example handling more than 9 positional parameters to macros). GNU M4 also has built-in functions for including files running shell commands doing arithmetic etc.
- GPL-3.0
-
-
- make
- 4.2.1
- Make is a tool which controls the generation of executables and other non-source files of a program from the program's source files. Make gets its knowledge of how to build your program from a file called the makefile which lists each of the non-source files and how to compute it from other files.
- GPL-3.0, LGPL-2.0
-
-
- makedepend
- 1.0.5
- The makedepend program reads each sourcefile in sequence and parses it like a C-preprocessor processing all #include #define #undef #ifdef #ifndef #endif #if #elif and #else directives so that it can correctly tell which #include directives would be used in a compilation. Any #include directives can reference files having other #include directives and parsing will occur in these files as well.
- MIT
-
-
- makedevs
- 1.0.1
- Tool for creating device nodes.
- GPL-2.0
-
-
- mklibs
- 0.1.43
- mklibs produces cut-down shared libraries that contain only the routines required by a particular set of executables.
- GPL-2.0
-
-
- modemmanager
- 1.7.991
- ModemManager is a DBus-activated daemon which controls mobile broadband (2G/3G/4G) devices and connections
- GPL-2.0, LGPL-2.1
-
-
- mokutil
- 0.3.0
- The utility to manipulate machines owner keys which managed in shim.
- GPL-3.0
-
-
- mozjs
- 17.0.0
- SpiderMonkey is Mozilla's JavaScript engine written in C/C++.
- MPL-2.0
-
-
- mpfr
- 3.1.5
- C library for multiple-precision floating-point computations with exact rounding.
- GPL-3.0, LGPL-3.0
-
-
- mtools
- 4.0.18
- Mtools is a collection of utilities to access MS-DOS disks from GNU and Unix without mounting them.
- GPL-3.0
-
-
- nasm
- 2.13.01
- General-purpose x86 assembler.
- BSD-2-Clause
-
-
- ncurses
- 6.0
- SVr4 and XSI-Curses compatible curses library and terminfo tools including tic infocmp captoinfo. Supports color multiple highlights forms-drawing characters and automatic recognition of keypad and function-key sequences. Extensions include resizable windows and mouse support on both xterm and Linux console using the gpm library.
- MIT
-
-
- net-snmp
- 5.7.3
- Various tools relating to the Simple Network Management Protocol.
- BSD
-
-
- net-tools
- 1.60-26
- A collection of programs that form the base set of the NET-3 networking distribution for the Linux operating system
- GPL-2.0
-
-
- netbase
- 5.4
- This package provides the necessary infrastructure for basic TCP/IP based networking
- GPL-2.0
-
-
- netcat-openbsd
- 1.105
- A simple Unix utility which reads and writes data across network connections using TCP or UDP protocol. It is designed to be a reliable 'back-end' tool that can be used directly or easily driven by other programs and scripts. At the same time it is a feature-rich network debugging and exploration tool since it can create almost any kind of connection you would need and has several interesting built-in capabilities.
- BSD-3-Clause
-
-
- netcf
- 0.2.8
- netcf is a cross-platform network configuration library.
- LGPL-2.1
-
-
- nettle
- 3.3
- A low level cryptographic library.
- LGPL-3.0, GPL-2.0
-
-
- networkmanager
- 1.10.10
- NetworkManager.
- GPL-2.0
-
-
- nfv-init
- 1.0
- Enea service expected to be run after cloud-init
- Enea
-
-
- nfv-installer
- 1.0
- Enea Edge installer
- Enea
-
-
- nfva-cfgtool
- 1.0
- Command line tool to for accessing the Enea Edge install configuration json file
- Enea
-
-
- nfva-hotfixes
- 1.0
- Different hotfixes
- Enea
-
-
- nfva-startup
- 1.0
- Service that configures the network according to installer settings
- Enea
-
-
- nodejs
- 8.4.0
- nodeJS Evented I/O for V8 JavaScript
- MIT, BSD, Artistic-2.0
-
-
- notary
- 0.4.2
- Notary is a Docker project that allows anyone to have trust over arbitrary collections of data
- Apache-2.0
-
-
- nspr
- 4.16
- Netscape Portable Runtime Library.
- GPL-2.0, MPL-2.0, LGPL-2.1
-
-
- nss
- 3.31.1
- Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSL v2 and v3 TLS PKCS 5 PKCS 7 PKCS 11 PKCS 12 S/MIME X.509 v3 certificates and other security standards.
- MPL-2.0, GPL-2.0, MPL-2.0, LGPL-2.1
-
-
- ntp-user-stub
- 1.0
- The NTP user/group were added in previous NFVA releases and are needed for OSTree upgrades to ensure backwards compatibility.
- Enea
-
-
- numactl
- 2.0.11
- Simple NUMA policy support. It consists of a numactl program to run other programs with a specific NUMA policy and a libnuma to do allocations with NUMA policy in applications.
- GPL-2.0, LGPL-2.1
-
-
- onig
- 5.9.6
- Regular expressions library. The characteristics of this library is that different character encoding for every regular expression object can be specified.
- BSD
-
-
- openipmi
- 2.0.24
- OpenIPMI is an effort to create a full-function IPMI system to allow full access to all IPMI information on a server and to abstract it to a level that will make it easy to use
- GPL-2.0, LGPL-2.1, BSD
-
-
- openjdk-8
- 102b14
- Java runtime based upon the OpenJDK Project
- GPL-2.0-with-classpath-exception
-
-
- openssh
- 7.5p1
- Secure rlogin/rsh/rcp/telnet replacement (OpenSSH) Ssh (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine.
- BSD
-
-
- openssl
- 1.0.2o
- Secure Socket Layer (SSL) binary and related cryptographic tools.
- OpenSSL
-
-
- openvswitch
- 2.9
- Open vSwitch is a production quality multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension while still supporting standard management interfaces and protocols (e.g. NetFlow sFlow SPAN RSPAN CLI LACP 802.1ag)
- Apache-2.0
-
-
- opkg-utils
- 0.3.5
- Additional utilities for the opkg package manager.
- GPL-2.0
-
-
- oro
- 2.0.8
- Perl5-compatible regular expressions library for Java
- Apache-2.0
-
-
- os-release
- 1.0
- The /etc/os-release file contains operating system identification data.
- MIT
-
-
- ostree-initrd
- 3
- Extremely basic live image init script.
- MIT
-
-
- ostree-rw
- 1.0
- Enea bash script to make current ostree hash writable
- Enea
-
-
- ostree
- v2018.7
- Tool for managing bootable immutable versioned filesystem trees.
- LGPL-2.0
-
-
- packagegroup-core-boot
- 1.0
- The minimal set of packages required to boot the system
- MIT
-
-
- packagegroup-core-ssh-openssh
- 1.0
- OpenSSH SSH client/server.
- MIT
-
-
- packagegroup-efi-secure-boot
- 1.0
- EFI Secure Boot packages for secure-environment.
- MIT
-
-
- packagegroup-enea-telemetry
- 1.0
- Packages for Telemetry.
- MIT
-
-
- packagegroup-enea-virtualization-4gusb-modems
- 1.0
- Packagegroup for 4G usb modems.
- MIT
-
-
- packagegroup-enea-virtualization-docker
- 1.0
- Packagegroup for Docker.
- MIT
-
-
- packagegroup-enea-virtualization-dpdk
- 1.0
- Packagegroup for DPDK.
- MIT
-
-
- packagegroup-enea-virtualization-guest
- 1.0
- This package group includes packages and packagegroups specific to the guest side of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-virtualization-host
- 1.0
- This package group includes packages and packagegroups specific to the host side of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-virtualization-libvirt
- 1.0
- Package group for libvirt.
- MIT
-
-
- packagegroup-enea-virtualization-lxc
- 1.0
- Packagegroup for LXC.
- MIT
-
-
- packagegroup-enea-virtualization-lxd
- 1.0
- Packagegroup for LXD.
- MIT
-
-
- packagegroup-enea-virtualization-ovs
- 1.0
- Packagegroup for Open vSwitch.
- MIT
-
-
- packagegroup-enea-virtualization-qemu
- 1.0
- Packagegroup for QEMU.
- MIT
-
-
- packagegroup-enea-virtualization
- 1.0
- This packagegroup includes packages and packagegroups required for both host and guest images of the Enea Linux Virtualization Profile.
- MIT
-
-
- packagegroup-enea-wifi
- 1.0
- This package group includes packages and packagegroups that enable WiFi connectivity in the Enea Edge Runtime
- MIT
-
-
- pango
- 1.40.6
- Pango is a library for laying out and rendering of text with an emphasis on internationalization. Pango can be used anywhere that text layout is needed though most of the work on Pango so far has been done in the context of the GTK+ widget toolkit. Pango forms the core of text and font handling for GTK+-2.x.
- LGPL-2.0
-
-
- parted
- 3.2
- Disk partition editing/resizing utility.
- GPL-3.0
-
-
- partrt
- 1.1
- partrt is a tool for dividing a SMP Linux system into a real time domain and a non-real time domain.
- BSD
-
-
- pciutils
- 3.5.5
- The PCI Utilities package contains a library for portable access to PCI bus configuration space and several utilities based on this library.
- GPL-2.0
-
-
- perl
- 5.24.1
- Perl scripting language.
- Artistic-1.0, GPL-1.0
-
-
- pigz
- 2.3.4
- pigz which stands for parallel implementation of gzip is a fully functional replacement for gzip that exploits multiple processors and multiple cores to the hilt when compressing data. pigz was written by Mark Adler and uses the zlib and pthread libraries.
- Zlib, Apache-2.0
-
-
- pixman
- 0.34.0
- Pixman provides a library for manipulating pixel regions -- a set of Y-X banded rectangles image compositing using the Porter/Duff model and implicit mask generation for geometric primitives including trapezoids triangles and rectangles.
- MIT, PD
-
-
- pkgconfig
- 0.29.2
- pkg-config is a helper tool used when compiling applications and libraries. It helps determined the correct compiler/link options. It is also language-agnostic.
- GPL-2.0
-
-
- pm-utils
- 1.4.1
- Simple shell command line tools to suspend and hibernate.
- GPL-2.0
-
-
- polkit
- 0.113
- The polkit package is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes.
- LGPL-2.0
-
-
- popt
- 1.16
- Library for parsing command line options.
- MIT
-
-
- prelink
- 1.0
- The prelink package contains a utility which modifies ELF shared libraries and executables so that far fewer relocations need to be resolved at runtime and thus programs come up faster.
- GPL-2.0
-
-
- procps
- 3.3.12
- Procps contains a set of system utilities that provide system information about processes using the /proc filesystem. The package includes the programs ps top vmstat w kill and skill.
- GPL-2.0, LGPL-2.0
-
-
- pseudo
- 1.8.2
- Pseudo gives fake root capabilities to a normal user.
- LGPL-2.1
-
-
- ptest-runner
- 2.1
- The ptest-runner2 package installs a ptest-runner program which loops through all installed ptest test suites and runs them in sequence.
- GPL-2.0
-
-
- python-asn1crypto
- 0.23.0
- Python binding to the Networking and Cryptography (NaCl) library
- Apache-2.0
-
-
- python-certifi
- 2017.7.27.1
- This installable Python package contains a CA Bundle that you can reference in your Python code. This is useful for verifying HTTP requests for example. This is the same CA Bundle which ships with the Requests codebase and is derived from Mozilla Firefox's canonical set.
- ISC
-
-
- python-cffi
- 1.11.2
- Foreign Function Interface for Python calling C code.
- MIT
-
-
- python-chardet
- 3.0.4
- Universal encoding detector for Python 2 and 3.
- LGPL-2.1
-
-
- python-cryptography-vectors
- 2.0.3
- Test vectors for the cryptography package..
- Apache-2.0, BSD
-
-
- python-cryptography
- 2.0.3
- Provides cryptographic recipes and primitives to python developers.
- Apache-2.0, BSD
-
-
- python-cython
- 0.27.1
- Cython is a language specially designed for writing Python extension modules. It's designed to bridge the gap between the nice high-level easy-to-use world of Python and the messy low-level world of C.
- Apache-2.0
-
-
- python-enum34
- 1.1.6
- backport of Python 3.4's enum package.
- BSD-3-Clause
-
-
- python-functools32
- 3.2.3-2
- Backport of the functools module from Python 3.2.3 for use on 2.7 and PyPy..
- Python-2.0
-
-
- python-futures
- 3.0.5
- The concurrent.futures module provides a high-level interface for asynchronously executing callables.
- BSD
-
-
- python-idna
- 2.6
- Internationalised Domain Names in Applications.
- BSD-3-Clause, Python-2.0, Unicode
-
-
- python-ipaddress
- 1.0.18
- Python 3.3+'s ipaddress for Python 2.6 2.7 3.2..
- Python-2.0
-
-
- python-iso8601
- 0.1.12
- Simple module to parse ISO 8601 dates.
- MIT
-
-
- python-jsonpatch
- 1.16
- Appling JSON patches in Python 2.6+ and 3.x.
- BSD
-
-
- python-jsonpointer
- 1.12
- Resolve JSON Pointers in Python.
- BSD
-
-
- python-jsonschema
- 2.6.0
- An implementation of JSON Schema validation for Python.
- MIT
-
-
- python-m2crypto
- 0.26.4
- A Python crypto and SSL toolkit.
- BSD
-
-
- python-ndg-httpsclient
- 0.4.3
- Provides enhanced HTTPS support for httplib and urllib2 using PyOpenSSL
- BSD
-
-
- python-netaddr
- 0.7.19
- A network address manipulation library for Python..
- BSD
-
-
- python-netifaces
- 0.10.6
- Portable network interface information.
- MIT
-
-
- python-pip
- 9.0.1
- PIP is a tool for installing and managing Python packages.
- MIT, LGPL-2.1
-
-
- python-pretend
- 1.0.8
- A library for stubbing in Python.
- BSD
-
-
- python-prettytable
- 0.7.2
- Python library for displaying tabular data in a ASCII table format.
- BSD
-
-
- python-psutil
- 5.3.1
- A cross-platform process and system utilities module for Python.
- BSD
-
-
- python-py
- 1.4.34
- Library with cross-python path ini-parsing io code log facilities.
- MIT
-
-
- python-pyasn1
- 0.3.6
- Python library implementing ASN.1 types..
- BSD-2-Clause
-
-
- python-pycparser
- 2.18
- Parser of the C language written in pure Python.
- BSD-3-Clause
-
-
- python-pyopenssl
- 17.3.0
- Simple Python wrapper around the OpenSSL library.
- Apache-2.0
-
-
- python-pysocks
- 1.6.7
- A Python SOCKS client module
- BSD
-
-
- python-pytest-runner
- 2.12.1
- Invoke py.test as distutils command with dependency resolution.
- MIT
-
-
- python-pytest
- 3.2.2
- Simple powerful teting with python.
- MIT
-
-
- python-pyyaml
- 3.11
- YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. . PyYAML features a complete YAML 1.1 parser Unicode support pickle support capable extension API and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. . PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistance.
- MIT
-
-
- python-requests
- 2.18.4
- Python HTTP for Humans.
- Apache-2.0
-
-
- python-rfc3987
- 1.3.7
- Parsing and validation of URIs (RFC 3986) and IRIs (RFC 3987).
- GPL-3.0
-
-
- python-setuptools-scm
- 1.15.6
- the blessed package to manage your versions by scm tags.
- MIT
-
-
- python-setuptools
- 36.2.7
- Download build install upgrade and uninstall Python packages.
- MIT
-
-
- python-six
- 1.11.0
- Python 2 and 3 compatibility library.
- MIT
-
-
- python-strict-rfc3339
- 0.7
- Strict simple lightweight RFC3339 function.s.
- GPL-3.0
-
-
- python-typing
- 3.6.2
- Simple Python module defined by PEP 484..
- Python-2.0
-
-
- python-urllib3
- 1.22
- Python HTTP library with thread-safe connection pooling file post support sanity friendly and more.
- MIT
-
-
- python-vcversioner
- 2.16.0.0
- Python vcversioner automagically update the project's version.
- ISC
-
-
- python
- 2.7.13
- The Python Programming Language.
- Python-2.0
-
-
- python3-netifaces
- 0.10.6
- Portable network interface information.
- MIT
-
-
- python3-pip
- 9.0.1
- The PyPA recommended tool for installing Python packages.
- MIT
-
-
- python3-setuptools
- 36.2.7
- Download build install upgrade and uninstall Python packages.
- MIT
-
-
- python3-six
- 1.10.0
- Python 2 and 3 compatibility library.
- MIT
-
-
- python3-twisted
- 13.2.0
- Twisted is an event-driven networking framework written in Python and licensed under the LGPL. Twisted supports TCP UDP SSL/TLS multicast Unix sockets a large number of protocols (including HTTP NNTP IMAP SSH IRC FTP and others) and much more.
- MIT
-
-
- python3-zopeinterface
- 4.4.3
- Interface definitions for Zope products.
- ZPL-2.1
-
-
- python3
- 3.5.3
- The Python Programming Language.
- Python-2.0
-
-
- qemu-helper
- 1.0
- Helper utilities needed by the runqemu script.
- GPL-2.0
-
-
- qemu
- 2.11.1
- Fast open source processor emulator.
- GPL-2.0, LGPL-2.1
-
-
- qemuwrapper
- 1.0
- QEMU wrapper script.
- MIT
-
-
- quilt
- 0.65
- Tool for working with series of patches.
- GPL-2.0
-
-
- randrproto
- 1.5.0
- This package provides the wire protocol for the X Resize Rotate and Reflect extension. This extension provides the ability to resize rotate and reflect the root window of a screen.
- MIT
-
-
- readline
- 7.0
- The GNU Readline library provides a set of functions for use by applications that allow users to edit command lines as they are typed in. Both Emacs and vi editing modes are available. The Readline library includes additional functions to maintain a list of previously-entered command lines to recall and perhaps reedit those lines and perform csh-like history expansion on previous commands.
- GPL-3.0
-
-
- regexp
- 1.5
- Java Regular Expression package
- Apache-2.0
-
-
- renderproto
- 0.11.1
- This package provides the wire protocol for the X Rendering extension. This is the basis the image composition within the X window system.
- MIT
-
-
- rhino
- 1.7r4
- Lexical analyzer generator for Java
- MPL-2.0
-
-
- rpm
- 4.13.90
- The RPM Package Manager (RPM) is a powerful command line driven package management system capable of installing uninstalling verifying querying and updating software packages. Each software package consists of an archive of files along with information about the package like its version a description etc.
- GPL-2.0
-
-
- rrdtool
- 1.6.0
- High performance data logging and graphing system for time series data.
- GPL-2.0
-
-
- rsync
- 3.1.3
- File synchronization tool.
- GPL-3.0
-
-
- run-postinsts
- 1.0
- Runs postinstall scripts on first boot of the target device.
- MIT
-
-
- runc-docker
- 1.0.0-rc3
- runc is a CLI tool for spawning and running containers according to the OCI specification.
- Apache-2.0
-
-
- sbsigntool
- 0.6
- Utilities for signing UEFI binaries for use with secure boot.
- GPL-3.0
-
-
- sed
- 4.2.2
- Stream EDitor (text filtering utility).
- GPL-3.0
-
-
- seloader
- 0.4.6
- The SELoader is designed to authenticate the non-PE files such as grub configuration initrd grub modules which cannot be verified by the MOK Verify Protocol registered by shim loader. In order to conveniently authenticate the PE file with gBS->LoadImage() and gBS->StartImage() the SELoader hooks EFI Security2 Architectural Protocol and employs MOK Verify Protocol to verify the PE file. If only UEFI Secure Boot is enabled the SELoader just simplily calls gBS->LoadImage() and gBS->StartImage() to allow BIOS to verify PE file. The SELoader publishes MOK2 Verify Protocol which provides a flexible interface to allow the bootloader to verify the file file buffer or memory buffer without knowing the file format.
- BSD-3-Clause
-
-
- servlet2.3
- 4.1.37
- Servlet API 2.3 (from Tomcat 4.1)
- Apache-2.0
-
-
- shadow-securetty
- 4.2.1
- Provider of the machine specific securetty file.
- MIT
-
-
- shadow-sysroot
- 4.2.1
- Shadow utils requirements for useradd.bbclass.
- BSD, Artistic-1.0
-
-
- shadow
- 4.2.1
- Tools to change and administer password and group data.
- BSD, Artistic-1.0
-
-
- shared-mime-info
- 1.8
- Shared MIME type database and specification.
- LGPL-2.0
-
-
- shim
- 12
- shim is a trivial EFI application that when run attempts to open and execute another application. It will initially attempt to do this via the standard EFI LoadImage() and StartImage() calls. If these fail (because secure boot is enabled and the binary is not signed with an appropriate key for instance) it will then validate the binary against a built-in certificate. If this succeeds and if the binary or signing key are not blacklisted then shim will relocate and execute the binary.
- BSD-2-Clause
-
-
- simpleproxy
- 1.0
- Simpleproxy.
- GPL-2.0
-
-
- slang
- 2.3.1a
- S-Lang is an interpreted language and a programming library. The S-Lang language was designed so that it can be easily embedded into a program to provide the program with a powerful extension language. The S-Lang library provided in this package provides the S-Lang extension language. S-Lang's syntax resembles C which makes it easy to recode S-Lang procedures in C if you need to.
- GPL-2.0
-
-
- sqlite3
- 3.20.0
- Embeddable SQL database engine.
- PD
-
-
- squashfs-tools
- 4.3
- Tools for manipulating SquashFS filesystems.
- GPL-2.0, PD
-
-
- sshpass
- 1.06
- Tool for non-interactivly performing ssh password authentication
- GPL-2.0
-
-
- swig
- 3.0.12
- SWIG - Simplified Wrapper and Interface Generator.
- BSD, GPL-3.0
-
-
- sysfsutils
- 2.1.0
- Tools for working with the sysfs virtual filesystem. The tool 'systool' can query devices by bus class and topology.
- GPL-2.0, LGPL-2.1
-
-
- sysklogd
- 1.5.1
- The sysklogd package implements two system log daemons: syslogd klogd
- GPL-2.0, BSD
-
-
- syslinux
- 6.03
- Multi-purpose linux bootloader.
- GPL-2.0
-
-
- systemd-boot
- 234
- systemd is a system and service 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.
- GPL-2.0, LGPL-2.1
-
-
- systemd-compat-units
- 1.0
- Enhances systemd compatilibity with existing SysVinit scripts.
- MIT
-
-
- systemd-serialgetty
- 1.0
- Serial terminal support for systemd.
- GPL-2.0
-
-
- systemd-systemctl
- 1.0
- Wrapper for enabling systemd services.
- MIT
-
-
- systemd
- 234
- systemd is a system and service 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.
- GPL-2.0, LGPL-2.1
-
-
- tar
- 1.29
- GNU tar saves many files together into a single tape or disk archive and can restore individual files from the archive.
- GPL-3.0
-
-
- tcl
- 8.6.7
- Tool Command Language.
- tcl, BSD-3-Clause
-
-
- tcpdump
- 4.9.2
- A sophisticated network protocol analyzer.
- BSD
-
-
- texinfo-dummy
- 1.0
- Fake version of the texinfo utility suite.
- MIT
-
-
- thin-provisioning-tools
- 0.6.3
- A suite of tools for manipulating the metadata of the dm-thin device-mapper target.
- GPL-3.0
-
-
- tunctl
- 1.5
- Tool for controlling the Linux TUN/TAP driver.
- GPL-2.0
-
-
- tzcode
- 2018c
- tzcode timezone zoneinfo utils -- zic zdump tzselect.
- PD, BSD, BSD-3-Clause
-
-
- tzdata
- 2018c
- Timezone data.
- PD, BSD, BSD-3-Clause
-
-
- udev-extraconf
- 1.1
- Extra machine specific configuration files for udev specifically blacklist information.
- MIT
-
-
- unifdef
- 2.11
- Selectively remove #ifdef statements from sources.
- BSD-2-Clause
-
-
- unzip
- 6.0
- Utilities for extracting and viewing files in .zip archives.
- BSD-3-Clause
-
-
- update-rc.d
- 0.7
- update-rc.d is a utility that allows the management of symlinks to the initscripts in the /etc/rcN.d directory structure.
- GPL-2.0
-
-
- usb-modeswitch-data
- 20170205
- Data files for usbmodeswitch.
- GPL-2.0
-
-
- usb-modeswitch
- 2.5.0
- A mode switching tool for controlling 'flip flop' (multiple device) USB gear.
- GPL-2.0
-
-
- usbutils
- 013
- Contains the lsusb utility for inspecting the devices connected to the USB bus.
- GPL-2.0, GPL-3.0
-
-
- util-linux
- 2.30
- Util-linux includes a suite of basic system administration utilities commonly found on most Linux systems. Some of the more important utilities include disk partitioning kernel message management filesystem creation and system login.
- GPL-2.0, LGPL-2.1, BSD
-
-
- util-macros
- 1.19.1
- M4 autotools macros used by various X.org programs.
- MIT
-
-
- v86d
- 0.1.10
- User support binary for the uvesafb kernel module.
- GPL-2.0
-
-
- vala
- 0.36.4
- Vala is a C#-like language dedicated to ease GObject programming. Vala compiles to plain C and has no runtime environment nor penalities whatsoever.
- LGPL-2.1
-
-
- volatile-binds
- 1.0
- Volatile bind mount setup and configuration for read-only-rootfs
- MIT
-
-
- web-installer-backend
- 0.1
- Web installer go server
- Enea, BSD-3-Clause
-
-
- web-installer-frontend
- 0.1
- Web installer post-install application
- Enea, Apache-2.0, BSD, BSD-2-Clause, BSD-3-Clause, CC-BY-4.0, ISC, MIT, Zlib
-
-
- which
- 2.21
- Which is a utility that prints out the full path of the executables that bash(1) would execute when the passed program names would have been entered on the shell prompt. It does this by using the exact same algorithm as bash.
- GPL-3.0
-
-
- wireless-regdb
- 2020.11.20
- Wireless Central Regulatory Domain Database.
- ISC
-
-
- wpa-supplicant
- 2.6
- Client for Wi-Fi Protected Access (WPA).
- BSD
-
-
- xalan-j
- 2.7.1
- Java XSLT processor
- Apache-2.0
-
-
- xcb-proto
- 1.12
- Function prototypes for the X protocol C-language Binding (XCB). XCB is a replacement for Xlib featuring a small footprint latency hiding direct access to the protocol improved threading support and extensibility.
- MIT
-
-
- xerces-j
- 2.11.0
- Reference implementation of XNI the Xerces Native Interface and also a fully conforming XML Schema processor.
- Apache-2.0
-
-
- xextproto
- 7.3.0
- This package provides the wire protocol for several X extensions. These protocol extensions include DOUBLE-BUFFER DPMS Extended-Visual-Information LBX MIT_SHM MIT_SUNDRY-NONSTANDARD Multi-Buffering SECURITY SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XTEST. In addition a small set of utility functions are also available.
- MIT
-
-
- xkeyboard-config
- 2.21
- The non-arch keyboard configuration database for X Window. The goal is to provide the consistent well-structured frequently released open source of X keyboard configuration data for X Window System implementations. The project is targeted to XKB-based systems.
- MIT
-
-
- xml-commons-resolver1.1
- 1.2
- Library to resolve various public or system identifiers into accessible URLs (Java)
- Apache-2.0
-
-
- xproto
- 7.0.31
- This package provides the basic headers for the X Window System.
- MIT
-
-
- xtrans
- 1.3.5
- The X Transport Interface is intended to combine all system and transport specific code into a single place. This API should be used by all libraries clients and servers of the X Window System. Use of this API should allow the addition of new types of transports and support for new platforms without making any changes to the source except in the X Transport Interface code.
- MIT
-
-
- xz
- 5.2.3
- Utilities for managing LZMA compressed files.
- GPL-2.0, GPL-3.0-with-autoconf-exception, LGPL-2.1, PD
-
-
- yajl
- 2.1.0
- YAJL is a small event-driven (SAX-style) JSON parser written in ANSI C and a small validating JSON generator.
- ISC
-
-
- zip
- 3.0
- Compressor/archiver for creating and modifying .zip files.
- BSD-3-Clause
-
-
- zisofs-tools
- 1.0.8
- Utilities for creating compressed CD-ROM filesystems.
- GPL-2.0
-
-
- zlib
- 1.2.11
- Zlib is a general-purpose patent-free lossless data compression library which is used by many different programs.
- Zlib
-
-
-
-
-
-
- Open Source Licenses
-
-AFL-2.0
-
-
-The Academic Free License
- v. 2.0
-
-This Academic Free License (the "License") applies to any original work of authorship
-(the "Original Work") whose owner (the "Licensor") has placed the following notice
-immediately following the copyright notice for the Original Work:
-Licensed under the Academic Free License version 2.0
-
-1) Grant of Copyright License. Licensor hereby grants You a world-wide, royalty-free,
-non-exclusive, perpetual, sublicenseable license to do the following:
-a) to reproduce the Original Work in copies;
-
-b) to prepare derivative works ("Derivative Works") based upon the Original Work;
-
-c) to distribute copies of the Original Work and Derivative Works to the public;
-
-d) to perform the Original Work publicly; and
-
-e) to display the Original Work publicly.
-
-2) Grant of Patent License. Licensor hereby grants You a world-wide, royalty-free,
-non-exclusive, perpetual, sublicenseable license, under patent claims owned or
-controlled by the Licensor that are embodied in the Original Work as furnished by the
-Licensor, to make, use, sell and offer for sale the Original Work and Derivative
-Works.
-
-3) Grant of Source Code License. The term "Source Code" means the preferred form of
-the Original Work for making modifications to it and all available documentation
-describing how to modify the Original Work. Licensor hereby agrees to provide a
-machine-readable copy of the Source Code of the Original Work along with each copy of
-the Original Work that Licensor distributes. Licensor reserves the right to satisfy
-this obligation by placing a machine-readable copy of the Source Code in an
-information repository reasonably calculated to permit inexpensive and convenient
-access by You for as long as Licensor continues to distribute the Original Work, and
-by publishing the address of that information repository in a notice immediately
-following the copyright notice that applies to the Original Work.
-
-4) Exclusions From License Grant. Neither the names of Licensor, nor the names of any
-contributors to the Original Work, nor any of their trademarks or service marks, may
-be used to endorse or promote products derived from this Original Work without express
-prior written permission of the Licensor. Nothing in this License shall be deemed to
-grant any rights to trademarks, copyrights, patents, trade secrets or any other
-intellectual property of Licensor except as expressly stated herein. No patent
-license is granted to make, use, sell or offer to sell embodiments of any patent
-claims other than the licensed claims defined in Section 2. No right is granted to
-the trademarks of Licensor even if such marks are included in the Original Work.
-Nothing in this License shall be interpreted to prohibit Licensor from licensing under
-different terms from this License any Original Work that Licensor otherwise would have
-a right to license.
-
-5) This section intentionally omitted.
-
-6) Attribution Rights. You must retain, in the Source Code of any Derivative Works
-that You create, all copyright, patent or trademark notices from the Source Code of
-the Original Work, as well as any notices of licensing and any descriptive text
-identified therein as an "Attribution Notice." You must cause the Source Code for any
-Derivative Works that You create to carry a prominent Attribution Notice reasonably
-calculated to inform recipients that You have modified the Original Work.
-
-7) Warranty of Provenance and Disclaimer of Warranty. Licensor warrants that the
-copyright in and to the Original Work and the patent rights granted herein by Licensor
-are owned by the Licensor or are sublicensed to You under the terms of this License
-with the permission of the contributor(s) of those copyrights and patent rights.
-Except as expressly stated in the immediately proceeding sentence, the Original Work
-is provided under this License on an "AS IS" BASIS and WITHOUT WARRANTY, either
-express or implied, including, without limitation, the warranties of NON-INFRINGEMENT,
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
-QUALITY OF THE ORIGINAL WORK IS WITH YOU. This DISCLAIMER OF WARRANTY constitutes an
-essential part of this License. No license to Original Work is granted hereunder
-except under this disclaimer.
-
-8) Limitation of Liability. Under no circumstances and under no legal theory, whether
-in tort (including negligence), contract, or otherwise, shall the Licensor be liable
-to any person for any direct, indirect, special, incidental, or consequential damages
-of any character arising as a result of this License or the use of the Original Work
-including, without limitation, damages for loss of goodwill, work stoppage, computer
-failure or malfunction, or any and all other commercial damages or losses. This
-limitation of liability shall not apply to liability for death or personal injury
-resulting from Licensor`s negligence to the extent applicable law prohibits such
-limitation. Some jurisdictions do not allow the exclusion or limitation of incidental
-or consequential damages, so this exclusion and limitation may not apply to You.
-
-9) Acceptance and Termination. If You distribute copies of the Original Work or a
-Derivative Work, You must make a reasonable effort under the circumstances to obtain
-the express assent of recipients to the terms of this License. Nothing else but this
-License (or another written agreement between Licensor and You) grants You permission
-to create Derivative Works based upon the Original Work or to exercise any of the
-rights granted in Section 1 herein, and any attempt to do so except under the terms of
-this License (or another written agreement between Licensor and You) is expressly
-prohibited by U.S. copyright law, the equivalent laws of other countries, and by
-international treaty. Therefore, by exercising any of the rights granted to You in
-Section 1 herein, You indicate Your acceptance of this License and all of its terms
-and conditions.
-
-10) Termination for Patent Action. This License shall terminate automatically and You
-may no longer exercise any of the rights granted to You by this License as of the date
-You commence an action, including a cross-claim or counterclaim, for patent
-infringement (i) against Licensor with respect to a patent applicable to software or
-(ii) against any entity with respect to a patent applicable to the Original Work (but
-excluding combinations of the Original Work with other software or hardware).
-
-11) Jurisdiction, Venue and Governing Law. Any action or suit relating to this License
-may be brought only in the courts of a jurisdiction wherein the Licensor resides or in
-which Licensor conducts its primary business, and under the laws of that jurisdiction
-excluding its conflict-of-law provisions. The application of the United Nations
-Convention on Contracts for the International Sale of Goods is expressly excluded.
-Any use of the Original Work outside the scope of this License or after its
-termination shall be subject to the requirements and penalties of the U.S. Copyright
-Act, 17 U.S.C. ¤ 101 et seq., the equivalent laws of other countries, and
-international treaty. This section shall survive the termination of this License.
-
-12) Attorneys Fees. In any action to enforce the terms of this License or seeking
-damages relating thereto, the prevailing party shall be entitled to recover its costs
-and expenses, including, without limitation, reasonable attorneys` fees and costs
-incurred in connection with such action, including any appeal of such action. This
-section shall survive the termination of this License.
-
-13) Miscellaneous. This License represents the complete agreement concerning the
-subject matter hereof. If any provision of this License is held to be unenforceable,
-such provision shall be reformed only to the extent necessary to make it enforceable.
-
-14) Definition of "You" in This License. "You" throughout this License, whether in
-upper or lower case, means an individual or a legal entity exercising rights under,
-and complying with all of the terms of, this License. For legal entities, "You"
-includes any entity that controls, is controlled by, or is under common control with
-you. For purposes of this definition, "control" means (i) the power, direct or
-indirect, to cause the direction or management of such entity, whether by contract or
-otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares,
-or (iii) beneficial ownership of such entity.
-
-15) Right to Use. You may use the Original Work in all ways not otherwise restricted
-or conditioned by this License or by law, and Licensor promises not to interfere with
-or be responsible for such uses by You.
-
-This license is Copyright (C) 2003 Lawrence E. Rosen. All rights reserved.
-Permission is hereby granted to copy and distribute this license without modification.
-This license may not be modified without the express written permission of its
-copyright owner.
-
-
-
-
-AMD
-
-� 2005 Advanced Micro Devices, Inc. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that existing copyright notices
-are retained in all copies, this notice is included verbatim in any
-distributions, and the terms and conditions hererin are met.
-
-Use of the this software manifests acceptance of the terms of this
-license by performance.
-
-The name of Advanced Micro Devices, Inc. may not be used to endorse or
-promote products derived from this software without specific prior
-written permission.
-
-THIS SOFTWARE IS PROVIDED BY ADVANCED MICRO DEVICES, INC. "AS IS" AND ANY
-EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
-PURPOSE AND NON-INFRINGEMENT, OR THOSE ARISING FROM CUSTOM OF TRADE OR
-COURSE OF USAGE ARE DISCLAIMED.
-
-IN NO EVENT SHALL ADVANCED MICRO DEVICES, INC. BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED, AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE ITS DOCUMENTATION OR ANY DERIVATIVES
-THEREOF, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BY USING THIS
-SOFTWARE WITHOUT CHARGE, YOU ACCEPT THIS ALLOCATION OF RISK. THIS
-DISCLAIMER OF LIABILITY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE.
-ADVANCED MICRO DEVICES, INC. HAS NO OBLIGATION TO PROVIDE MAINTENANCE,
-SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS OF THIS SOFTWARE.
-
-In the redistribution and use of this software, each party shall at all
-times comply with all applicable governmental laws, statutes, ordinances,
-rules, regulations, orders, and other requirements, including without
-limitation such governmental requirements applicable to environmental
-protection, health, safety, wages, hours, equal employment opportunity,
-nondiscrimination, working conditions, import or export control, and
-transportation. Without limiting the foregoing, each party shall adhere
-to the U.S. Export Administration Regulations (EAR), currently found at
-15 C.F.R. Sections 730 through 744, and, unless properly authorized by
-the U.S. Government, shall not (1) export, re-export or release restricted
-technology, software, or source code to a national of a country in Country
-Groups D:1 or E:1, or (2) export to Country Groups D:1 or E:1 the direct
-product of such technology or software, if such foreign produced direct
-product is subject to national security controls as identified on the
-Commerce Control List (currently found in Supplement 1 to Section 774 of EAR).
-These export requirements shall survive any expiration or termination
-of this agreement.
-
-
-
-Apache-2.0
-
-
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don`t include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
-
-Artistic-1.0
-
-
-The Artistic License
-Preamble
-
-The intent of this document is to state the conditions under which a Package may be
-copied, such that the Copyright Holder maintains some semblance of artistic control
-over the development of the package, while giving the users of the package the right
-to use and distribute the Package in a more-or-less customary fashion, plus the right
-to make reasonable modifications.
-
-Definitions:
-
-"Package" refers to the collection of files distributed by the Copyright Holder, and
-derivatives of that collection of files created through textual modification.
-"Standard Version" refers to such a Package if it has not been modified, or has been
-modified in accordance with the wishes of the Copyright Holder.
-"Copyright Holder" is whoever is named in the copyright or copyrights for the package.
-"You" is you, if you`re thinking about copying or distributing this Package.
-"Reasonable copying fee" is whatever you can justify on the basis of media cost,
-duplication charges, time of people involved, and so on. (You will not be required to
-justify it to the Copyright Holder, but only to the computing community at large as a
-market that must bear the fee.)
-"Freely Available" means that no fee is charged for the item itself, though there may
-be fees involved in handling the item. It also means that recipients of the item may
-redistribute it under the same conditions they received it.
-1. You may make and give away verbatim copies of the source form of the Standard
-Version of this Package without restriction, provided that you duplicate all of the
-original copyright notices and associated disclaimers.
-
-2. You may apply bug fixes, portability fixes and other modifications derived from the
-Public Domain or from the Copyright Holder. A Package modified in such a way shall
-still be considered the Standard Version.
-
-3. You may otherwise modify your copy of this Package in any way, provided that you
-insert a prominent notice in each changed file stating how and when you changed that
-file, and provided that you do at least ONE of the following:
-
-a) place your modifications in the Public Domain or otherwise make them Freely
-Available, such as by posting said modifications to Usenet or an equivalent medium, or
-placing the modifications on a major archive site 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.
-
-4. You may distribute the programs of this Package in object code or executable form,
-provided that you do at least ONE of the following:
-
-a) distribute a Standard Version of the executables and library files, together with
-instructions (in the manual page or equivalent) on where to get the Standard Version.
-
-b) accompany the distribution with the machine-readable source of the Package with
-your modifications.
-
-c) accompany any non-standard executables with their corresponding Standard Version
-executables, giving the non-standard executables non-standard names, and clearly
-documenting the differences in manual pages (or equivalent), together with
-instructions on where to get the Standard Version.
-
-d) make other distribution arrangements with the Copyright Holder.
-
-5. You may charge a reasonable copying fee for any distribution of this Package. You
-may charge any fee you choose for support of this Package. You may not charge a fee
-for this Package itself. However, you may distribute this Package in aggregate with
-other (possibly commercial) programs as part of a larger (possibly commercial)
-software distribution provided that you do not advertise this Package as a product of
-your own.
-
-6. The scripts and library files supplied as input to or produced as output from the
-programs of this Package do not automatically fall under the copyright of this
-Package, but belong to whomever generated them, and may be sold commercially, and may
-be aggregated with this Package.
-
-7. C or perl subroutines supplied by you and linked into this Package shall not be
-considered part of this Package.
-
-8. The name of the Copyright Holder may not be used to endorse or promote products
-derived from this software without specific prior written permission.
-
-9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
-INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS
-FOR A PARTICULAR PURPOSE.
-
-The End
-
-
-
-
-Artistic-2.0
-
-
- The Artistic License 2.0
-
- Copyright (c) 2000-2006, The Perl Foundation.
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-Preamble
-
-This license establishes the terms under which a given free software
-Package may be copied, modified, distributed, and/or redistributed.
-The intent is that the Copyright Holder maintains some artistic
-control over the development of that Package while still keeping the
-Package available as open source and free software.
-
-You are always permitted to make arrangements wholly outside of this
-license directly with the Copyright Holder of a given Package. If the
-terms of this license do not permit the full use that you propose to
-make of the Package, you should contact the Copyright Holder and seek
-a different licensing arrangement.
-
-Definitions
-
- "Copyright Holder" means the individual(s) or organization(s)
- named in the copyright notice for the entire Package.
-
- "Contributor" means any party that has contributed code or other
- material to the Package, in accordance with the Copyright Holder`s
- procedures.
-
- "You" and "your" means any person who would like to copy,
- distribute, or modify the Package.
-
- "Package" means the collection of files distributed by the
- Copyright Holder, and derivatives of that collection and/or of
- those files. A given Package may consist of either the Standard
- Version, or a Modified Version.
-
- "Distribute" means providing a copy of the Package or making it
- accessible to anyone else, or in the case of a company or
- organization, to others outside of your company or organization.
-
- "Distributor Fee" means any fee that you charge for Distributing
- this Package or providing support for this Package to another
- party. It does not mean licensing fees.
-
- "Standard Version" refers to the Package if it has not been
- modified, or has been modified only in ways explicitly requested
- by the Copyright Holder.
-
- "Modified Version" means the Package, if it has been changed, and
- such changes were not explicitly requested by the Copyright
- Holder.
-
- "Original License" means this Artistic License as Distributed with
- the Standard Version of the Package, in its current version or as
- it may be modified by The Perl Foundation in the future.
-
- "Source" form means the source code, documentation source, and
- configuration files for the Package.
-
- "Compiled" form means the compiled bytecode, object code, binary,
- or any other form resulting from mechanical transformation or
- translation of the Source form.
-
-
-Permission for Use and Modification Without Distribution
-
-(1) You are permitted to use the Standard Version and create and use
-Modified Versions for any purpose without restriction, provided that
-you do not Distribute the Modified Version.
-
-
-Permissions for Redistribution of the Standard Version
-
-(2) You may Distribute verbatim copies of the Source form of the
-Standard Version of this Package in any medium without restriction,
-either gratis or for a Distributor Fee, provided that you duplicate
-all of the original copyright notices and associated disclaimers. At
-your discretion, such verbatim copies may or may not include a
-Compiled form of the Package.
-
-(3) You may apply any bug fixes, portability changes, and other
-modifications made available from the Copyright Holder. The resulting
-Package will still be considered the Standard Version, and as such
-will be subject to the Original License.
-
-
-Distribution of Modified Versions of the Package as Source
-
-(4) You may Distribute your Modified Version as Source (either gratis
-or for a Distributor Fee, and with or without a Compiled form of the
-Modified Version) provided that you clearly document how it differs
-from the Standard Version, including, but not limited to, documenting
-any non-standard features, executables, or modules, and provided that
-you do at least ONE of the following:
-
- (a) make the Modified Version available to the Copyright Holder
- of the Standard Version, under the Original License, so that the
- Copyright Holder may include your modifications in the Standard
- Version.
-
- (b) ensure that installation of your Modified Version does not
- prevent the user installing or running the Standard Version. In
- addition, the Modified Version must bear a name that is different
- from the name of the Standard Version.
-
- (c) allow anyone who receives a copy of the Modified Version to
- make the Source form of the Modified Version available to others
- under
-
- (i) the Original License or
-
- (ii) a license that permits the licensee to freely copy,
- modify and redistribute the Modified Version using the same
- licensing terms that apply to the copy that the licensee
- received, and requires that the Source form of the Modified
- Version, and of any works derived from it, be made freely
- available in that license fees are prohibited but Distributor
- Fees are allowed.
-
-
-Distribution of Compiled Forms of the Standard Version
-or Modified Versions without the Source
-
-(5) You may Distribute Compiled forms of the Standard Version without
-the Source, provided that you include complete instructions on how to
-get the Source of the Standard Version. Such instructions must be
-valid at the time of your distribution. If these instructions, at any
-time while you are carrying out such distribution, become invalid, you
-must provide new instructions on demand or cease further distribution.
-If you provide valid instructions or cease distribution within thirty
-days after you become aware that the instructions are invalid, then
-you do not forfeit any of your rights under this license.
-
-(6) You may Distribute a Modified Version in Compiled form without
-the Source, provided that you comply with Section 4 with respect to
-the Source of the Modified Version.
-
-
-Aggregating or Linking the Package
-
-(7) You may aggregate the Package (either the Standard Version or
-Modified Version) with other packages and Distribute the resulting
-aggregation provided that you do not charge a licensing fee for the
-Package. Distributor Fees are permitted, and licensing fees for other
-components in the aggregation are permitted. The terms of this license
-apply to the use and Distribution of the Standard or Modified Versions
-as included in the aggregation.
-
-(8) You are permitted to link Modified and Standard Versions with
-other works, to embed the Package in a larger work of your own, or to
-build stand-alone binary or bytecode versions of applications that
-include the Package, and Distribute the result without restriction,
-provided the result does not expose a direct interface to the Package.
-
-
-Items That are Not Considered Part of a Modified Version
-
-(9) Works (including, but not limited to, modules and scripts) that
-merely extend or make use of the Package, do not, by themselves, cause
-the Package to be a Modified Version. In addition, such works are not
-considered parts of the Package itself, and are not subject to the
-terms of this license.
-
-
-General Provisions
-
-(10) Any use, modification, and distribution of the Standard or
-Modified Versions is governed by this Artistic License. By using,
-modifying or distributing the Package, you accept this license. Do not
-use, modify, or distribute the Package, if you do not accept this
-license.
-
-(11) If your Modified Version has been derived from a Modified
-Version made by someone other than you, you are nevertheless required
-to ensure that your Modified Version complies with the requirements of
-this license.
-
-(12) This license does not grant you the right to use any trademark,
-service mark, tradename, or logo of the Copyright Holder.
-
-(13) This license includes the non-exclusive, worldwide,
-free-of-charge patent license to make, have made, use, offer to sell,
-sell, import and otherwise transfer the Package with respect to any
-patent claims licensable by the Copyright Holder that are necessarily
-infringed by the Package. If you institute patent litigation
-(including a cross-claim or counterclaim) against any party alleging
-that the Package constitutes direct or contributory patent
-infringement, then this Artistic License to you shall terminate on the
-date that such litigation is filed.
-
-(14) Disclaimer of Warranty:
-THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS
-IS` AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
-NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL
-LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL
-BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
-DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-BSD
-
-Copyright (c) The Regents of the University of California.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. Neither the name of the University nor the names of its contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-
-
-BSD-2-Clause
-
-
-The FreeBSD Copyright
-
-Copyright 1992-2010 The FreeBSD Project. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions of source code must retain the above copyright notice, this list of
-conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright notice, this list of
-conditions and the following disclaimer in the documentation and/or other materials
-provided with the distribution.
-THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS`` AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD
-PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-The views and conclusions contained in the software and documentation are those of the
-authors and should not be interpreted as representing official policies, either
-expressed or implied, of the FreeBSD Project.
-
-
-
-
-BSD-3-Clause
-
-
-Copyright (c) <YEAR>, <OWNER>
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions of source code must retain the above copyright notice, this list of
-conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright notice, this list of
-conditions and the following disclaimer in the documentation and/or other materials
-provided with the distribution.
-Neither the name of the <ORGANIZATION> nor the names of its contributors may be
-used to endorse or promote products derived from this software without specific prior
-written permission.
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
-EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
-SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
-TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
-WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGE.
-
-
-
-
-BSD-4-Clause
-
-
-Copyright (c) <year>, <copyright holder>
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. All advertising materials mentioning features or use of this software
- must display the following acknowledgement:
- This product includes software developed by the <organization>.
-4. Neither the name of the <organization> nor the
- names of its contributors may be used to endorse or promote products
- derived from this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY <COPYRIGHT HOLDER> ``AS IS`` AND ANY
-EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
-DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
-ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-BSL-1.0
-
-
-Boost Software License - Version 1.0 - August 17th, 2003
-
-Permission is hereby granted, free of charge, to any person or organization
-obtaining a copy of the software and accompanying documentation covered by
-this license (the "Software") to use, reproduce, display, distribute,
-execute, and transmit the Software, and to prepare derivative works of the
-Software, and to permit third-parties to whom the Software is furnished to
-do so, all subject to the following:
-
-The copyright notices in the Software and this entire statement, including
-the above license grant, this restriction and the following disclaimer,
-must be included in all copies of the Software, in whole or in part, and
-all derivative works of the Software, unless such copies or derivative
-works are solely in the form of machine-executable object code generated by
-a source language processor.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
-SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
-FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
-ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
-DEALINGS IN THE SOFTWARE.
-
-
-
-
-CC-BY-4.0
-
-Attribution 4.0 International
-
-=======================================================================
-
-Creative Commons Corporation ("Creative Commons") is not a law firm and
-does not provide legal services or legal advice. Distribution of
-Creative Commons public licenses does not create a lawyer-client or
-other relationship. Creative Commons makes its licenses and related
-information available on an "as-is" basis. Creative Commons gives no
-warranties regarding its licenses, any material licensed under their
-terms and conditions, or any related information. Creative Commons
-disclaims all liability for damages resulting from their use to the
-fullest extent possible.
-
-Using Creative Commons Public Licenses
-
-Creative Commons public licenses provide a standard set of terms and
-conditions that creators and other rights holders may use to share
-original works of authorship and other material subject to copyright
-and certain other rights specified in the public license below. The
-following considerations are for informational purposes only, are not
-exhaustive, and do not form part of our licenses.
-
- Considerations for licensors: Our public licenses are
- intended for use by those authorized to give the public
- permission to use material in ways otherwise restricted by
- copyright and certain other rights. Our licenses are
- irrevocable. Licensors should read and understand the terms
- and conditions of the license they choose before applying it.
- Licensors should also secure all rights necessary before
- applying our licenses so that the public can reuse the
- material as expected. Licensors should clearly mark any
- material not subject to the license. This includes other CC-
- licensed material, or material used under an exception or
- limitation to copyright. More considerations for licensors:
- wiki.creativecommons.org/Considerations_for_licensors
-
- Considerations for the public: By using one of our public
- licenses, a licensor grants the public permission to use the
- licensed material under specified terms and conditions. If
- the licensor's permission is not necessary for any reason--for
- example, because of any applicable exception or limitation to
- copyright--then that use is not regulated by the license. Our
- licenses grant only permissions under copyright and certain
- other rights that a licensor has authority to grant. Use of
- the licensed material may still be restricted for other
- reasons, including because others have copyright or other
- rights in the material. A licensor may make special requests,
- such as asking that all changes be marked or described.
- Although not required by our licenses, you are encouraged to
- respect those requests where reasonable. More_considerations
- for the public:
- wiki.creativecommons.org/Considerations_for_licensees
-
-=======================================================================
-
-Creative Commons Attribution 4.0 International Public License
-
-By exercising the Licensed Rights (defined below), You accept and agree
-to be bound by the terms and conditions of this Creative Commons
-Attribution 4.0 International Public License ("Public License"). To the
-extent this Public License may be interpreted as a contract, You are
-granted the Licensed Rights in consideration of Your acceptance of
-these terms and conditions, and the Licensor grants You such rights in
-consideration of benefits the Licensor receives from making the
-Licensed Material available under these terms and conditions.
-
-
-Section 1 -- Definitions.
-
- a. Adapted Material means material subject to Copyright and Similar
- Rights that is derived from or based upon the Licensed Material
- and in which the Licensed Material is translated, altered,
- arranged, transformed, or otherwise modified in a manner requiring
- permission under the Copyright and Similar Rights held by the
- Licensor. For purposes of this Public License, where the Licensed
- Material is a musical work, performance, or sound recording,
- Adapted Material is always produced where the Licensed Material is
- synched in timed relation with a moving image.
-
- b. Adapter's License means the license You apply to Your Copyright
- and Similar Rights in Your contributions to Adapted Material in
- accordance with the terms and conditions of this Public License.
-
- c. Copyright and Similar Rights means copyright and/or similar rights
- closely related to copyright including, without limitation,
- performance, broadcast, sound recording, and Sui Generis Database
- Rights, without regard to how the rights are labeled or
- categorized. For purposes of this Public License, the rights
- specified in Section 2(b)(1)-(2) are not Copyright and Similar
- Rights.
-
- d. Effective Technological Measures means those measures that, in the
- absence of proper authority, may not be circumvented under laws
- fulfilling obligations under Article 11 of the WIPO Copyright
- Treaty adopted on December 20, 1996, and/or similar international
- agreements.
-
- e. Exceptions and Limitations means fair use, fair dealing, and/or
- any other exception or limitation to Copyright and Similar Rights
- that applies to Your use of the Licensed Material.
-
- f. Licensed Material means the artistic or literary work, database,
- or other material to which the Licensor applied this Public
- License.
-
- g. Licensed Rights means the rights granted to You subject to the
- terms and conditions of this Public License, which are limited to
- all Copyright and Similar Rights that apply to Your use of the
- Licensed Material and that the Licensor has authority to license.
-
- h. Licensor means the individual(s) or entity(ies) granting rights
- under this Public License.
-
- i. Share means to provide material to the public by any means or
- process that requires permission under the Licensed Rights, such
- as reproduction, public display, public performance, distribution,
- dissemination, communication, or importation, and to make material
- available to the public including in ways that members of the
- public may access the material from a place and at a time
- individually chosen by them.
-
- j. Sui Generis Database Rights means rights other than copyright
- resulting from Directive 96/9/EC of the European Parliament and of
- the Council of 11 March 1996 on the legal protection of databases,
- as amended and/or succeeded, as well as other essentially
- equivalent rights anywhere in the world.
-
- k. You means the individual or entity exercising the Licensed Rights
- under this Public License. Your has a corresponding meaning.
-
-
-Section 2 -- Scope.
-
- a. License grant.
-
- 1. Subject to the terms and conditions of this Public License,
- the Licensor hereby grants You a worldwide, royalty-free,
- non-sublicensable, non-exclusive, irrevocable license to
- exercise the Licensed Rights in the Licensed Material to:
-
- a. reproduce and Share the Licensed Material, in whole or
- in part; and
-
- b. produce, reproduce, and Share Adapted Material.
-
- 2. Exceptions and Limitations. For the avoidance of doubt, where
- Exceptions and Limitations apply to Your use, this Public
- License does not apply, and You do not need to comply with
- its terms and conditions.
-
- 3. Term. The term of this Public License is specified in Section
- 6(a).
-
- 4. Media and formats; technical modifications allowed. The
- Licensor authorizes You to exercise the Licensed Rights in
- all media and formats whether now known or hereafter created,
- and to make technical modifications necessary to do so. The
- Licensor waives and/or agrees not to assert any right or
- authority to forbid You from making technical modifications
- necessary to exercise the Licensed Rights, including
- technical modifications necessary to circumvent Effective
- Technological Measures. For purposes of this Public License,
- simply making modifications authorized by this Section 2(a)
- (4) never produces Adapted Material.
-
- 5. Downstream recipients.
-
- a. Offer from the Licensor -- Licensed Material. Every
- recipient of the Licensed Material automatically
- receives an offer from the Licensor to exercise the
- Licensed Rights under the terms and conditions of this
- Public License.
-
- b. No downstream restrictions. You may not offer or impose
- any additional or different terms or conditions on, or
- apply any Effective Technological Measures to, the
- Licensed Material if doing so restricts exercise of the
- Licensed Rights by any recipient of the Licensed
- Material.
-
- 6. No endorsement. Nothing in this Public License constitutes or
- may be construed as permission to assert or imply that You
- are, or that Your use of the Licensed Material is, connected
- with, or sponsored, endorsed, or granted official status by,
- the Licensor or others designated to receive attribution as
- provided in Section 3(a)(1)(A)(i).
-
- b. Other rights.
-
- 1. Moral rights, such as the right of integrity, are not
- licensed under this Public License, nor are publicity,
- privacy, and/or other similar personality rights; however, to
- the extent possible, the Licensor waives and/or agrees not to
- assert any such rights held by the Licensor to the limited
- extent necessary to allow You to exercise the Licensed
- Rights, but not otherwise.
-
- 2. Patent and trademark rights are not licensed under this
- Public License.
-
- 3. To the extent possible, the Licensor waives any right to
- collect royalties from You for the exercise of the Licensed
- Rights, whether directly or through a collecting society
- under any voluntary or waivable statutory or compulsory
- licensing scheme. In all other cases the Licensor expressly
- reserves any right to collect such royalties.
-
-
-Section 3 -- License Conditions.
-
-Your exercise of the Licensed Rights is expressly made subject to the
-following conditions.
-
- a. Attribution.
-
- 1. If You Share the Licensed Material (including in modified
- form), You must:
-
- a. retain the following if it is supplied by the Licensor
- with the Licensed Material:
-
- i. identification of the creator(s) of the Licensed
- Material and any others designated to receive
- attribution, in any reasonable manner requested by
- the Licensor (including by pseudonym if
- designated);
-
- ii. a copyright notice;
-
- iii. a notice that refers to this Public License;
-
- iv. a notice that refers to the disclaimer of
- warranties;
-
- v. a URI or hyperlink to the Licensed Material to the
- extent reasonably practicable;
-
- b. indicate if You modified the Licensed Material and
- retain an indication of any previous modifications; and
-
- c. indicate the Licensed Material is licensed under this
- Public License, and include the text of, or the URI or
- hyperlink to, this Public License.
-
- 2. You may satisfy the conditions in Section 3(a)(1) in any
- reasonable manner based on the medium, means, and context in
- which You Share the Licensed Material. For example, it may be
- reasonable to satisfy the conditions by providing a URI or
- hyperlink to a resource that includes the required
- information.
-
- 3. If requested by the Licensor, You must remove any of the
- information required by Section 3(a)(1)(A) to the extent
- reasonably practicable.
-
- 4. If You Share Adapted Material You produce, the Adapter's
- License You apply must not prevent recipients of the Adapted
- Material from complying with this Public License.
-
-
-Section 4 -- Sui Generis Database Rights.
-
-Where the Licensed Rights include Sui Generis Database Rights that
-apply to Your use of the Licensed Material:
-
- a. for the avoidance of doubt, Section 2(a)(1) grants You the right
- to extract, reuse, reproduce, and Share all or a substantial
- portion of the contents of the database;
-
- b. if You include all or a substantial portion of the database
- contents in a database in which You have Sui Generis Database
- Rights, then the database in which You have Sui Generis Database
- Rights (but not its individual contents) is Adapted Material; and
-
- c. You must comply with the conditions in Section 3(a) if You Share
- all or a substantial portion of the contents of the database.
-
-For the avoidance of doubt, this Section 4 supplements and does not
-replace Your obligations under this Public License where the Licensed
-Rights include other Copyright and Similar Rights.
-
-
-Section 5 -- Disclaimer of Warranties and Limitation of Liability.
-
- a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
- EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
- AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
- ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
- IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
- WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
- PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
- ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
- KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
- ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
-
- b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
- TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
- NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
- INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
- COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
- USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
- ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
- DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
- IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
-
- c. The disclaimer of warranties and limitation of liability provided
- above shall be interpreted in a manner that, to the extent
- possible, most closely approximates an absolute disclaimer and
- waiver of all liability.
-
-
-Section 6 -- Term and Termination.
-
- a. This Public License applies for the term of the Copyright and
- Similar Rights licensed here. However, if You fail to comply with
- this Public License, then Your rights under this Public License
- terminate automatically.
-
- b. Where Your right to use the Licensed Material has terminated under
- Section 6(a), it reinstates:
-
- 1. automatically as of the date the violation is cured, provided
- it is cured within 30 days of Your discovery of the
- violation; or
-
- 2. upon express reinstatement by the Licensor.
-
- For the avoidance of doubt, this Section 6(b) does not affect any
- right the Licensor may have to seek remedies for Your violations
- of this Public License.
-
- c. For the avoidance of doubt, the Licensor may also offer the
- Licensed Material under separate terms or conditions or stop
- distributing the Licensed Material at any time; however, doing so
- will not terminate this Public License.
-
- d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
- License.
-
-
-Section 7 -- Other Terms and Conditions.
-
- a. The Licensor shall not be bound by any additional or different
- terms or conditions communicated by You unless expressly agreed.
-
- b. Any arrangements, understandings, or agreements regarding the
- Licensed Material not stated herein are separate from and
- independent of the terms and conditions of this Public License.
-
-
-Section 8 -- Interpretation.
-
- a. For the avoidance of doubt, this Public License does not, and
- shall not be interpreted to, reduce, limit, restrict, or impose
- conditions on any use of the Licensed Material that could lawfully
- be made without permission under this Public License.
-
- b. To the extent possible, if any provision of this Public License is
- deemed unenforceable, it shall be automatically reformed to the
- minimum extent necessary to make it enforceable. If the provision
- cannot be reformed, it shall be severed from this Public License
- without affecting the enforceability of the remaining terms and
- conditions.
-
- c. No term or condition of this Public License will be waived and no
- failure to comply consented to unless expressly agreed to by the
- Licensor.
-
- d. Nothing in this Public License constitutes or may be interpreted
- as a limitation upon, or waiver of, any privileges and immunities
- that apply to the Licensor or You, including from the legal
- processes of any jurisdiction or authority.
-
-
-=======================================================================
-
-Creative Commons is not a party to its public
-licenses. Notwithstanding, Creative Commons may elect to apply one of
-its public licenses to material it publishes and in those instances
-will be considered the ”Licensor.” The text of the Creative Commons
-public licenses is dedicated to the public domain under the CC0 Public
-Domain Dedication. Except for the limited purpose of indicating that
-material is shared under a Creative Commons public license or as
-otherwise permitted by the Creative Commons policies published at
-creativecommons.org/policies, Creative Commons does not authorize the
-use of the trademark "Creative Commons" or any other trademark or logo
-of Creative Commons without its prior written consent including,
-without limitation, in connection with any unauthorized modifications
-to any of its public licenses or any other arrangements,
-understandings, or agreements concerning use of licensed material. For
-the avoidance of doubt, this paragraph does not form part of the
-public licenses.
-
-Creative Commons may be contacted at creativecommons.org.
-
-
-
-CDDL-1.0
-
-
-COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
-Version 1.0
-1. Definitions.
-
-1.1. “Contributor” means each individual or entity that creates or
-contributes to the creation of Modifications.
-
-1.2. “Contributor Version” means the combination of the Original
-Software, prior Modifications used by a Contributor (if any), and the Modifications
-made by that particular Contributor.
-
-1.3. “Covered Software” means (a) the Original Software, or (b)
-Modifications, or (c) the combination of files containing Original Software with files
-containing Modifications, in each case including portions thereof.
-
-1.4. “Executable” means the Covered Software in any form other
-than Source Code.
-
-1.5. “Initial Developer” means the individual or entity that first
-makes Original Software available under this License.
-
-1.6. “Larger Work” means a work which combines Covered Software or
-portions thereof with code not governed by the terms of this License.
-
-1.7. “License” means this document.
-
-1.8. “Licensable” means having the right to grant, to the maximum
-extent possible, whether at the time of the initial grant or subsequently acquired,
-any and all of the rights conveyed herein.
-
-1.9. “Modifications” means the Source Code and Executable form of
-any of the following:
-
-A. Any file that results from an addition to, deletion from or modification of the
-contents of a file containing Original Software or previous Modifications;
-
-B. Any new file that contains any part of the Original Software or previous
-Modification; or
-
-C. Any new file that is contributed or otherwise made available under the terms of
-this License.
-
-1.10. “Original Software” means the Source Code and Executable
-form of computer software code that is originally released under this License.
-
-1.11. “Patent Claims” means any patent claim(s), now owned or
-hereafter acquired, including without limitation, method, process, and apparatus
-claims, in any patent Licensable by grantor.
-
-1.12. “Source Code” means (a) the common form of computer software
-code in which modifications are made and (b) associated documentation included in or
-with such code.
-
-1.13. “You” (or “Your”) means an individual or
-a legal entity exercising rights under, and complying with all of the terms of, this
-License. For legal entities, “You” includes any entity which
-controls, is controlled by, or is under common control with You. For purposes of this
-definition, “control” means (a) the power, direct or indirect, to
-cause the direction or management of such entity, whether by contract or otherwise, or
-(b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial
-ownership of such entity.
-
-2. License Grants.
-
-2.1. The Initial Developer Grant.
-
-Conditioned upon Your compliance with Section 3.1 below and subject to third party
-intellectual property claims, the Initial Developer hereby grants You a world-wide,
-royalty-free, non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark) Licensable by
-Initial Developer, to use, reproduce, modify, display, perform, sublicense and
-distribute the Original Software (or portions thereof), with or without Modifications,
-and/or as part of a Larger Work; and
-
-(b) under Patent Claims infringed by the making, using or selling of Original
-Software, to make, have made, use, practice, sell, and offer for sale, and/or
-otherwise dispose of the Original Software (or portions thereof).
-
-(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial
-Developer first distributes or otherwise makes the Original Software available to a
-third party under the terms of this License.
-
-(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code
-that You delete from the Original Software, or (2) for infringements caused by: (i)
-the modification of the Original Software, or (ii) the combination of the Original
-Software with other software or devices.
-
-2.2. Contributor Grant.
-
-Conditioned upon Your compliance with Section 3.1 below and subject to third party
-intellectual property claims, each Contributor hereby grants You a world-wide,
-royalty-free, non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark) Licensable by
-Contributor to use, reproduce, modify, display, perform, sublicense and distribute the
-Modifications created by such Contributor (or portions thereof), either on an
-unmodified basis, with other Modifications, as Covered Software and/or as part of a
-Larger Work; and
-
-(b) under Patent Claims infringed by the making, using, or selling of Modifications
-made by that Contributor either alone and/or in combination with its Contributor
-Version (or portions of such combination), to make, use, sell, offer for sale, have
-made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or
-portions thereof); and (2) the combination of Modifications made by that Contributor
-with its Contributor Version (or portions of such combination).
-
-(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
-Contributor first distributes or otherwise makes the Modifications available to a
-third party.
-
-(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any
-code that Contributor has deleted from the Contributor Version; (2) for infringements
-caused by: (i) third party modifications of Contributor Version, or (ii) the
-combination of Modifications made by that Contributor with other software (except as
-part of the Contributor Version) or other devices; or (3) under Patent Claims
-infringed by Covered Software in the absence of Modifications made by that
-Contributor.
-
-3. Distribution Obligations.
-
-3.1. Availability of Source Code.
-
-Any Covered Software that You distribute or otherwise make available in Executable
-form must also be made available in Source Code form and that Source Code form must be
-distributed only under the terms of this License. You must include a copy of this
-License with every copy of the Source Code form of the Covered Software You distribute
-or otherwise make available. You must inform recipients of any such Covered Software
-in Executable form as to how they can obtain such Covered Software in Source Code form
-in a reasonable manner on or through a medium customarily used for software exchange.
-
-3.2. Modifications.
-
-The Modifications that You create or to which You contribute are governed by the terms
-of this License. You represent that You believe Your Modifications are Your original
-creation(s) and/or You have sufficient rights to grant the rights conveyed by this
-License.
-
-3.3. Required Notices.
-
-You must include a notice in each of Your Modifications that identifies You as the
-Contributor of the Modification. You may not remove or alter any copyright, patent or
-trademark notices contained within the Covered Software, or any notices of licensing
-or any descriptive text giving attribution to any Contributor or the Initial
-Developer.
-
-3.4. Application of Additional Terms.
-
-You may not offer or impose any terms on any Covered Software in Source Code form that
-alters or restricts the applicable version of this License or the
-recipients’ rights hereunder. You may choose to offer, and to charge a fee
-for, warranty, support, indemnity or liability obligations to one or more recipients
-of Covered Software. However, you may do so only on Your own behalf, and not on behalf
-of the Initial Developer or any Contributor. You must make it absolutely clear that
-any such warranty, support, indemnity or liability obligation is offered by You alone,
-and You hereby agree to indemnify the Initial Developer and every Contributor for any
-liability incurred by the Initial Developer or such Contributor as a result of
-warranty, support, indemnity or liability terms You offer.
-
-3.5. Distribution of Executable Versions.
-
-You may distribute the Executable form of the Covered Software under the terms of this
-License or under the terms of a license of Your choice, which may contain terms
-different from this License, provided that You are in compliance with the terms of
-this License and that the license for the Executable form does not attempt to limit or
-alter the recipient’s rights in the Source Code form from the rights set
-forth in this License. If You distribute the Covered Software in Executable form under
-a different license, You must make it absolutely clear that any terms which differ
-from this License are offered by You alone, not by the Initial Developer or
-Contributor. You hereby agree to indemnify the Initial Developer and every Contributor
-for any liability incurred by the Initial Developer or such Contributor as a result of
-any such terms You offer.
-
-3.6. Larger Works.
-
-You may create a Larger Work by combining Covered Software with other code not
-governed by the terms of this License and distribute the Larger Work as a single
-product. In such a case, You must make sure the requirements of this License are
-fulfilled for the Covered Software.
-
-4. Versions of the License.
-
-4.1. New Versions.
-
-Sun Microsystems, Inc. is the initial license steward and may publish revised and/or
-new versions of this License from time to time. Each version will be given a
-distinguishing version number. Except as provided in Section 4.3, no one other than
-the license steward has the right to modify this License.
-
-4.2. Effect of New Versions.
-
-You may always continue to use, distribute or otherwise make the Covered Software
-available under the terms of the version of the License under which You originally
-received the Covered Software. If the Initial Developer includes a notice in the
-Original Software prohibiting it from being distributed or otherwise made available
-under any subsequent version of the License, You must distribute and make the Covered
-Software available under the terms of the version of the License under which You
-originally received the Covered Software. Otherwise, You may also choose to use,
-distribute or otherwise make the Covered Software available under the terms of any
-subsequent version of the License published by the license steward.
-
-4.3. Modified Versions.
-
-When You are an Initial Developer and You want to create a new license for Your
-Original Software, You may create and use a modified version of this License if You:
-(a) rename the license and remove any references to the name of the license steward
-(except to note that the license differs from this License); and (b) otherwise make it
-clear that the license contains terms which differ from this License.
-
-5. DISCLAIMER OF WARRANTY.
-
-COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS”
-BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
-LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT
-FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
-PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
-DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR)
-ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
-WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE
-IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
-
-6. TERMINATION.
-
-6.1. This License and the rights granted hereunder will terminate automatically if You
-fail to comply with terms herein and fail to cure such breach within 30 days of
-becoming aware of the breach. Provisions which, by their nature, must remain in effect
-beyond the termination of this License shall survive.
-
-6.2. If You assert a patent infringement claim (excluding declaratory judgment
-actions) against Initial Developer or a Contributor (the Initial Developer or
-Contributor against whom You assert such claim is referred to as
-“Participant”) alleging that the Participant Software (meaning the
-Contributor Version where the Participant is a Contributor or the Original Software
-where the Participant is the Initial Developer) directly or indirectly infringes any
-patent, then any and all rights granted directly or indirectly to You by such
-Participant, the Initial Developer (if the Initial Developer is not the Participant)
-and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days
-notice from Participant terminate prospectively and automatically at the expiration of
-such 60 day notice period, unless if within such 60 day period You withdraw Your claim
-with respect to the Participant Software against such Participant either unilaterally
-or pursuant to a written agreement with Participant.
-
-6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user
-licenses that have been validly granted by You or any distributor hereunder prior to
-termination (excluding licenses granted to You by any distributor) shall survive
-termination.
-
-7. LIMITATION OF LIABILITY.
-
-UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
-CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR
-ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE
-TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
-CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,
-WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL
-DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF
-SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
-PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EXTENT
-APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
-EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
-LIMITATION MAY NOT APPLY TO YOU.
-
-8. U.S. GOVERNMENT END USERS.
-
-The Covered Software is a “commercial item,” as that term is
-defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of “commercial computer
-software” (as that term is defined at 48 C.F.R. §
-252.227-7014(a)(1)) and “commercial computer software
-documentation” as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
-Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
-1995), all U.S. Government End Users acquire Covered Software with only those rights
-set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes,
-any other FAR, DFAR, or other clause or provision that addresses Government rights in
-computer software under this License.
-
-9. MISCELLANEOUS.
-
-This License represents the complete agreement concerning subject matter hereof. If
-any provision of this License is held to be unenforceable, such provision shall be
-reformed only to the extent necessary to make it enforceable. This License shall be
-governed by the law of the jurisdiction specified in a notice contained within the
-Original Software (except to the extent applicable law, if any, provides otherwise),
-excluding such jurisdiction’s conflict-of-law provisions. Any litigation
-relating to this License shall be subject to the jurisdiction of the courts located in
-the jurisdiction and venue specified in a notice contained within the Original
-Software, with the losing party responsible for costs, including, without limitation,
-court costs and reasonable attorneys’ fees and expenses. The application of
-the United Nations Convention on Contracts for the International Sale of Goods is
-expressly excluded. Any law or regulation which provides that the language of a
-contract shall be construed against the drafter shall not apply to this License. You
-agree that You alone are responsible for compliance with the United States export
-administration regulations (and the export control laws and regulation of any other
-countries) when You use, distribute or otherwise make available any Covered Software.
-
-10. RESPONSIBILITY FOR CLAIMS.
-
-As between Initial Developer and the Contributors, each party is responsible for
-claims and damages arising, directly or indirectly, out of its utilization of rights
-under this License and You agree to work with Initial Developer and Contributors to
-distribute such responsibility on an equitable basis. Nothing herein is intended or
-shall be deemed to constitute any admission of liability.
-
-
-
-
-CDS
-
-This software is copyrighted by Cadence Design Systems, Inc., and other
-parties. The following terms apply to all files associated with the
-software unless explicitly disclaimed in individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
------------------------------------------------------------------------
- Following is the original agreement for the Tcl/Tk software from
- Sun Microsystems.
------------------------------------------------------------------------
-
-This software is copyrighted by the Regents of the University of
-California, Sun Microsystems, Inc., and other parties. The following
-terms apply to all files associated with the software unless explicitly
-disclaimed in individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
-
-
-CPL-1.0
-
-
-Common Public License Version 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
-LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
-CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-
-"Contribution" means:
-
-a) in the case of the initial Contributor, the initial code and
-documentation distributed under this Agreement, and
-
-b) in the case of each subsequent Contributor:
-
-i) changes to the Program, and
-
-ii) additions to the Program;
-
-where such changes and/or additions to the Program originate from and are
-distributed by that particular Contributor. A Contribution `originates` from a
-Contributor if it was added to the Program by such Contributor itself or anyone
-acting on such Contributor`s behalf. Contributions do not include additions to
-the Program which: (i) are separate modules of software distributed in
-conjunction with the Program under their own license agreement, and (ii) are not
-derivative works of the Program.
-
-"Contributor" means any person or entity that distributes the Program.
-
-"Licensed Patents " mean patent claims licensable by a Contributor which are
-necessarily infringed by the use or sale of its Contribution alone or when
-combined with the Program.
-
-"Program" means the Contributions distributed in accordance with this Agreement.
-
-"Recipient" means anyone who receives the Program under this Agreement,
-including all Contributors.
-
-2. GRANT OF RIGHTS
-
-a) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free copyright license to
-reproduce, prepare derivative works of, publicly display, publicly perform,
-distribute and sublicense the Contribution of such Contributor, if any, and such
-derivative works, in source code and object code form.
-
-b) Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
-Patents to make, use, sell, offer to sell, import and otherwise transfer the
-Contribution of such Contributor, if any, in source code and object code form.
-This patent license shall apply to the combination of the Contribution and the
-Program if, at the time the Contribution is added by the Contributor, such
-addition of the Contribution causes such combination to be covered by the
-Licensed Patents. The patent license shall not apply to any other combinations
-which include the Contribution. No hardware per se is licensed hereunder.
-
-c) Recipient understands that although each Contributor grants the licenses
-to its Contributions set forth herein, no assurances are provided by any
-Contributor that the Program does not infringe the patent or other intellectual
-property rights of any other entity. Each Contributor disclaims any liability to
-Recipient for claims brought by any other entity based on infringement of
-intellectual property rights or otherwise. As a condition to exercising the
-rights and licenses granted hereunder, each Recipient hereby assumes sole
-responsibility to secure any other intellectual property rights needed, if any.
-For example, if a third party patent license is required to allow Recipient to
-distribute the Program, it is Recipient`s responsibility to acquire that license
-before distributing the Program.
-
-d) Each Contributor represents that to its knowledge it has sufficient
-copyright rights in its Contribution, if any, to grant the copyright license set
-forth in this Agreement.
-
-3. REQUIREMENTS
-
-A Contributor may choose to distribute the Program in object code form under its
-own license agreement, provided that:
-
-a) it complies with the terms and conditions of this Agreement; and
-
-b) its license agreement:
-
-i) effectively disclaims on behalf of all Contributors all warranties and
-conditions, express and implied, including warranties or conditions of title and
-non-infringement, and implied warranties or conditions of merchantability and
-fitness for a particular purpose;
-
-ii) effectively excludes on behalf of all Contributors all liability for
-damages, including direct, indirect, special, incidental and consequential
-damages, such as lost profits;
-
-iii) states that any provisions which differ from this Agreement are offered
-by that Contributor alone and not by any other party; and
-
-iv) states that source code for the Program is available from such
-Contributor, and informs licensees how to obtain it in a reasonable manner on or
-through a medium customarily used for software exchange.
-
-When the Program is made available in source code form:
-
-a) it must be made available under this Agreement; and
-
-b) a copy of this Agreement must be included with each copy of the Program.
-
-Contributors may not remove or alter any copyright notices contained within the
-Program.
-
-Each Contributor must identify itself as the originator of its Contribution, if
-any, in a manner that reasonably allows subsequent Recipients to identify the
-originator of the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-
-Commercial distributors of software may accept certain responsibilities with
-respect to end users, business partners and the like. While this license is
-intended to facilitate the commercial use of the Program, the Contributor who
-includes the Program in a commercial product offering should do so in a manner
-which does not create potential liability for other Contributors. Therefore, if
-a Contributor includes the Program in a commercial product offering, such
-Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
-every other Contributor ("Indemnified Contributor") against any losses, damages
-and costs (collectively "Losses") arising from claims, lawsuits and other legal
-actions brought by a third party against the Indemnified Contributor to the
-extent caused by the acts or omissions of such Commercial Contributor in
-connection with its distribution of the Program in a commercial product
-offering. The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement. In order
-to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
-Contributor in writing of such claim, and b) allow the Commercial Contributor to
-control, and cooperate with the Commercial Contributor in, the defense and any
-related settlement negotiations. The Indemnified Contributor may participate in
-any such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial product
-offering, Product X. That Contributor is then a Commercial Contributor. If that
-Commercial Contributor then makes performance claims, or offers warranties
-related to Product X, those performance claims and warranties are such
-Commercial Contributor`s responsibility alone. Under this section, the
-Commercial Contributor would have to defend claims against the other
-Contributors related to those performance claims and warranties, and if a court
-requires any other Contributor to pay any damages as a result, the Commercial
-Contributor must pay those damages.
-
-5. NO WARRANTY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
-IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
-NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
-Recipient is solely responsible for determining the appropriateness of using and
-distributing the Program and assumes all risks associated with its exercise of
-rights under this Agreement, including but not limited to the risks and costs of
-program errors, compliance with applicable laws, damage to or loss of data,
-programs or equipment, and unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
-CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
-PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
-STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
-GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-
-If any provision of this Agreement is invalid or unenforceable under applicable
-law, it shall not affect the validity or enforceability of the remainder of the
-terms of this Agreement, and without further action by the parties hereto, such
-provision shall be reformed to the minimum extent necessary to make such
-provision valid and enforceable.
-
-If Recipient institutes patent litigation against a Contributor with respect to
-a patent applicable to software (including a cross-claim or counterclaim in a
-lawsuit), then any patent licenses granted by that Contributor to such Recipient
-under this Agreement shall terminate as of the date such litigation is filed. In
-addition, if Recipient institutes patent litigation against any entity
-(including a cross-claim or counterclaim in a lawsuit) alleging that the Program
-itself (excluding combinations of the Program with other software or hardware)
-infringes such Recipient`s patent(s), then such Recipient`s rights granted under
-Section 2(b) shall terminate as of the date such litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it fails to
-comply with any of the material terms or conditions of this Agreement and does
-not cure such failure in a reasonable period of time after becoming aware of
-such noncompliance. If all Recipient`s rights under this Agreement terminate,
-Recipient agrees to cease use and distribution of the Program as soon as
-reasonably practicable. However, Recipient`s obligations under this Agreement
-and any licenses granted by Recipient relating to the Program shall continue and
-survive.
-
-Everyone is permitted to copy and distribute copies of this Agreement, but in
-order to avoid inconsistency the Agreement is copyrighted and may only be
-modified in the following manner. The Agreement Steward reserves the right to
-publish new versions (including revisions) of this Agreement from time to time.
-No one other than the Agreement Steward has the right to modify this Agreement.
-IBM is the initial Agreement Steward. IBM may assign the responsibility to serve
-as the Agreement Steward to a suitable separate entity. Each new version of the
-Agreement will be given a distinguishing version number. The Program (including
-Contributions) may always be distributed subject to the version of the Agreement
-under which it was received. In addition, after a new version of the Agreement
-is published, Contributor may elect to distribute the Program (including its
-Contributions) under the new version. Except as expressly stated in Sections
-2(a) and 2(b) above, Recipient receives no rights or licenses to the
-intellectual property of any Contributor under this Agreement, whether
-expressly, by implication, estoppel or otherwise. All rights in the Program not
-expressly granted under this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and the
-intellectual property laws of the United States of America. No party to this
-Agreement will bring a legal action under this Agreement more than one year
-after the cause of action arose. Each party waives its rights to a jury trial in
-any resulting litigation.
-
-
-
-
-CUP
-
-CUP PARSER GENERATOR COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
-
-Copyright 1996 by Scott Hudson, Frank Flannery, C. Scott Ananian
-
-Permission to use, copy, modify, and distribute this software and its
-documentation for any purpose and without fee is hereby granted,
-provided that the above copyright notice appear in all copies and that
-both the copyright notice and this permission notice and warranty
-disclaimer appear in supporting documentation, and that the names of
-the authors or their employers not be used in advertising or publicity
-pertaining to distribution of the software without specific, written
-prior permission.
-
-The authors and their employers disclaim all warranties with regard to
-this software, including all implied warranties of merchantability and
-fitness. In no event shall the authors or their employers be liable
-for any special, indirect or consequential damages or any damages
-whatsoever resulting from loss of use, data or profits, whether in an
-action of contract, negligence or other tortious action, arising out of
-or in connection with the use or performance of this software.
-
-
-
-EPL-1.0
-
-
-Eclipse Public License - v 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE
-("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES
-RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-
-"Contribution" means:
-
-a) in the case of the initial Contributor, the initial code and documentation
-distributed under this Agreement, and
-b) in the case of each subsequent Contributor:
-i) changes to the Program, and
-ii) additions to the Program;
-where such changes and/or additions to the Program originate from and are distributed
-by that particular Contributor. A Contribution `originates` from a Contributor if it
-was added to the Program by such Contributor itself or anyone acting on such
-Contributor`s behalf. Contributions do not include additions to the Program which: (i)
-are separate modules of software distributed in conjunction with the Program under
-their own license agreement, and (ii) are not derivative works of the Program.
-"Contributor" means any person or entity that distributes the Program.
-
-"Licensed Patents" mean patent claims licensable by a Contributor which are
-necessarily infringed by the use or sale of its Contribution alone or when combined
-with the Program.
-
-"Program" means the Contributions distributed in accordance with this Agreement.
-
-"Recipient" means anyone who receives the Program under this Agreement, including all
-Contributors.
-
-2. GRANT OF RIGHTS
-
-a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
-non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare
-derivative works of, publicly display, publicly perform, distribute and sublicense the
-Contribution of such Contributor, if any, and such derivative works, in source code
-and object code form.
-b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a
-non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make,
-use, sell, offer to sell, import and otherwise transfer the Contribution of such
-Contributor, if any, in source code and object code form. This patent license shall
-apply to the combination of the Contribution and the Program if, at the time the
-Contribution is added by the Contributor, such addition of the Contribution causes
-such combination to be covered by the Licensed Patents. The patent license shall not
-apply to any other combinations which include the Contribution. No hardware per se is
-licensed hereunder.
-c) Recipient understands that although each Contributor grants the licenses to its
-Contributions set forth herein, no assurances are provided by any Contributor that the
-Program does not infringe the patent or other intellectual property rights of any
-other entity. Each Contributor disclaims any liability to Recipient for claims brought
-by any other entity based on infringement of intellectual property rights or
-otherwise. As a condition to exercising the rights and licenses granted hereunder,
-each Recipient hereby assumes sole responsibility to secure any other intellectual
-property rights needed, if any. For example, if a third party patent license is
-required to allow Recipient to distribute the Program, it is Recipient`s
-responsibility to acquire that license before distributing the Program.
-d) Each Contributor represents that to its knowledge it has sufficient copyright
-rights in its Contribution, if any, to grant the copyright license set forth in this
-Agreement.
-3. REQUIREMENTS
-
-A Contributor may choose to distribute the Program in object code form under its own
-license agreement, provided that:
-
-a) it complies with the terms and conditions of this Agreement; and
-b) its license agreement:
-i) effectively disclaims on behalf of all Contributors all warranties and conditions,
-express and implied, including warranties or conditions of title and non-infringement,
-and implied warranties or conditions of merchantability and fitness for a particular
-purpose;
-ii) effectively excludes on behalf of all Contributors all liability for damages,
-including direct, indirect, special, incidental and consequential damages, such as
-lost profits;
-iii) states that any provisions which differ from this Agreement are offered by that
-Contributor alone and not by any other party; and
-iv) states that source code for the Program is available from such Contributor, and
-informs licensees how to obtain it in a reasonable manner on or through a medium
-customarily used for software exchange.
-When the Program is made available in source code form:
-
-a) it must be made available under this Agreement; and
-b) a copy of this Agreement must be included with each copy of the Program.
-Contributors may not remove or alter any copyright notices contained within the
-Program.
-
-Each Contributor must identify itself as the originator of its Contribution, if any,
-in a manner that reasonably allows subsequent Recipients to identify the originator of
-the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-
-Commercial distributors of software may accept certain responsibilities with respect
-to end users, business partners and the like. While this license is intended to
-facilitate the commercial use of the Program, the Contributor who includes the Program
-in a commercial product offering should do so in a manner which does not create
-potential liability for other Contributors. Therefore, if a Contributor includes the
-Program in a commercial product offering, such Contributor ("Commercial Contributor")
-hereby agrees to defend and indemnify every other Contributor ("Indemnified
-Contributor") against any losses, damages and costs (collectively "Losses") arising
-from claims, lawsuits and other legal actions brought by a third party against the
-Indemnified Contributor to the extent caused by the acts or omissions of such
-Commercial Contributor in connection with its distribution of the Program in a
-commercial product offering. The obligations in this section do not apply to any
-claims or Losses relating to any actual or alleged intellectual property infringement.
-In order to qualify, an Indemnified Contributor must: a) promptly notify the
-Commercial Contributor in writing of such claim, and b) allow the Commercial
-Contributor to control, and cooperate with the Commercial Contributor in, the defense
-and any related settlement negotiations. The Indemnified Contributor may participate
-in any such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial product offering,
-Product X. That Contributor is then a Commercial Contributor. If that Commercial
-Contributor then makes performance claims, or offers warranties related to Product X,
-those performance claims and warranties are such Commercial Contributor`s
-responsibility alone. Under this section, the Commercial Contributor would have to
-defend claims against the other Contributors related to those performance claims and
-warranties, and if a court requires any other Contributor to pay any damages as a
-result, the Commercial Contributor must pay those damages.
-
-5. NO WARRANTY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS"
-BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED
-INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
-NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient
-is solely responsible for determining the appropriateness of using and distributing
-the Program and assumes all risks associated with its exercise of rights under this
-Agreement , including but not limited to the risks and costs of program errors,
-compliance with applicable laws, damage to or loss of data, programs or equipment, and
-unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
-CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS),
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR
-DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-
-If any provision of this Agreement is invalid or unenforceable under applicable law,
-it shall not affect the validity or enforceability of the remainder of the terms of
-this Agreement, and without further action by the parties hereto, such provision shall
-be reformed to the minimum extent necessary to make such provision valid and
-enforceable.
-
-If Recipient institutes patent litigation against any entity (including a cross-claim
-or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations
-of the Program with other software or hardware) infringes such Recipient`s patent(s),
-then such Recipient`s rights granted under Section 2(b) shall terminate as of the date
-such litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it fails to comply with
-any of the material terms or conditions of this Agreement and does not cure such
-failure in a reasonable period of time after becoming aware of such noncompliance. If
-all Recipient`s rights under this Agreement terminate, Recipient agrees to cease use
-and distribution of the Program as soon as reasonably practicable. However,
-Recipient`s obligations under this Agreement and any licenses granted by Recipient
-relating to the Program shall continue and survive.
-
-Everyone is permitted to copy and distribute copies of this Agreement, but in order to
-avoid inconsistency the Agreement is copyrighted and may only be modified in the
-following manner. The Agreement Steward reserves the right to publish new versions
-(including revisions) of this Agreement from time to time. No one other than the
-Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is
-the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to
-serve as the Agreement Steward to a suitable separate entity. Each new version of the
-Agreement will be given a distinguishing version number. The Program (including
-Contributions) may always be distributed subject to the version of the Agreement under
-which it was received. In addition, after a new version of the Agreement is published,
-Contributor may elect to distribute the Program (including its Contributions) under
-the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
-receives no rights or licenses to the intellectual property of any Contributor under
-this Agreement, whether expressly, by implication, estoppel or otherwise. All rights
-in the Program not expressly granted under this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and the intellectual
-property laws of the United States of America. No party to this Agreement will bring a
-legal action under this Agreement more than one year after the cause of action arose.
-Each party waives its rights to a jury trial in any resulting litigation.
-
-
-
-
-Elfutils-Exception
-
- This file describes the limits of the Exception under which you are allowed
- to distribute Non-GPL Code in linked combination with Red Hat elfutils.
- For the full text of the license, please see one of the header files
- included with the source distribution or the file COPYING found in the
- top level directory of the source.
-
- The Approved Interfaces are the functions declared in the files:
-
- libelf.h
- libdw.h
- libdwfl.h
-
-
-
-
-FSF-Unlimited
-
-Copyright (C) 1997-2010 Free Software Foundation, Inc.
-This file is free software; the Free Software Foundation
-gives unlimited permission to copy and/or distribute it,
-with or without modifications, as long as this notice is preserved.
-
-
-
-FreeType
-
- The FreeType Project LICENSE
- ----------------------------
-
- 2006-Jan-27
-
- Copyright 1996-2002, 2006 by
- David Turner, Robert Wilhelm, and Werner Lemberg
-
-
-
-Introduction
-============
-
- The FreeType Project is distributed in several archive packages;
- some of them may contain, in addition to the FreeType font engine,
- various tools and contributions which rely on, or relate to, the
- FreeType Project.
-
- This license applies to all files found in such packages, and
- which do not fall under their own explicit license. The license
- affects thus the FreeType font engine, the test programs,
- documentation and makefiles, at the very least.
-
- This license was inspired by the BSD, Artistic, and IJG
- (Independent JPEG Group) licenses, which all encourage inclusion
- and use of free software in commercial and freeware products
- alike. As a consequence, its main points are that:
-
- o We don't promise that this software works. However, we will be
- interested in any kind of bug reports. (`as is' distribution)
-
- o You can use this software for whatever you want, in parts or
- full form, without having to pay us. (`royalty-free' usage)
-
- o You may not pretend that you wrote this software. If you use
- it, or only parts of it, in a program, you must acknowledge
- somewhere in your documentation that you have used the
- FreeType code. (`credits')
-
- We specifically permit and encourage the inclusion of this
- software, with or without modifications, in commercial products.
- We disclaim all warranties covering The FreeType Project and
- assume no liability related to The FreeType Project.
-
-
- Finally, many people asked us for a preferred form for a
- credit/disclaimer to use in compliance with this license. We thus
- encourage you to use the following text:
-
- """
- Portions of this software are copyright � <year> The FreeType
- Project (www.freetype.org). All rights reserved.
- """
-
- Please replace <year> with the value from the FreeType version you
- actually use.
-
-
-Legal Terms
-===========
-
-0. Definitions
---------------
-
- Throughout this license, the terms `package', `FreeType Project',
- and `FreeType archive' refer to the set of files originally
- distributed by the authors (David Turner, Robert Wilhelm, and
- Werner Lemberg) as the `FreeType Project', be they named as alpha,
- beta or final release.
-
- `You' refers to the licensee, or person using the project, where
- `using' is a generic term including compiling the project's source
- code as well as linking it to form a `program' or `executable'.
- This program is referred to as `a program using the FreeType
- engine'.
-
- This license applies to all files distributed in the original
- FreeType Project, including all source code, binaries and
- documentation, unless otherwise stated in the file in its
- original, unmodified form as distributed in the original archive.
- If you are unsure whether or not a particular file is covered by
- this license, you must contact us to verify this.
-
- The FreeType Project is copyright (C) 1996-2000 by David Turner,
- Robert Wilhelm, and Werner Lemberg. All rights reserved except as
- specified below.
-
-1. No Warranty
---------------
-
- THE FREETYPE PROJECT IS PROVIDED `AS IS' WITHOUT WARRANTY OF ANY
- KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
- WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
- PURPOSE. IN NO EVENT WILL ANY OF THE AUTHORS OR COPYRIGHT HOLDERS
- BE LIABLE FOR ANY DAMAGES CAUSED BY THE USE OR THE INABILITY TO
- USE, OF THE FREETYPE PROJECT.
-
-2. Redistribution
------------------
-
- This license grants a worldwide, royalty-free, perpetual and
- irrevocable right and license to use, execute, perform, compile,
- display, copy, create derivative works of, distribute and
- sublicense the FreeType Project (in both source and object code
- forms) and derivative works thereof for any purpose; and to
- authorize others to exercise some or all of the rights granted
- herein, subject to the following conditions:
-
- o Redistribution of source code must retain this license file
- (`FTL.TXT') unaltered; any additions, deletions or changes to
- the original files must be clearly indicated in accompanying
- documentation. The copyright notices of the unaltered,
- original files must be preserved in all copies of source
- files.
-
- o Redistribution in binary form must provide a disclaimer that
- states that the software is based in part of the work of the
- FreeType Team, in the distribution documentation. We also
- encourage you to put an URL to the FreeType web page in your
- documentation, though this isn't mandatory.
-
- These conditions apply to any software derived from or based on
- the FreeType Project, not just the unmodified files. If you use
- our work, you must acknowledge us. However, no fee need be paid
- to us.
-
-3. Advertising
---------------
-
- Neither the FreeType authors and contributors nor you shall use
- the name of the other for commercial, advertising, or promotional
- purposes without specific prior written permission.
-
- We suggest, but do not require, that you use one or more of the
- following phrases to refer to this software in your documentation
- or advertising materials: `FreeType Project', `FreeType Engine',
- `FreeType library', or `FreeType Distribution'.
-
- As you have not signed this license, you are not required to
- accept it. However, as the FreeType Project is copyrighted
- material, only this license, or another one contracted with the
- authors, grants you the right to use, distribute, and modify it.
- Therefore, by using, distributing, or modifying the FreeType
- Project, you indicate that you understand and accept all the terms
- of this license.
-
-4. Contacts
------------
-
- There are two mailing lists related to FreeType:
-
- o freetype@nongnu.org
-
- Discusses general use and applications of FreeType, as well as
- future and wanted additions to the library and distribution.
- If you are looking for support, start in this list if you
- haven't found anything to help you in the documentation.
-
- o freetype-devel@nongnu.org
-
- Discusses bugs, as well as engine internals, design issues,
- specific licenses, porting, etc.
-
- Our home page can be found at
-
- http://www.freetype.org
-
-
---- end of FTL.TXT ---
-
-
-
-
-GPL-1.0
-
-
-GNU General Public License, version 1
-
- GNU GENERAL PUBLIC LICENSE
- Version 1, February 1989
-
- Copyright (C) 1989 Free Software Foundation, Inc.
- 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The license agreements of most software companies try to keep users
-at the mercy of those companies. By contrast, our General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. The
-General Public License applies to the Free Software Foundation`s
-software and to any other program whose authors commit to using it.
-You can use it for your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Specifically, the General Public License is designed to make
-sure that you have the freedom to give away or sell copies of free
-software, that you receive source code or can get it if you want it,
-that you can change the software or use pieces of it in new free
-programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of a such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must tell them their rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author`s protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors` reputations.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License Agreement applies to any program or other work which
-contains a notice placed by the copyright holder saying it may be
-distributed under the terms of this General Public License. The
-"Program", below, refers to any such program or work, and a "work based
-on the Program" means either the Program or any work containing the
-Program or a portion of it, either verbatim or with modifications. Each
-licensee is addressed as "you".
-
- 1. You may copy and distribute verbatim copies of the Program`s source
-code as you receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice and
-disclaimer of warranty; keep intact all the notices that refer to this
-General Public License and to the absence of any warranty; and give any
-other recipients of the Program a copy of this General Public License
-along with the Program. You may charge a fee for the physical act of
-transferring a copy.
-
- 2. You may modify your copy or copies of the Program or any portion of
-it, and copy and distribute such modifications under the terms of Paragraph
-1 above, provided that you also do the following:
-
- a) cause the modified files to carry prominent notices stating that
- you changed the files and the date of any change; and
-
- b) cause the whole of any work that you distribute or publish, that
- in whole or in part contains the Program or any part thereof, either
- with or without modifications, to be licensed at no charge to all
- third parties under the terms of this General Public License (except
- that you may choose to grant warranty protection to some or all
- third parties, at your option).
-
- c) If the modified program normally reads commands interactively when
- run, you must cause it, when started running for such interactive use
- in the simplest and most usual way, to print or display an
- announcement including an appropriate copyright notice and a notice
- that there is no warranty (or else, saying that you provide a
- warranty) and that users may redistribute the program under these
- conditions, and telling the user how to view a copy of this General
- Public License.
-
- d) You may charge a fee for the physical act of transferring a
- copy, and you may at your option offer warranty protection in
- exchange for a fee.
-
-Mere aggregation of another independent work with the Program (or its
-derivative) on a volume of a storage or distribution medium does not bring
-the other work under the scope of these terms.
-
- 3. You may copy and distribute the Program (or a portion or derivative of
-it, under Paragraph 2) in object code or executable form under the terms of
-Paragraphs 1 and 2 above provided that you also do one of the following:
-
- a) accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- b) accompany it with a written offer, valid for at least three
- years, to give any third party free (except for a nominal charge
- for the cost of distribution) a complete machine-readable copy of the
- corresponding source code, to be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- c) accompany it with the information you received as to where the
- corresponding source code may be obtained. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form alone.)
-
-Source code for a work means the preferred form of the work for making
-modifications to it. For an executable file, complete source code means
-all the source code for all modules it contains; but, as a special
-exception, it need not include source code for modules which are standard
-libraries that accompany the operating system on which the executable
-file runs, or for standard header files or definitions files that
-accompany that operating system.
-
- 4. You may not copy, modify, sublicense, distribute or transfer the
-Program except as expressly provided under this General Public License.
-Any attempt otherwise to copy, modify, sublicense, distribute or transfer
-the Program is void, and will automatically terminate your rights to use
-the Program under this License. However, parties who have received
-copies, or rights to use copies, from you under this General Public
-License will not have their licenses terminated so long as such parties
-remain in full compliance.
-
- 5. By copying, distributing or modifying the Program (or any work based
-on the Program) you indicate your acceptance of this license to do so,
-and all its terms and conditions.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the original
-licensor to copy, distribute or modify the Program subject to these
-terms and conditions. You may not impose any further restrictions on the
-recipients` exercise of the rights granted herein.
-
- 7. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of the license which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-the license, you may choose any version ever published by the Free Software
-Foundation.
-
- 8. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- 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
-the exclusion of warranty; and each file should have at least the
-"copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program`s name and a brief idea of what it does.>
- Copyright (C) 19yy <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 1, or (at your option)
- any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) 19xx name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w`.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c` for details.
-
-The hypothetical commands `show w` and `show c` should show the
-appropriate parts of the General Public License. Of course, the
-commands you use may be called something other than `show w` and `show
-c`; they could even be mouse-clicks or menu items--whatever suits your
-program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the
- program `Gnomovision` (a program to direct compilers to make passes
- at assemblers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-That`s all there is to it!
-
-
-
-
-GPL-2.0
-
-
-GNU GENERAL PUBLIC LICENSE
-
-Version 2, June 1991
-
-Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-Preamble
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public License is intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users. This General Public License applies to most of the Free Software
-Foundation`s software and to any other program whose authors commit to using it. (Some
-other Free Software Foundation software is covered by the GNU Lesser General Public
-License instead.) You can apply it to your programs, too.
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for this service if you wish), that you receive
-source code or can get it if you want it, that you can change the software or use
-pieces of it in new free programs; and that you know you can do these things.
-
-To protect your rights, we need to make restrictions that forbid anyone to deny you
-these rights or to ask you to surrender the rights. These restrictions translate to
-certain responsibilities for you if you distribute copies of the software, or if you
-modify it.
-
-For example, if you distribute copies of such a program, whether gratis or for a fee,
-you must give the recipients all the rights that you have. You must make sure that
-they, too, receive or can get the source code. And you must show them these terms so
-they know their rights.
-
-We protect your rights with two steps: (1) copyright the software, and (2) offer you
-this license which gives you legal permission to copy, distribute and/or modify the
-software.
-
-Also, for each author`s protection and ours, we want to make certain that everyone
-understands that there is no warranty for this free software. If the software is
-modified by someone else and passed on, we want its recipients to know that what they
-have is not the original, so that any problems introduced by others will not reflect
-on the original authors` reputations.
-
-Finally, any free program is threatened constantly by software patents. We wish to
-avoid the danger that redistributors of a free program will individually obtain patent
-licenses, in effect making the program proprietary. To prevent this, we have made it
-clear that any patent must be licensed for everyone`s free use or not licensed at all.
-
-The precise terms and conditions for copying, distribution and modification follow.
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-0. This License applies to any program or other work which contains a notice placed by
-the copyright holder saying it may be distributed under the terms of this General
-Public License. The "Program", below, refers to any such program or work, and a "work
-based on the Program" means either the Program or any derivative work under copyright
-law: that is to say, a work containing the Program or a portion of it, either verbatim
-or with modifications and/or translated into another language. (Hereinafter,
-translation is included without limitation in the term "modification".) Each licensee
-is addressed as "you".
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running the Program is not restricted,
-and the output from the Program is covered only if its contents constitute a work
-based on the Program (independent of having been made by running the Program). Whether
-that is true depends on what the Program does.
-
-1. You may copy and distribute verbatim copies of the Program`s source code as you
-receive it, in any medium, provided that you conspicuously and appropriately publish
-on each copy an appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any warranty; and
-give any other recipients of the Program a copy of this License along with the
-Program.
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-2. You may modify your copy or copies of the Program or any portion of it, thus
-forming a work based on the Program, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-a) You must cause the modified files to carry prominent notices stating that you
-changed the files and the date of any change.
-b) You must cause any work that you distribute or publish, that in whole or in part
-contains or is derived from the Program or any part thereof, to be licensed as a whole
-at no charge to all third parties under the terms of this License.
-c) If the modified program normally reads commands interactively when run, you must
-cause it, when started running for such interactive use in the most ordinary way, to
-print or display an announcement including an appropriate copyright notice and a
-notice that there is no warranty (or else, saying that you provide a warranty) and
-that users may redistribute the program under these conditions, and telling the user
-how to view a copy of this License. (Exception: if the Program itself is interactive
-but does not normally print such an announcement, your work based on the Program is
-not required to print an announcement.)
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Program, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Program,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program with the
-Program (or with a work based on the Program) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-3. You may copy and distribute the Program (or a work based on it, under Section 2) in
-object code or executable form under the terms of Sections 1 and 2 above provided that
-you also do one of the following:
-
-a) Accompany it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a medium customarily
-used for software interchange; or,
-b) Accompany it with a written offer, valid for at least three years, to give any
-third party, for a charge no more than your cost of physically performing source
-distribution, a complete machine-readable copy of the corresponding source code, to be
-distributed under the terms of Sections 1 and 2 above on a medium customarily used for
-software interchange; or,
-c) Accompany it with the information you received as to the offer to distribute
-corresponding source code. (This alternative is allowed only for noncommercial
-distribution and only if you received the program in object code or executable form
-with such an offer, in accord with Subsection b above.)
-The source code for a work means the preferred form of the work for making
-modifications to it. For an executable work, complete source code means all the source
-code for all modules it contains, plus any associated interface definition files, plus
-the scripts used to control compilation and installation of the executable. However,
-as a special exception, the source code distributed need not include anything that is
-normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-If distribution of executable or object code is made by offering access to copy from a
-designated place, then offering equivalent access to copy the source code from the
-same place counts as distribution of the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-4. You may not copy, modify, sublicense, or distribute the Program except as expressly
-provided under this License. Any attempt otherwise to copy, modify, sublicense or
-distribute the Program is void, and will automatically terminate your rights under
-this License. However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such parties remain in
-full compliance.
-
-5. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Program or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Program or works based on it.
-
-6. Each time you redistribute the Program (or any work based on the Program), the
-recipient automatically receives a license from the original licensor to copy,
-distribute or modify the Program subject to these terms and conditions. You may not
-impose any further restrictions on the recipients` exercise of the rights granted
-herein. You are not responsible for enforcing compliance by third parties to this
-License.
-
-7. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Program at all. For example, if a patent license would not permit royalty-free
-redistribution of the Program by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply and the section as a
-whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system,
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-8. If the distribution and/or use of the Program is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Program under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-9. The Free Software Foundation may publish revised and/or new versions of the General
-Public License from time to time. Such new versions will be similar in spirit to the
-present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Program does not
-specify a version number of this License, you may choose any version ever published by
-the Free Software Foundation.
-
-10. If you wish to incorporate parts of the Program into other free programs whose
-distribution conditions are different, write to the author to ask for permission. For
-software which is copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this. Our decision will be
-guided by the two goals of preserving the free status of all derivatives of our free
-software and of promoting the sharing and reuse of software generally.
-
-NO WARRANTY
-
-11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
-WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-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 the "copyright" line and a pointer to where the
-full notice is found.
-
-one line to give the program`s name and an idea of what it does.
-Copyright (C) yyyy name of author
-
-This program is free software; you can redistribute it and/or
-modify it under the terms of the GNU General Public License
-as published by the Free Software Foundation; either version 2
-of the License, or (at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this when it starts
-in an interactive mode:
-
-Gnomovision version 69, Copyright (C) year name of author
-Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
-type `show w`. This is free software, and you are welcome
-to redistribute it under certain conditions; type `show c`
-for details.
-The hypothetical commands `show w` and `show c` should show the appropriate parts of
-the General Public License. Of course, the commands you use may be called something
-other than `show w` and `show c`; they could even be mouse-clicks or menu
-items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample;
-alter the names:
-
-Yoyodyne, Inc., hereby disclaims all copyright
-interest in the program `Gnomovision`
-(which makes passes at compilers) written
-by James Hacker.
-
-signature of Ty Coon, 1 April 1989
-Ty Coon, President of Vice
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may consider it
-more useful to permit linking proprietary applications with the library. If this is
-what you want to do, use the GNU Lesser General Public License instead of this
-License.
-
-
-
-
-GPL-2.0-with-GCC-exception
-
-
-insert GPL v2 text here
-
-GCC Linking Exception
-In addition to the permissions in the GNU General Public License, the Free
-Software Foundation gives you unlimited permission to link the compiled version
-of this file into combinations with other programs, and to distribute those
-combinations without any restriction coming from the use of this file. (The
-General Public License restrictions do apply in other respects; for example,
-they cover modification of the file, and distribution when not linked into a
-combine executable.)
-
-
-
-
-
-
-
-
-
-GPL-2.0-with-classpath-exception
-
-
-insert GPL v2 license text here
-
-Linking this library statically or dynamically with other modules is making a combined
-work based on this library. Thus, the terms and conditions of the GNU General Public
-License cover the whole combination.
-
-As a special exception, the copyright holders of this library give you permission to
-link this library with independent modules to produce an executable, regardless of the
-license terms of these independent modules, and to copy and distribute the resulting
-executable under terms of your choice, provided that you also meet, for each linked
-independent module, the terms and conditions of the license of that module. An
-independent module is a module which is not derived from or based on this library. If
-you modify this library, you may extend this exception to your version of the library,
-but you are not obligated to do so. If you do not wish to do so, delete this exception
-statement from your version.
-
-
-
-
-GPL-3.0
-
-GNU GENERAL PUBLIC LICENSE
-
-Version 3, 29 June 2007
-
-Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-Preamble
-
-The GNU General Public License is a free, copyleft license for software and other
-kinds of works.
-
-The licenses for most software and other practical works are designed to take away
-your freedom to share and change the works. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change all versions of a
-program--to make sure it remains free software for all its users. We, the Free
-Software Foundation, use the GNU General Public License for most of our software; it
-applies also to any other work released this way by its authors. You can apply it to
-your programs, too.
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for them if you wish), that you receive source
-code or can get it if you want it, that you can change the software or use pieces of
-it in new free programs, and that you know you can do these things.
-
-To protect your rights, we need to prevent others from denying you these rights or
-asking you to surrender the rights. Therefore, you have certain responsibilities if
-you distribute copies of the software, or if you modify it: responsibilities to
-respect the freedom of others.
-
-For example, if you distribute copies of such a program, whether gratis or for a fee,
-you must pass on to the recipients the same freedoms that you received. You must make
-sure that they, too, receive or can get the source code. And you must show them these
-terms so they know their rights.
-
-Developers that use the GNU GPL protect your rights with two steps: (1) assert
-copyright on the software, and (2) offer you this License giving you legal permission
-to copy, distribute and/or modify it.
-
-For the developers' and authors' protection, the GPL clearly explains that there is no
-warranty for this free software. For both users' and authors' sake, the GPL requires
-that modified versions be marked as changed, so that their problems will not be
-attributed erroneously to authors of previous versions.
-
-Some devices are designed to deny users access to install or run modified versions of
-the software inside them, although the manufacturer can do so. This is fundamentally
-incompatible with the aim of protecting users' freedom to change the software. The
-systematic pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable. Therefore, we have designed
-this version of the GPL to prohibit the practice for those products. If such problems
-arise substantially in other domains, we stand ready to extend this provision to those
-domains in future versions of the GPL, as needed to protect the freedom of users.
-
-Finally, every program is threatened constantly by software patents. States should not
-allow patents to restrict development and use of software on general-purpose
-computers, but in those that do, we wish to avoid the special danger that patents
-applied to a free program could make it effectively proprietary. To prevent this, the
-GPL assures that patents cannot be used to render the program non-free.
-
-The precise terms and conditions for copying, distribution and modification follow.
-TERMS AND CONDITIONS
-0. Definitions.
-
-”This License” refers to version 3 of the GNU General Public License.
-
-”Copyright” also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-”The Program” refers to any copyrightable work licensed under this
-License. Each licensee is addressed as ”you”. ”Licensees”
-and ”recipients” may be individuals or organizations.
-
-To ”modify” a work means to copy from or adapt all or part of the work in
-a fashion requiring copyright permission, other than the making of an exact copy. The
-resulting work is called a ”modified version” of the earlier work or a
-work ”based on” the earlier work.
-
-A ”covered work” means either the unmodified Program or a work based on
-the Program.
-
-To ”propagate” a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for infringement under
-applicable copyright law, except executing it on a computer or modifying a private
-copy. Propagation includes copying, distribution (with or without modification),
-making available to the public, and in some countries other activities as well.
-
-To ”convey” a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user through a computer
-network, with no transfer of a copy, is not conveying.
-
-An interactive user interface displays ”Appropriate Legal Notices” to the
-extent that it includes a convenient and prominently visible feature that (1) displays
-an appropriate copyright notice, and (2) tells the user that there is no warranty for
-the work (except to the extent that warranties are provided), that licensees may
-convey the work under this License, and how to view a copy of this License. If the
-interface presents a list of user commands or options, such as a menu, a prominent
-item in the list meets this criterion.
-1. Source Code.
-
-The ”source code” for a work means the preferred form of the work for
-making modifications to it. ”Object code” means any non-source form of a
-work.
-
-A ”Standard Interface” means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of interfaces
-specified for a particular programming language, one that is widely used among
-developers working in that language.
-
-The ”System Libraries” of an executable work include anything, other than
-the work as a whole, that (a) is included in the normal form of packaging a Major
-Component, but which is not part of that Major Component, and (b) serves only to
-enable use of the work with that Major Component, or to implement a Standard Interface
-for which an implementation is available to the public in source code form. A
-”Major Component”, in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system (if any) on which
-the executable work runs, or a compiler used to produce the work, or an object code
-interpreter used to run it.
-
-The ”Corresponding Source” for a work in object code form means all the
-source code needed to generate, install, and (for an executable work) run the object
-code and to modify the work, including scripts to control those activities. However,
-it does not include the work's System Libraries, or general-purpose tools or generally
-available free programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source includes interface
-definition files associated with source files for the work, and the source code for
-shared libraries and dynamically linked subprograms that the work is specifically
-designed to require, such as by intimate data communication or control flow between
-those subprograms and other parts of the work.
-
-The Corresponding Source need not include anything that users can regenerate
-automatically from other parts of the Corresponding Source.
-
-The Corresponding Source for a work in source code form is that same work.
-2. Basic Permissions.
-
-All rights granted under this License are granted for the term of copyright on the
-Program, and are irrevocable provided the stated conditions are met. This License
-explicitly affirms your unlimited permission to run the unmodified Program. The output
-from running a covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your rights of fair use
-or other equivalent, as provided by copyright law.
-
-You may make, run and propagate covered works that you do not convey, without
-conditions so long as your license otherwise remains in force. You may convey covered
-works to others for the sole purpose of having them make modifications exclusively for
-you, or provide you with facilities for running those works, provided that you comply
-with the terms of this License in conveying all material for which you do not control
-copyright. Those thus making or running the covered works for you must do so
-exclusively on your behalf, under your direction and control, on terms that prohibit
-them from making any copies of your copyrighted material outside their relationship
-with you.
-
-Conveying under any other circumstances is permitted solely under the conditions
-stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
-3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-No covered work shall be deemed part of an effective technological measure under any
-applicable law fulfilling obligations under article 11 of the WIPO copyright treaty
-adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention
-of such measures.
-
-When you convey a covered work, you waive any legal power to forbid circumvention of
-technological measures to the extent such circumvention is effected by exercising
-rights under this License with respect to the covered work, and you disclaim any
-intention to limit operation or modification of the work as a means of enforcing,
-against the work's users, your or third parties' legal rights to forbid circumvention
-of technological measures.
-4. Conveying Verbatim Copies.
-
-You may convey verbatim copies of the Program's source code as you receive it, in any
-medium, provided that you conspicuously and appropriately publish on each copy an
-appropriate copyright notice; keep intact all notices stating that this License and
-any non-permissive terms added in accord with section 7 apply to the code; keep intact
-all notices of the absence of any warranty; and give all recipients a copy of this
-License along with the Program.
-
-You may charge any price or no price for each copy that you convey, and you may offer
-support or warranty protection for a fee.
-5. Conveying Modified Source Versions.
-
-You may convey a work based on the Program, or the modifications to produce it from
-the Program, in the form of source code under the terms of section 4, provided that
-you also meet all of these conditions:
-
- * a) The work must carry prominent notices stating that you modified it, and
-giving a relevant date.
- * b) The work must carry prominent notices stating that it is released under this
-License and any conditions added under section 7. This requirement modifies the
-requirement in section 4 to ”keep intact all notices”.
- * c) You must license the entire work, as a whole, under this License to anyone
-who comes into possession of a copy. This License will therefore apply, along with any
-applicable section 7 additional terms, to the whole of the work, and all its parts,
-regardless of how they are packaged. This License gives no permission to license the
-work in any other way, but it does not invalidate such permission if you have
-separately received it.
- * d) If the work has interactive user interfaces, each must display Appropriate
-Legal Notices; however, if the Program has interactive interfaces that do not display
-Appropriate Legal Notices, your work need not make them do so.
-
-A compilation of a covered work with other separate and independent works, which are
-not by their nature extensions of the covered work, and which are not combined with it
-such as to form a larger program, in or on a volume of a storage or distribution
-medium, is called an ”aggregate” if the compilation and its resulting
-copyright are not used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work in an aggregate
-does not cause this License to apply to the other parts of the aggregate.
-6. Conveying Non-Source Forms.
-
-You may convey a covered work in object code form under the terms of sections 4 and 5,
-provided that you also convey the machine-readable Corresponding Source under the
-terms of this License, in one of these ways:
-
- * a) Convey the object code in, or embodied in, a physical product (including a
-physical distribution medium), accompanied by the Corresponding Source fixed on a
-durable physical medium customarily used for software interchange.
- * b) Convey the object code in, or embodied in, a physical product (including a
-physical distribution medium), accompanied by a written offer, valid for at least
-three years and valid for as long as you offer spare parts or customer support for
-that product model, to give anyone who possesses the object code either (1) a copy of
-the Corresponding Source for all the software in the product that is covered by this
-License, on a durable physical medium customarily used for software interchange, for a
-price no more than your reasonable cost of physically performing this conveying of
-source, or (2) access to copy the Corresponding Source from a network server at no
-charge.
- * c) Convey individual copies of the object code with a copy of the written offer
-to provide the Corresponding Source. This alternative is allowed only occasionally and
-noncommercially, and only if you received the object code with such an offer, in
-accord with subsection 6b.
- * d) Convey the object code by offering access from a designated place (gratis or
-for a charge), and offer equivalent access to the Corresponding Source in the same way
-through the same place at no further charge. You need not require recipients to copy
-the Corresponding Source along with the object code. If the place to copy the object
-code is a network server, the Corresponding Source may be on a different server
-(operated by you or a third party) that supports equivalent copying facilities,
-provided you maintain clear directions next to the object code saying where to find
-the Corresponding Source. Regardless of what server hosts the Corresponding Source,
-you remain obligated to ensure that it is available for as long as needed to satisfy
-these requirements.
- * e) Convey the object code using peer-to-peer transmission, provided you inform
-other peers where the object code and Corresponding Source of the work are being
-offered to the general public at no charge under subsection 6d.
-
-A separable portion of the object code, whose source code is excluded from the
-Corresponding Source as a System Library, need not be included in conveying the object
-code work.
-
-A ”User Product” is either (1) a ”consumer product”, which
-means any tangible personal property which is normally used for personal, family, or
-household purposes, or (2) anything designed or sold for incorporation into a
-dwelling. In determining whether a product is a consumer product, doubtful cases shall
-be resolved in favor of coverage. For a particular product received by a particular
-user, ”normally used” refers to a typical or common use of that class of
-product, regardless of the status of the particular user or of the way in which the
-particular user actually uses, or expects or is expected to use, the product. A
-product is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent the only
-significant mode of use of the product.
-
-”Installation Information” for a User Product means any methods,
-procedures, authorization keys, or other information required to install and execute
-modified versions of a covered work in that User Product from a modified version of
-its Corresponding Source. The information must suffice to ensure that the continued
-functioning of the modified object code is in no case prevented or interfered with
-solely because modification has been made.
-
-If you convey an object code work under this section in, or with, or specifically for
-use in, a User Product, and the conveying occurs as part of a transaction in which the
-right of possession and use of the User Product is transferred to the recipient in
-perpetuity or for a fixed term (regardless of how the transaction is characterized),
-the Corresponding Source conveyed under this section must be accompanied by the
-Installation Information. But this requirement does not apply if neither you nor any
-third party retains the ability to install modified object code on the User Product
-(for example, the work has been installed in ROM).
-
-The requirement to provide Installation Information does not include a requirement to
-continue to provide support service, warranty, or updates for a work that has been
-modified or installed by the recipient, or for the User Product in which it has been
-modified or installed. Access to a network may be denied when the modification itself
-materially and adversely affects the operation of the network or violates the rules
-and protocols for communication across the network.
-
-Corresponding Source conveyed, and Installation Information provided, in accord with
-this section must be in a format that is publicly documented (and with an
-implementation available to the public in source code form), and must require no
-special password or key for unpacking, reading or copying.
-7. Additional Terms.
-
-”Additional permissions” are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions. Additional
-permissions that are applicable to the entire Program shall be treated as though they
-were included in this License, to the extent that they are valid under applicable law.
-If additional permissions apply only to part of the Program, that part may be used
-separately under those permissions, but the entire Program remains governed by this
-License without regard to the additional permissions.
-
-When you convey a copy of a covered work, you may at your option remove any additional
-permissions from that copy, or from any part of it. (Additional permissions may be
-written to require their own removal in certain cases when you modify the work.) You
-may place additional permissions on material, added by you to a covered work, for
-which you have or can give appropriate copyright permission.
-
-Notwithstanding any other provision of this License, for material you add to a covered
-work, you may (if authorized by the copyright holders of that material) supplement the
-terms of this License with terms:
-
- * a) Disclaiming warranty or limiting liability differently from the terms of
-sections 15 and 16 of this License; or
- * b) Requiring preservation of specified reasonable legal notices or author
-attributions in that material or in the Appropriate Legal Notices displayed by works
-containing it; or
- * c) Prohibiting misrepresentation of the origin of that material, or requiring
-that modified versions of such material be marked in reasonable ways as different from
-the original version; or
- * d) Limiting the use for publicity purposes of names of licensors or authors of
-the material; or
- * e) Declining to grant rights under trademark law for use of some trade names,
-trademarks, or service marks; or
- * f) Requiring indemnification of licensors and authors of that material by anyone
-who conveys the material (or modified versions of it) with contractual assumptions of
-liability to the recipient, for any liability that these contractual assumptions
-directly impose on those licensors and authors.
-
-All other non-permissive additional terms are considered ”further
-restrictions” within the meaning of section 10. If the Program as you received
-it, or any part of it, contains a notice stating that it is governed by this License
-along with a term that is a further restriction, you may remove that term. If a
-license document contains a further restriction but permits relicensing or conveying
-under this License, you may add to a covered work material governed by the terms of
-that license document, provided that the further restriction does not survive such
-relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you must place, in the
-relevant source files, a statement of the additional terms that apply to those files,
-or a notice indicating where to find the applicable terms.
-
-Additional terms, permissive or non-permissive, may be stated in the form of a
-separately written license, or stated as exceptions; the above requirements apply
-either way.
-8. Termination.
-
-You may not propagate or modify a covered work except as expressly provided under this
-License. Any attempt otherwise to propagate or modify it is void, and will
-automatically terminate your rights under this License (including any patent licenses
-granted under the third paragraph of section 11).
-
-However, if you cease all violation of this License, then your license from a
-particular copyright holder is reinstated (a) provisionally, unless and until the
-copyright holder explicitly and finally terminates your license, and (b) permanently,
-if the copyright holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is reinstated permanently if
-the copyright holder notifies you of the violation by some reasonable means, this is
-the first time you have received notice of violation of this License (for any work)
-from that copyright holder, and you cure the violation prior to 30 days after your
-receipt of the notice.
-
-Termination of your rights under this section does not terminate the licenses of
-parties who have received copies or rights from you under this License. If your rights
-have been terminated and not permanently reinstated, you do not qualify to receive new
-licenses for the same material under section 10.
-9. Acceptance Not Required for Having Copies.
-
-You are not required to accept this License in order to receive or run a copy of the
-Program. Ancillary propagation of a covered work occurring solely as a consequence of
-using peer-to-peer transmission to receive a copy likewise does not require
-acceptance. However, nothing other than this License grants you permission to
-propagate or modify any covered work. These actions infringe copyright if you do not
-accept this License. Therefore, by modifying or propagating a covered work, you
-indicate your acceptance of this License to do so.
-10. Automatic Licensing of Downstream Recipients.
-
-Each time you convey a covered work, the recipient automatically receives a license
-from the original licensors, to run, modify and propagate that work, subject to this
-License. You are not responsible for enforcing compliance by third parties with this
-License.
-
-An ”entity transaction” is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an organization, or
-merging organizations. If propagation of a covered work results from an entity
-transaction, each party to that transaction who receives a copy of the work also
-receives whatever licenses to the work the party's predecessor in interest had or
-could give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if the predecessor
-has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the rights granted or
-affirmed under this License. For example, you may not impose a license fee, royalty,
-or other charge for exercise of rights granted under this License, and you may not
-initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging
-that any patent claim is infringed by making, using, selling, offering for sale, or
-importing the Program or any portion of it.
-11. Patents.
-
-A ”contributor” is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The work thus licensed
-is called the contributor's ”contributor version”.
-
-A contributor's ”essential patent claims” are all patent claims owned or
-controlled by the contributor, whether already acquired or hereafter acquired, that
-would be infringed by some manner, permitted by this License, of making, using, or
-selling its contributor version, but do not include claims that would be infringed
-only as a consequence of further modification of the contributor version. For purposes
-of this definition, ”control” includes the right to grant patent
-sublicenses in a manner consistent with the requirements of this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free patent license
-under the contributor's essential patent claims, to make, use, sell, offer for sale,
-import and otherwise run, modify and propagate the contents of its contributor
-version.
-
-In the following three paragraphs, a ”patent license” is any express
-agreement or commitment, however denominated, not to enforce a patent (such as an
-express permission to practice a patent or covenant not to sue for patent
-infringement). To ”grant” such a patent license to a party means to make
-such an agreement or commitment not to enforce a patent against the party.
-
-If you convey a covered work, knowingly relying on a patent license, and the
-Corresponding Source of the work is not available for anyone to copy, free of charge
-and under the terms of this License, through a publicly available network server or
-other readily accessible means, then you must either (1) cause the Corresponding
-Source to be so available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner consistent with
-the requirements of this License, to extend the patent license to downstream
-recipients. ”Knowingly relying” means you have actual knowledge that, but
-for the patent license, your conveying the covered work in a country, or your
-recipient's use of the covered work in a country, would infringe one or more
-identifiable patents in that country that you have reason to believe are valid.
-
-If, pursuant to or in connection with a single transaction or arrangement, you convey,
-or propagate by procuring conveyance of, a covered work, and grant a patent license to
-some of the parties receiving the covered work authorizing them to use, propagate,
-modify or convey a specific copy of the covered work, then the patent license you
-grant is automatically extended to all recipients of the covered work and works based
-on it.
-
-A patent license is ”discriminatory” if it does not include within the
-scope of its coverage, prohibits the exercise of, or is conditioned on the
-non-exercise of one or more of the rights that are specifically granted under this
-License. You may not convey a covered work if you are a party to an arrangement with a
-third party that is in the business of distributing software, under which you make
-payment to the third party based on the extent of your activity of conveying the work,
-and under which the third party grants, to any of the parties who would receive the
-covered work from you, a discriminatory patent license (a) in connection with copies
-of the covered work conveyed by you (or copies made from those copies), or (b)
-primarily for and in connection with specific products or compilations that contain
-the covered work, unless you entered into that arrangement, or that patent license was
-granted, prior to 28 March 2007.
-
-Nothing in this License shall be construed as excluding or limiting any implied
-license or other defenses to infringement that may otherwise be available to you under
-applicable patent law.
-12. No Surrender of Others' Freedom.
-
-If conditions are imposed on you (whether by court order, agreement or otherwise) that
-contradict the conditions of this License, they do not excuse you from the conditions
-of this License. If you cannot convey a covered work so as to satisfy simultaneously
-your obligations under this License and any other pertinent obligations, then as a
-consequence you may not convey it at all. For example, if you agree to terms that
-obligate you to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this License would be
-to refrain entirely from conveying the Program.
-13. Use with the GNU Affero General Public License.
-
-Notwithstanding any other provision of this License, you have permission to link or
-combine any covered work with a work licensed under version 3 of the GNU Affero
-General Public License into a single combined work, and to convey the resulting work.
-The terms of this License will continue to apply to the part which is the covered
-work, but the special requirements of the GNU Affero General Public License, section
-13, concerning interaction through a network will apply to the combination as such.
-14. Revised Versions of this License.
-
-The Free Software Foundation may publish revised and/or new versions of the GNU
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program specifies that a
-certain numbered version of the GNU General Public License ”or any later
-version” applies to it, you have the option of following the terms and
-conditions either of that numbered version or of any later version published by the
-Free Software Foundation. If the Program does not specify a version number of the GNU
-General Public License, you may choose any version ever published by the Free Software
-Foundation.
-
-If the Program specifies that a proxy can decide which future versions of the GNU
-General Public License can be used, that proxy's public statement of acceptance of a
-version permanently authorizes you to choose that version for the Program.
-
-Later license versions may give you additional or different permissions. However, no
-additional obligations are imposed on any author or copyright holder as a result of
-your choosing to follow a later version.
-15. Disclaimer of Warranty.
-
-THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM ”AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
-EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
-QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
-DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-16. Limitation of Liability.
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
-WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-17. Interpretation of Sections 15 and 16.
-
-If the disclaimer of warranty and limitation of liability provided above cannot be
-given local legal effect according to their terms, reviewing courts shall apply local
-law that most closely approximates an absolute waiver of all civil liability in
-connection with the Program, unless a warranty or assumption of liability accompanies
-a copy of the Program in return for a fee.
-
-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 the ”copyright” line and a pointer to
-where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program does terminal interaction, make it output a short notice like this when
-it starts in an interactive mode:
-
- <program> Copyright (C) <year> <name of author>
- This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate parts of
-the General Public License. Of course, your program's commands might be different; for
-a GUI interface, you would use an ”about box”.
-
-You should also get your employer (if you work as a programmer) or school, if any, to
-sign a ”copyright disclaimer” for the program, if necessary. For more
-information on this, and how to apply and follow the GNU GPL, see
-<http://www.gnu.org/licenses/>.
-
-The GNU General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may consider it
-more useful to permit linking proprietary applications with the library. If this is
-what you want to do, use the GNU Lesser General Public License instead of this
-License. But first, please read
-<http://www.gnu.org/philosophy/why-not-lgpl.html>.
-
-
-
-GPL-3.0-with-GCC-exception
-
-
-insert GPL v3 text here
-
-GCC RUNTIME LIBRARY EXCEPTION
-Version 3.1, 31 March 2009
-
-General information:
-http://www.gnu.org/licenses/gcc-exception.html
-Copyright (C) 2009 Free Software Foundation, Inc. <http://fsf.org/>
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-This GCC Runtime Library Exception ("Exception") is an additional permission under
-section 7 of the GNU General Public License, version 3 ("GPLv3"). It applies to a
-given file (the "Runtime Library") that bears a notice placed by the copyright holder
-of the file stating that the file is governed by GPLv3 along with this Exception.
-When you use GCC to compile a program, GCC may combine portions of certain GCC header
-files and runtime libraries with the compiled program. The purpose of this Exception
-is to allow compilation of non-GPL (including proprietary) programs to use, in this
-way, the header files and runtime libraries covered by this Exception.
-
-0. Definitions.
-A file is an "Independent Module" if it either requires the Runtime Library for
-execution after a Compilation Process, or makes use of an interface provided by the
-Runtime Library, but is not otherwise based on the Runtime Library.
-"GCC" means a version of the GNU Compiler Collection, with or without modifications,
-governed by version 3 (or a specified later version) of the GNU General Public License
-(GPL) with the option of using any subsequent versions published by the FSF.
-"GPL-compatible Software" is software whose conditions of propagation, modification
-and use would permit combination with GCC in accord with the license of GCC.
-"Target Code" refers to output from any compiler for a real or virtual target
-processor architecture, in executable form or suitable for input to an assembler,
-loader, linker and/or execution phase. Notwithstanding that, Target Code does not
-include data in any format that is used as a compiler intermediate representation, or
-used for producing a compiler intermediate representation.
-The "Compilation Process" transforms code entirely represented in non-intermediate
-languages designed for human-written code, and/or in Java Virtual Machine byte code,
-into Target Code. Thus, for example, use of source code generators and preprocessors
-need not be considered part of the Compilation Process, since the Compilation Process
-can be understood as starting with the output of the generators or preprocessors.
-A Compilation Process is "Eligible" if it is done using GCC, alone or with other
-GPL-compatible software, or if it is done without using any work based on GCC. For
-example, using non-GPL-compatible Software to optimize any GCC intermediate
-representations would not qualify as an Eligible Compilation Process.
-
-1. Grant of Additional Permission.
-You have permission to propagate a work of Target Code formed by combining the Runtime
-Library with Independent Modules, even if such propagation would otherwise violate the
-terms of GPLv3, provided that all Target Code was generated by Eligible Compilation
-Processes. You may then convey such a combination under terms of your choice,
-consistent with the licensing of the Independent Modules.
-
-2. No Weakening of GCC Copyleft.
-The availability of this Exception does not imply any general presumption that
-third-party software is unaffected by the copyleft requirements of the license of GCC.
-
-
-
-
-GPL-3.0-with-autoconf-exception
-
-
-insert GPL v3 text here
-
-AUTOCONF CONFIGURE SCRIPT EXCEPTION
-
-Version 3.0, 18 August 2009
-
-Copyright © 2009 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-
-This Exception is an additional permission under section 7 of the GNU General Public
-License, version 3 ("GPLv3"). It applies to a given file that bears a notice placed by
-the copyright holder of the file stating that the file is governed by GPLv3 along with
-this Exception.
-
-The purpose of this Exception is to allow distribution of Autoconf`s typical output
-under terms of the recipient`s choice (including proprietary).
-
-0. Definitions.
-"Covered Code" is the source or object code of a version of Autoconf that is a covered
-work under this License.
-
-"Normally Copied Code" for a version of Autoconf means all parts of its Covered Code
-which that version can copy from its code (i.e., not from its input file) into its
-minimally verbose, non-debugging and non-tracing output.
-
-"Ineligible Code" is Covered Code that is not Normally Copied Code.
-
-1. Grant of Additional Permission.
-You have permission to propagate output of Autoconf, even if such propagation would
-otherwise violate the terms of GPLv3. However, if by modifying Autoconf you cause any
-Ineligible Code of the version you received to become Normally Copied Code of your
-modified version, then you void this Exception for the resulting covered work. If you
-convey that resulting covered work, you must remove this Exception in accordance with
-the second paragraph of Section 7 of GPLv3.
-
-2. No Weakening of Autoconf Copyleft.
-The availability of this Exception does not imply any general presumption that
-third-party software is unaffected by the copyleft requirements of the license of
-Autoconf.
-
-
-
-
-ICU
-
-COPYRIGHT AND PERMISSION NOTICE
-
-Copyright (c) 1995-2012 International Business Machines Corporation and others
-
-All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this
-software and associated documentation files (the "Software"), to deal in the Software
-without restriction, including without limitation the rights to use, copy, modify,
-merge, publish, distribute, and/or sell copies of the Software, and to permit persons
-to whom the Software is furnished to do so, provided that the above copyright
-notice(s) and this permission notice appear in all copies of the Software and that
-both the above copyright notice(s) and this permission notice appear in supporting
-documentation.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
-INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
-PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
-COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
-SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
-LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
-TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
-SOFTWARE.
-
-Except as contained in this notice, the name of a copyright holder shall not be used
-in advertising or otherwise to promote the sale, use or other dealings in this
-Software without prior written authorization of the copyright holder.
-
-All trademarks and registered trademarks mentioned herein are the property of their
-respective owners.
-
-
-
-IPL-1.0
-
-
-IBM Public License Version 1.0
-
-THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS IBM
-PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
-OF THE PROGRAM CONSTITUTES RECIPIENT`S ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS
-"Contribution" means:
-
-in the case of International Business Machines Corporation ("IBM"), the Original
-Program, and
-in the case of each Contributor,
-changes to the Program, and
-additions to the Program;
-where such changes and/or additions to the Program originate from and
-are distributed by that particular Contributor. A Contribution
-`originates` from a Contributor if it was added to the Program by
-such Contributor itself or anyone acting on such Contributor`s
-behalf. Contributions do not include additions to the Program which:
-(i) are separate modules of software distributed in conjunction with
-the Program under their own license agreement, and (ii) are not
-derivative works of the Program.
-
-"Contributor" means IBM and any other entity that distributes the Program.
-
-"Licensed Patents " mean patent claims licensable by a
-Contributor which are necessarily infringed by the use or sale of its
-Contribution alone or when combined with the Program.
-
-"Original Program" means the original version of the software
-accompanying this Agreement as released by IBM, including source
-code, object code and documentation, if any.
-
-"Program" means the Original Program and Contributions.
-
-"Recipient" means anyone who receives the Program under this
-Agreement, including all Contributors.
-
-2. GRANT OF RIGHTS
-Subject to the terms of this Agreement, each Contributor hereby
-grants Recipient a non-exclusive, worldwide, royalty-free copyright
-license to reproduce, prepare derivative works of, publicly display,
-publicly perform, distribute and sublicense the Contribution of such
-Contributor, if any, and such derivative works, in source code and
-object code form.
-Subject to the terms of this Agreement, each Contributor hereby
-grants Recipient a non-exclusive, worldwide, royalty-free patent
-license under Licensed Patents to make, use, sell, offer to sell,
-import and otherwise transfer the Contribution of such Contributor,
-if any, in source code and object code form. This patent license
-shall apply to the combination of the Contribution and the Program
-if, at the time the Contribution is added by the Contributor, such
-addition of the Contribution causes such combination to be covered by
-the Licensed Patents. The patent license shall not apply to any
-other combinations which include the Contribution. No hardware per
-se is licensed hereunder.
-
-Recipient understands that although each Contributor grants the
-licenses to its Contributions set forth herein, no assurances are
-provided by any Contributor that the Program does not infringe the
-patent or other intellectual property rights of any other entity.
-Each Contributor disclaims any liability to Recipient for claims
-brought by any other entity based on infringement of intellectual
-property rights or otherwise. As a condition to exercising the
-rights and licenses granted hereunder, each Recipient hereby assumes
-sole responsibility to secure any other intellectual property rights
-needed, if any. For example, if a third party patent license is
-required to allow Recipient to distribute the Program, it is
-Recipient`s responsibility to acquire that license before
-distributing the Program.
-Each Contributor represents that to its knowledge it has
-sufficient copyright rights in its Contribution, if any, to grant the
-copyright license set forth in this Agreement.
-3. REQUIREMENTS
-A Contributor may choose to distribute
-the Program in object code form under its own license agreement,
-provided that:
-
-it complies with the terms and conditions of this Agreement; and
-its license agreement:
-effectively disclaims on behalf of all Contributors all warranties
-and conditions, express and implied, including warranties or
-conditions of title and non-infringement, and implied warranties or
-conditions of merchantability and fitness for a particular purpose;
-effectively excludes on behalf of all Contributors all liability
-for damages, including direct, indirect, special, incidental and
-consequential damages, such as lost profits;
-states that any provisions which differ from this Agreement are
-offered by that Contributor alone and not by any other party; and
-
-states that source code for the Program is available from such
-Contributor, and informs licensees how to obtain it in a reasonable
-manner on or through a medium customarily used for software exchange.
-When the Program is made available in source code form:
-
-it must be made available under this Agreement; and
-a copy of this Agreement must be included with each copy of the
-Program.
-Each Contributor must include the following in a conspicuous location in the Program:
-
-Copyright (C) 1996, 1999 International Business Machines Corporation and others. All
-Rights Reserved.
-
-In addition, each Contributor must identify itself as the originator
-of its Contribution, if any, in a manner that reasonably allows
-subsequent Recipients to identify the originator of the Contribution.
-
-4. COMMERCIAL DISTRIBUTION
-Commercial distributors of software may accept certain
-responsibilities with respect to end users, business partners and the
-like. While this license is intended to facilitate the commercial
-use of the Program, the Contributor who includes the Program in a
-commercial product offering should do so in a manner which does not
-create potential liability for other Contributors. Therefore, if a
-Contributor includes the Program in a commercial product offering,
-such Contributor ("Commercial Contributor") hereby agrees to defend
-and indemnify every other Contributor ("Indemnified Contributor")
-against any losses, damages and costs (collectively "Losses") arising
-from claims, lawsuits and other legal actions brought by a third
-party against the Indemnified Contributor to the extent caused by the
-acts or omissions of such Commercial Contributor in connection with
-its distribution of the Program in a commercial product offering.
-The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement.
-In order to qualify, an Indemnified Contributor must: a) promptly
-notify the Commercial Contributor in writing of such claim, and b)
-allow the Commercial Contributor to control, and cooperate with the
-Commercial Contributor in, the defense and any related settlement
-negotiations. The Indemnified Contributor may participate in any
-such claim at its own expense.
-
-For example, a Contributor might include the Program in a commercial
-product offering, Product X. That Contributor is then a Commercial
-Contributor. If that Commercial Contributor then makes performance
-claims, or offers warranties related to Product X, those performance
-claims and warranties are such Commercial Contributor`s
-responsibility alone. Under this section, the Commercial Contributor
-would have to defend claims against the other Contributors related to
-those performance claims and warranties, and if a court requires any
-other Contributor to pay any damages as a result, the Commercial
-Contributor must pay those damages.
-
-5. NO WARRANTY
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS
-PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
-WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY
-OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
-responsible for determining the appropriateness of using and
-distributing the Program and assumes all risks associated with its
-exercise of rights under this Agreement, including but not limited to
-the risks and costs of program errors, compliance with applicable
-laws, damage to or loss of data, programs or equipment, and
-unavailability or interruption of operations.
-
-6. DISCLAIMER OF LIABILITY
-EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT
-NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
-TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
-THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
-GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-7. GENERAL
-If any provision of this Agreement is invalid or unenforceable under
-applicable law, it shall not affect the validity or enforceability of
-the remainder of the terms of this Agreement, and without further
-action by the parties hereto, such provision shall be reformed to the
-minimum extent necessary to make such provision valid and enforceable.
-
-If Recipient institutes patent litigation against a Contributor with
-respect to a patent applicable to software (including a cross-claim
-or counterclaim in a lawsuit), then any patent licenses granted by
-that Contributor to such Recipient under this Agreement shall
-terminate as of the date such litigation is filed. In addition, if
-Recipient institutes patent litigation against any entity (including
-a cross-claim or counterclaim in a lawsuit) alleging that the Program
-itself (excluding combinations of the Program with other software or
-hardware) infringes such Recipient`s patent(s), then such Recipient`s
-rights granted under Section 2(b) shall terminate as of the date such
-litigation is filed.
-
-All Recipient`s rights under this Agreement shall terminate if it
-fails to comply with any of the material terms or conditions of this
-Agreement and does not cure such failure in a reasonable period of
-time after becoming aware of such noncompliance. If all Recipient`s
-rights under this Agreement terminate, Recipient agrees to cease use
-and distribution of the Program as soon as reasonably practicable.
-However, Recipient`s obligations under this Agreement and any
-licenses granted by Recipient relating to the Program shall continue
-and survive.
-
-IBM may publish new versions (including revisions) of this Agreement
-from time to time. Each new version of the Agreement will be given a
-distinguishing version number. The Program (including Contributions)
-may always be distributed subject to the version of the Agreement
-under which it was received. In addition, after a new version of the
-Agreement is published, Contributor may elect to distribute the
-Program (including its Contributions) under the new version. No one
-other than IBM has the right to modify this Agreement. Except as
-expressly stated in Sections 2(a) and 2(b) above, Recipient receives
-no rights or licenses to the intellectual property of any Contributor
-under this Agreement, whether expressly, by implication, estoppel or
-otherwise. All rights in the Program not expressly granted under
-this Agreement are reserved.
-
-This Agreement is governed by the laws of the State of New York and
-the intellectual property laws of the United States of America. No
-party to this Agreement will bring a legal action under this
-Agreement more than one year after the cause of action arose. Each
-party waives its rights to a jury trial in any resulting litigation.
-
-
-
-
-ISC
-
-
-ISC License:
-
-Copyright © 2004-2010 by Internet Systems Consortium, Inc. ("ISC")
-Copyright © 1995-2003 by Internet Software Consortium
-
-Permission to use, copy, modify, and/or distribute this software for any purpose with
-or without fee is hereby granted, provided that the above copyright notice and this
-permission notice appear in all copies.
-
-THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
-SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT
-SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY
-DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
-OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
-THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
-
-
-
-JLEX
-
- JLEX COPYRIGHT NOTICE, LICENSE, AND DISCLAIMER
- Copyright 1996-2000 by Elliot Joel Berk and C. Scott Ananian
-
- Permission to use, copy, modify, and distribute this software and its
- documentation for any purpose and without fee is hereby granted,
- provided that the above copyright notice appear in all copies and that
- both the copyright notice and this permission notice and warranty
- disclaimer appear in supporting documentation, and that the name of
- the authors or their employers not be used in advertising or publicity
- pertaining to distribution of the software without specific, written
- prior permission.
-
- The authors and their employers disclaim all warranties with regard to
- this software, including all implied warranties of merchantability and
- fitness. In no event shall the authors or their employers be liable
- for any special, indirect or consequential damages or any damages
- whatsoever resulting from loss of use, data or profits, whether in an
- action of contract, negligence or other tortious action, arising out
- of or in connection with the use or performance of this software.
-
-
-
-LGPL-2.0
-
-GNU LIBRARY GENERAL PUBLIC LICENSE
-
-
-
-Version 2, June 1991
-
-
-
-Copyright (C) 1991 Free Software Foundation, Inc.
-
-51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
-
-Everyone is permitted to copy and distribute verbatim copies
-
-of this license document, but changing it is not allowed.
-
-
-
-[This is the first released version of the library GPL. It is
-
- numbered 2 because it goes with version 2 of the ordinary GPL.]
-
-Preamble
-
-
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public Licenses are intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users.
-
-
-
-This license, the Library General Public License, applies to some specially designated
-Free Software Foundation software, and to any other libraries whose authors decide to
-use it. You can use it for your libraries, too.
-
-
-
-When we speak of free software, we are referring to freedom, not price. Our General
-Public Licenses are designed to make sure that you have the freedom to distribute
-copies of free software (and charge for this service if you wish), that you receive
-source code or can get it if you want it, that you can change the software or use
-pieces of it in new free programs; and that you know you can do these things.
-
-
-
-To protect your rights, we need to make restrictions that forbid anyone to deny you
-these rights or to ask you to surrender the rights. These restrictions translate to
-certain responsibilities for you if you distribute copies of the library, or if you
-modify it.
-
-
-
-For example, if you distribute copies of the library, whether gratis or for a fee, you
-must give the recipients all the rights that we gave you. You must make sure that
-they, too, receive or can get the source code. If you link a program with the library,
-you must provide complete object files to the recipients so that they can relink them
-with the library, after making changes to the library and recompiling it. And you must
-show them these terms so they know their rights.
-
-
-
-Our method of protecting your rights has two steps: (1) copyright the library, and (2)
-offer you this license which gives you legal permission to copy, distribute and/or
-modify the library.
-
-
-
-Also, for each distributor's protection, we want to make certain that everyone
-understands that there is no warranty for this free library. If the library is
-modified by someone else and passed on, we want its recipients to know that what they
-have is not the original version, so that any problems introduced by others will not
-reflect on the original authors' reputations.
-
-
-
-Finally, any free program is threatened constantly by software patents. We wish to
-avoid the danger that companies distributing free software will individually obtain
-patent licenses, thus in effect transforming the program into proprietary software. To
-prevent this, we have made it clear that any patent must be licensed for everyone's
-free use or not licensed at all.
-
-
-
-Most GNU software, including some libraries, is covered by the ordinary GNU General
-Public License, which was designed for utility programs. This license, the GNU Library
-General Public License, applies to certain designated libraries. This license is quite
-different from the ordinary one; be sure to read it in full, and don't assume that
-anything in it is the same as in the ordinary license.
-
-
-
-The reason we have a separate public license for some libraries is that they blur the
-distinction we usually make between modifying or adding to a program and simply using
-it. Linking a program with a library, without changing the library, is in some sense
-simply using the library, and is analogous to running a utility program or application
-program. However, in a textual and legal sense, the linked executable is a combined
-work, a derivative of the original library, and the ordinary General Public License
-treats it as such.
-
-
-
-Because of this blurred distinction, using the ordinary General Public License for
-libraries did not effectively promote software sharing, because most developers did
-not use the libraries. We concluded that weaker conditions might promote sharing
-better.
-
-
-
-However, unrestricted linking of non-free programs would deprive the users of those
-programs of all benefit from the free status of the libraries themselves. This Library
-General Public License is intended to permit developers of non-free programs to use
-free libraries, while preserving your freedom as a user of such programs to change the
-free libraries that are incorporated in them. (We have not seen how to achieve this as
-regards changes in header files, but we have achieved it as regards changes in the
-actual functions of the Library.) The hope is that this will lead to faster
-development of free libraries.
-
-
-
-The precise terms and conditions for copying, distribution and modification follow.
-Pay close attention to the difference between a "work based on the library" and a
-"work that uses the library". The former contains code derived from the library, while
-the latter only works together with the library.
-
-
-
-Note that it is possible for a library to be covered by the ordinary General Public
-License rather than by this special one.
-
-
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-
-
-0. This License Agreement applies to any software library which contains a notice
-placed by the copyright holder or other authorized party saying it may be distributed
-under the terms of this Library General Public License (also called "this License").
-Each licensee is addressed as "you".
-
-
-
-A "library" means a collection of software functions and/or data prepared so as to be
-conveniently linked with application programs (which use some of those functions and
-data) to form executables.
-
-
-
-The "Library", below, refers to any such software library or work which has been
-distributed under these terms. A "work based on the Library" means either the Library
-or any derivative work under copyright law: that is to say, a work containing the
-Library or a portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is included without
-limitation in the term "modification".)
-
-
-
-"Source code" for a work means the preferred form of the work for making modifications
-to it. For a library, complete source code means all the source code for all modules
-it contains, plus any associated interface definition files, plus the scripts used to
-control compilation and installation of the library.
-
-
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running a program using the Library is
-not restricted, and output from such a program is covered only if its contents
-constitute a work based on the Library (independent of the use of the Library in a
-tool for writing it). Whether that is true depends on what the Library does and what
-the program that uses the Library does.
-
-
-
-1. You may copy and distribute verbatim copies of the Library's complete source code
-as you receive it, in any medium, provided that you conspicuously and appropriately
-publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
-intact all the notices that refer to this License and to the absence of any warranty;
-and distribute a copy of this License along with the Library.
-
-
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-
-
-2. You may modify your copy or copies of the Library or any portion of it, thus
-forming a work based on the Library, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-
-
-a) The modified work must itself be a software library.
-
-b) You must cause the files modified to carry prominent notices stating that you
-changed the files and the date of any change.
-
-c) You must cause the whole of the work to be licensed at no charge to all third
-parties under the terms of this License.
-
-d) If a facility in the modified Library refers to a function or a table of data to be
-supplied by an application program that uses the facility, other than as an argument
-passed when the facility is invoked, then you must make a good faith effort to ensure
-that, in the event an application does not supply such function or table, the facility
-still operates, and performs whatever part of its purpose remains meaningful.
-
-(For example, a function in a library to compute square roots has a purpose that is
-entirely well-defined independent of the application. Therefore, Subsection 2d
-requires that any application-supplied function or table used by this function must be
-optional: if the application does not supply it, the square root function must still
-compute square roots.)
-
-
-
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Library, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Library,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Library.
-
-
-
-In addition, mere aggregation of another work not based on the Library with the
-Library (or with a work based on the Library) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-
-
-3. You may opt to apply the terms of the ordinary GNU General Public License instead
-of this License to a given copy of the Library. To do this, you must alter all the
-notices that refer to this License, so that they refer to the ordinary GNU General
-Public License, version 2, instead of to this License. (If a newer version than
-version 2 of the ordinary GNU General Public License has appeared, then you can
-specify that version instead if you wish.) Do not make any other change in these
-notices.
-
-
-
-Once this change is made in a given copy, it is irreversible for that copy, so the
-ordinary GNU General Public License applies to all subsequent copies and derivative
-works made from that copy.
-
-
-
-This option is useful when you wish to copy part of the code of the Library into a
-program that is not a library.
-
-
-
-4. You may copy and distribute the Library (or a portion or derivative of it, under
-Section 2) in object code or executable form under the terms of Sections 1 and 2 above
-provided that you accompany it with the complete corresponding machine-readable source
-code, which must be distributed under the terms of Sections 1 and 2 above on a medium
-customarily used for software interchange.
-
-
-
-If distribution of object code is made by offering access to copy from a designated
-place, then offering equivalent access to copy the source code from the same place
-satisfies the requirement to distribute the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-
-
-5. A program that contains no derivative of any portion of the Library, but is
-designed to work with the Library by being compiled or linked with it, is called a
-"work that uses the Library". Such a work, in isolation, is not a derivative work of
-the Library, and therefore falls outside the scope of this License.
-
-
-
-However, linking a "work that uses the Library" with the Library creates an executable
-that is a derivative of the Library (because it contains portions of the Library),
-rather than a "work that uses the library". The executable is therefore covered by
-this License. Section 6 states terms for distribution of such executables.
-
-
-
-When a "work that uses the Library" uses material from a header file that is part of
-the Library, the object code for the work may be a derivative work of the Library even
-though the source code is not. Whether this is true is especially significant if the
-work can be linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
-
-
-If such an object file uses only numerical parameters, data structure layouts and
-accessors, and small macros and small inline functions (ten lines or less in length),
-then the use of the object file is unrestricted, regardless of whether it is legally a
-derivative work. (Executables containing this object code plus portions of the Library
-will still fall under Section 6.)
-
-
-
-Otherwise, if the work is a derivative of the Library, you may distribute the object
-code for the work under the terms of Section 6. Any executables containing that work
-also fall under Section 6, whether or not they are linked directly with the Library
-itself.
-
-
-
-6. As an exception to the Sections above, you may also compile or link a "work that
-uses the Library" with the Library to produce a work containing portions of the
-Library, and distribute that work under terms of your choice, provided that the terms
-permit modification of the work for the customer's own use and reverse engineering for
-debugging such modifications.
-
-
-
-You must give prominent notice with each copy of the work that the Library is used in
-it and that the Library and its use are covered by this License. You must supply a
-copy of this License. If the work during execution displays copyright notices, you
-must include the copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one of these things:
-
-
-
-a) Accompany the work with the complete corresponding machine-readable source code for
-the Library including whatever changes were used in the work (which must be
-distributed under Sections 1 and 2 above); and, if the work is an executable linked
-with the Library, with the complete machine-readable "work that uses the Library", as
-object code and/or source code, so that the user can modify the Library and then
-relink to produce a modified executable containing the modified Library. (It is
-understood that the user who changes the contents of definitions files in the Library
-will not necessarily be able to recompile the application to use the modified
-definitions.)
-
-b) Accompany the work with a written offer, valid for at least three years, to give
-the same user the materials specified in Subsection 6a, above, for a charge no more
-than the cost of performing this distribution.
-
-c) If distribution of the work is made by offering access to copy from a designated
-place, offer equivalent access to copy the above specified materials from the same
-place.
-
-d) Verify that the user has already received a copy of these materials or that you
-have already sent this user a copy.
-
-For an executable, the required form of the "work that uses the Library" must include
-any data and utility programs needed for reproducing the executable from it. However,
-as a special exception, the source code distributed need not include anything that is
-normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-
-
-It may happen that this requirement contradicts the license restrictions of other
-proprietary libraries that do not normally accompany the operating system. Such a
-contradiction means you cannot use both them and the Library together in an executable
-that you distribute.
-
-
-
-7. You may place library facilities that are a work based on the Library side-by-side
-in a single library together with other library facilities not covered by this
-License, and distribute such a combined library, provided that the separate
-distribution of the work based on the Library and of the other library facilities is
-otherwise permitted, and provided that you do these two things:
-
-
-
-a) Accompany the combined library with a copy of the same work based on the Library,
-uncombined with any other library facilities. This must be distributed under the terms
-of the Sections above.
-
-b) Give prominent notice with the combined library of the fact that part of it is a
-work based on the Library, and explaining where to find the accompanying uncombined
-form of the same work.
-
-8. You may not copy, modify, sublicense, link with, or distribute the Library except
-as expressly provided under this License. Any attempt otherwise to copy, modify,
-sublicense, link with, or distribute the Library is void, and will automatically
-terminate your rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses terminated so long
-as such parties remain in full compliance.
-
-
-
-9. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Library or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Library or works based on it.
-
-
-
-10. Each time you redistribute the Library (or any work based on the Library), the
-recipient automatically receives a license from the original licensor to copy,
-distribute, link with or modify the Library subject to these terms and conditions. You
-may not impose any further restrictions on the recipients' exercise of the rights
-granted herein. You are not responsible for enforcing compliance by third parties to
-this License.
-
-
-
-11. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Library at all. For example, if a patent license would not permit royalty-free
-redistribution of the Library by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply, and the section as a
-whole is intended to apply in other circumstances.
-
-
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-
-
-12. If the distribution and/or use of the Library is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Library under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-
-
-13. The Free Software Foundation may publish revised and/or new versions of the
-Library General Public License from time to time. Such new versions will be similar in
-spirit to the present version, but may differ in detail to address new problems or
-concerns.
-
-
-
-Each version is given a distinguishing version number. If the Library specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Library does not
-specify a license version number, you may choose any version ever published by the
-Free Software Foundation.
-
-
-
-14. If you wish to incorporate parts of the Library into other free programs whose
-distribution conditions are incompatible with these, write to the author to ask for
-permission. For software which is copyrighted by the Free Software Foundation, write
-to the Free Software Foundation; we sometimes make exceptions for this. Our decision
-will be guided by the two goals of preserving the free status of all derivatives of
-our free software and of promoting the sharing and reuse of software generally.
-
-
-
-NO WARRANTY
-
-
-
-15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-
-
-16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
-WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-
-
-END OF TERMS AND CONDITIONS
-
-
-
-How to Apply These Terms to Your New Libraries
-
-
-
-If you develop a new library, and you want it to be of the greatest possible use to
-the public, we recommend making it free software that everyone can redistribute and
-change. You can do so by permitting redistribution under these terms (or,
-alternatively, under the terms of the ordinary General Public License).
-
-
-
-To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
-where the full notice is found.
-
-
-
-one line to give the library's name and an idea of what it does.
-
-Copyright (C) year name of author
-
-
-
-This library is free software; you can redistribute it and/or
-
-modify it under the terms of the GNU Library General Public
-
-License as published by the Free Software Foundation; either
-
-version 2 of the License, or (at your option) any later version.
-
-
-
-This library is distributed in the hope that it will be useful,
-
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-
-Library General Public License for more details.
-
-
-
-You should have received a copy of the GNU Library General Public
-
-License along with this library; if not, write to the
-
-Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
-
-Boston, MA 02110-1301, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
-alter the names:
-
-
-
-Yoyodyne, Inc., hereby disclaims all copyright interest in
-
-the library `Frob' (a library for tweaking knobs) written
-
-by James Random Hacker.
-
-
-
-signature of Ty Coon, 1 April 1990
-
-Ty Coon, President of Vice
-
-That's all there is to it!
-
-
-
-
-LGPL-2.1
-
-
-GNU LESSER GENERAL PUBLIC LICENSE
-
-Version 2.1, February 1999
-
-Copyright (C) 1991, 1999 Free Software Foundation, Inc.
-51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL. It also counts
- as the successor of the GNU Library Public License, version 2, hence
- the version number 2.1.]
-Preamble
-
-The licenses for most software are designed to take away your freedom to share and
-change it. By contrast, the GNU General Public Licenses are intended to guarantee your
-freedom to share and change free software--to make sure the software is free for all
-its users.
-
-This license, the Lesser General Public License, applies to some specially designated
-software packages--typically libraries--of the Free Software Foundation and other
-authors who decide to use it. You can use it too, but we suggest you first think
-carefully about whether this license or the ordinary General Public License is the
-better strategy to use in any particular case, based on the explanations below.
-
-When we speak of free software, we are referring to freedom of use, not price. Our
-General Public Licenses are designed to make sure that you have the freedom to
-distribute copies of free software (and charge for this service if you wish); that you
-receive source code or can get it if you want it; that you can change the software and
-use pieces of it in new free programs; and that you are informed that you can do these
-things.
-
-To protect your rights, we need to make restrictions that forbid distributors to deny
-you these rights or to ask you to surrender these rights. These restrictions translate
-to certain responsibilities for you if you distribute copies of the library or if you
-modify it.
-
-For example, if you distribute copies of the library, whether gratis or for a fee, you
-must give the recipients all the rights that we gave you. You must make sure that
-they, too, receive or can get the source code. If you link other code with the
-library, you must provide complete object files to the recipients, so that they can
-relink them with the library after making changes to the library and recompiling it.
-And you must show them these terms so they know their rights.
-
-We protect your rights with a two-step method: (1) we copyright the library, and (2)
-we offer you this license, which gives you legal permission to copy, distribute and/or
-modify the library.
-
-To protect each distributor, we want to make it very clear that there is no warranty
-for the free library. Also, if the library is modified by someone else and passed on,
-the recipients should know that what they have is not the original version, so that
-the original author`s reputation will not be affected by problems that might be
-introduced by others.
-
-Finally, software patents pose a constant threat to the existence of any free program.
-We wish to make sure that a company cannot effectively restrict the users of a free
-program by obtaining a restrictive license from a patent holder. Therefore, we insist
-that any patent license obtained for a version of the library must be consistent with
-the full freedom of use specified in this license.
-
-Most GNU software, including some libraries, is covered by the ordinary GNU General
-Public License. This license, the GNU Lesser General Public License, applies to
-certain designated libraries, and is quite different from the ordinary General Public
-License. We use this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
-When a program is linked with a library, whether statically or using a shared library,
-the combination of the two is legally speaking a combined work, a derivative of the
-original library. The ordinary General Public License therefore permits such linking
-only if the entire combination fits its criteria of freedom. The Lesser General Public
-License permits more lax criteria for linking other code with the library.
-
-We call this license the "Lesser" General Public License because it does Less to
-protect the user`s freedom than the ordinary General Public License. It also provides
-other free software developers Less of an advantage over competing non-free programs.
-These disadvantages are the reason we use the ordinary General Public License for many
-libraries. However, the Lesser license provides advantages in certain special
-circumstances.
-
-For example, on rare occasions, there may be a special need to encourage the widest
-possible use of a certain library, so that it becomes a de-facto standard. To achieve
-this, non-free programs must be allowed to use the library. A more frequent case is
-that a free library does the same job as widely used non-free libraries. In this case,
-there is little to gain by limiting the free library to free software only, so we use
-the Lesser General Public License.
-
-In other cases, permission to use a particular library in non-free programs enables a
-greater number of people to use a large body of free software. For example, permission
-to use the GNU C Library in non-free programs enables many more people to use the
-whole GNU operating system, as well as its variant, the GNU/Linux operating system.
-
-Although the Lesser General Public License is Less protective of the users` freedom,
-it does ensure that the user of a program that is linked with the Library has the
-freedom and the wherewithal to run that program using a modified version of the
-Library.
-
-The precise terms and conditions for copying, distribution and modification follow.
-Pay close attention to the difference between a "work based on the library" and a
-"work that uses the library". The former contains code derived from the library,
-whereas the latter must be combined with the library in order to run.
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-0. This License Agreement applies to any software library or other program which
-contains a notice placed by the copyright holder or other authorized party saying it
-may be distributed under the terms of this Lesser General Public License (also called
-"this License"). Each licensee is addressed as "you".
-
-A "library" means a collection of software functions and/or data prepared so as to be
-conveniently linked with application programs (which use some of those functions and
-data) to form executables.
-
-The "Library", below, refers to any such software library or work which has been
-distributed under these terms. A "work based on the Library" means either the Library
-or any derivative work under copyright law: that is to say, a work containing the
-Library or a portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is included without
-limitation in the term "modification".)
-
-"Source code" for a work means the preferred form of the work for making modifications
-to it. For a library, complete source code means all the source code for all modules
-it contains, plus any associated interface definition files, plus the scripts used to
-control compilation and installation of the library.
-
-Activities other than copying, distribution and modification are not covered by this
-License; they are outside its scope. The act of running a program using the Library is
-not restricted, and output from such a program is covered only if its contents
-constitute a work based on the Library (independent of the use of the Library in a
-tool for writing it). Whether that is true depends on what the Library does and what
-the program that uses the Library does.
-
-1. You may copy and distribute verbatim copies of the Library`s complete source code
-as you receive it, in any medium, provided that you conspicuously and appropriately
-publish on each copy an appropriate copyright notice and disclaimer of warranty; keep
-intact all the notices that refer to this License and to the absence of any warranty;
-and distribute a copy of this License along with the Library.
-
-You may charge a fee for the physical act of transferring a copy, and you may at your
-option offer warranty protection in exchange for a fee.
-
-2. You may modify your copy or copies of the Library or any portion of it, thus
-forming a work based on the Library, and copy and distribute such modifications or
-work under the terms of Section 1 above, provided that you also meet all of these
-conditions:
-
-a) The modified work must itself be a software library.
-b) You must cause the files modified to carry prominent notices stating that you
-changed the files and the date of any change.
-c) You must cause the whole of the work to be licensed at no charge to all third
-parties under the terms of this License.
-d) If a facility in the modified Library refers to a function or a table of data to be
-supplied by an application program that uses the facility, other than as an argument
-passed when the facility is invoked, then you must make a good faith effort to ensure
-that, in the event an application does not supply such function or table, the facility
-still operates, and performs whatever part of its purpose remains meaningful.
-(For example, a function in a library to compute square roots has a purpose that is
-entirely well-defined independent of the application. Therefore, Subsection 2d
-requires that any application-supplied function or table used by this function must be
-optional: if the application does not supply it, the square root function must still
-compute square roots.)
-
-These requirements apply to the modified work as a whole. If identifiable sections of
-that work are not derived from the Library, and can be reasonably considered
-independent and separate works in themselves, then this License, and its terms, do not
-apply to those sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based on the Library,
-the distribution of the whole must be on the terms of this License, whose permissions
-for other licensees extend to the entire whole, and thus to each and every part
-regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest your rights to
-work written entirely by you; rather, the intent is to exercise the right to control
-the distribution of derivative or collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library with the
-Library (or with a work based on the Library) on a volume of a storage or distribution
-medium does not bring the other work under the scope of this License.
-
-3. You may opt to apply the terms of the ordinary GNU General Public License instead
-of this License to a given copy of the Library. To do this, you must alter all the
-notices that refer to this License, so that they refer to the ordinary GNU General
-Public License, version 2, instead of to this License. (If a newer version than
-version 2 of the ordinary GNU General Public License has appeared, then you can
-specify that version instead if you wish.) Do not make any other change in these
-notices.
-
-Once this change is made in a given copy, it is irreversible for that copy, so the
-ordinary GNU General Public License applies to all subsequent copies and derivative
-works made from that copy.
-
-This option is useful when you wish to copy part of the code of the Library into a
-program that is not a library.
-
-4. You may copy and distribute the Library (or a portion or derivative of it, under
-Section 2) in object code or executable form under the terms of Sections 1 and 2 above
-provided that you accompany it with the complete corresponding machine-readable source
-code, which must be distributed under the terms of Sections 1 and 2 above on a medium
-customarily used for software interchange.
-
-If distribution of object code is made by offering access to copy from a designated
-place, then offering equivalent access to copy the source code from the same place
-satisfies the requirement to distribute the source code, even though third parties are
-not compelled to copy the source along with the object code.
-
-5. A program that contains no derivative of any portion of the Library, but is
-designed to work with the Library by being compiled or linked with it, is called a
-"work that uses the Library". Such a work, in isolation, is not a derivative work of
-the Library, and therefore falls outside the scope of this License.
-
-However, linking a "work that uses the Library" with the Library creates an executable
-that is a derivative of the Library (because it contains portions of the Library),
-rather than a "work that uses the library". The executable is therefore covered by
-this License. Section 6 states terms for distribution of such executables.
-
-When a "work that uses the Library" uses material from a header file that is part of
-the Library, the object code for the work may be a derivative work of the Library even
-though the source code is not. Whether this is true is especially significant if the
-work can be linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
-If such an object file uses only numerical parameters, data structure layouts and
-accessors, and small macros and small inline functions (ten lines or less in length),
-then the use of the object file is unrestricted, regardless of whether it is legally a
-derivative work. (Executables containing this object code plus portions of the Library
-will still fall under Section 6.)
-
-Otherwise, if the work is a derivative of the Library, you may distribute the object
-code for the work under the terms of Section 6. Any executables containing that work
-also fall under Section 6, whether or not they are linked directly with the Library
-itself.
-
-6. As an exception to the Sections above, you may also combine or link a "work that
-uses the Library" with the Library to produce a work containing portions of the
-Library, and distribute that work under terms of your choice, provided that the terms
-permit modification of the work for the customer`s own use and reverse engineering for
-debugging such modifications.
-
-You must give prominent notice with each copy of the work that the Library is used in
-it and that the Library and its use are covered by this License. You must supply a
-copy of this License. If the work during execution displays copyright notices, you
-must include the copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one of these things:
-
-a) Accompany the work with the complete corresponding machine-readable source code for
-the Library including whatever changes were used in the work (which must be
-distributed under Sections 1 and 2 above); and, if the work is an executable linked
-with the Library, with the complete machine-readable "work that uses the Library", as
-object code and/or source code, so that the user can modify the Library and then
-relink to produce a modified executable containing the modified Library. (It is
-understood that the user who changes the contents of definitions files in the Library
-will not necessarily be able to recompile the application to use the modified
-definitions.)
-b) Use a suitable shared library mechanism for linking with the Library. A suitable
-mechanism is one that (1) uses at run time a copy of the library already present on
-the user`s computer system, rather than copying library functions into the executable,
-and (2) will operate properly with a modified version of the library, if the user
-installs one, as long as the modified version is interface-compatible with the version
-that the work was made with.
-c) Accompany the work with a written offer, valid for at least three years, to give
-the same user the materials specified in Subsection 6a, above, for a charge no more
-than the cost of performing this distribution.
-d) If distribution of the work is made by offering access to copy from a designated
-place, offer equivalent access to copy the above specified materials from the same
-place.
-e) Verify that the user has already received a copy of these materials or that you
-have already sent this user a copy.
-For an executable, the required form of the "work that uses the Library" must include
-any data and utility programs needed for reproducing the executable from it. However,
-as a special exception, the materials to be distributed need not include anything that
-is normally distributed (in either source or binary form) with the major components
-(compiler, kernel, and so on) of the operating system on which the executable runs,
-unless that component itself accompanies the executable.
-
-It may happen that this requirement contradicts the license restrictions of other
-proprietary libraries that do not normally accompany the operating system. Such a
-contradiction means you cannot use both them and the Library together in an executable
-that you distribute.
-
-7. You may place library facilities that are a work based on the Library side-by-side
-in a single library together with other library facilities not covered by this
-License, and distribute such a combined library, provided that the separate
-distribution of the work based on the Library and of the other library facilities is
-otherwise permitted, and provided that you do these two things:
-
-a) Accompany the combined library with a copy of the same work based on the Library,
-uncombined with any other library facilities. This must be distributed under the terms
-of the Sections above.
-b) Give prominent notice with the combined library of the fact that part of it is a
-work based on the Library, and explaining where to find the accompanying uncombined
-form of the same work.
-8. You may not copy, modify, sublicense, link with, or distribute the Library except
-as expressly provided under this License. Any attempt otherwise to copy, modify,
-sublicense, link with, or distribute the Library is void, and will automatically
-terminate your rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses terminated so long
-as such parties remain in full compliance.
-
-9. You are not required to accept this License, since you have not signed it. However,
-nothing else grants you permission to modify or distribute the Library or its
-derivative works. These actions are prohibited by law if you do not accept this
-License. Therefore, by modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and all its terms and
-conditions for copying, distributing or modifying the Library or works based on it.
-
-10. Each time you redistribute the Library (or any work based on the Library), the
-recipient automatically receives a license from the original licensor to copy,
-distribute, link with or modify the Library subject to these terms and conditions. You
-may not impose any further restrictions on the recipients` exercise of the rights
-granted herein. You are not responsible for enforcing compliance by third parties with
-this License.
-
-11. If, as a consequence of a court judgment or allegation of patent infringement or
-for any other reason (not limited to patent issues), conditions are imposed on you
-(whether by court order, agreement or otherwise) that contradict the conditions of
-this License, they do not excuse you from the conditions of this License. If you
-cannot distribute so as to satisfy simultaneously your obligations under this License
-and any other pertinent obligations, then as a consequence you may not distribute the
-Library at all. For example, if a patent license would not permit royalty-free
-redistribution of the Library by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any particular
-circumstance, the balance of the section is intended to apply, and the section as a
-whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any patents or other
-property right claims or to contest validity of any such claims; this section has the
-sole purpose of protecting the integrity of the free software distribution system
-which is implemented by public license practices. Many people have made generous
-contributions to the wide range of software distributed through that system in
-reliance on consistent application of that system; it is up to the author/donor to
-decide if he or she is willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-This section is intended to make thoroughly clear what is believed to be a consequence
-of the rest of this License.
-
-12. If the distribution and/or use of the Library is restricted in certain countries
-either by patents or by copyrighted interfaces, the original copyright holder who
-places the Library under this License may add an explicit geographical distribution
-limitation excluding those countries, so that distribution is permitted only in or
-among countries not thus excluded. In such case, this License incorporates the
-limitation as if written in the body of this License.
-
-13. The Free Software Foundation may publish revised and/or new versions of the Lesser
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library specifies a
-version number of this License which applies to it and "any later version", you have
-the option of following the terms and conditions either of that version or of any
-later version published by the Free Software Foundation. If the Library does not
-specify a license version number, you may choose any version ever published by the
-Free Software Foundation.
-
-14. If you wish to incorporate parts of the Library into other free programs whose
-distribution conditions are incompatible with these, write to the author to ask for
-permission. For software which is copyrighted by the Free Software Foundation, write
-to the Free Software Foundation; we sometimes make exceptions for this. Our decision
-will be guided by the two goals of preserving the free status of all derivatives of
-our free software and of promoting the sharing and reuse of software generally.
-
-NO WARRANTY
-
-15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
-LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN
-WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
-RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
-PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
-COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS
-PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
-OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE
-WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-END OF TERMS AND CONDITIONS
-
-How to Apply These Terms to Your New Libraries
-
-If you develop a new library, and you want it to be of the greatest possible use to
-the public, we recommend making it free software that everyone can redistribute and
-change. You can do so by permitting redistribution under these terms (or,
-alternatively, under the terms of the ordinary General Public License).
-
-To apply these terms, attach the following notices to the library. 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 the "copyright" line and a pointer to
-where the full notice is found.
-
-one line to give the library`s name and an idea of what it does.
-Copyright (C) year name of author
-
-This library is free software; you can redistribute it and/or
-modify it under the terms of the GNU Lesser General Public
-License as published by the Free Software Foundation; either
-version 2.1 of the License, or (at your option) any later version.
-
-This library is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-Lesser General Public License for more details.
-
-You should have received a copy of the GNU Lesser General Public
-License along with this library; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
-Also add information on how to contact you by electronic and paper mail.
-
-You should also get your employer (if you work as a programmer) or your school, if
-any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample;
-alter the names:
-
-Yoyodyne, Inc., hereby disclaims all copyright interest in
-the library `Frob` (a library for tweaking knobs) written
-by James Random Hacker.
-
-signature of Ty Coon, 1 April 1990
-Ty Coon, President of Vice
-That`s all there is to it!
-
-
-
-
-LGPL-3.0
-
-GNU LESSER GENERAL PUBLIC LICENSE
-
-Version 3, 29 June 2007
-
-Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this license document,
-but changing it is not allowed.
-
-This version of the GNU Lesser General Public License incorporates the terms and
-conditions of version 3 of the GNU General Public License, supplemented by the
-additional permissions listed below.
-0. Additional Definitions.
-
-As used herein, ”this License” refers to version 3 of the GNU Lesser
-General Public License, and the ”GNU GPL” refers to version 3 of the GNU
-General Public License.
-
-”The Library” refers to a covered work governed by this License, other
-than an Application or a Combined Work as defined below.
-
-An ”Application” is any work that makes use of an interface provided by
-the Library, but which is not otherwise based on the Library. Defining a subclass of a
-class defined by the Library is deemed a mode of using an interface provided by the
-Library.
-
-A ”Combined Work” is a work produced by combining or linking an
-Application with the Library. The particular version of the Library with which the
-Combined Work was made is also called the ”Linked Version”.
-
-The ”Minimal Corresponding Source” for a Combined Work means the
-Corresponding Source for the Combined Work, excluding any source code for portions of
-the Combined Work that, considered in isolation, are based on the Application, and not
-on the Linked Version.
-
-The ”Corresponding Application Code” for a Combined Work means the object
-code and/or source code for the Application, including any data and utility programs
-needed for reproducing the Combined Work from the Application, but excluding the
-System Libraries of the Combined Work.
-1. Exception to Section 3 of the GNU GPL.
-
-You may convey a covered work under sections 3 and 4 of this License without being
-bound by section 3 of the GNU GPL.
-2. Conveying Modified Versions.
-
-If you modify a copy of the Library, and, in your modifications, a facility refers to
-a function or data to be supplied by an Application that uses the facility (other than
-as an argument passed when the facility is invoked), then you may convey a copy of the
-modified version:
-
- * a) under this License, provided that you make a good faith effort to ensure
-that, in the event an Application does not supply the function or data, the facility
-still operates, and performs whatever part of its purpose remains meaningful, or
- * b) under the GNU GPL, with none of the additional permissions of this License
-applicable to that copy.
-
-3. Object Code Incorporating Material from Library Header Files.
-
-The object code form of an Application may incorporate material from a header file
-that is part of the Library. You may convey such object code under terms of your
-choice, provided that, if the incorporated material is not limited to numerical
-parameters, data structure layouts and accessors, or small macros, inline functions
-and templates (ten or fewer lines in length), you do both of the following:
-
- * a) Give prominent notice with each copy of the object code that the Library is
-used in it and that the Library and its use are covered by this License.
- * b) Accompany the object code with a copy of the GNU GPL and this license
-document.
-
-4. Combined Works.
-
-You may convey a Combined Work under terms of your choice that, taken together,
-effectively do not restrict modification of the portions of the Library contained in
-the Combined Work and reverse engineering for debugging such modifications, if you
-also do each of the following:
-
- * a) Give prominent notice with each copy of the Combined Work that the Library is
-used in it and that the Library and its use are covered by this License.
- * b) Accompany the Combined Work with a copy of the GNU GPL and this license
-document.
- * c) For a Combined Work that displays copyright notices during execution, include
-the copyright notice for the Library among these notices, as well as a reference
-directing the user to the copies of the GNU GPL and this license document.
- * d) Do one of the following:
- o 0) Convey the Minimal Corresponding Source under the terms of this
-License, and the Corresponding Application Code in a form suitable for, and under
-terms that permit, the user to recombine or relink the Application with a modified
-version of the Linked Version to produce a modified Combined Work, in the manner
-specified by section 6 of the GNU GPL for conveying Corresponding Source.
- o 1) Use a suitable shared library mechanism for linking with the Library. A
-suitable mechanism is one that (a) uses at run time a copy of the Library already
-present on the user's computer system, and (b) will operate properly with a modified
-version of the Library that is interface-compatible with the Linked Version.
- * e) Provide Installation Information, but only if you would otherwise be required
-to provide such information under section 6 of the GNU GPL, and only to the extent
-that such information is necessary to install and execute a modified version of the
-Combined Work produced by recombining or relinking the Application with a modified
-version of the Linked Version. (If you use option 4d0, the Installation Information
-must accompany the Minimal Corresponding Source and Corresponding Application Code. If
-you use option 4d1, you must provide the Installation Information in the manner
-specified by section 6 of the GNU GPL for conveying Corresponding Source.)
-
-5. Combined Libraries.
-
-You may place library facilities that are a work based on the Library side by side in
-a single library together with other library facilities that are not Applications and
-are not covered by this License, and convey such a combined library under terms of
-your choice, if you do both of the following:
-
- * a) Accompany the combined library with a copy of the same work based on the
-Library, uncombined with any other library facilities, conveyed under the terms of
-this License.
- * b) Give prominent notice with the combined library that part of it is a work
-based on the Library, and explaining where to find the accompanying uncombined form of
-the same work.
-
-6. Revised Versions of the GNU Lesser General Public License.
-
-The Free Software Foundation may publish revised and/or new versions of the GNU Lesser
-General Public License from time to time. Such new versions will be similar in spirit
-to the present version, but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library as you received
-it specifies that a certain numbered version of the GNU Lesser General Public License
-”or any later version” applies to it, you have the option of following
-the terms and conditions either of that published version or of any later version
-published by the Free Software Foundation. If the Library as you received it does not
-specify a version number of the GNU Lesser General Public License, you may choose any
-version of the GNU Lesser General Public License ever published by the Free Software
-Foundation.
-
-If the Library as you received it specifies that a proxy can decide whether future
-versions of the GNU Lesser General Public License shall apply, that proxy's public
-statement of acceptance of any version is permanent authorization for you to choose
-that version for the Library.
-
-
-
-Libpng
-
-
-This copy of the libpng notices is provided for your convenience. In case of
-any discrepancy between this copy and the notices in the file png.h that is
-included in the libpng distribution, the latter shall prevail.
-
-COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
-
-If you modify libpng you may insert additional notices immediately following
-this sentence.
-
-This code is released under the libpng license.
-
-libpng versions 1.2.6, August 15, 2004, through 1.4.5, December 9, 2010, are
-Copyright (c) 2004, 2006-2010 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-1.2.5
-with the following individual added to the list of Contributing Authors
-
- Cosmin Truta
-
-libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are
-Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-1.0.6
-with the following individuals added to the list of Contributing Authors
-
- Simon-Pierre Cadieux
- Eric S. Raymond
- Gilles Vollant
-
-and with the following additions to the disclaimer:
-
- There is no warranty against interference with your enjoyment of the
- library or against infringement. There is no warranty that our
- efforts or the library will fulfill any of your particular purposes
- or needs. This library is provided with all faults, and the entire
- risk of satisfactory quality, performance, accuracy, and effort is with
- the user.
-
-libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
-Copyright (c) 1998, 1999 Glenn Randers-Pehrson, and are
-distributed according to the same disclaimer and license as libpng-0.96,
-with the following individuals added to the list of Contributing Authors:
-
- Tom Lane
- Glenn Randers-Pehrson
- Willem van Schaik
-
-libpng versions 0.89, June 1996, through 0.96, May 1997, are
-Copyright (c) 1996, 1997 Andreas Dilger
-Distributed according to the same disclaimer and license as libpng-0.88,
-with the following individuals added to the list of Contributing Authors:
-
- John Bowler
- Kevin Bracey
- Sam Bushell
- Magnus Holmgren
- Greg Roelofs
- Tom Tanner
-
-libpng versions 0.5, May 1995, through 0.88, January 1996, are
-Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.
-
-For the purposes of this copyright and license, "Contributing Authors"
-is defined as the following set of individuals:
-
- Andreas Dilger
- Dave Martindale
- Guy Eric Schalnat
- Paul Schmidt
- Tim Wegner
-
-The PNG Reference Library is supplied "AS IS". The Contributing Authors
-and Group 42, Inc. disclaim all warranties, expressed or implied,
-including, without limitation, the warranties of merchantability and of
-fitness for any purpose. The Contributing Authors and Group 42, Inc.
-assume no liability for direct, indirect, incidental, special, exemplary,
-or consequential damages, which may result from the use of the PNG
-Reference Library, even if advised of the possibility of such damage.
-
-Permission is hereby granted to use, copy, modify, and distribute this
-source code, or portions hereof, for any purpose, without fee, subject
-to the following restrictions:
-
-1. The origin of this source code must not be misrepresented.
-
-2. Altered versions must be plainly marked as such and must not
- be misrepresented as being the original source.
-
-3. This Copyright notice may not be removed or altered from any
- source or altered source distribution.
-
-The Contributing Authors and Group 42, Inc. specifically permit, without
-fee, and encourage the use of this source code as a component to
-supporting the PNG file format in commercial products. If you use this
-source code in a product, acknowledgment is not required but would be
-appreciated.
-
-
-A "png_get_copyright" function is available, for convenient use in "about"
-boxes and the like:
-
- printf("%s",png_get_copyright(NULL));
-
-Also, the PNG logo (in PNG format, of course) is supplied in the
-files "pngbar.png" and "pngbar.jpg (88x31) and "pngnow.png" (98x31).
-
-Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a
-certification mark of the Open Source Initiative.
-
-Glenn Randers-Pehrson
-glennrp at users.sourceforge.net
-December 9, 2010
-
-
-
-
-MIT
-
-
-MIT License
-
-Copyright (c) <year> <copyright holders>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-
-
-MPL-1.0
-
-
-MOZILLA PUBLIC LICENSE
-Version 1.0
-
-1. Definitions.
-
-1.1. ``Contributor`` means each entity that creates or contributes to the creation of
-Modifications.
-1.2. ``Contributor Version`` means the combination of the Original Code, prior
-Modifications used by a Contributor, and the Modifications made by that particular
-Contributor.
-
-1.3. ``Covered Code`` means the Original Code or Modifications or the combination of
-the Original Code and Modifications, in each case including portions thereof.
-
-1.4. ``Electronic Distribution Mechanism`` means a mechanism generally accepted in the
-software development community for the electronic transfer of data.
-
-1.5. ``Executable`` means Covered Code in any form other than Source Code.
-
-1.6. ``Initial Developer`` means the individual or entity identified as the Initial
-Developer in the Source Code notice required by Exhibit A.
-
-1.7. ``Larger Work`` means a work which combines Covered Code or portions thereof with
-code not governed by the terms of this License.
-
-1.8. ``License`` means this document.
-
-1.9. ``Modifications`` means any addition to or deletion from the substance or
-structure of either the Original Code or any previous Modifications. When Covered Code
-is released as a series of files, a Modification is:
-
-A. Any addition to or deletion from the contents of a file containing Original Code or
-previous Modifications.
-
-B. Any new file that contains any part of the Original Code or previous Modifications.
-
-1.10. ``Original Code`` means Source Code of computer software code which is described
-in the Source Code notice required by Exhibit A as Original Code, and which, at the
-time of its release under this License is not already Covered Code governed by this
-License.
-
-1.11. ``Source Code`` means the preferred form of the Covered Code for making
-modifications to it, including all modules it contains, plus any associated interface
-definition files, scripts used to control compilation and installation of an
-Executable, or a list of source code differential comparisons against either the
-Original Code or another well known, available Covered Code of the Contributor`s
-choice. The Source Code can be in a compressed or archival form, provided the
-appropriate decompression or de-archiving software is widely available for no charge.
-
-1.12. ``You`` means an individual or a legal entity exercising rights under, and
-complying with all of the terms of, this License or a future version of this License
-issued under Section 6.1. For legal entities, ``You`` includes any entity which
-controls, is controlled by, or is under common control with You. For purposes of this
-definition, ``control`` means (a) the power, direct or indirect, to cause the
-direction or management of such entity, whether by contract or otherwise, or (b)
-ownership of fifty percent (50%) or more of the outstanding shares or beneficial
-ownership of such entity.
-
-2. Source Code License.
-2.1. The Initial Developer Grant.
-The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive
-license, subject to third party intellectual property claims:
-(a) to use, reproduce, modify, display, perform, sublicense and distribute the
-Original Code (or portions thereof) with or without Modifications, or as part of a
-Larger Work; and
-
-(b) under patents now or hereafter owned or controlled by Initial Developer, to make,
-have made, use and sell (``Utilize``) the Original Code (or portions thereof), but
-solely to the extent that any such patent is reasonably necessary to enable You to
-Utilize the Original Code (or portions thereof) and not to any greater extent that may
-be necessary to Utilize further Modifications or combinations.
-
-2.2. Contributor Grant.
-Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license,
-subject to third party intellectual property claims:
-
-(a) to use, reproduce, modify, display, perform, sublicense and distribute the
-Modifications created by such Contributor (or portions thereof) either on an
-unmodified basis, with other Modifications, as Covered Code or as part of a Larger
-Work; and
-
-(b) under patents now or hereafter owned or controlled by Contributor, to Utilize the
-Contributor Version (or portions thereof), but solely to the extent that any such
-patent is reasonably necessary to enable You to Utilize the Contributor Version (or
-portions thereof), and not to any greater extent that may be necessary to Utilize
-further Modifications or combinations.
-
-3. Distribution Obligations.
-3.1. Application of License.
-The Modifications which You create or to which You contribute are governed by the
-terms of this License, including without limitation Section 2.2. The Source Code
-version of Covered Code may be distributed only under the terms of this License or a
-future version of this License released under Section 6.1, and You must include a copy
-of this License with every copy of the Source Code You distribute. You may not offer
-or impose any terms on any Source Code version that alters or restricts the applicable
-version of this License or the recipients` rights hereunder. However, You may include
-an additional document offering the additional rights described in Section 3.5.
-3.2. Availability of Source Code.
-Any Modification which You create or to which You contribute must be made available in
-Source Code form under the terms of this License either on the same media as an
-Executable version or via an accepted Electronic Distribution Mechanism to anyone to
-whom you made an Executable version available; and if made available via Electronic
-Distribution Mechanism, must remain available for at least twelve (12) months after
-the date it initially became available, or at least six (6) months after a subsequent
-version of that particular Modification has been made available to such recipients.
-You are responsible for ensuring that the Source Code version remains available even
-if the Electronic Distribution Mechanism is maintained by a third party.
-
-3.3. Description of Modifications.
-You must cause all Covered Code to which you contribute to contain a file documenting
-the changes You made to create that Covered Code and the date of any change. You must
-include a prominent statement that the Modification is derived, directly or
-indirectly, from Original Code provided by the Initial Developer and including the
-name of the Initial Developer in (a) the Source Code, and (b) in any notice in an
-Executable version or related documentation in which You describe the origin or
-ownership of the Covered Code.
-
-3.4. Intellectual Property Matters
-
-(a) Third Party Claims.
-If You have knowledge that a party claims an intellectual property right in particular
-functionality or code (or its utilization under this License), you must include a text
-file with the source code distribution titled ``LEGAL`` which describes the claim and
-the party making the claim in sufficient detail that a recipient will know whom to
-contact. If you obtain such knowledge after You make Your Modification available as
-described in Section 3.2, You shall promptly modify the LEGAL file in all copies You
-make available thereafter and shall take other steps (such as notifying appropriate
-mailing lists or newsgroups) reasonably calculated to inform those who received the
-Covered Code that new knowledge has been obtained.
-
-(b) Contributor APIs.
-If Your Modification is an application programming interface and You own or control
-patents which are reasonably necessary to implement that API, you must also include
-this information in the LEGAL file.
-
-3.5. Required Notices.
-You must duplicate the notice in Exhibit A in each file of the Source Code, and this
-License in any documentation for the Source Code, where You describe recipients`
-rights relating to Covered Code. If You created one or more Modification(s), You may
-add your name as a Contributor to the notice described in Exhibit A. If it is not
-possible to put such notice in a particular Source Code file due to its structure,
-then you must include such notice in a location (such as a relevant directory file)
-where a user would be likely to look for such a notice. You may choose to offer, and
-to charge a fee for, warranty, support, indemnity or liability obligations to one or
-more recipients of Covered Code. However, You may do so only on Your own behalf, and
-not on behalf of the Initial Developer or any Contributor. You must make it absolutely
-clear than any such warranty, support, indemnity or liability obligation is offered by
-You alone, and You hereby agree to indemnify the Initial Developer and every
-Contributor for any liability incurred by the Initial Developer or such Contributor as
-a result of warranty, support, indemnity or liability terms You offer.
-
-3.6. Distribution of Executable Versions.
-You may distribute Covered Code in Executable form only if the requirements of Section
-3.1-3.5 have been met for that Covered Code, and if You include a notice stating that
-the Source Code version of the Covered Code is available under the terms of this
-License, including a description of how and where You have fulfilled the obligations
-of Section 3.2. The notice must be conspicuously included in any notice in an
-Executable version, related documentation or collateral in which You describe
-recipients` rights relating to the Covered Code. You may distribute the Executable
-version of Covered Code under a license of Your choice, which may contain terms
-different from this License, provided that You are in compliance with the terms of
-this License and that the license for the Executable version does not attempt to limit
-or alter the recipient`s rights in the Source Code version from the rights set forth
-in this License. If You distribute the Executable version under a different license
-You must make it absolutely clear that any terms which differ from this License are
-offered by You alone, not by the Initial Developer or any Contributor. You hereby
-agree to indemnify the Initial Developer and every Contributor for any liability
-incurred by the Initial Developer or such Contributor as a result of any such terms
-You offer.
-
-3.7. Larger Works.
-You may create a Larger Work by combining Covered Code with other code not governed by
-the terms of this License and distribute the Larger Work as a single product. In such
-a case, You must make sure the requirements of this License are fulfilled for the
-Covered Code.
-
-4. Inability to Comply Due to Statute or Regulation.
-If it is impossible for You to comply with any of the terms of this License with
-respect to some or all of the Covered Code due to statute or regulation then You must:
-(a) comply with the terms of this License to the maximum extent possible; and (b)
-describe the limitations and the code they affect. Such description must be included
-in the LEGAL file described in Section 3.4 and must be included with all distributions
-of the Source Code. Except to the extent prohibited by statute or regulation, such
-description must be sufficiently detailed for a recipient of ordinary skill to be able
-to understand it.
-
-5. Application of this License.
-This License applies to code to which the Initial Developer has attached the notice in
-Exhibit A, and to related Covered Code.
-6. Versions of the License.
-6.1. New Versions.
-Netscape Communications Corporation (``Netscape``) may publish revised and/or new
-versions of the License from time to time. Each version will be given a distinguishing
-version number.
-6.2. Effect of New Versions.
-Once Covered Code has been published under a particular version of the License, You
-may always continue to use it under the terms of that version. You may also choose to
-use such Covered Code under the terms of any subsequent version of the License
-published by Netscape. No one other than Netscape has the right to modify the terms
-applicable to Covered Code created under this License.
-
-6.3. Derivative Works.
-If you create or use a modified version of this License (which you may only do in
-order to apply it to code which is not already Covered Code governed by this License),
-you must (a) rename Your license so that the phrases ``Mozilla``, ``MOZILLAPL``,
-``MOZPL``, ``Netscape``, ``NPL`` or any confusingly similar phrase do not appear
-anywhere in your license and (b) otherwise make it clear that your version of the
-license contains terms which differ from the Mozilla Public License and Netscape
-Public License. (Filling in the name of the Initial Developer, Original Code or
-Contributor in the notice described in Exhibit A shall not of themselves be deemed to
-be modifications of this License.)
-
-7. DISCLAIMER OF WARRANTY.
-COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS`` BASIS, WITHOUT WARRANTY OF
-ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT
-THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
-NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
-IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE
-INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
-SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL
-PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER
-THIS DISCLAIMER.
-8. TERMINATION.
-This License and the rights granted hereunder will terminate automatically if You fail
-to comply with terms herein and fail to cure such breach within 30 days of becoming
-aware of the breach. All sublicenses to the Covered Code which are properly granted
-shall survive any termination of this License. Provisions which, by their nature, must
-remain in effect beyond the termination of this License shall survive.
-9. LIMITATION OF LIABILITY.
-UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
-CONTRACT, OR OTHERWISE, SHALL THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY
-DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU
-OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF
-ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK
-STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
-LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH
-DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
-PERSONAL INJURY RESULTING FROM SUCH PARTY`S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
-PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION
-OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT EXCLUSION AND LIMITATION MAY NOT APPLY
-TO YOU.
-10. U.S. GOVERNMENT END USERS.
-The Covered Code is a ``commercial item,`` as that term is defined in 48 C.F.R. 2.101
-(Oct. 1995), consisting of ``commercial computer software`` and ``commercial computer
-software documentation,`` as such terms are used in 48 C.F.R. 12.212 (Sept. 1995).
-Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June
-1995), all U.S. Government End Users acquire Covered Code with only those rights set
-forth herein.
-11. MISCELLANEOUS.
-This License represents the complete agreement concerning subject matter hereof. If
-any provision of this License is held to be unenforceable, such provision shall be
-reformed only to the extent necessary to make it enforceable. This License shall be
-governed by California law provisions (except to the extent applicable law, if any,
-provides otherwise), excluding its conflict-of-law provisions. With respect to
-disputes in which at least one party is a citizen of, or an entity chartered or
-registered to do business in, the United States of America: (a) unless otherwise
-agreed in writing, all disputes relating to this License (excepting any dispute
-relating to intellectual property rights) shall be subject to final and binding
-arbitration, with the losing party paying all costs of arbitration; (b) any
-arbitration relating to this Agreement shall be held in Santa Clara County,
-California, under the auspices of JAMS/EndDispute; and (c) any litigation relating to
-this Agreement shall be subject to the jurisdiction of the Federal Courts of the
-Northern District of California, with venue lying in Santa Clara County, California,
-with the losing party responsible for costs, including without limitation, court costs
-and reasonable attorneys fees and expenses. The application of the United Nations
-Convention on Contracts for the International Sale of Goods is expressly excluded. Any
-law or regulation which provides that the language of a contract shall be construed
-against the drafter shall not apply to this License.
-12. RESPONSIBILITY FOR CLAIMS.
-Except in cases where another Contributor has failed to comply with Section 3.4, You
-are responsible for damages arising, directly or indirectly, out of Your utilization
-of rights under this License, based on the number of copies of Covered Code you made
-available, the revenues you received from utilizing such rights, and other relevant
-factors. You agree to work with affected parties to distribute responsibility on an
-equitable basis.
-EXHIBIT A.
-``The contents of this file are subject to the Mozilla Public License Version 1.0 (the
-"License"); you may not use this file except in compliance with the License. You may
-obtain a copy of the License at http://www.mozilla.org/MPL/
-Software distributed under the License is distributed on an "AS IS" basis, WITHOUT
-WARRANTY OF ANY KIND, either express or implied. See the License for the specific
-language governing rights and limitations under the License.
-
-The Original Code is ______________________________________.
-
-The Initial Developer of the Original Code is ________________________. Portions
-created by ______________________ are Copyright (C) ______ _______________________.
-All Rights Reserved.
-
-Contributor(s): ______________________________________.``
-
-
-
-
-MPL-2.0
-
-Mozilla Public License Version 2.0
-==================================
-
-1. Definitions
---------------
-
-1.1. "Contributor"
- means each individual or legal entity that creates, contributes to
- the creation of, or owns Covered Software.
-
-1.2. "Contributor Version"
- means the combination of the Contributions of others (if any) used
- by a Contributor and that particular Contributor's Contribution.
-
-1.3. "Contribution"
- means Covered Software of a particular Contributor.
-
-1.4. "Covered Software"
- means Source Code Form to which the initial Contributor has attached
- the notice in Exhibit A, the Executable Form of such Source Code
- Form, and Modifications of such Source Code Form, in each case
- including portions thereof.
-
-1.5. "Incompatible With Secondary Licenses"
- means
-
- (a) that the initial Contributor has attached the notice described
- in Exhibit B to the Covered Software; or
-
- (b) that the Covered Software was made available under the terms of
- version 1.1 or earlier of the License, but not also under the
- terms of a Secondary License.
-
-1.6. "Executable Form"
- means any form of the work other than Source Code Form.
-
-1.7. "Larger Work"
- means a work that combines Covered Software with other material, in
- a separate file or files, that is not Covered Software.
-
-1.8. "License"
- means this document.
-
-1.9. "Licensable"
- means having the right to grant, to the maximum extent possible,
- whether at the time of the initial grant or subsequently, any and
- all of the rights conveyed by this License.
-
-1.10. "Modifications"
- means any of the following:
-
- (a) any file in Source Code Form that results from an addition to,
- deletion from, or modification of the contents of Covered
- Software; or
-
- (b) any new file in Source Code Form that contains any Covered
- Software.
-
-1.11. "Patent Claims" of a Contributor
- means any patent claim(s), including without limitation, method,
- process, and apparatus claims, in any patent Licensable by such
- Contributor that would be infringed, but for the grant of the
- License, by the making, using, selling, offering for sale, having
- made, import, or transfer of either its Contributions or its
- Contributor Version.
-
-1.12. "Secondary License"
- means either the GNU General Public License, Version 2.0, the GNU
- Lesser General Public License, Version 2.1, the GNU Affero General
- Public License, Version 3.0, or any later versions of those
- licenses.
-
-1.13. "Source Code Form"
- means the form of the work preferred for making modifications.
-
-1.14. "You" (or "Your")
- means an individual or a legal entity exercising rights under this
- License. For legal entities, "You" includes any entity that
- controls, is controlled by, or is under common control with You. For
- purposes of this definition, "control" means (a) the power, direct
- or indirect, to cause the direction or management of such entity,
- whether by contract or otherwise, or (b) ownership of more than
- fifty percent (50%) of the outstanding shares or beneficial
- ownership of such entity.
-
-2. License Grants and Conditions
---------------------------------
-
-2.1. Grants
-
-Each Contributor hereby grants You a world-wide, royalty-free,
-non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark)
- Licensable by such Contributor to use, reproduce, make available,
- modify, display, perform, distribute, and otherwise exploit its
- Contributions, either on an unmodified basis, with Modifications, or
- as part of a Larger Work; and
-
-(b) under Patent Claims of such Contributor to make, use, sell, offer
- for sale, have made, import, and otherwise transfer either its
- Contributions or its Contributor Version.
-
-2.2. Effective Date
-
-The licenses granted in Section 2.1 with respect to any Contribution
-become effective for each Contribution on the date the Contributor first
-distributes such Contribution.
-
-2.3. Limitations on Grant Scope
-
-The licenses granted in this Section 2 are the only rights granted under
-this License. No additional rights or licenses will be implied from the
-distribution or licensing of Covered Software under this License.
-Notwithstanding Section 2.1(b) above, no patent license is granted by a
-Contributor:
-
-(a) for any code that a Contributor has removed from Covered Software;
- or
-
-(b) for infringements caused by: (i) Your and any other third party's
- modifications of Covered Software, or (ii) the combination of its
- Contributions with other software (except as part of its Contributor
- Version); or
-
-(c) under Patent Claims infringed by Covered Software in the absence of
- its Contributions.
-
-This License does not grant any rights in the trademarks, service marks,
-or logos of any Contributor (except as may be necessary to comply with
-the notice requirements in Section 3.4).
-
-2.4. Subsequent Licenses
-
-No Contributor makes additional grants as a result of Your choice to
-distribute the Covered Software under a subsequent version of this
-License (see Section 10.2) or under the terms of a Secondary License (if
-permitted under the terms of Section 3.3).
-
-2.5. Representation
-
-Each Contributor represents that the Contributor believes its
-Contributions are its original creation(s) or it has sufficient rights
-to grant the rights to its Contributions conveyed by this License.
-
-2.6. Fair Use
-
-This License is not intended to limit any rights You have under
-applicable copyright doctrines of fair use, fair dealing, or other
-equivalents.
-
-2.7. Conditions
-
-Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
-in Section 2.1.
-
-3. Responsibilities
--------------------
-
-3.1. Distribution of Source Form
-
-All distribution of Covered Software in Source Code Form, including any
-Modifications that You create or to which You contribute, must be under
-the terms of this License. You must inform recipients that the Source
-Code Form of the Covered Software is governed by the terms of this
-License, and how they can obtain a copy of this License. You may not
-attempt to alter or restrict the recipients' rights in the Source Code
-Form.
-
-3.2. Distribution of Executable Form
-
-If You distribute Covered Software in Executable Form then:
-
-(a) such Covered Software must also be made available in Source Code
- Form, as described in Section 3.1, and You must inform recipients of
- the Executable Form how they can obtain a copy of such Source Code
- Form by reasonable means in a timely manner, at a charge no more
- than the cost of distribution to the recipient; and
-
-(b) You may distribute such Executable Form under the terms of this
- License, or sublicense it under different terms, provided that the
- license for the Executable Form does not attempt to limit or alter
- the recipients' rights in the Source Code Form under this License.
-
-3.3. Distribution of a Larger Work
-
-You may create and distribute a Larger Work under terms of Your choice,
-provided that You also comply with the requirements of this License for
-the Covered Software. If the Larger Work is a combination of Covered
-Software with a work governed by one or more Secondary Licenses, and the
-Covered Software is not Incompatible With Secondary Licenses, this
-License permits You to additionally distribute such Covered Software
-under the terms of such Secondary License(s), so that the recipient of
-the Larger Work may, at their option, further distribute the Covered
-Software under the terms of either this License or such Secondary
-License(s).
-
-3.4. Notices
-
-You may not remove or alter the substance of any license notices
-(including copyright notices, patent notices, disclaimers of warranty,
-or limitations of liability) contained within the Source Code Form of
-the Covered Software, except that You may alter any license notices to
-the extent required to remedy known factual inaccuracies.
-
-3.5. Application of Additional Terms
-
-You may choose to offer, and to charge a fee for, warranty, support,
-indemnity or liability obligations to one or more recipients of Covered
-Software. However, You may do so only on Your own behalf, and not on
-behalf of any Contributor. You must make it absolutely clear that any
-such warranty, support, indemnity, or liability obligation is offered by
-You alone, and You hereby agree to indemnify every Contributor for any
-liability incurred by such Contributor as a result of warranty, support,
-indemnity or liability terms You offer. You may include additional
-disclaimers of warranty and limitations of liability specific to any
-jurisdiction.
-
-4. Inability to Comply Due to Statute or Regulation
----------------------------------------------------
-
-If it is impossible for You to comply with any of the terms of this
-License with respect to some or all of the Covered Software due to
-statute, judicial order, or regulation then You must: (a) comply with
-the terms of this License to the maximum extent possible; and (b)
-describe the limitations and the code they affect. Such description must
-be placed in a text file included with all distributions of the Covered
-Software under this License. Except to the extent prohibited by statute
-or regulation, such description must be sufficiently detailed for a
-recipient of ordinary skill to be able to understand it.
-
-5. Termination
---------------
-
-5.1. The rights granted under this License will terminate automatically
-if You fail to comply with any of its terms. However, if You become
-compliant, then the rights granted under this License from a particular
-Contributor are reinstated (a) provisionally, unless and until such
-Contributor explicitly and finally terminates Your grants, and (b) on an
-ongoing basis, if such Contributor fails to notify You of the
-non-compliance by some reasonable means prior to 60 days after You have
-come back into compliance. Moreover, Your grants from a particular
-Contributor are reinstated on an ongoing basis if such Contributor
-notifies You of the non-compliance by some reasonable means, this is the
-first time You have received notice of non-compliance with this License
-from such Contributor, and You become compliant prior to 30 days after
-Your receipt of the notice.
-
-5.2. If You initiate litigation against any entity by asserting a patent
-infringement claim (excluding declaratory judgment actions,
-counter-claims, and cross-claims) alleging that a Contributor Version
-directly or indirectly infringes any patent, then the rights granted to
-You by any and all Contributors for the Covered Software under Section
-2.1 of this License shall terminate.
-
-5.3. In the event of termination under Sections 5.1 or 5.2 above, all
-end user license agreements (excluding distributors and resellers) which
-have been validly granted by You or Your distributors under this License
-prior to termination shall survive termination.
-
-************************************************************************
-* *
-* 6. Disclaimer of Warranty *
-* ------------------------- *
-* *
-* Covered Software is provided under this License on an "as is" *
-* basis, without warranty of any kind, either expressed, implied, or *
-* statutory, including, without limitation, warranties that the *
-* Covered Software is free of defects, merchantable, fit for a *
-* particular purpose or non-infringing. The entire risk as to the *
-* quality and performance of the Covered Software is with You. *
-* Should any Covered Software prove defective in any respect, You *
-* (not any Contributor) assume the cost of any necessary servicing, *
-* repair, or correction. This disclaimer of warranty constitutes an *
-* essential part of this License. No use of any Covered Software is *
-* authorized under this License except under this disclaimer. *
-* *
-************************************************************************
-
-************************************************************************
-* *
-* 7. Limitation of Liability *
-* -------------------------- *
-* *
-* Under no circumstances and under no legal theory, whether tort *
-* (including negligence), contract, or otherwise, shall any *
-* Contributor, or anyone who distributes Covered Software as *
-* permitted above, be liable to You for any direct, indirect, *
-* special, incidental, or consequential damages of any character *
-* including, without limitation, damages for lost profits, loss of *
-* goodwill, work stoppage, computer failure or malfunction, or any *
-* and all other commercial damages or losses, even if such party *
-* shall have been informed of the possibility of such damages. This *
-* limitation of liability shall not apply to liability for death or *
-* personal injury resulting from such party's negligence to the *
-* extent applicable law prohibits such limitation. Some *
-* jurisdictions do not allow the exclusion or limitation of *
-* incidental or consequential damages, so this exclusion and *
-* limitation may not apply to You. *
-* *
-************************************************************************
-
-8. Litigation
--------------
-
-Any litigation relating to this License may be brought only in the
-courts of a jurisdiction where the defendant maintains its principal
-place of business and such litigation shall be governed by laws of that
-jurisdiction, without reference to its conflict-of-law provisions.
-Nothing in this Section shall prevent a party's ability to bring
-cross-claims or counter-claims.
-
-9. Miscellaneous
-----------------
-
-This License represents the complete agreement concerning the subject
-matter hereof. If any provision of this License is held to be
-unenforceable, such provision shall be reformed only to the extent
-necessary to make it enforceable. Any law or regulation which provides
-that the language of a contract shall be construed against the drafter
-shall not be used to construe this License against a Contributor.
-
-10. Versions of the License
----------------------------
-
-10.1. New Versions
-
-Mozilla Foundation is the license steward. Except as provided in Section
-10.3, no one other than the license steward has the right to modify or
-publish new versions of this License. Each version will be given a
-distinguishing version number.
-
-10.2. Effect of New Versions
-
-You may distribute the Covered Software under the terms of the version
-of the License under which You originally received the Covered Software,
-or under the terms of any subsequent version published by the license
-steward.
-
-10.3. Modified Versions
-
-If you create software not governed by this License, and you want to
-create a new license for such software, you may create and use a
-modified version of this License if you rename the license and remove
-any references to the name of the license steward (except to note that
-such modified license differs from this License).
-
-10.4. Distributing Source Code Form that is Incompatible With Secondary
-Licenses
-
-If You choose to distribute Source Code Form that is Incompatible With
-Secondary Licenses under the terms of this version of the License, the
-notice described in Exhibit B of this License must be attached.
-
-Exhibit A - Source Code Form License Notice
--------------------------------------------
-
- This Source Code Form is subject to the terms of the Mozilla Public
- License, v. 2.0. If a copy of the MPL was not distributed with this
- file, You can obtain one at http://mozilla.org/MPL/2.0/.
-
-If it is not possible or desirable to put the notice in a particular
-file, then You may include the notice in a location (such as a LICENSE
-file in a relevant directory) where a recipient would be likely to look
-for such a notice.
-
-You may add additional accurate notices of copyright ownership.
-
-Exhibit B - "Incompatible With Secondary Licenses" Notice
----------------------------------------------------------
-
- This Source Code Form is "Incompatible With Secondary Licenses", as
- defined by the Mozilla Public License, v. 2.0.
-
-
-
-OFL-1.1
-
-
-SIL OPEN FONT LICENSE
-
-Version 1.1 - 26 February 2007
-
-PREAMBLE
-The goals of the Open Font License (OFL) are to stimulate worldwide
-development of collaborative font projects, to support the font creation
-efforts of academic and linguistic communities, and to provide a free and
-open framework in which fonts may be shared and improved in partnership
-with others.
-
-The OFL allows the licensed fonts to be used, studied, modified and
-redistributed freely as long as they are not sold by themselves. The
-fonts, including any derivative works, can be bundled, embedded,
-redistributed and/or sold with any software provided that any reserved
-names are not used by derivative works. The fonts and derivatives,
-however, cannot be released under any other type of license. The
-requirement for fonts to remain under this license does not apply
-to any document created using the fonts or their derivatives.
-
-DEFINITIONS
-"Font Software" refers to the set of files released by the Copyright
-Holder(s) under this license and clearly marked as such. This may
-include source files, build scripts and documentation.
-
-"Reserved Font Name" refers to any names specified as such after the
-copyright statement(s).
-
-"Original Version" refers to the collection of Font Software components as
-distributed by the Copyright Holder(s).
-
-"Modified Version" refers to any derivative made by adding to, deleting,
-or substituting -- in part or in whole -- any of the components of the
-Original Version, by changing formats or by porting the Font Software to a
-new environment.
-
-"Author" refers to any designer, engineer, programmer, technical
-writer or other person who contributed to the Font Software.
-
-PERMISSION & CONDITIONS
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of the Font Software, to use, study, copy, merge, embed, modify,
-redistribute, and sell modified and unmodified copies of the Font
-Software, subject to the following conditions:
-
-1) Neither the Font Software nor any of its individual components,
-in Original or Modified Versions, may be sold by itself.
-
-2) Original or Modified Versions of the Font Software may be bundled,
-redistributed and/or sold with any software, provided that each copy
-contains the above copyright notice and this license. These can be
-included either as stand-alone text files, human-readable headers or
-in the appropriate machine-readable metadata fields within text or
-binary files as long as those fields can be easily viewed by the user.
-
-3) No Modified Version of the Font Software may use the Reserved Font
-Name(s) unless explicit written permission is granted by the corresponding
-Copyright Holder. This restriction only applies to the primary font name as
-presented to the users.
-
-4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
-Software shall not be used to promote, endorse or advertise any
-Modified Version, except to acknowledge the contribution(s) of the
-Copyright Holder(s) and the Author(s) or with their explicit written
-permission.
-
-5) The Font Software, modified or unmodified, in part or in whole,
-must be distributed entirely under this license, and must not be
-distributed under any other license. The requirement for fonts to
-remain under this license does not apply to any document created
-using the Font Software.
-
-TERMINATION
-This license becomes null and void if any of the above conditions are
-not met.
-
-DISCLAIMER
-THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
-OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
-COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
-DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
-OTHER DEALINGS IN THE FONT SOFTWARE.
-
-
-
-
-OpenSSL
-
-
-OpenSSL License
-
- ====================================================================
- Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the
- distribution.
-
- 3. All advertising materials mentioning features or use of this
- software must display the following acknowledgment:
- "This product includes software developed by the OpenSSL Project
- for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
-
- 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
- endorse or promote products derived from this software without
- prior written permission. For written permission, please contact
- openssl-core@openssl.org.
-
- 5. Products derived from this software may not be called "OpenSSL"
- nor may "OpenSSL" appear in their names without prior written
- permission of the OpenSSL Project.
-
- 6. Redistributions of any form whatsoever must retain the following
- acknowledgment:
- "This product includes software developed by the OpenSSL Project
- for use in the OpenSSL Toolkit (http://www.openssl.org/)"
-
- THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS`` AND ANY
- EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
- PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
- ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
- NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
- LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
- STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
- OF THE POSSIBILITY OF SUCH DAMAGE.
- ====================================================================
-
- This product includes cryptographic software written by Eric Young
- (eay@cryptsoft.com). This product includes software written by Tim
- Hudson (tjh@cryptsoft.com).
-
-
- Original SSLeay License
- -----------------------
-
-Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
-All rights reserved.
-
- This package is an SSL implementation written
- by Eric Young (eay@cryptsoft.com).
- The implementation was written so as to conform with Netscapes SSL.
-
- This library is free for commercial and non-commercial use as long as
- the following conditions are aheared to. The following conditions
- apply to all code found in this distribution, be it the RC4, RSA,
- lhash, DES, etc., code; not just the SSL code. The SSL documentation
- included with this distribution is covered by the same copyright terms
- except that the holder is Tim Hudson (tjh@cryptsoft.com).
-
- Copyright remains Eric Young`s, and as such any Copyright notices in
- the code are not to be removed.
- If this package is used in a product, Eric Young should be given attribution
- as the author of the parts of the library used.
- This can be in the form of a textual message at program startup or
- in documentation (online or textual) provided with the package.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
- 1. Redistributions of source code must retain the copyright
- notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
- 3. All advertising materials mentioning features or use of this software
- must display the following acknowledgement:
- "This product includes cryptographic software written by
- Eric Young (eay@cryptsoft.com)"
- The word `cryptographic` can be left out if the rouines from the library
- being used are not cryptographic related :-).
- 4. If you include any Windows specific code (or a derivative thereof) from
- the apps directory (application code) you must include an acknowledgement:
- "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
-
- THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS`` AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
-CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- The licence and distribution terms for any publically available version or
-derivative of this code cannot be changed. i.e. this code cannot simply be copied and
-put under another distribution licence
- [including the GNU Public Licence.]
-
-
-
-
-
-
-
-PD
-
-This is a placeholder for the Public Domain License
-
-
-
-Python-2.0
-
-
-PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
---------------------------------------------
-
-1. This LICENSE AGREEMENT is between the Python Software Foundation
-("PSF"), and the Individual or Organization ("Licensee") accessing and
-otherwise using this software ("Python") in source or binary form and
-its associated documentation.
-
-2. Subject to the terms and conditions of this License Agreement, PSF
-hereby grants Licensee a nonexclusive, royalty-free, world-wide
-license to reproduce, analyze, test, perform and/or display publicly,
-prepare derivative works, distribute, and otherwise use Python
-alone or in any derivative version, provided, however, that PSF`s
-License Agreement and PSF`s notice of copyright, i.e., "Copyright (c)
-2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights
-Reserved" are retained in Python alone or in any derivative version
-prepared by Licensee.
-
-3. In the event Licensee prepares a derivative work that is based on
-or incorporates Python or any part thereof, and wants to make
-the derivative work available to others as provided herein, then
-Licensee hereby agrees to include in any such work a brief summary of
-the changes made to Python.
-
-4. PSF is making Python available to Licensee on an "AS IS"
-basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
-FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
-A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
-OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-6. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-7. Nothing in this License Agreement shall be deemed to create any
-relationship of agency, partnership, or joint venture between PSF and
-Licensee. This License Agreement does not grant permission to use PSF
-trademarks or trade name in a trademark sense to endorse or promote
-products or services of Licensee, or any third party.
-
-8. By copying, installing or otherwise using Python, Licensee
-agrees to be bound by the terms and conditions of this License
-Agreement.
-
-BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
--------------------------------------------
-
-BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
-
-1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
-office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
-Individual or Organization ("Licensee") accessing and otherwise using
-this software in source or binary form and its associated
-documentation ("the Software").
-
-2. Subject to the terms and conditions of this BeOpen Python License
-Agreement, BeOpen hereby grants Licensee a non-exclusive,
-royalty-free, world-wide license to reproduce, analyze, test, perform
-and/or display publicly, prepare derivative works, distribute, and
-otherwise use the Software alone or in any derivative version,
-provided, however, that the BeOpen Python License is retained in the
-Software, alone or in any derivative version prepared by Licensee.
-
-3. BeOpen is making the Software available to Licensee on an "AS IS"
-basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
-SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
-AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
-DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-5. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-6. This License Agreement shall be governed by and interpreted in all
-respects by the law of the State of California, excluding conflict of
-law provisions. Nothing in this License Agreement shall be deemed to
-create any relationship of agency, partnership, or joint venture
-between BeOpen and Licensee. This License Agreement does not grant
-permission to use BeOpen trademarks or trade names in a trademark
-sense to endorse or promote products or services of Licensee, or any
-third party. As an exception, the "BeOpen Python" logos available at
-http://www.pythonlabs.com/logos.html may be used according to the
-permissions granted on that web page.
-
-7. By copying, installing or otherwise using the software, Licensee
-agrees to be bound by the terms and conditions of this License
-Agreement.
-
-CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
----------------------------------------
-
-1. This LICENSE AGREEMENT is between the Corporation for National
-Research Initiatives, having an office at 1895 Preston White Drive,
-Reston, VA 20191 ("CNRI"), and the Individual or Organization
-("Licensee") accessing and otherwise using Python 1.6.1 software in
-source or binary form and its associated documentation.
-
-2. Subject to the terms and conditions of this License Agreement, CNRI
-hereby grants Licensee a nonexclusive, royalty-free, world-wide
-license to reproduce, analyze, test, perform and/or display publicly,
-prepare derivative works, distribute, and otherwise use Python 1.6.1
-alone or in any derivative version, provided, however, that CNRI`s
-License Agreement and CNRI`s notice of copyright, i.e., "Copyright (c)
-1995-2001 Corporation for National Research Initiatives; All Rights
-Reserved" are retained in Python 1.6.1 alone or in any derivative
-version prepared by Licensee. Alternately, in lieu of CNRI`s License
-Agreement, Licensee may substitute the following text (omitting the
-quotes): "Python 1.6.1 is made available subject to the terms and
-conditions in CNRI`s License Agreement. This Agreement together with
-Python 1.6.1 may be located on the Internet using the following
-unique, persistent identifier (known as a handle): 1895.22/1013. This
-Agreement may also be obtained from a proxy server on the Internet
-using the following URL: http://hdl.handle.net/1895.22/1013".
-
-3. In the event Licensee prepares a derivative work that is based on
-or incorporates Python 1.6.1 or any part thereof, and wants to make
-the derivative work available to others as provided herein, then
-Licensee hereby agrees to include in any such work a brief summary of
-the changes made to Python 1.6.1.
-
-4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
-basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
-IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
-DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
-FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
-INFRINGE ANY THIRD PARTY RIGHTS.
-
-5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
-1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
-A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
-OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
-
-6. This License Agreement will automatically terminate upon a material
-breach of its terms and conditions.
-
-7. This License Agreement shall be governed by the federal
-intellectual property law of the United States, including without
-limitation the federal copyright law, and, to the extent such
-U.S. federal law does not apply, by the law of the Commonwealth of
-Virginia, excluding Virginia`s conflict of law provisions.
-Notwithstanding the foregoing, with regard to derivative works based
-on Python 1.6.1 that incorporate non-separable material that was
-previously distributed under the GNU General Public License (GPL), the
-law of the Commonwealth of Virginia shall govern this License
-Agreement only as to issues arising under or with respect to
-Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
-License Agreement shall be deemed to create any relationship of
-agency, partnership, or joint venture between CNRI and Licensee. This
-License Agreement does not grant permission to use CNRI trademarks or
-trade name in a trademark sense to endorse or promote products or
-services of Licensee, or any third party.
-
-8. By clicking on the "ACCEPT" button where indicated, or by copying,
-installing or otherwise using Python 1.6.1, Licensee agrees to be
-bound by the terms and conditions of this License Agreement.
-
-ACCEPT
-
-CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
---------------------------------------------------
-
-Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
-The Netherlands. All rights reserved.
-
-Permission to use, copy, modify, and distribute this software and its
-documentation for any purpose and without fee is hereby granted,
-provided that the above copyright notice appear in all copies and that
-both that copyright notice and this permission notice appear in
-supporting documentation, and that the name of Stichting Mathematisch
-Centrum or CWI not be used in advertising or publicity pertaining to
-distribution of the software without specific, written prior
-permission.
-
-STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
-THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
-FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
-FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
-WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
-ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
-OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
-
-
-
-SAX-PD
-
-
-Copyright Status for SAX
-
-SAX is free!
-
-In fact, it`s not possible to own a license to SAX, since it`s been placed in the
-public domain.
-
-No Warranty
-
-Because SAX is released to the public domain, there is no warranty for the design or
-for the software implementation, to the extent permitted by applicable law. Except
-when otherwise stated in writing the copyright holders and/or other parties provide
-SAX "as is" without warranty of any kind, either expressed or implied, including, but
-not limited to, the implied warranties of merchantability and fitness for a particular
-purpose. The entire risk as to the quality and performance of SAX is with you. Should
-SAX prove defective, you assume the cost of all necessary servicing, repair or
-correction.
-
-In no event unless required by applicable law or agreed to in writing will any
-copyright holder, or any other party who may modify and/or redistribute SAX, be liable
-to you for damages, including any general, special, incidental or consequential
-damages arising out of the use or inability to use SAX (including but not limited to
-loss of data or data being rendered inaccurate or losses sustained by you or third
-parties or a failure of the SAX to operate with any other programs), even if such
-holder or other party has been advised of the possibility of such damages.
-
-Copyright Disclaimers
-
-This page includes statements to that effect by David Megginson, who would have been
-able to claim copyright for the original work.
-
-SAX 1.0
-
-Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of
-the XML-DEV mailing list, is hereby released into the public domain.
-
-No one owns SAX: you may use it freely in both commercial and non-commercial
-applications, bundle it with your software distribution, include it on a CD-ROM, list
-the source code in a book, mirror the documentation at your own web site, or use it in
-any other way you see fit.
-
-David Megginson, Megginson Technologies Ltd.
-1998-05-11
-
-SAX 2.0
-
-I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release
-all of the SAX 2.0 source code, compiled code, and documentation contained in this
-distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of
-fitness for any purpose.
-
-David Megginson, Megginson Technologies Ltd.
-2000-05-05
-
-
-
-
-SMAIL_GPL
-
-This is the Debian GNU/Linux package debianutils.
-
-It is an original Debian package. Programs in it were maintained by
-Guy Maor <maor@debian.org>, and are now maintained by Clint Adams
-<schizo@debian.org>.
-
-All its programs except readlink, savelog, and which may be
-redistributed under the terms of the GNU GPL, Version 2 or later,
-found on Debian systems in the file /usr/share/common-licenses/GPL.
-
-which is in the public domain.
-
-readlink is Copyright (c) 1997 Kenneth Stailey, and may also be
-distributed under the terms of the BSD copyright.
-
-savelog may be redistributed under the following terms: (The rest of
-this file consists of savelog's distribution terms.)
-
-#ident "@(#)smail:RELEASE-3_2:COPYING,v 1.2 1996/06/14 18:59:10 woods Exp"
-
- SMAIL GENERAL PUBLIC LICENSE
- (Clarified 11 Feb 1988)
-
- Copyright (C) 1988 Landon Curt Noll & Ronald S. Karr
- Copyright (C) 1992 Ronald S. Karr
- Copyleft (GNU) 1988 Landon Curt Noll & Ronald S. Karr
-
- Everyone is permitted to copy and distribute verbatim copies
- of this license, but changing it is not allowed. You can also
- use this wording to make the terms for other programs.
-
- The license agreements of most software companies keep you at the
-mercy of those companies. By contrast, our general public license is
-intended to give everyone the right to share SMAIL. To make sure that
-you get the rights we want you to have, we need to make restrictions
-that forbid anyone to deny you these rights or to ask you to surrender
-the rights. Hence this license agreement.
-
- Specifically, we want to make sure that you have the right to give
-away copies of SMAIL, that you receive source code or else can get it
-if you want it, that you can change SMAIL or use pieces of it in new
-free programs, and that you know you can do these things.
-
- To make sure that everyone has such rights, we have to forbid you to
-deprive anyone else of these rights. For example, if you distribute
-copies of SMAIL, you must give the recipients all the rights that you
-have. You must make sure that they, too, receive or can get the
-source code. And you must tell them their rights.
-
- Also, for our own protection, we must make certain that everyone
-finds out that there is no warranty for SMAIL. If SMAIL is modified by
-someone else and passed on, we want its recipients to know that what
-they have is not what we distributed, so that any problems introduced
-by others will not reflect on our reputation.
-
- Therefore we (Landon Curt Noll and Ronald S. Karr) make the following
-terms which say what you must do to be allowed to distribute or change
-SMAIL.
-
-
- COPYING POLICIES
-
- 1. You may copy and distribute verbatim copies of SMAIL source code
-as you receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy a valid copyright notice "Copyright
-(C) 1988 Landon Curt Noll & Ronald S. Karr" (or with whatever year is
-appropriate); keep intact the notices on all files that refer to this
-License Agreement and to the absence of any warranty; and give any
-other recipients of the SMAIL program a copy of this License
-Agreement along with the program. You may charge a distribution fee
-for the physical act of transferring a copy.
-
- 2. You may modify your copy or copies of SMAIL or any portion of it,
-and copy and distribute such modifications under the terms of
-Paragraph 1 above, provided that you also do the following:
-
- a) cause the modified files to carry prominent notices stating
- that you changed the files and the date of any change; and
-
- b) cause the whole of any work that you distribute or publish,
- that in whole or in part contains or is a derivative of SMAIL or
- any part thereof, to be licensed at no charge to all third
- parties on terms identical to those contained in this License
- Agreement (except that you may choose to grant more extensive
- warranty protection to some or all third parties, at your option).
-
- c) You may charge a distribution fee for the physical act of
- transferring a copy, and you may at your option offer warranty
- protection in exchange for a fee.
-
-Mere aggregation of another unrelated program with this program (or its
-derivative) on a volume of a storage or distribution medium does not bring
-the other program under the scope of these terms.
-
- 3. You may copy and distribute SMAIL (or a portion or derivative of it,
-under Paragraph 2) in object code or executable form under the terms of
-Paragraphs 1 and 2 above provided that you also do one of the following:
-
- a) accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- b) accompany it with a written offer, valid for at least three
- years, to give any third party free (except for a nominal
- shipping charge) a complete machine-readable copy of the
- corresponding source code, to be distributed under the terms of
- Paragraphs 1 and 2 above; or,
-
- c) accompany it with the information you received as to where the
- corresponding source code may be obtained. (This alternative is
- allowed only for non-commercial distribution and only if you
- received the program in object code or executable form alone.)
-
-For an executable file, complete source code means all the source code for
-all modules it contains; but, as a special exception, it need not include
-source code for modules which are standard libraries that accompany the
-operating system on which the executable file runs.
-
- 4. You may not copy, sublicense, distribute or transfer SMAIL
-except as expressly provided under this License Agreement. Any attempt
-otherwise to copy, sublicense, distribute or transfer SMAIL is void and
-your rights to use the program under this License agreement shall be
-automatically terminated. However, parties who have received computer
-software programs from you with this License Agreement will not have
-their licenses terminated so long as such parties remain in full compliance.
-
- 5. If you wish to incorporate parts of SMAIL into other free
-programs whose distribution conditions are different, write to Landon
-Curt Noll & Ronald S. Karr via the Free Software Foundation at 51
-Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. We have not yet
-worked out a simple rule that can be stated here, but we will often
-permit this. We will be guided by the two goals of preserving the
-free status of all derivatives of our free software and of promoting
-the sharing and reuse of software.
-
-Your comments and suggestions about our licensing policies and our
-software are welcome! This contract was based on the contract made by
-the Free Software Foundation. Please contact the Free Software
-Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301,
-USA, or call (617) 542-5942 for details on copylefted material in
-general.
-
- NO WARRANTY
-
- BECAUSE SMAIL IS LICENSED FREE OF CHARGE, WE PROVIDE ABSOLUTELY NO
-WARRANTY, TO THE EXTENT PERMITTED BY APPLICABLE STATE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING, LANDON CURT NOLL & RONALD S. KARR AND/OR
-OTHER PARTIES PROVIDE SMAIL "AS IS" WITHOUT WARRANTY OF ANY KIND,
-EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
-THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF SMAIL IS WITH
-YOU. SHOULD SMAIL PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
-NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW WILL LANDON CURT NOLL &
-RONALD S. KARR AND/OR ANY OTHER PARTY WHO MAY MODIFY AND REDISTRIBUTE
-SMAIL AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-LOST PROFITS, LOST MONIES, OR OTHER SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
-(INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
-INACCURATE OR LOSSES SUSTAINED BY THIRD PARTIES OR A FAILURE OF THE
-PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS) SMAIL, EVEN IF YOU HAVE
-BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY
-ANY OTHER PARTY.
-
-
-
-SUN
-
-SUN MICROSYSTEMS, INC. THROUGH ITS SUN MICROSYSTEMS LABORATORIES
-DIVISION ("SUN") WILL LICENSE THIS SOFTWARE AND THE ACCOMPANYING
-DOCUMENTATION TO YOU (a "Licensee") ONLY ON YOUR ACCEPTANCE OF ALL
-THE TERMS SET FORTH BELOW.
-
-Sun grants Licensee a non-exclusive, royalty-free right to download,
-install, compile, use, copy and distribute the Software, modify or
-otherwise create derivative works from the Software (each, a
-"Modification") and distribute any Modification in source code and/or
-binary code form to its customers with a license agreement containing
-these terms and noting that the Software has been modified. The
-Software is copyrighted by Sun and other third parties and Licensee
-shall retain and reproduce all copyright and other notices presently
-on the Software. As between Sun and Licensee, Sun is the sole owner of
-all rights in and to the Software other than the limited rights
-granted to Licensee herein; Licensee will own its Modifications,
-expressly subject to Sun's continuing ownership of the
-Software. Licensee will, at its expense, defend and indemnify Sun and
-its licensors from and against any third party claims, including costs
-and reasonable attorneys' fees, and be wholly responsible for any
-liabilities arising out of or related to Licensee's development, use
-or distribution of the Software or Modifications. Any distribution of
-the Software and Modifications must comply with all applicable United
-States export control laws.
-
-THE SOFTWARE IS BEING PROVIDED TO LICENSEE "AS IS" AND ALL EXPRESS OR
-IMPLIED CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
-ARE DISCLAIMED. IN NO EVENT WILL SUN BE LIABLE HEREUNDER FOR ANY
-DIRECT DAMAGES OR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES OF ANY KIND.
-
-
-
-Sleepycat
-
-
-The Sleepycat License
-Copyright (c) 1990-1999
-Sleepycat Software. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Redistributions in any form must be accompanied by information on
-how to obtain complete source code for the DB software and any
-accompanying software that uses the DB software. The source code
-must either be included in the distribution or be available for no
-more than the cost of distribution plus a nominal fee, and must be
-freely redistributable under reasonable conditions. For an
-executable file, complete source code means the source code for all
-modules it contains. It does not include source code for modules or
-files that typically accompany the major components of the operating
-system on which the executable file runs.
-THIS SOFTWARE IS PROVIDED BY SLEEPYCAT SOFTWARE ``AS IS`` AND ANY EXPRESS
-OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
-NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL SLEEPYCAT SOFTWARE
-BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
-THE POSSIBILITY OF SUCH DAMAGE.
-
-Copyright (c) 1990, 1993, 1994, 1995
-The Regents of the University of California. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Neither the name of the University nor the names of its contributors
-may be used to endorse or promote products derived from this software
-without specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS`` AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-Copyright (c) 1995, 1996
-The President and Fellows of Harvard University. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-Neither the name of the University nor the names of its contributors
-may be used to endorse or promote products derived from this software
-without specific prior written permission.
-THIS SOFTWARE IS PROVIDED BY HARVARD AND ITS CONTRIBUTORS ``AS IS`` AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL HARVARD OR ITS CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGE.
-
-
-
-
-UCB
-
- Copyright (c) 1987, 1989, 1990, 1991, 1992, 1993, 1994
- The Regents of the University of California. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
- 3. Neither the name of the University nor the names of its contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
- ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
- ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
- FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
- DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
- OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
- OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
- SUCH DAMAGE.
-
-
-
-Unicode
-
-COPYRIGHT AND PERMISSION NOTICE
-
-Copyright 1991-2015 Unicode, Inc. All rights reserved.
-Distributed under the Terms of Use in
-http://www.unicode.org/copyright.html.
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of the Unicode data files and any associated documentation
-(the "Data Files") or Unicode software and any associated documentation
-(the "Software") to deal in the Data Files or Software
-without restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, and/or sell copies of
-the Data Files or Software, and to permit persons to whom the Data Files
-or Software are furnished to do so, provided that
-(a) this copyright and permission notice appear with all copies
-of the Data Files or Software,
-(b) this copyright and permission notice appear in associated
-documentation, and
-(c) there is clear notice in each modified Data File or in the Software
-as well as in the documentation associated with the Data File(s) or
-Software that the data or software has been modified.
-
-THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF
-ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT OF THIRD PARTY RIGHTS.
-IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
-NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
-DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
-DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
-TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
-PERFORMANCE OF THE DATA FILES OR SOFTWARE.
-
-Except as contained in this notice, the name of a copyright holder
-shall not be used in advertising or otherwise to promote the sale,
-use or other dealings in these Data Files or Software without prior
-written authorization of the copyright holder.
-
-
-
-W3C
-
-
-W3C SOFTWARE NOTICE AND LICENSE
-This work (and included software, documentation such as READMEs, or other related
-items) is being provided by the copyright holders under the following license.
-License
-By obtaining, using and/or copying this work, you (the licensee) agree that you have
-read, understood, and will comply with the following terms and conditions.
-Permission to copy, modify, and distribute this software and its documentation, with
-or without modification, for any purpose and without fee or royalty is hereby granted,
-provided that you include the following on ALL copies of the software and
-documentation or portions thereof, including modifications:
-The full text of this NOTICE in a location viewable to users of the redistributed or
-derivative work.
-Any pre-existing intellectual property disclaimers, notices, or terms and conditions.
-If none exist, the W3C Software Short Notice should be included (hypertext is
-preferred, text is permitted) within the body of any redistributed or derivative code.
-Notice of any changes or modifications to the files, including the date changes were
-made. (We recommend you provide URIs to the location from which the code is derived.)
-Disclaimers
-THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
-REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
-WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF
-THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
-TRADEMARKS OR OTHER RIGHTS.
-COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
-The name and trademarks of copyright holders may NOT be used in advertising or
-publicity pertaining to the software without specific, written prior permission. Title
-to copyright in this software and any associated documentation will at all times
-remain with copyright holders.
-Notes
-This version: http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
-This formulation of W3C`s notice and license became active on December 31 2002. This
-version removes the copyright ownership notice such that this license can be used with
-materials other than those owned by the W3C, reflects that ERCIM is now a host of the
-W3C, includes references to this specific dated version of the license, and removes
-the ambiguous grant of "use". Otherwise, this version is the same as the previous
-version and is written so as to preserve the Free Software Foundation`s assessment of
-GPL compatibility and OSI`s certification under the Open Source Definition.
-
-
-
-
-ZPL-2.1
-
-
-ZPL 2.1
-Zope Public License (ZPL) Version 2.1
-
-A copyright notice accompanies this license document that identifies the copyright
-holders.
-
-This license has been certified as open source. It has also been designated as GPL
-compatible by the Free Software Foundation (FSF).
-
-Redistribution and use in source and binary forms, with or without modification, are
-permitted provided that the following conditions are met:
-
-Redistributions in source code must retain the accompanying copyright notice, this
-list of conditions, and the following disclaimer.
-Redistributions in binary form must reproduce the accompanying copyright notice, this
-list of conditions, and the following disclaimer in the documentation and/or other
-materials provided with the distribution.
-Names of the copyright holders must not be used to endorse or promote products derived
-from this software without prior written permission from the copyright holders.
-The right to distribute this software or to use it for any purpose does not give you
-the right to use Servicemarks (sm) or Trademarks (tm) of the copyright holders. Use of
-them is covered by separate agreement with the copyright holders.
-If any files are modified, you must cause the modified files to carry prominent
-notices stating that you changed the files and the date of any change.
-Disclaimer
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS`` AND ANY EXPRESSED OR
-IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
-THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
-Zlib
-
-
-zlib License
-
-
- This software is provided `as-is`, without any express or implied
- warranty. In no event will the authors be held liable for any damages
- arising from the use of this software.
-
- Permission is granted to anyone to use this software for any purpose,
- including commercial applications, and to alter it and redistribute it
- freely, subject to the following restrictions:
-
- 1. The origin of this software must not be misrepresented; you must not
- claim that you wrote the original software. If you use this software
- in a product, an acknowledgment in the product documentation would be
- appreciated but is not required.
- 2. Altered source versions must be plainly marked as such, and must not be
- misrepresented as being the original software.
- 3. This notice may not be removed or altered from any source distribution.
-
-
-
-
-
-copyleft-next-0.3.0
-
- copyleft-next 0.3.0 ("this License")
- Release date: 2013-05-16
-
-1. License Grants; No Trademark License
-
- Subject to the terms of this License, I grant You:
-
- a) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
- copyright license, to reproduce, Distribute, prepare derivative works
- of, publicly perform and publicly display My Work.
-
- b) A non-exclusive, worldwide, perpetual, royalty-free, irrevocable
- patent license under Licensed Patents to make, have made, use, sell,
- offer for sale, and import Covered Works.
-
- This License does not grant any rights in My name, trademarks, service
- marks, or logos.
-
-2. Distribution: General Conditions
-
- You may Distribute Covered Works, provided that You (i) inform
- recipients how they can obtain a copy of this License; (ii) satisfy the
- applicable conditions of sections 3 through 6; and (iii) preserve all
- Legal Notices contained in My Work (to the extent they remain
- pertinent). "Legal Notices" means copyright notices, license notices,
- license texts, and author attributions, but does not include logos,
- other graphical images, trademarks or trademark legends.
-
-3. Conditions for Distributing Derived Works; Outbound GPL Compatibility
-
- If You Distribute a Derived Work, You must license the entire Derived
- Work as a whole under this License, with prominent notice of such
- licensing. This condition may not be avoided through such means as
- separate Distribution of portions of the Derived Work. You may
- additionally license the Derived Work under the GPL, so that the
- recipient may further Distribute the Derived Work under either this
- License or the GPL.
-
-4. Condition Against Further Restrictions; Inbound License Compatibility
-
- When Distributing a Covered Work, You may not impose further
- restrictions on the exercise of rights in the Covered Work granted under
- this License. This condition is not excused merely because such
- restrictions result from Your compliance with conditions or obligations
- extrinsic to this License (such as a court order or an agreement with a
- third party).
-
- However, You may Distribute a Covered Work incorporating material
- governed by a license that is both OSI-Approved and FSF-Free as of the
- release date of this License, provided that Your Distribution complies
- with such other license.
-
-5. Conditions for Distributing Object Code
-
- You may Distribute an Object Code form of a Covered Work, provided that
- you accompany the Object Code with a URL through which the Corresponding
- Source is made available, at no charge, by some standard or customary
- means of providing network access to source code.
-
- If you Distribute the Object Code in a physical product or tangible
- storage medium ("Product"), the Corresponding Source must be available
- through such URL for two years from the date of Your most recent
- Distribution of the Object Code in the Product. However, if the Product
- itself contains or is accompanied by the Corresponding Source (made
- available in a customarily accessible manner), You need not also comply
- with the first paragraph of this section.
-
- Each recipient of the Covered Work from You is an intended third-party
- beneficiary of this License solely as to this section 5, with the right
- to enforce its terms.
-
-6. Symmetrical Licensing Condition for Upstream Contributions
-
- If You Distribute a work to Me specifically for inclusion in or
- modification of a Covered Work (a "Patch"), and no explicit licensing
- terms apply to the Patch, You license the Patch under this License, to
- the extent of Your copyright in the Patch. This condition does not
- negate the other conditions of this License, if applicable to the Patch.
-
-7. Nullification of Copyleft/Proprietary Dual Licensing
-
- If I offer to license, for a fee, a Covered Work under terms other than
- a license that is OSI-Approved or FSF-Free as of the release date of this
- License or a numbered version of copyleft-next released by the
- Copyleft-Next Project, then the license I grant You under section 1 is no
- longer subject to the conditions in sections 2 through 5.
-
-8. Copyleft Sunset
-
- The conditions in sections 2 through 5 no longer apply once fifteen
- years have elapsed from the date of My first Distribution of My Work
- under this License.
-
-9. Pass-Through
-
- When You Distribute a Covered Work, the recipient automatically receives
- a license to My Work from Me, subject to the terms of this License.
-
-10. Termination
-
- Your license grants under section 1 are automatically terminated if You
-
- a) fail to comply with the conditions of this License, unless You cure
- such noncompliance within thirty days after becoming aware of it, or
-
- b) initiate a patent infringement litigation claim (excluding
- declaratory judgment actions, counterclaims, and cross-claims)
- alleging that any part of My Work directly or indirectly infringes
- any patent.
-
- Termination of Your license grants extends to all copies of Covered
- Works You subsequently obtain. Termination does not terminate the
- rights of those who have received copies or rights from You subject to
- this License.
-
- To the extent permission to make copies of a Covered Work is necessary
- merely for running it, such permission is not terminable.
-
-11. Later License Versions
-
- The Copyleft-Next Project may release new versions of copyleft-next,
- designated by a distinguishing version number ("Later Versions").
- Unless I explicitly remove the option of Distributing Covered Works
- under Later Versions, You may Distribute Covered Works under any Later
- Version.
-
-** 12. No Warranty **
-** **
-** My Work is provided "as-is", without warranty. You bear the risk **
-** of using it. To the extent permitted by applicable law, each **
-** Distributor of My Work excludes the implied warranties of title, **
-** merchantability, fitness for a particular purpose and **
-** non-infringement. **
-
-** 13. Limitation of Liability **
-** **
-** To the extent permitted by applicable law, in no event will any **
-** Distributor of My Work be liable to You for any damages **
-** whatsoever, whether direct, indirect, special, incidental, or **
-** consequential damages, whether arising under contract, tort **
-** (including negligence), or otherwise, even where the Distributor **
-** knew or should have known about the possibility of such damages. **
-
-14. Severability
-
- The invalidity or unenforceability of any provision of this License
- does not affect the validity or enforceability of the remainder of
- this License. Such provision is to be reformed to the minimum extent
- necessary to make it valid and enforceable.
-
-15. Definitions
-
- "Copyleft-Next Project" means the project that maintains the source
- code repository at <https://gitorious.org/copyleft-next/> as of the
- release date of this License.
-
- "Corresponding Source" of a Covered Work in Object Code form means (i)
- the Source Code form of the Covered Work; (ii) all scripts,
- instructions and similar information that are reasonably necessary for
- a skilled developer to generate such Object Code from the Source Code
- provided under (i); and (iii) a list clearly identifying all Separate
- Works (other than those provided in compliance with (ii)) that were
- specifically used in building and (if applicable) installing the
- Covered Work (for example, a specified proprietary compiler including
- its version number). Corresponding Source must be machine-readable.
-
- "Covered Work" means My Work or a Derived Work.
-
- "Derived Work" means a work of authorship that copies from, modifies,
- adapts, is based on, is a derivative work of, transforms, translates or
- contains all or part of My Work, such that copyright permission is
- required. The following are not Derived Works: (i) Mere Aggregation;
- (ii) a mere reproduction of My Work; and (iii) if My Work fails to
- explicitly state an expectation otherwise, a work that merely makes
- reference to My Work.
-
- "Distribute" means to distribute, transfer or make a copy available to
- someone else, such that copyright permission is required.
-
- "Distributor" means Me and anyone else who Distributes a Covered Work.
-
- "FSF-Free" means classified as 'free' by the Free Software Foundation.
-
- "GPL" means a version of the GNU General Public License or the GNU
- Affero General Public License.
-
- "I"/"Me"/"My" refers to the individual or legal entity that places My
- Work under this License. "You"/"Your" refers to the individual or legal
- entity exercising rights in My Work under this License. A legal entity
- includes each entity that controls, is controlled by, or is under
- common control with such legal entity. "Control" means (a) the power to
- direct the actions of such legal entity, whether by contract or
- otherwise, or (b) ownership of more than fifty percent of the
- outstanding shares or beneficial ownership of such legal entity.
-
- "Licensed Patents" means all patent claims licensable royalty-free by
- Me, now or in the future, that are necessarily infringed by making,
- using, or selling My Work, and excludes claims that would be infringed
- only as a consequence of further modification of My Work.
-
- "Mere Aggregation" means an aggregation of a Covered Work with a
- Separate Work.
-
- "My Work" means the particular work of authorship I license to You
- under this License.
-
- "Object Code" means any form of a work that is not Source Code.
-
- "OSI-Approved" means approved as 'Open Source' by the Open Source
- Initiative.
-
- "Separate Work" means a work that is separate from and independent of a
- particular Covered Work and is not by its nature an extension or
- enhancement of the Covered Work, and/or a runtime library, standard
- library or similar component that is used to generate an Object Code
- form of a Covered Work.
-
- "Source Code" means the preferred form of a work for making
- modifications to it.
-
-
-
-tcl
-
-This software is copyrighted by the Regents of the University of
-California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState
-Corporation and other parties. The following terms apply to all files
-associated with the software unless explicitly disclaimed in
-individual files.
-
-The authors hereby grant permission to use, copy, modify, distribute,
-and license this software and its documentation for any purpose, provided
-that existing copyright notices are retained in all copies and that this
-notice is included verbatim in any distributions. No written agreement,
-license, or royalty fee is required for any of the authorized uses.
-Modifications to this software may be copyrighted by their authors
-and need not follow the licensing terms described here, provided that
-the new terms are clearly indicated on the first page of each file where
-they apply.
-
-IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY
-FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY
-DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE
-IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE
-NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-
-GOVERNMENT USE: If you are acquiring this software on behalf of the
-U.S. government, the Government shall have only "Restricted Rights"
-in the software and related documentation as defined in the Federal
-Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you
-are acquiring the software on behalf of the Department of Defense, the
-software shall be classified as "Commercial Computer Software" and the
-Government shall have only "Restricted Rights" as defined in Clause
-252.227-7014 (b) (3) of DFARs. Notwithstanding the foregoing, the
-authors grant the U.S. Government and others acting in its behalf
-permission to use and distribute the software in accordance with the
-terms specified in this license.
-
-
-
-
- Proprietary Licenses
-
-Enea
-
- Copyright (C) 2006 by Enea.
- All rights reserved.
-
- This Software is furnished under a software license agreement and
- may be used only in accordance with the terms of such agreement.
- Any other use or reproduction is prohibited. No title to and
- ownership of the Software is hereby transferred.
-
- PROPRIETARY NOTICE
- This Software consists of confidential information.
- Trade secret law and copyright law protect this Software.
- The above notice of copyright on this Software does not indicate
- any actual or intended publication of such Software.
-
-
-
-
diff --git a/doc/book-enea-nfv-access-platform-open-source/swcomp.mk b/doc/book-enea-nfv-access-platform-open-source/swcomp.mk
deleted file mode 100644
index 20202e4..0000000
--- a/doc/book-enea-nfv-access-platform-open-source/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-platform-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Runtime Open Source Report"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
deleted file mode 100644
index 960f136..0000000
--- a/doc/book-enea-nfv-access-release-info/doc/about_release.xml
+++ /dev/null
@@ -1,184 +0,0 @@
-
-
-
- About This Release
-
- Enea Edge is a complete NFVI software platform designed for
- deployment on any white box uCPE device, and optimized for common use cases.
- Enea Edge includes both the Enea Edge Runtime deployed on a white box,
- and a management component with automation tools deployed in a private or
- public cloud.
-
- The Enea Edge Release includes a new version of
- the major components as well as other features and optimizations, and
- documentation updates. A list of new features and improvements can be found
- in Section 2.1 New Features and
- Improvements .
-
-
- Enea Edge Release Content
-
- The release content is detailed below:
-
-
-
- Enea_Edge_Runtime_C3000_<version>-build<build_number>.tar.gz
-
-
-
- Enea_Edge_Runtime_XeonD_<version>-build<build_number>.tar.gz
-
-
-
- Enea_Edge_Automation_<version>-build<build_number>.zip
-
-
-
- Enea_Edge_Management_<version>-build<build_number>.tar.gz
-
-
-
- Enea_Edge_Telemetry_Deploy_<version>-build<build_number>.tar.gz
-
-
-
- VNF_example_configurations.tar.gz
-
-
-
- Enea_Edge_AF-TH_<version>-build<build_number>.zip
- (deprecated, see Section 2.1 New Features and
- Improvements .)
-
-
-
- -- documentation/
- /* Enea Edge documentation */
--- README
--- aarch64 /* architecture */
- -- cn8304/
- /* artifacts for the host side */
- -- deb/
- /* deb packages */
- -- images/
- -- enea-nfv-access
- /* precompiled artifacts for the platform release image */
- -- various artifacts (rootfs, kernel, config etc.)
- -- enea-nfv-access-dev
- /* precompiled artifacts for the development process. The image
- contains userspace tools and kernel configurations necessary
- for developing, debugging and profiling applications and
- kernel modules */
- -- various artifacts
- -- qemuarm64
- /* artifacts for the guest side */
- -- deb/
- /* deb packages */
- -- images/
- -- enea-nfv-access-guest
- /* precompiled artifacts for the QEMU/Docker release image */
- -- various artifacts
- -- enea-nfv-access-guest-dev
- /* precompiled artifacts for the development process. The image
- contains userspace tools and kernel configurations necessary
- for developing, debugging and profiling applications and
- kernel modules */
- -- various artifacts
-
-
- INFO Below is a complete section with ID
- "eltf-target-tables-section" included from elft_params_updated.xml. It
- contains a variable number of target tables and the section title should be
- "Supported Targets with Parameters". It has have a short sentence about what
- it is in the beginning. The subtitles shall have the directory name of the
- target in the manifest.
-
-
-
-
- User Documentation
-
- This release of Enea Edge contains the following set of
- documents:
-
-
-
- Enea Edge Release Information. Describes the Enea Edge
- release content, main changes, the list of known issues and
- limitations.
-
-
-
- .
- Describes how to deploy and upgrade an Enea Edge base
- configuration, advanced configurations of the system and
- troubleshooting information.
-
-
-
- .
- Describes examples of onboarding, instantiating and configuring
- various VNFs.
-
-
-
- .
- Describes the Automation Framework for Enea Edge.
-
-
-
- . Describes the
- Automation Framework and Test Harness for Enea Edge and
- provides instructions regarding the necessary steps to run these
- software tools (deprecated, see
- Section 2.1 New Features
- and Improvements ).
-
-
-
- .
- Describes a sample Test Suite for System Testing of Enea Edge.
- (deprecated, see Section 2.1
- New Features and Improvements ).
-
-
-
-
-
- Supported Web Browsers
-
- These need to be updated
-
- The current release supports using the following web browsers:
-
-
-
- Google Chrome (tested with version 86).
-
-
-
- Mozilla Firefox (tested with version 82).
-
-
-
- Microsoft Edge (tested with version 84).
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info/doc/book.xml b/doc/book-enea-nfv-access-release-info/doc/book.xml
deleted file mode 100644
index 413eb6f..0000000
--- a/doc/book-enea-nfv-access-release-info/doc/book.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-]>
-
- Enea Edge Release
- Information
-
- Release Version
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml b/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml
deleted file mode 100644
index 9eecd3c..0000000
--- a/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-
-
-
- Getting Enea NFV Access
-
- Enea NFV Access releases and updates are available as binaries ready
- for download.
-
- Downloading Enea NFV Access
-Does the content below need to be revised to no longer make reference or mention to Enea Portal?
-
-
- Log in to the link above using the credentials provided by
- Enea.
-
-
-
- From the right corner of the top main menu, choose the
- Access section.
-
-
-
- The Files section on the left will display each
- official release of Enea NFV Access, with the latest at the top.
-
- Each release listing displays the dates for release and updates
- available, along with a Download button that allows
- you to directly save the version you wish to use.
-
-
-
- By clicking on the link at the top of any listing of Enea NFV
- Access, you'll access the changelog page for that version. At the bottom
- of the page are clearly labeled region-specific zip files containing the
- binary sources.
-
- Documentation is also available at the bottom of the page.
-
-
-
- On the right side of the main Access page is
- the Online Documentation section, listing pdfs for
- the latest versions of documentation. They can all be accessed for
- indiviudual downloading without the need to download the binaries
- first.
-
-
-
- For details about the books delivered and their purpose, refer to
- . For information concerning the
- contents of the release package, please see .
-
diff --git a/doc/book-enea-nfv-access-release-info/doc/jiraissues_override.xml b/doc/book-enea-nfv-access-release-info/doc/jiraissues_override.xml
deleted file mode 100644
index 7282d0f..0000000
--- a/doc/book-enea-nfv-access-release-info/doc/jiraissues_override.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
deleted file mode 100644
index 1f5fb0c..0000000
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ /dev/null
@@ -1,217 +0,0 @@
-
-
-
- Known Issues and Limitations in this Release
-
- This chapter lists the known general issues and limitations that
- affect the current release.
-
-
-
- LXCR-9904 Enea Edge Runtime cannot be installed on
- USB storage devices.
-
-
-
- LXCR-9799 Proper boot order is not ensured if a
- uCPE device has more than one HDD attached.
-
-
-
- ELCCR-527 Cancelling a file upload in the Enea
- Edge Management will require the user to close and reopen the upload window
- for the next upload to work.
-
-
-
- ELCCR-577 If Enea Edge Management is restored from a backup
- made on a release version older than Enea NFV Access 2.2.3, VNFs cannot be instantiated
- from the GUI.
-
-
-
- ELCCR-474 Deleting VNF instances with flows
- configured on the OVS bridges can be done only after removing the
- flows.
-
-
-
- ELCCR-572 Sometimes when selecting and deleting
- more than one VNF instance simultaneously, an error message might be
- triggered, even if the delete operation succeeds.
-
-
-
- ELCCR-847 The Juniper vSRX VNF cannot be
- instantiated on the Xeon-D architectures due to missing CPU features in
- the VNF's domain XML. This impacts all example use cases where the Juniper VNF is used.
-
-
-
- USERDOCAP-648 The storage size
- parameter on the VNF onboarding page is ignored. The default storage
- size specified when creating the VM image is used when instantiating the
- VM and when presenting VM information.
-
-
-
- LXCR-9853 The WAN interface of a uCPE device needs
- to be connected to a network with at least a router/gateway installed
- for next-hop communication.
-
-
-
- LXCR-9992 Depending on hardware capabilities,
- there are certain limitations regarding the vfio-pci
- and igb_uio drivers. While the Enea Edge
- Runtime uses the vfio-pci driver by default,
- for certain hardware configurations, igb_uio should
- be used instead, by providing custom scripting. Please contact Enea for
- further details.
-
-
-
- STCR-6224 The Enea Edge Automation
- and the Enea Edge Automation Framework and Test Harness do not
- support multiple custom scripts uploaded to a uCPE device at the same
- time.
-
-
-
- STCR-6292 Management of WAN Interfaces is not
- implemented in the Enea Edge Automation Framework and Test Harness.
-
-
-
- USERDOCAP-628 Enea Edge Automation Framework
- and Test Harness does not have support for product features implemented
- in Enea Edge 2.4.0 or newer.
-
-
-
- ELCCR-912 When the Enea Edge Management is installed
- on CentOS 7, prior to C7.1804 (kernel version 3.10.0-862), adding an
- upgrade image fails. As a workaround, please update
- glib2 to version 2.54.2 or later, using #yum
- update glib2 .
-
-
-
- ELCCR-854 Changing the management interface IP
- address will result in a temporary loss of connection with the uCPE
- device. If the device is behind a NAT, while using the Call Home
- connection, reestablishing the connection automatically could take up to
- 20 minutes. Restarting the vCPE Overlay will immediately reestablish the
- connection, but that implies the existence of an alternate way to
- trigger the vCPE restart operation on the device.
-
-
-
- USERDOCAP-641 Enea Edge does not have
- support for IPv6 addresses on both uCPE devices and the Enea Edge
- Management installation.
-
-
-
- ELCCR-1428 Wireless AP creation through the REST
- API does not validate that the wireless interface and LAN bridge are
- configured. Using these parameters may result in undefined
- behavior.
-
-
-
- USERDOCAP-651 Wireless AP configuration is
- optimized for wireless modules that use the ath10k
- driver. Using other wireless modules may result in undefined
- behavior.
-
-
-
- ELCCR-1351 The updated
- .Keystore and server.xml files
- from the
- /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/
- folder are overwritten during a product upgrade. As a workaround for
- this issue, after an upgrade, copy the updated
- .Keystore and server.xml files
- into the
- /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/
- folder and restart the ucpemanager service.
-
-
-
- ELCCR-1371 The current self-signed certificate for
- the Enea Edge Management is generated at build time, with a hard-coded
- common-name causing the uCPE device upgrade to fail in HTTPS mode. As a
- workaround, another certificate (containing an IP based common-name)
- must be generated.
-
- Perform the following the steps to generate the
- certificate:
-
-
-
- Stop the Edge Management service.
-
-
-
- Create the certificate using the
- createCertificate.sh script from distribution
- folder. This will create a new .Keystore file
- and copy it into the
- /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates
- folder.
-
-
-
- Start the Enea Edge Management, the new certificate should now
- take effect.
-
-
-
-
-
- ELCCR-1378 Modifying the type of the external
- interfaces can lead to errors. Instead of modifying, it is recommended
- to delete the old interfaces and recreate them with the desired
- type.
-
-
-
- ELCCR-907 At times the VIP address is not acquired
- by any of the backup nodes if a power failure happens on primary node in
- a High Availability setup. To recover, follow the official documentation
- available at Galera Cluster
- Recovery .
-
-
-
- LXCR-3283 PDF
- navigation : When using links to open other PDFs, or jump to
- another place in the same PDF, jumping back sometimes fails. This has
- been observed when opening a PDF in Adobe Reader, inside a browser with
- PDF add-on, as well as when the browser is configured to open PDF files
- in an external PDF reader. As a workaround, open the HTML version of the
- document.
-
-
-
- ELCCR-1468 When using the Enea Edge Management in
- HTTPS mode, upgrading a device from NFV Access 2.3.0 is not possible.
- Either switch to HTTP mode (for more details see The uCPE device Upgrade Process in the
-
- Manual) or install it manually.
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
deleted file mode 100644
index c01a149..0000000
--- a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
+++ /dev/null
@@ -1,162 +0,0 @@
-
-
-
- Main Changes
-
- Below you'll find information about the new features and updates made
- in this release, as well as details on the provided packages and the
- backwards compatibility with previous versions.
-
-
- New Features and Improvements
-
- New Features:
-
-
-
- CPDX-3496 Embedded WiFi support for all-in-one
- store/home office deployment.
-
-
-
- CPDX-3499 Expanded hardware, OS and network
- monitoring capability with Grafana integration.
-
-
-
- CPDX-3498 High Availability support with redundant
- Enea Edge Management in active standby configuration.
-
-
-
- CPDX-3407 HTTPS based downloads of VNFs for
- simplified deployment of the Enea Edge Management in cloud
- environments.
-
-
-
- CPDX-3500 The Enea Edge Automation,
- a tool for automatic system configuration based on Python
- scripting that will replace the existing Enea Edge Automation
- Framework and Test Harness in the next major release.
-
- The Enea Edge Automation Framework and Test Harness, and
- its related documentation the
- and the
- are deprecated starting with Enea Edge 2.4.0.
-
-
-
- Improvements:
-
-
-
- A new Requirements page has
- been added to the Web-installer, displaying device characteristics and
- checking minimal hardware requirements.
-
-
-
- A Web-installer's log is displayed on the last page in case the
- installation process has failed.
-
-
-
- Extended Web-installer support for NVME disks.
-
-
-
- Early Access Features:
-
- The following Early Access features are included in this release
- (made originally available with Enea NFV Access 2.3.0):
-
-
-
- Platform and VNF Snapshots:
-
-
-
- Platform Snapshots allow users to store, manage and restore
- snapshots of the Enea Edge Runtime configuration,
- with the purpose of recovering after a failed reconfiguration.
- This feature is disabled by default.
-
-
-
- VNF Snapshots allow users to store, manage and restore
- snapshots of VNFs deployed on the Enea Edge
- Runtime, with the purpose of restoring the VNF after a persistent
- VNF failure. This feature is disabled by default.
-
-
-
-
- Users that would like to try out the Snapshot features should
- contact Enea Support for additional documentation and
- assistance.
-
-
-
-
- Early Access features are provided for evaluation and early
- feedback. They are not allowed to be used for business-critical
- deployment, unless previously approved by Enea. Support cases reported on
- Early Access features may only be set to a Minor Priority, with the intent
- of addressing them in upcoming GA releases.
-
-
-
- Open Source
-
- For more information about the Open Source packages included, please
- refer to the Enea Edge Open Source Reports listed below. Each report
- contains open source and license information pertaining to packages
- provided with this release, for their respective component.
-
-
-
- .
-
-
-
- .
-
-
-
- .
-
-
-
- .
-
-
-
- .
-
-
-
-
-
- Compatibility
-
- This release does not contain any change impacting
- compatibility.
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml b/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml
deleted file mode 100644
index b0317b3..0000000
--- a/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml
+++ /dev/null
@@ -1,62 +0,0 @@
-
-
-
- Host Requirements
-
- Using Enea NFV Access or compiling applications requires certain
- packages to be installed on your build host. The requirements listed below
- are extensive to allow getting Enea NFV Access to be booted on target
- machines and for building applications.
-
-
-
-
-
-
-
-
-
-
-
- Build Host
- Requirements
- host requirements
-
-
-
-
- Linux distribution
-
- The downloaded product can installed on the target machine
- using a Linux host. For information about supported hosts and
- targets, see .
-
-
-
- Packages
-
- Depending on the Linux distribution and version of the host,
- certain packages may be required. See details on what packages are
- needed and how to install them in the following sections.
-
-
-
- Disk space
-
- Your build host should have at least 50 GB of free disk space
- for installing the SDK, eSDK or cross-compiling
- applications.
-
-
-
- Recommended RAM
-
- Your build host must have at least 4 GB available
- RAM.
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-release-info/swcomp.mk b/doc/book-enea-nfv-access-release-info/swcomp.mk
deleted file mode 100644
index 76991ee..0000000
--- a/doc/book-enea-nfv-access-release-info/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-release-info
-BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) Release Information"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/book.xml b/doc/book-enea-nfv-access-system-test-specification/doc/book.xml
deleted file mode 100644
index 9192ef5..0000000
--- a/doc/book-enea-nfv-access-system-test-specification/doc/book.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-]>
-
- Enea Edge System Test Specification
-
- Release Version
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml b/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml
deleted file mode 100644
index 62d9b72..0000000
--- a/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-
-
- Configuration
-
-
- Test Objects
-
- The test objects for the Test Harness are the Enea Edge and
- Enea Edge Management installations performed as indicated in the Components chapter of the .
-
-
-
- Test Environment
-
- To set up the required Test Harness environment please refer to
- Getting Started with the Automation Framework
- and Test Harness in the .
-
-
-
- Preconditions and Execution
-
- Please refer to section Prerequisites in the
- and section Installation and Initial Setup in the
-
- for more details.
-
-
- Before running any test case, make sure the uCPE device(s) needed
- have been added to the Enea Edge Management.
-
-
- For detailed execution steps of the sample test cases included with
- the Test Harness please see the following chapter.
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml b/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml
deleted file mode 100644
index 07c5ef7..0000000
--- a/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml
+++ /dev/null
@@ -1,109 +0,0 @@
-
-
- Overview
-
- This document describes the Test Harness (TH) sample test cases for
- the System Testing of Enea Edge, and the necessary environment setup
- to run these tests successfully.
-
-
- Definitions and Acronyms
-
-
- Definitions
-
-
-
-
-
-
- Component
-
- Description
-
-
-
-
-
- Enea Edge
-
- The Enea Edge (with ODM) Runtime and the
- Enea Edge Management.
-
-
-
-
-
-
- Acronyms
-
-
-
-
-
-
- Component
-
- Description
-
-
-
-
-
- AF
-
- Automation Framework for Enea Edge.
-
-
-
- JSON
-
- JavaScript Object Notation.
-
-
-
- NIC
-
- Network Interface Card.
-
-
-
- NFV
-
- Network Functions Virtualization.
-
-
-
- ODM
-
- Enea Element On Device Management.
-
-
-
- OVS
-
- Open vSwitch.
-
-
-
- TH
-
- Test Harness for Enea Edge.
-
-
-
- Enea Edge Management
-
- Enea Universal Customer Premises Equipment Manager.
-
-
-
- VNF
-
- Virtualized Network Function.
-
-
-
-
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
deleted file mode 100644
index b1bfa1e..0000000
--- a/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
+++ /dev/null
@@ -1,1804 +0,0 @@
-
-
- Sample Test Cases
-
- The test cases specified in this chapter are implemented as a Sample
- Test Suite included in the TH.
-
-
- VNF, Device and Network Smoke Test Cases
-
- The following is an automated test suite that acts as basic smoke
- tests for Enea Edge, and as a sanity-check test suite for the AF and
- TH.
-
-
- VNF - Onboard a VNF Image
-
- Description: Onboarding a VNF
- Image into the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/onboardVNFImage.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/vnf/onboardVNFRaw.py
-
-
-
- Preconditions:
-
-
-
- Add the VNF Image in the vnf_image folder
- in the QCOW2 format: <AF-TH-install-dir>/vnf_image/<VNF-Image-name>.qcow2
-
-
-
- A VNF Image JSON configuration file is created:
- <AF-TH-install-dir>/vnf_config/<VNF-Descriptor-name>/<VNF-Descriptor-name>.json Example: <AF-TH-install-dir>/vnf_config/fortigateImage/fortigateImage.json
-
-
-
- Action: Run the
- onboardVNFImage.yml Ansible Playbook with the
- <VNF-Image-name> and the
- <VNF-Descriptor-name> as extra-vars:
- ansible-playbook playbooks/onboardVNFImage.yml -e "vnfb=<VNF-Image-name> \
-vnfd=<VNF-Descriptor-name>"
-
- Result: Output of the test case
- run using the Test Harness:# Onboard VNF Image task result
-<VNF-Descriptor-name> successfully onboarded! Note: The test will not fail if the VNF Image is
- already onboarded. The output will instead contain: # debug <VNF-Descriptor-name> already onboarded!
-
-
-
- VNF - Offboard a VNF
-
- Description: Removing a VNF
- Descriptor from the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/offboardVNF.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/vnf/offboardVNF.py
-
-
-
- Precondition: The VNF has been
- previously onboarded in the Enea Edge Management instance.
-
- Action: Run the
- offboardVNF.yml Ansible Playbook with the
- <VNF-Descriptor-name> as extra-vars:
- ansible-playbook playbooks/offboardVNF.yml -e "vnfd=<VNF-Descriptor-name>"
-
- Result: Output of the test case
- run using the Test Harness: # Remove Descriptor task result
-<VNF-Descriptor-name> was removed! Note: The test will not fail if the VNF
- Descriptor does not exist. The output will instead contain:
- # debug No Descriptor with name <VNF-Descriptor-name>!
-
-
-
- Device - Add a device
-
- Description: Adding a uCPE device
- to the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/addDevice.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/device/addDevice.py
-
-
-
- Precondition: A device JSON
- configuration file must be created: <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json
-
- Example: <AF-TH-install-dir>/lab_config/intelc3850-2/intelc3850-2.json
-
- Action: Run the
- addDevice.yml Ansible playbook with the
- <Device-name> as extra-vars: ansible-playbook playbooks/addDevice.yml -e "device=<Device-name>"
-
- Result: Output of the test case
- run using the Test Harness: # Add Device task result
-<Device-name> device was added! Note: The test will not fail if the device
- already exists. The output will instead contain: # debug
-<Device-name> device already exists!
-
-
-
- Device - Upload a Edge image
-
- Description: Upload a Edge
- image file onto the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/uploadImage.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/device/uploadImage.py
-
-
-
- Precondition: The image path must
- already exist.
-
- Action: Run the
- uploadImage.yml Ansible playbook with the
- <Image-path> and
- <Upgrade-type> as extra-vars:
-
- ansible-playbook playbooks/deleteUpgradeFile.yml -e \
-image_path="<Image-path>" -e upgrade_type="<Upgrade-type>"
-
- Example: ansible-playbook playbooks/uploadImage.yml -e \
-image_path="/tmp/enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \
-upgrade_type="xeon_d"
-
- Result: Output of the test case
- run using the Test Harness:
-
- TASK [Upload NFVA image -- Run uploadImage.py module from automation_framework]
-localhost : ok=1 changed=1 unreachable=0 failed=0 Note: The test will fail if the image file has
- already been uploaded.
-
- TASK [Upload NFVA image -- Run uploadImage.py module from automation_framework]
-ok=0 changed=0 unreachable=0 failed=1
-
-# debug
-A file with the same name is already uploaded.
-
-
-
- Device - Delete Upgraded File
-
- Description: Deleting an uploaded
- Edge image file from the Enea Edge Management. For details please refer
- to:
-
-
-
- <AF-TH-install-dir>/playbooks/deleteUpgradeFile.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/device/deleteUpgradeFile.py
-
-
-
- Preconditions: The image file
- must already be uploaded onto the Enea Edge Management.
-
- Action: Run the
- deleteUpgradeFile.yml Ansible Playbook with the
- <Image-name> as extra-vars:ansible-playbook playbooks/deleteUpgradeFile.yml -e \
-image_name="<Image-name>"
-
- Example: ansible-playbook playbooks/deleteUpgradeFile.yml -e \
-image_name="enea-nfv-access-xeon-d.rootfs.ostree.tar.bz2"
-
- Result: Output of the test case
- run using the Test Harness:TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework]
-localhost : ok=1 changed=1 unreachable=0 failed=0
- Note: The test will fail if the image
- file does not exist: TASK [Remove NFVA image -- Run deleteUpgradeFile.py module from automation_framework]
-ok=0 changed=0 unreachable=0 failed=1
-
-# debug
-No oid found for '<image_name>' image name
-
-
-
- Device - Clear information about upgrades of uCPE devices
-
- Description: Clear information
- about upgrades of uCPE devices. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/clearCompletedUpgradesInfo.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/device/clearCompletedUpgradesInfo.py
-
-
-
- Preconditions: No preconditions
- needed.
-
- Action: Run the
- clearCompletedUpgradesInfo.yml Ansible
- Playbook:ansible-playbook playbooks/clearCompletedUpgradesInfo.yml
-
- Result: Output of the test case
- run using the Test Harness:TASK [Clear completed info about upgrading -- Run \
-clearCompletedUpgradesInfo.py module from automation framework]]
-localhost : ok=1 changed=1 unreachable=0 failed=0
-
-
-
- Device - Install and Activate a Edge image
-
- Description: Installing and
- Activating a Edge image on a uCPE device from the Enea Edge Management.
- For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/installAndActivate.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/device/installAndActivate.py
-
-
-
- Preconditions:
-
- The device must be previously added to the Enea Edge Management
- instance.
-
-
-
- The image file must already be uploaded onto the Enea Edge
- Management.
-
-
-
- Action: Run the
- installAndActivate.yml Ansible Playbook with the
- <Image-name> ,
- <Upgrade-type> , and the
- <Device-name> as extra-vars:ansible-playbook playbooks/installAndActivate.yml -e \
-image_name="<Image_name>" -e upgrade_type="<Upgrade_type>" -e \
-device="<Device-name>"
-
- Example: ansible-playbook playbooks/installAndActivate.yml -e \
-image_name="enea-nfv-access-xeon-d6.rootfs.ostree.tar.bz2" -e \
-upgrade_type=xeon_d -e device=inteld1521-16"
-
- Result: Output of the test case
- run using the Test Harness:TASK \
-[Install And Activate -- Run installAndActivate.py module from automation_framework]
-localhost : ok=1 changed=1 unreachable=0 failed=0
- Note: The test will fail if the image
- has already been installed on the uCPE device:TASK \
-[Install And Activate -- Run installAndActivate.py module from automation_framework]
-ok=0 changed=0 unreachable=0 failed=1
-
-# debug
-Duplicate entry - Release already installed
-
-
-
- Device - Upload, Install and Activate a Edge image on a
- uCPE device
-
- Description: Upload, install and
- activate a Edge image on a uCPE device from the Enea Edge Management. For
- details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/installNFVAImage.yml
-
-
-
- The playbook imports the previously described
- playbooks:
-
-
-
- playbooks/waitDeviceUp.yml
-
-
-
- playbook/uploadImage.yml
-
-
-
- playbook/installAndActivate.yml
-
-
-
- playbook/deleteUpgradeFile.yml
-
-
-
- playbook/clearCompletedUpgradesInfo.yml
-
-
-
-
-
- Preconditions:
-
-
-
- The device has to be previously added to the Enea Edge Management
- instance.
-
-
-
- A device JSON configuration file must be created:
-
- <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json
-
-
-
- Action: Run the
- installNFVAImage.yml Ansible Playbook with the
- <Image-path> ,
- <Image-name> ,
- <Upgrade-type> , and the
- <Device-name> as extra-vars: ansible-playbook playbooks/installNFVAImage.yml -e \
-device="<Device-name>" -e image_path="<Image-path>" -e \
-image_name="<Image-name>" -e upgrade_type="<Upgrade-type>"
-
- Example: ansible-playbook playbooks/installNFVAImage.yml -e \
-device="inteld1521-16" -e \
-image_path=/tmp/enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \
-image_name=enea-nfv-access-xeon-d5.rootfs.ostree.tar.bz2 -e \
-upgrade_type=xeon_d
-
- Result: Output of the test case
- run using the Test Harness:localhost : ok=1 changed=1 unreachable=0 failed=0
- Note: The test will fail if the one
- imported playbook fails:ok=0 changed=0 unreachable=0 failed=1
-
-
-
- Device - Wait a Device
-
- Description: Wait for a uCPE
- device to connect to the Enea Edge Management. For details please refer
- to:
-
-
-
- <AF-TH-install-dir>/playbooks/waitDeviceUp.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/device/waitDeviceUp.py
-
-
-
- Preconditions:
-
-
-
- The device has to be previously added to the Enea Edge Management
- instance.
-
-
-
- The device JSON configuration file must exist:
- <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json
-
-
-
- Action: Run the
- waitDeviceUp.yml Ansible Playbook with the
- <Device-name> as extra-vars: ansible-playbook playbooks/waitDeviceUp.yml -e "device=<Device-name>"
-
- Result: Output of the test case
- run using the Test Harness:# Wait Device task result
-<Device-name> device is connected! Note: The test will fail if the device does not
- exist or it is not connected.
-
-
-
- Device - Remove a Device
-
- Description: Removing a uCPE
- device from the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/removeDevice.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/device/removeDevice.py
-
-
-
- Preconditions:
-
-
-
- The device has to be previously added to the Enea Edge Management
- instance.
-
-
-
- The device JSON configuration file must exist:
- <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json
-
-
-
- Action: Run the
- removeDevice.yml Ansible Playbook with the
- <Device-name> as extra-vars: ansible-playbook playbooks/removeDevice.yml -e "device=<Device-name>"
-
- Result: Output of the test case
- run using the Test Harness:# Remove Device task result
-<Device-name> device was removed! Note: The test will not fail if the device does
- not exist. The output will contain: # debug
-<Device-name> device was not found!
-
-
-
- Network - Bind a NIC
-
- Description: Binding a physical
- network interface (NIC) to a device. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/bindNIC.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/network/bindNetworkInterface.py
-
-
-
- Preconditions:
-
-
-
- A device must have been previously added and connected to the
- Enea Edge Management instance.
-
-
-
- A NIC JSON configuration file must exist: <AF-TH-install-dir>/lab_config/<Device-name>/<NIC>.json
-
- Example: <AF-TH-install-dir>/lab_config/intelc3850-2/wan_nic.json
-<AF-TH-install-dir>/lab_config/intelc3850-2/lan_nic.json
-
-
-
- Action: Run the
- bindNIC.yml Ansible Playbook with the
- <Device-name> and
- <NIC> as extra-vars: ansible-playbook playbooks/bindNIC.yml -e "device=<Device-name> nic=<NIC>"
-
- Result: Output of the test case
- run using the Test Harness:# Bind NIC task result
-<NIC> binded successfully! Note: The test will not fail if the NIC is
- already bound, it will be unbound and bound again with the provided
- configuration.
-
-
-
- Network - Unbind a NIC
-
- Description: Unbinding a physical
- network interface (NIC) from a device. For details please refer
- to:
-
-
-
- <AF-TH-install-dir>/playbooks/unbindNIC.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/network/unbindNetworkInterface.py
-
-
-
- Preconditions:
-
-
-
- A NIC is bound to a device in a Enea Edge Management instance.
-
-
-
- A NIC JSON configuration file exists: <AF-TH-install-dir>/lab_config/<Device-name>/<NIC>.json
-
-
-
- Action: Run the
- unbindNIC.yml Ansible Playbook with the
- <Device-name> and
- <NIC> as extra-vars: ansible-playbook playbooks/unbindNIC.yml -e "device=<Device-name> nic=<NIC>"
-
- Result: Output of the test case
- run using the Test Harness: # Unbind NIC task result
-<NIC> unbinded! Note:
- The test will not fail if the NIC is not bound. The output will instead
- contain:# debug
-<NIC> is not binded!
-
-
-
- Network - Create a Bridge
-
- Description: Creating an OVS
- network bridge on a uCPE device. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/addBridge.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/network/newNetworkBridge.py
-
-
-
- Preconditions:
-
- A NIC is bound to a device in a Enea Edge Management
- instance.
-
-
-
- A Bridge JSON configuration file exists:<AF-TH-install-dir>/lab_config/<Device-name>/<Bridge-name>.json
-
- Example: <AF-TH-install-dir>/lab_config/intelc3850-2/wan_br.json
-<AF-TH-install-dir>/lab_config/intelc3850-2/lan_br.json
-
-
-
- Action: Run the
- addBridge.yml Ansible Playbook with the
- <Device-name> and the
- <Bridge-name> as extra-vars: ansible-playbook playbooks/addBridge.yml -e "device=<Device-name> bridge=<Bridge-name>"
-
- Result: Output of the test case
- run using the Test Harness: # Add Bridge task result
-<Bridge-name> network bridge was added! Note: The test will not fail if there already
- exists a bridge with the same name. It will be deleted and the bridge
- will be created again with the provided configuration.
-
-
-
- Network - Remove a Bridge
-
- Description: Removing an OVS
- network bridge from a uCPE device. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/deleteBridge.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/network/delNetworkBridge.py
-
-
-
- Preconditions:
-
- A Bridge exists for a device in a Enea Edge Management
- instance.
-
-
-
- A Bridge JSON configuration file exists: <AF-TH-install-dir>/lab_config/<Device-name>/<Bridge-name>.json
-
- Action: Run the
- deleteBridge.yml Ansible Playbook with the
- <Device-name> and the
- <Bridge-name> as extra-vars: ansible-playbook playbooks/deleteBridge.yml -e "device=<Device-name> \
-bridge=<Bridge-name>"
-
- Result: Output of the test case
- run using the Test Harness: # Delete Bridge task result
-<Bridge-name> network bridge was deleted! Note: The test will not fail if the bridge does
- not exist: # debug
-<Bridge-name> bridge not found!
-
-
-
- Network - Configure a DPDK
-
- Description: Enabling or
- Disabling the DPDK support in OVS. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/configDPDK.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/network/configDPDK.py .
-
-
-
- Precondition:
-
- A device must have been previously added and connected to the Enea Edge
- Management instance.
-
- Action: Run the
- configDPDK.yml Ansible Playbook with the
- <Device-name> and
- <enable/disable> as extra-vars:ansible-playbook playbooks/configDPDK.yml -e "device=<Device-name> \
-state=<enable/disable>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Configure DPDK task result
-DEBUG: Set DPDK state to <enable/disable> Note: DPDK use cannot be disabled if DPDK
- interfaces are configured. The task will fail in this case.
-
-
-
- Custom Scripts - Upload a Custom Script to the Enea Edge
- Management
-
- Description: Upload a Custom
- Script to the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/uploadCustomScript.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/customScripts/upload.py .
-
-
-
- Precondition:
-
- <AF-TH-install-dir>/lab_config/customScripts
- must contain a Custom Script file.
-
- Action: Run the
- uploadCustomScript.yml Ansible Playbook with the
- <scriptName> and
- <phase> as extra-vars: ansible-playbook playbooks/uploadCustomScript.yml -e "scriptName=<scriptName> \
-phase=
-<always-after-startup|once-after-startup|always-before-startup|once-before-startup>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Upload Custom Script task result
-DEBUG: "{{ scriptName }} was uploaded to Enea Edge Management!"
-
-
-
- Custom Scripts - Upload a Custom Script from the Enea Edge Management to
- a Device
-
- Description: Upload a Custom
- Script from the Enea Edge Management to a Device. For details please refer
- to:
-
-
-
- <AF-TH-install-dir>/playbooks/uploadCustomScriptOnDevice.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/customScripts/uploadOnDevice.py .
-
-
-
- Preconditions:
-
-
-
- A device must have been previously added and connected to the
- Enea Edge Management instance.
-
-
-
- A Custom Script must have been previously added to the Enea Edge
- Management instance.
-
-
-
- Action: Run the
- uploadCustomScriptOnDevice.yml Ansible Playbook
- with the <scriptName> ,
- <phase> and
- <deviceName> as extra-vars: ansible-playbook playbooks/uploadCustomScriptOnDevice.yml -e "scriptName=<scriptName> \
-phase=
-<always-after-startup|once-after-startup|always-before-startup|once-before-startup> \
-device=<deviceName>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Upload Custom Script on Device task result
-DEBUG: "{{ scriptName }} was uploaded to {{ device }}!"
-
-
-
- Custom Scripts - Remove a Custom Script from the Enea Edge
- Management
-
- Description: Remove a Custom
- Script from the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/removeCustomScript.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/customScripts/delete.py .
-
-
-
- Precondition:
-
- A Custom Script must have been previously added to the Enea Edge
- Management.
-
- Action: Run the
- removeCustomScript.yml Ansible Playbook with the
- <scriptName> and
- <phase> as extra-vars: ansible-playbook playbooks/removeCustomScript.yml -e "scriptName=<scriptName> \
-phase=
-<always-after-startup|once-after-startup|always-before-startup|once-before-startup>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Remove Custom Script in phase from Enea Edge Management task result
-DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from Enea Edge Management!"
-
-
-
- Custom Scripts - Remove a Custom Script from a Device
-
- Description: Remove a Custom
- Script from a Device. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/removeCustomScriptOnDevice.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/customScripts/deleteOnDevice.py .
-
-
-
- Preconditions:
-
-
-
- A device must have been previously added and connected to the
- Enea Edge Management instance.
-
-
-
- A Custom Script must have been previously added to the
- Device.
-
-
-
- Action: Run the
- removeCustomScriptOnDevice.yml Ansible Playbook
- with the <scriptName> ,
- <phase> and
- <deviceName> as extra-vars: ansible-playbook playbooks/removeCustomScriptOnDevice.yml -e "scriptName=<scriptName> \
-phase=
-<always-after-startup|once-after-startup|always-before-startup|once-before-startup> \
-device=<deviceName>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Remove Custom Script in phase from Device task result
-DEBUG: "{{ scriptName }} from phase {{ phase }} was removed from {{ device }}!"
-
-
-
- Offline Configuration - Add an Offline Configuration
- Store
-
- Description: Adding an Offline
- Config Store to the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/addConfigStore.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/device/addConfigStore.py .
-
-
-
- Precondition:
-
- The Offline Configuration Store should not already exist on
- the Enea Edge Management. If it exists, the test will report a
- duplicate.
-
-
-
- A store JSON file needs to exist: <AF-TH-install-dir>/lab_config/<device-name>/store.json
-
-
-
- Action: Run the
- addConfigStore.yml Ansible Playbook with the
- <device-name> as extra-vars: ansible-playbook playbooks/addConfigStore.yml -e \
-"device=<device-name>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Add Config Store task result
-**********************************************************
-**********************************
- * localhost - changed=False
---------------------------------------------------
- Config store for intelc3850-2 device was added!
-
-
-
- Offline Configuration - Remove an Offline Configuration
- Store
-
- Description: Removing an Offline
- Config Store from the Enea Edge Management. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/removeConfigStore.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/device/removeConfigStore.py .
-
-
-
- Precondition:
-
- The Offline Configuration Store the user wishes to remove should
- exist in the Enea Edge Management. If it does not, the test will say so.
-
- Action: Run the
- removeConfigStore.yml Ansible Playbook with the
- <store-name> as extra-vars: ansible-playbook playbooks/removeConfigStore.yml -e \
-"store=<store-name>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Remove Config Store task result **********************************
-*******************************************************
- * localhost - changed=False
- -- intelc3850-2 config store was removed! ---------
-
-
-
- Offline Configuration - Add a network bridge to an Offline
- Configuration Store
-
- Description: Adding a network
- bridge to an Offline Config Store in Enea Edge Management. For details please
- refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/addOfflineBridge.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/network/newNetworkBridge.py .
-
-
-
- Precondition:
-
-
-
- The Offline Configuration Store should exist in the Enea Edge
- Management. If it does not, the test will say so.
-
-
-
- A Bridge JSON configuration file needs to exist:
- <AF-TH-install-dir>/lab_config/<device-name>/<bridge-name>.json
-
-
-
- Action: Run the
- addOfflineBridge.yml Ansible Playbook with the
- <device-name> ,
- <store-name> and
- <bridge-name> as extra-vars: ansible-playbook playbooks/addOfflineBridge.yml -e \
-"device=<device-name> store=<store-name> bridge=<bridge-name>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # debug *************************************************************
-******************************************************
- * localhost - changed=False
---------------------------------------------------
- lan_br bridge already exists
- --- will be deleted to create it with the provided configuration
-..
-# Add Bridge task result ********************************************
-******************************************************
- * localhost - changed=False
- -- lan_br network bridge was added! ------------
-
- Note: if the bridge exists, it
- will be removed and then re-added, as the output above shows.
-
-
-
- Offline Configuration - Configure a DPDK
-
- Description: Adding an "enable"
- or "disable" DPDK state to an Offline Config Store. For details please
- refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/configOfflineDPDK.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/network/configDPDK.py .
-
-
-
- Precondition:
-
- An empty Offline Configuration Store should exist in Enea Edge
- Management.
-
- Action: Run the
- configOfflineDPDK.yml Ansible Playbook with the
- <store-name> and
- <enable/disable> as extra-vars:
- ansible-playbook playbooks/configOfflineDPDK.yml -e \
-"store=<store-name> state=<enable/disable>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- DEBUG: Set DPDK state to disable
-INFO: Done
-
- Note: the DPDK state cannot be
- changed. Recreate the Offline Config Store and set the DPDK again if you
- want to change the state.
-
-
-
- Offline Configuration - Upload an offline configuration onto a
- uCPE Device
-
- Description: Uploading an offline
- configuration to a uCPE Device. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/uploadConfigStore.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/device/uploadConfigStore.py .
-
-
-
- Precondition:
-
-
-
- The Offline Configuration Store should exist in the Enea Edge
- Management.
-
-
-
- The device should be connected to the Enea Edge Management.
-
-
-
- Action: Run the
- uploadConfigStore.yml Ansible Playbook with the
- <store-name> and
- <device-name> as extra-vars:
-
- ansible-playbook playbooks/uploadConfigStore.yml -e \
-"store=<store-name> device=<device-name>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Upload Config Store task result ****************************
- * localhost - changed=False ---------------
- 2020-10-08 13:29:41,062 - INFO: Upload offline \
- configuration to uCPE Device
- 2020-10-08 13:30:01,315 - INFO: The '<store-name>' config \
- store was successfully uploaded on device!
- 2020-10-08 13:30:01,316 - INFO: Done
-
-
-
- Offline Configuration - Get the offline configuration upload
- status on the uCPE Device
-
- Description: Get the offline
- configuration upload status to a uCPE Device. For details please refer
- to:
-
-
-
- <AF-TH-install-dir>/playbooks/getUploadStatus.yml .
-
-
-
- <AF-TH-install-dir>/automation_framework/device/getUploadStatus.py .
-
-
-
- Precondition:
-
-
-
- An upload of the offline configuration should be done on the
- uCPE Device.
-
-
-
- The device should be connected to the Enea Edge Management.
-
-
-
- Action: Run the
- getUploadStatus.yml Ansible Playbook with the
- <device-name> as extra-vars:
-
- ansible-playbook playbooks/getUploadStatus.yml -e \
-"device=<device-name>"
-
- Result: Output of the test case
- run using the Test Harness:
-
- # Upload Config Store task result ****************************
- * localhost - changed=False ---------------
- 2020-10-08 14:13:24,422 - INFO: Get upload offline configure \
- status on uCPE Device
- 2020-10-08 14:13:24,521 - INFO: Successful: True
- 2020-10-08 14:13:24,522 - INFO: Store name: <store-name>
- 2020-10-08 14:13:24,523 - INFO: In progress: False
- 2020-10-08 14:13:24,524 - INFO: A config store was successfully \
- uploaded on device!
- 2020-10-08 14:13:24,525 - INFO: Done
-
-
-
-
- VNF Deployment and Lifecycle
-
- The following details the automated suite that handles the testing
- of the instantiation, lifecycle and destruction of a VNF for Enea Edge.
-
-
- Instantiating a VNFI
-
- Description: Creating a VNF
- instance on a uCPE device. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/instantiateVNFI.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/vnf/instantiateVNFI.py
-
-
-
- Preconditions:
-
- A VNF Image is onboarded and a device is added and connected
- to the Enea Edge Management. Depending on the VNF, other steps may be
- required.
-
-
-
- A VNFI JSON configuration file exists: <AF-TH-install-dir>/vnf_config/<VNF-Descriptor-name>/<VNFI-name>.json
-
- Example: <AF-TH-install-dir>/vnf_config/fortigateImage/fortigateFWInstance.json
-
-
-
- Action: Run the
- instantiateVNFI.yml Ansible Playbook with the
- <Device-name> ,
- <VNF-Descriptor-name> and the
- <VNFI-name> as extra-vars: ansible-playbook playbooks/instantiateVNFI.yml -e "device=<Device-name> \
-vnfd=<VNF-Descriptor-name> vnfi=<VNFI-name>"
-
- Result: Output of the test case
- run using the Test Harness: # Instantiate VNF task result
-<VNFI-name> was instantiated! Note: The test will not fail if the VNF instance
- already exists. The output will instead contain: # debug
-<VNFI-name> already exists!
-
-
-
- Controlling a VNFI
-
- Description: Changing the status
- of a VNF instance (Pause, Resume, Stop, Start). For details please refer
- to:
-
-
-
- <AF-TH-install-dir>/playbooks/controlVNFI.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/vnf/controlVNFI.py
-
-
-
- Precondition: A VNF is
- instantiated on a uCPE device.
-
- Action: Run the
- controlVNFI.yml Ansible Playbook with the
- <Device-name> ,
- <VNFI-name> and the
- <Command> as extra-vars: ansible-playbook playbooks/controlVNFI.yml -e "device=<Device-name> \
-vnfi=<VNFI-name> status=<pause|resume|start|stop>"
-
- Result: Output of the test case
- run using the Test Harness: # Change VNFI Status task result
-<VNFI-name> status was set to <Command> Note: The test will not fail if the VNF instance
- does not exist or if the specified command is not valid. Depending on
- the case, the output will contain: # debug
-<VNFI-name> was not found! or# debug
-Invalid VNF Instance control command specified - <Command>
-
-
-
- Destroying a VNFI
-
- Description: Destroying a VNF
- instance from a uCPE device. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/destroyVNFI.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/vnf/destroyVNFI.py
-
-
-
- Precondition: A VNF is
- instantiated on a uCPE device.
-
- Action: Run the
- destroyVNFI.yml Ansible Playbook with the
- <Device-name> and the
- <VNFI-name> as extra-vars: ansible-playbook playbooks/destroyVNFI.yml -e "device=<Device-name> \
-vnfi=<VNFI-name>" Result: Output of the test case run using the
- Test Harness:# Destroy VNFI task result
-<VNFI-name> was destroyed! Note: The test will not fail if the VNF instance
- does not exist. The output will instead contain: # debug
-<VNFI-name> was not found!
-
-
-
-
- Service Creation and Lifecycle
-
- This test suite contains more complex test cases designed to verify
- service creation and service lifecycle management. These test cases also
- serve as examples of how different services can be deployed using the
- Automation Framework (AF) and the Test Harness (TH).
-
-
- Fortigate VNF as a Firewall
-
- This test case was implemented in two different ways to exemplify
- both methods supported by the AF and TH to deploy such services.
-
- How to deploy the FortiGate VNF as a
- Firewall:
-
-
-
- Add a uCPE device.
-
-
-
- Wait for the uCPE device to be connected in the Enea Edge
- Management.
-
-
-
- Onboard the FortiGate VNF Image.
-
-
-
- Bind 2 physical interfaces: wan_nic (this
- physical interface has to be connected to the Lab Network) and
- lan_nic .
-
-
-
- Create 2 bridges: wan_br (using the
- wan_nic interface) and lan_br
- (using the lan_nic interface).
-
-
-
- Instantiate the FortiGate VNF using the basic Firewall
- configuration provided with your Enea Edge Release, and the
- Fortigate License file.
-
-
- Please contact the local Fortinet sales representatives in
- your region to get the Fortigate License file.
-
-
-
-
- For more information please refer to section FortiGate VNF as a Firewall in the
-
- Manual.
-
-
- FortigateFWInstance Test
-
- Description: Instantiate the
- FortiGate VNF as a Firewall and test it using an isolated network
- namespace.
-
- This example was implemented with the "Test Harness" method,
- based on Ansible Playbooks. For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/fortigateFWService/instantiateFortigateFW.yml
-
-
-
- <AF-TH-install-dir>/playbooks/fortigateFWService/testFortigateFWInstance.yml
-
-
-
- <AF-TH-install-dir>/playbooks/fortigateFWService/cleanupTestFortigateFWInstance.yml
-
-
-
- <AF-TH-install-dir>/playbooks/fortigateFWService/cleanupFortigateFWInstance.yml
-
-
-
- Preconditions:
-
-
-
- A device must have been previously added and connected to
- the Enea Edge Management instance.
-
-
-
- Add the Fortigate VNF Image
- (fortios.qcow2 ) to the
- <AF-TH-install-dir>/vnf_image
- folder.
-
-
-
- The device JSON configuration file is created:
- <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json .
-
-
-
- Add device settings in the hosts Ansible
- inventory file under [fortigateFW] and remove
- the intelc3850-2 example.
-
- Example: intelc3850-2 ansible_host=172.24.12.114 ansible_port=22 \
-ansible_user=root ansible_pass=root
-
-
-
- NIC JSON configuration files are created:
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/wan_nic.json
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/lan_nic.json
-
-
-
-
-
- Bridge JSON configuration files are created:
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/wan_br.json
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/lan_br.json
-
-
-
-
-
- Download the FortiGate VNF Firewall basic configuration file
- from Enea, copy it into the
- <AF-TH-install-dir>/vnf_config/fortigateImage
- directory and rename it to
- fortigateFW.conf .
-
-
-
- Retrieve the FortiGate VNF license file from Fortinet or
- Enea, copy it into the
- <AF-TH-install-dir>/vnf_config/fortigateImage
- directory and rename it to
- fortigateLicense.lic .
-
- For more information please refer to section FortiGate VNF as a Firewall in
- the
- Manual.
-
-
-
- Action: Run the
- instantiateFortigateFW.yml Ansible Playbook with
- the <Device-name> as
- extra-vars:ansible-playbook playbooks/fortigateFWService/instantiateFortigateFW.yml \
--e "device=<Device-name>"
-
- Result: Output of the test case
- run using the Test Harness: # Test FortigateFWInstance task result
-FortigateFWInstance tested successfully!
-
- Cleanup: Run the
- cleanupFortigateFWInstance.yml Ansible Playbook
- with the <Device-name> as extra-vars:
- ansible-playbook playbooks/fortigateFWService/cleanupFortigateFWInstance.yml \
--e "device=<Device-name>"
-
-
-
- DeployFortigateFW Scenario
-
- Description: Deploy the
- Fortigate VNF as a Firewall. This example was implemented with the
- "Automation Framework" method, based on the
- unittestSuite.py Python module.
-
- For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/unittestSuiteTest/deployFortigateFWScenario.yml
-
-
-
- <AF-TH-install-dir>/playbooks/unittestSuiteTest/cleanupFortigateFWScenario.yml
-
-
-
- <AF-TH-install-dir>/automation_framework/unittestSuite
- directory.
-
-
-
- Preconditions:
-
-
-
- A device must have been previously added and connected to
- the Enea Edge Management instance.
-
-
-
- Add the FortiGate VNF Image
- (fortios.qcow2 ) to the
- <AF-TH-install-dir>/vnf_image
- folder.
-
-
-
- The device JSON configuration file is created:
-
- <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json .
-
-
-
- The NIC JSON configuration files are created:
-
- <AF-TH-install-dir>/lab_config/<Device-name>/wan_nic.json
-
- <AF-TH-install-dir>/lab_config/<Device-name>/lan_nic.json
-
-
-
- The Bridge JSON configuration files are created:
-
- <AF-TH-install-dir>/lab_config/<Device-name>/wan_br.json
-
- <AF-TH-install-dir>/lab_config/<Device-name>/lan_br.json
-
-
-
- Download the FortiGate VNF Firewall basic configuration from
- Enea, copy it into the
- <AF-TH-install-dir>/vnf_config/fortigateImage
- directory and rename it to
- fortigateFW.conf .
-
-
-
- Retrieve the FortiGate VNF license file from Fortinet or
- Enea, copy it into the
- <AF-TH-install-dir>/vnf_config/fortigateImage
- directory and rename it to
- fortigateLicense.lic .
-
- For more details, please refer to:
-
-
-
- FortiGate VNF as a
- Firewall in the
- Manual.
-
-
-
- Python Unit-Test Suite in
- .
-
-
-
-
-
- Action: Run the
- deployFortigateFWScenario.yml Ansible Playbook
- with the <Device-name> as extra-vars:
- ansible-playbook playbooks/unittestSuiteTest/deployFortigateFWScenario.yml \
--e "device=<Device-name>"
-
- Result: Output of the test case
- run using the Test Harness: # unittestSuite Deploy Test task result
-FortigateFW Scenario deployed successfully!
-
- Cleanup: Run the
- cleanupFortigateFWScenario.yml Ansible Playbook
- with the <Device-name> as extra-vars:
- ansible-playbook playbooks/unittestSuiteTest/cleanupFortigateFWScenario.yml \
--e "device=<Device-name>"
-
-
-
-
- chainedVNFsService
-
- Description: This sample test
- case corresponds to the "VNF Chaining Example Use-case" from the Enea
- Edge Example Use-cases manual.
-
- For details please refer to:
-
-
-
- <AF-TH-install-dir>/playbooks/chainedVNFsService/chainedVNFsService.yml
-
-
-
- <AF-TH-install-dir>/playbooks/chainedVNFsService/testChainedVNFsService.yml
-
-
-
- <AF-TH-install-dir>/playbooks/chainedVNFsService/cleanupChainedVNFsService.yml
-
-
-
- Preconditions:
-
-
-
- Two devices must have been previously added and connected to
- the Enea Edge Management instance.
-
-
-
- Add the Fortigate VNF Image
- (fortios.qcow2 ) to the
- vnf_image folder.
-
-
-
- Add the Juniper vSRX VNF Image
- (juniper.qcow2 ) to the
- vnf_image folder.
-
-
-
- The device JSON configuration file(s) is created, e.g.:
-
- <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json .
-
-
-
- Add device settings in the hosts Ansible
- inventory file under [chainedVNFs] . Keep both
- devices, the "site1" and "site2" entries, and update the values for
- ansible_host , ansible_port ,
- ansible_user and ansible_pass ,
- as applicable.
-
- Example:
-
- site1 ansible_host=172.24.14.157 ansible_port=22 ansible_user=root \
-ansible_pass=root
-
- site2 ansible_host=172.24.14.50 ansible_port=22 ansible_user=root \
-ansible_pass=root
-
-
-
- NIC JSON configuration files are created for each of the
- devices, where mgmt_nic is connected to the DHCP
- from the Lab Network and wan_nic is connected
- back to back to the other device:
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/mgmt_nic.json
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/wan_nic.json
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/lan_nic.json
-
-
-
-
-
- Bridge JSON configuration files are created for each of the
- devices:
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/vnf_mgmt_br.json
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/sfc_br.json
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/wan_br.json
-
-
-
- <AF-TH-install-dir>/lab_config/<Device-name>/lan_br.json
-
-
-
- Note that sample configuration files needed for devices' NICs
- and bridges can be found in:
- <AF-TH-install-dir>/lab_config/inteld1521-1
- and
- <AF-TH-install-dir>/lab_config/inteld1521-2 .
-
-
-
- Retrieve the FortiGate VNF Firewall basic configuration files
- from Enea (FortiFW-Site1.conf and
- FortiFW-Site2.conf ), and copy them into the
- <AF-TH-install-dir>/vnf_config/fortigateFWImage
- directory.
-
-
-
- Retrieve the FortiGate VNF license file from Fortinet or Enea,
- copy it into the
- <AF-TH-install-dir>/vnf_config/fortigateFWImage
- directory and rename it to
- fortigateLicense.lic .
-
-
-
- Retrieve the Juniper vSRX basic configuration files from Enea
- (vSRX-Site1.iso and
- vSRX-Site2.iso ), and copy them into the
- <AF-TH-install-dir>/vnf_config/junipervSRXImage
- directory.
-
-
-
- Retrieve the vSRX-domain-update-script
- from Enea and copy it into the junipervSRXImage
- directory.
-
- Please refer to the Chapter concerning the VNF Chaining Example Use-case in the
-
- manual for additional information about preconditions.
-
-
-
- Action: Run the
- chainedVNFsService.yml Ansible Playbook as
- follows:ansible-playbook playbooks/chainedVNFsService/chainedVNFsService.yml \
--e "site1=inteld1521-1 site2=inteld1521-2 arch=XeonD"
-
- Note that "arch" may either be { XeonD | AtomC } depending on the
- target set chosen.
-
- Result: Output of the test case
- run using the Test Harness: # testChainedVNFsService task result
-******************************************************************************
- * site1 - changed=False ----------------------------------------------
-----
-<site1_lan-ip> ---> <site2_lan-ip>
-LAN-to-LAN connectivity (through VPN tunnel)tested successfully!
-
- Cleanup: Run the
- cleanupChainedVNFsService.yml Ansible Playbook as
- follows: ansible-playbook playbooks/chainedVNFsService/cleanupChainedVNFsService.yml \
--e "site1=inteld1521-1 site2=inteld1521-2 arch=XeonD"
-
-
-
-
- Custom Scripts - Basic Test
-
- The basic test script can be found in
- <AF-TH-install-dir>/playbooks/customScripts/basicTest.yml .
-
- The basicTest.yml script requires the following
- steps:
-
-
-
- Upload a Custom Script onto the Enea Edge Management.
-
-
-
- Upload the Custom Script onto a Device.
-
-
-
- Reboot the Device.
-
-
-
- Wait for the Device to be up and running.
-
-
-
- Remove the Custom Script from the Device.
-
-
-
- Remove the Custom Script from the Enea Edge Management.
-
-
-
- Preconditions:
-
-
-
- A device must have been previously added and connected to the
- Enea Edge Management.
-
-
-
- The device JSON configuration file must have been created:
- <AF-TH-install-dir>/lab_config/<Device-name>/<Device-name>.json .
-
-
-
- The custom script should have been previously saved in
- <AF-TH-install-dir>/lab_config/customScripts .
-
-
-
- Add device settings in the hosts Ansible inventory file under
- [customScriptDevice] and remove the inteld1521-1
- example.
-
-
-
- Example:
-
- [customScriptDevice]
-inteld1521-1 ansible_host=172.24.12.73 ansible_port=22 ansible_user=root \
- ansible_pass=root
-
- Action: Run
- basicTest.yml (example data for
- test_success_after_always ):
-
- ansible-playbook playbooks/customScripts/basicTest.yml -e "device=<Device-name>" \
--e "scriptName=test_success_after_always" -e "phase=always-after-startup" \
--e "expectedStatus=success"
-
- Result: Output of
- basicTest.yml :
-
- test_success_after_always was uploaded to Enea Edge Management!
-test_success_after_always was uploaded to <Device-name>!
-
-<Device-name> device is connected!
-test_success_after_always from phase always-after-startup was removed \
-from <Device-name>!
-
-test_success_after_always from phase always-after-startup was removed \
-from Enea Edge Management!
-
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-system-test-specification/swcomp.mk b/doc/book-enea-nfv-access-system-test-specification/swcomp.mk
deleted file mode 100755
index 6e08a56..0000000
--- a/doc/book-enea-nfv-access-system-test-specification/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-system-test-specification
-BOOKDESC_$(BOOKPACKAGES) := "Enea Edge $(PROD_VER) System Test Specification"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-telemetry-open-source/doc/README b/doc/book-enea-nfv-access-telemetry-open-source/doc/README
deleted file mode 100644
index 1077acb..0000000
--- a/doc/book-enea-nfv-access-telemetry-open-source/doc/README
+++ /dev/null
@@ -1,4 +0,0 @@
-The licenses.xml in the git repository of Enea NFV Access Open Source Report
-is the frozen version belonging to the last official release of Enea NFV Access.
-The contents must be generated from the release script to obtain the latest
-lists of packages and licenses.
diff --git a/doc/book-enea-nfv-access-telemetry-open-source/doc/about.xml b/doc/book-enea-nfv-access-telemetry-open-source/doc/about.xml
deleted file mode 100644
index 5366626..0000000
--- a/doc/book-enea-nfv-access-telemetry-open-source/doc/about.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- About this Report
-
- This document contains the open source and license information
- pertaining to telemetry packages provided with Enea Edge .
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-telemetry-open-source/doc/book.xml b/doc/book-enea-nfv-access-telemetry-open-source/doc/book.xml
deleted file mode 100644
index c671fd7..0000000
--- a/doc/book-enea-nfv-access-telemetry-open-source/doc/book.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-]>
-
- Enea Edge Telemetry Open Source Report
- Release Version
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-telemetry-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-telemetry-open-source/doc/licenses.xml
deleted file mode 100644
index 3cffaae..0000000
--- a/doc/book-enea-nfv-access-telemetry-open-source/doc/licenses.xml
+++ /dev/null
@@ -1,290 +0,0 @@
-
-
-
- Packages and Licenses
-
-
- Packages
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Package Name
- Version
- Description
- License
-
-
-
-
-
-
-
- InfluxDB
- 1.3.7
- InfluxDB database for Telemetry
- MIT License
-
-
-
- Grafana
- 4.6.3
- Analytics and interactive visualization web application
- Apache License 2.0
-
-
-
-
-
-
-
-
- Open Source Licenses
-
-
- InfluxDB
-
- MIT License
-
- Copyright (c) 2018 InfluxData
-
- Permission is hereby granted, free of charge, to any person obtaining a copy
- of this software and associated documentation files (the "Software"), to deal
- in the Software without restriction, including without limitation the rights
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
- copies of the Software, and to permit persons to whom the Software is
- furnished to do so, subject to the following conditions:
-
- The above copyright notice and this permission notice shall be included in all
- copies or substantial portions of the Software.
-
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
- SOFTWARE.
-
-
-
- Grafana
-
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright 2015 Grafana Labs
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
diff --git a/doc/book-enea-nfv-access-telemetry-open-source/swcomp.mk b/doc/book-enea-nfv-access-telemetry-open-source/swcomp.mk
deleted file mode 100644
index 332d0c8..0000000
--- a/doc/book-enea-nfv-access-telemetry-open-source/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-telemetry-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Telemetry Open Source Report"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-nfv-access-ucpem-open-source/doc/README b/doc/book-enea-nfv-access-ucpem-open-source/doc/README
deleted file mode 100644
index 1077acb..0000000
--- a/doc/book-enea-nfv-access-ucpem-open-source/doc/README
+++ /dev/null
@@ -1,4 +0,0 @@
-The licenses.xml in the git repository of Enea NFV Access Open Source Report
-is the frozen version belonging to the last official release of Enea NFV Access.
-The contents must be generated from the release script to obtain the latest
-lists of packages and licenses.
diff --git a/doc/book-enea-nfv-access-ucpem-open-source/doc/about.xml b/doc/book-enea-nfv-access-ucpem-open-source/doc/about.xml
deleted file mode 100644
index 05cea19..0000000
--- a/doc/book-enea-nfv-access-ucpem-open-source/doc/about.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- About this Report
-
- This document contains the open source and license information
- pertaining to packages provided with Enea Edge .
-
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-ucpem-open-source/doc/book.xml b/doc/book-enea-nfv-access-ucpem-open-source/doc/book.xml
deleted file mode 100644
index 7401818..0000000
--- a/doc/book-enea-nfv-access-ucpem-open-source/doc/book.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-]>
-
- Enea Edge Management Open Source Report
- Release Version
-
-
-
-
-
-
diff --git a/doc/book-enea-nfv-access-ucpem-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-ucpem-open-source/doc/licenses.xml
deleted file mode 100644
index 92b4729..0000000
--- a/doc/book-enea-nfv-access-ucpem-open-source/doc/licenses.xml
+++ /dev/null
@@ -1,5872 +0,0 @@
-
-
-
- Packages and Licenses
-
-
- Packages
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Package Name
- Version
- Description
- License
-
-
-
-
-
-
-
- 7-zip
-
- Windows Zip/Unzip utility
- GNU LGPL + unRAR restriction + BSD 3-clause License
-
-
-
- ANTLR Runtime
- 4.5.2
- Java-based Parser-Generator
- BSD
-
-
-
- ASM
- 3.1
- Java bytecode manipulation library
- 3-Clause BSD License
-
-
-
- Apache FtpServer
- 1.0.3
- FTP server implementation
- Apache 2.0
-
-
-
- Apache SSHD
- 0.3.0
- SSH server implementation
- Apache 2.0
-
-
-
- Apache Tomcat
- 9.0.14
- Servlet Container
- Apache 2.0
-
-
-
-
- Apache HTTP Components
- 4.5.1
- HTTP client libraries
- Apache 2.0
-
-
-
- Apache HTTP Client
- 3.1
- HTTP commons libraries
- Apache 2.0
-
-
-
- Apache Log4j
- 2.0
- Logging libraries
- Apache 2.0
-
-
-
- Apache Commons Codec
- 1.9
- MD5 libraries
- Apache 2.0
-
-
-
- Application Icons
-
- Graphical Icon Images
- Freeware
-
-
-
- Atomikos TransactionsEssentials
- 4.0.6
- Transaction management
- Apache 2.0
-
-
-
- BeanShell
- 2.0
- http://www.beanshell.org
- Apache 2.0
-
-
-
- Browser-based SSH terminal
-
- shell_in_a_box.js,vt100.js
- Commercially licensed to ENEA
-
-
-
- Byte Buddy
-
- Byte Buddy is a code generation and manipulation library for creating and modifying Java classes.
- Apache 2.0
-
-
-
- ClassMate
-
- Library for introspecting types with full generic information including resolving of field and method types.
- Apache 2.0
-
-
-
- CGLib Nodep
-
- CGLib Nodep.
- Apache 2.0
-
-
-
- Commons Compress
- 1.5
- Compression libraries
- Apache 2.0
-
-
-
- Commons Lang
- 3.8.1
- Java Language utilities libraries
- Apache 2.0
-
-
-
- EasyMock
- 3.4
- Java framework that allows to create mocks in unit tests.
- Apache 2.0
-
-
-
- flot
- 0.8.3
- JS Graphing lib
- Flot license
-
-
-
- flot.tooltip
-
- tool tip plugin for flot
- MIT
-
-
-
- flot.axis.labels
-
- label plugin for flot
- MIT
-
-
-
- GNU Crypto
- 2.0.1
- Included with JRadius, this is used for Radius login and authentication.
- GPL with the "library exception"
- (GNU GPL V3 License)
-
-
-
-
- guava
- 18.0
- Java utilities
- Apache 2.0
-
-
-
- Google Web Toolkit
- 2.8.2
- RIA Web GUI Creation
- Apache 2.0
-
-
-
- GWT Maps
- 3.8.0-pre1
- GWT Library to Google Maps API
- Apache 2.0
-
-
-
- GWT Beans Binding
- 0.3
- Bean utilities for GWT
- GNU Lesser GPL
-
-
-
- gwt-dispatch
- 1.1.0
- gwt RPC enhancement
- BSD 3-Clause
-
-
-
- GWT GIN
- 1.0
- Google Injection - GIN and GUICE
- Apache 2.0
-
-
-
- GWT Graphics
- 0.9.7 (modified)
- Vector Graphics for GWT [MODIFIED BY ENEA]
- Apache 2.0
-
-
-
- GWT Incubator
- 2.1.0
- GWT Incubator Jar
- Apache 2.0
-
-
-
- GWT-Log
- 3.3.2
- Library for GWT Logging
- Apache 2.0
-
-
-
- GWT Voices
- 3.3.2
- GWT Support for playing MP3 files in the browser
- Apache 2.0
-
-
-
- GWT Upload
- 1.0.3
- GWT GUI support for File Uploading
- Apache 2.0
-
-
-
- Hazelcast
- 3.6.2
- In-Memory Data Grid
- Apache 2.0
-
-
-
- Hibernate
- 5.4.1
- Relational Persistence for Java
- GNU LesserGPL 2.1
-
-
-
- Javassist
- 3.24
- Java byte-code manipulation library
- Mozilla Public License Version 1.1 , GNU Lesser General Public License, version 2.1 , APACHE LICENSES (included in zip, free to distribute)
-
-
-
- Jackson
- 2.9.8
- JSON processor
- Apache 2.0
-
-
-
- JavaMail API
- 1.5.1
- Mail API used for sending mail
- Dual license consisting of the CDDL v1.1 and GPL v2 with
- CPE
-
-
-
- Jersey
- 2.30
- JAX-RS Reference implementation
- Eclipse Public License - v 2.0 , The GNU General Public License (GPL) Version 2, June
- 1991
-
-
-
- Jersey Filtering
- 2.30
- Jersey extension module providing support for Entity Data Filtering.
- Apache 2.0 ,BSD 2-clause ,EDL 1.0 ,EPL 2.0 ,MIT ,Public ,W3C
-
-
-
- Jersey Media JSON Jackson
- 2.30
- JJersey JSON Jackson (2.x) entity providers support module.
- Apache 2.0 ,EPL 2.0 ,GNU
-
-
-
- Jersey Media Moxy
- 2.30
- Jersey JSON entity providers support module based on EclipseLink MOXy.
- Apache 2.0 ,BSD 2-clause ,EDL 1.0 ,EPL 2.0 ,MIT ,Public ,W3C
-
-
-
- Jersey Media Multipart
- 2.30
- Jersey Multipart entity providers support module.
- Apache 2.0 ,BSD 2-clause ,EDL 1.0 ,EPL 2.0 ,MIT ,Public ,W3C
-
-
-
- JAX-WS
- 2.3.1
- Java Web Service Reference implementation
- Dual license consisting of the CDDL v1.1 and GPL v2
- with CPE
-
-
-
- Jakarta Commons Net
- 3.3
- Network Protocol client libraries
- Apache 2.0
-
-
-
- JAXB API
-
- JAXB API
- CDDL 1.1
-
-
-
- JTDS
- 1.2.5
- SQLServer Driver
- GNU Lesser GPL
-
-
-
- JSch
- 0.1.54
- Java SSH2 Implementation
- BSD-style
-
-
-
- Jython
- 2.7.1
- Python interpreter for Java
- Python Software Foundation
-
-
-
- JBoss Cache
- 3.2.5
- Tree-based memory cache
- GNU LesserGPL 2.1
-
-
-
- JDOM
- 1.1.1
- XML Document Parser
- Apache-style open source
-
-
-
- JRadius
- 1.1.4 (From Coova)
- A Radius client used to perform Radius authentication and accounting.
- GNU Lesser GPL
-
-
-
- JSOCKS
-
- Pure-Java implementation of SOCKS protocol
- GNU Lesser GPL v3
-
-
-
- jQuery
-
- JS lib
- MIT license
-
-
-
- MariaDB Java client
- 2.7.2
- Java client for MariaDB database and MySQL
- GNU LesserGPL 2.1
-
-
-
- Open CSV
- 2.2
- Used for CSV output utilities
- Apache 2.0
-
-
-
- OpenStack4j
- 3.0.3
- Java OpenStack client libraries
- Apache 2.0
-
-
-
- Objenesis
- 2.4
- Objenesis is a library dedicated to bypass the constructor when creating an object.
- Apache 2.0
-
-
-
- OSHI
- 3.13
- Native Operating System and Hardware Information libraries
- MIT License
-
-
-
- PostgreSQL Database
- 9.0.4-1
- Relational Database
- PostgreSQL license (similar to BSD or MIT)
-
-
-
- PostgreSQL JDBC Driver
- 9.0-801
- Java driver for PostgreSQL Relational Database
- PostgreSQL license (similar
- to BSD or MIT)
-
-
-
- PowerMock
- 1.7.1
- Java framework that allows to create mocks in unit tests for cases that are not possible with EasyMock.
- Apache 2.0
-
-
-
- Quartz
- 2.2.1
- Scheduling system
- Apache 2.0
-
-
-
- Rox
- 1.2
- XML RPC
- BSD-style
-
-
-
- SLF4J
- 1.7.25
- Logging framework
- SLF4J MIT License
-
-
-
- SNMP4J
- 2.1
- SNMP Client Library
- Apache 2.0
-
-
-
- SNMP4J-Agent
- 2.0.7
- SNMP Agent Library
- Apache 2.0
-
-
-
- Spring Framework
- 5.1.4
- Micro Container, Utilities
- Apache 2.0
-
-
-
- Syslog4j
- 0.9.46
- Syslog implementation in Java
- GNU Lesser GPL 2.1
-
-
-
- True License
- 1.29
- Licensing framework
- Apache 2.0
-
-
-
- UUID
- 3.1
- High-performance UUID generator
- MIT
-
-
-
- XMLBeans
- 2.5.0
- XML binding to Java types
- Apache 2.0
-
-
-
- YAJSW
- 12.14
- Service wrapper for Java applications
- Apache 2.0
-
-
-
-
-
-
-
-
- Open Source Licenses
-
-
- 7-Zip
-
-
-
- ~~~~~
- License for use and distribution
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
- 7-Zip Copyright (C) 1999-2012 Igor Pavlov.
-
- Licenses for files are:
-
- 1) 7z.dll: GNU LGPL + unRAR restriction
- 2) All other files: GNU LGPL
-
- The GNU LGPL + unRAR restriction means that you must follow both
- GNU LGPL rules and unRAR restriction rules.
-
-
- Note:
- You can use 7-Zip on any computer, including a computer in a commercial
- organization. You don't need to register or pay for 7-Zip.
-
-
- GNU LGPL information
- --------------------
-
- This library is free software; you can redistribute it and/or
- modify it under the terms of the GNU Lesser General Public
- License as published by the Free Software Foundation; either
- version 2.1 of the License, or (at your option) any later version.
-
- This library is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- Lesser General Public License for more details.
-
- You can receive a copy of the GNU Lesser General Public License from
- http://www.gnu.org/
-
-
- unRAR restriction
- -----------------
-
- The decompression engine for RAR archives was developed using source
- code of unRAR program.
- All copyrights to original unRAR code are owned by Alexander Roshal.
-
- The license for original unRAR code has the following restriction:
-
- The unRAR sources cannot be used to re-create the RAR compression algorithm,
- which is proprietary. Distribution of modified unRAR sources in separate form
- or as a part of other software is permitted, provided that it is clearly
- stated in the documentation and source comments that the code may
- not be used to develop a RAR (WinRAR) compatible archiver.
-
-
- --
- Igor Pavlov
-
-
-
-
- ANTLR 4 License
-
-[The BSD License] Copyright (c) 2012 Terence Parr and Sam Harwell All rights
-reserved. Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-Redistributions of source code must retain the above copyright notice, this
-list of conditions and the following disclaimer. Redistributions in binary form
-must reproduce the above copyright notice, this list of conditions and the
-following disclaimer in the documentation and/or other materials provided with
-the distribution. Neither the name of the author nor the names of its
-contributors may be used to endorse or promote products derived from this
-software without specific prior written permission. THIS SOFTWARE IS PROVIDED
-BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
-EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
-OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
- FLOT LICENSE
-
-
-
-
-Copyright (c) 2007-2014 IOLA and Ole Laursen
-
-Permission is hereby granted, free of charge, to any person
-obtaining a copy of this software and associated documentation
-files (the "Software"), to deal in the Software without
-restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following
-conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
-HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
-OTHER DEALINGS IN THE SOFTWARE.
-
-
-
-
- France Télécom
-
-
-Copyright (c) 2012 France Télécom
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. Neither the name of the copyright holders nor the names of its
- contributors may be used to endorse or promote products derived from
- this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
-LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
-THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
- Apache License
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
- GNU LESSER GENERAL PUBLIC LICENSE
-
- GNU LESSER GENERAL PUBLIC LICENSE
- Version 2.1, February 1999
-
- Copyright (C) 1991, 1999 Free Software Foundation, Inc.
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL. It also counts
- as the successor of the GNU Library Public License, version 2, hence
- the version number 2.1.]
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-Licenses are intended to guarantee your freedom to share and change
-free software--to make sure the software is free for all its users.
-
- This license, the Lesser General Public License, applies to some
-specially designated software packages--typically libraries--of the
-Free Software Foundation and other authors who decide to use it. You
-can use it too, but we suggest you first think carefully about whether
-this license or the ordinary General Public License is the better
-strategy to use in any particular case, based on the explanations below.
-
- When we speak of free software, we are referring to freedom of use,
-not price. Our General Public Licenses are designed to make sure that
-you have the freedom to distribute copies of free software (and charge
-for this service if you wish); that you receive source code or can get
-it if you want it; that you can change the software and use pieces of
-it in new free programs; and that you are informed that you can do
-these things.
-
- To protect your rights, we need to make restrictions that forbid
-distributors to deny you these rights or to ask you to surrender these
-rights. These restrictions translate to certain responsibilities for
-you if you distribute copies of the library or if you modify it.
-
- For example, if you distribute copies of the library, whether gratis
-or for a fee, you must give the recipients all the rights that we gave
-you. You must make sure that they, too, receive or can get the source
-code. If you link other code with the library, you must provide
-complete object files to the recipients, so that they can relink them
-with the library after making changes to the library and recompiling
-it. And you must show them these terms so they know their rights.
-
- We protect your rights with a two-step method: (1) we copyright the
-library, and (2) we offer you this license, which gives you legal
-permission to copy, distribute and/or modify the library.
-
- To protect each distributor, we want to make it very clear that
-there is no warranty for the free library. Also, if the library is
-modified by someone else and passed on, the recipients should know
-that what they have is not the original version, so that the original
-author's reputation will not be affected by problems that might be
-introduced by others.
-
-
- Finally, software patents pose a constant threat to the existence of
-any free program. We wish to make sure that a company cannot
-effectively restrict the users of a free program by obtaining a
-restrictive license from a patent holder. Therefore, we insist that
-any patent license obtained for a version of the library must be
-consistent with the full freedom of use specified in this license.
-
- Most GNU software, including some libraries, is covered by the
-ordinary GNU General Public License. This license, the GNU Lesser
-General Public License, applies to certain designated libraries, and
-is quite different from the ordinary General Public License. We use
-this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
- When a program is linked with a library, whether statically or using
-a shared library, the combination of the two is legally speaking a
-combined work, a derivative of the original library. The ordinary
-General Public License therefore permits such linking only if the
-entire combination fits its criteria of freedom. The Lesser General
-Public License permits more lax criteria for linking other code with
-the library.
-
- We call this license the "Lesser" General Public License because it
-does Less to protect the user's freedom than the ordinary General
-Public License. It also provides other free software developers Less
-of an advantage over competing non-free programs. These disadvantages
-are the reason we use the ordinary General Public License for many
-libraries. However, the Lesser license provides advantages in certain
-special circumstances.
-
- For example, on rare occasions, there may be a special need to
-encourage the widest possible use of a certain library, so that it becomes
-a de-facto standard. To achieve this, non-free programs must be
-allowed to use the library. A more frequent case is that a free
-library does the same job as widely used non-free libraries. In this
-case, there is little to gain by limiting the free library to free
-software only, so we use the Lesser General Public License.
-
- In other cases, permission to use a particular library in non-free
-programs enables a greater number of people to use a large body of
-free software. For example, permission to use the GNU C Library in
-non-free programs enables many more people to use the whole GNU
-operating system, as well as its variant, the GNU/Linux operating
-system.
-
- Although the Lesser General Public License is Less protective of the
-users' freedom, it does ensure that the user of a program that is
-linked with the Library has the freedom and the wherewithal to run
-that program using a modified version of the Library.
-
- The precise terms and conditions for copying, distribution and
-modification follow. Pay close attention to the difference between a
-"work based on the library" and a "work that uses the library". The
-former contains code derived from the library, whereas the latter must
-be combined with the library in order to run.
-
-
- GNU LESSER GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License Agreement applies to any software library or other
-program which contains a notice placed by the copyright holder or
-other authorized party saying it may be distributed under the terms of
-this Lesser General Public License (also called "this License").
-Each licensee is addressed as "you".
-
- A "library" means a collection of software functions and/or data
-prepared so as to be conveniently linked with application programs
-(which use some of those functions and data) to form executables.
-
- The "Library", below, refers to any such software library or work
-which has been distributed under these terms. A "work based on the
-Library" means either the Library or any derivative work under
-copyright law: that is to say, a work containing the Library or a
-portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is
-included without limitation in the term "modification".)
-
- "Source code" for a work means the preferred form of the work for
-making modifications to it. For a library, complete source code means
-all the source code for all modules it contains, plus any associated
-interface definition files, plus the scripts used to control compilation
-and installation of the library.
-
- Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running a program using the Library is not restricted, and output from
-such a program is covered only if its contents constitute a work based
-on the Library (independent of the use of the Library in a tool for
-writing it). Whether that is true depends on what the Library does
-and what the program that uses the Library does.
-
- 1. You may copy and distribute verbatim copies of the Library's
-complete source code as you receive it, in any medium, provided that
-you conspicuously and appropriately publish on each copy an
-appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any
-warranty; and distribute a copy of this License along with the
-Library.
-
- You may charge a fee for the physical act of transferring a copy,
-and you may at your option offer warranty protection in exchange for a
-fee.
-
-
- 2. You may modify your copy or copies of the Library or any portion
-of it, thus forming a work based on the Library, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) The modified work must itself be a software library.
-
- b) You must cause the files modified to carry prominent notices
- stating that you changed the files and the date of any change.
-
- c) You must cause the whole of the work to be licensed at no
- charge to all third parties under the terms of this License.
-
- d) If a facility in the modified Library refers to a function or a
- table of data to be supplied by an application program that uses
- the facility, other than as an argument passed when the facility
- is invoked, then you must make a good faith effort to ensure that,
- in the event an application does not supply such function or
- table, the facility still operates, and performs whatever part of
- its purpose remains meaningful.
-
- (For example, a function in a library to compute square roots has
- a purpose that is entirely well-defined independent of the
- application. Therefore, Subsection 2d requires that any
- application-supplied function or table used by this function must
- be optional: if the application does not supply it, the square
- root function must still compute square roots.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Library,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Library, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote
-it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library
-with the Library (or with a work based on the Library) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may opt to apply the terms of the ordinary GNU General Public
-License instead of this License to a given copy of the Library. To do
-this, you must alter all the notices that refer to this License, so
-that they refer to the ordinary GNU General Public License, version 2,
-instead of to this License. (If a newer version than version 2 of the
-ordinary GNU General Public License has appeared, then you can specify
-that version instead if you wish.) Do not make any other change in
-these notices.
-
-
- Once this change is made in a given copy, it is irreversible for
-that copy, so the ordinary GNU General Public License applies to all
-subsequent copies and derivative works made from that copy.
-
- This option is useful when you wish to copy part of the code of
-the Library into a program that is not a library.
-
- 4. You may copy and distribute the Library (or a portion or
-derivative of it, under Section 2) in object code or executable form
-under the terms of Sections 1 and 2 above provided that you accompany
-it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a
-medium customarily used for software interchange.
-
- If distribution of object code is made by offering access to copy
-from a designated place, then offering equivalent access to copy the
-source code from the same place satisfies the requirement to
-distribute the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 5. A program that contains no derivative of any portion of the
-Library, but is designed to work with the Library by being compiled or
-linked with it, is called a "work that uses the Library". Such a
-work, in isolation, is not a derivative work of the Library, and
-therefore falls outside the scope of this License.
-
- However, linking a "work that uses the Library" with the Library
-creates an executable that is a derivative of the Library (because it
-contains portions of the Library), rather than a "work that uses the
-library". The executable is therefore covered by this License.
-Section 6 states terms for distribution of such executables.
-
- When a "work that uses the Library" uses material from a header file
-that is part of the Library, the object code for the work may be a
-derivative work of the Library even though the source code is not.
-Whether this is true is especially significant if the work can be
-linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
- If such an object file uses only numerical parameters, data
-structure layouts and accessors, and small macros and small inline
-functions (ten lines or less in length), then the use of the object
-file is unrestricted, regardless of whether it is legally a derivative
-work. (Executables containing this object code plus portions of the
-Library will still fall under Section 6.)
-
- Otherwise, if the work is a derivative of the Library, you may
-distribute the object code for the work under the terms of Section 6.
-Any executables containing that work also fall under Section 6,
-whether or not they are linked directly with the Library itself.
-
-
- 6. As an exception to the Sections above, you may also combine or
-link a "work that uses the Library" with the Library to produce a
-work containing portions of the Library, and distribute that work
-under terms of your choice, provided that the terms permit
-modification of the work for the customer's own use and reverse
-engineering for debugging such modifications.
-
- You must give prominent notice with each copy of the work that the
-Library is used in it and that the Library and its use are covered by
-this License. You must supply a copy of this License. If the work
-during execution displays copyright notices, you must include the
-copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one
-of these things:
-
- a) Accompany the work with the complete corresponding
- machine-readable source code for the Library including whatever
- changes were used in the work (which must be distributed under
- Sections 1 and 2 above); and, if the work is an executable linked
- with the Library, with the complete machine-readable "work that
- uses the Library", as object code and/or source code, so that the
- user can modify the Library and then relink to produce a modified
- executable containing the modified Library. (It is understood
- that the user who changes the contents of definitions files in the
- Library will not necessarily be able to recompile the application
- to use the modified definitions.)
-
- b) Use a suitable shared library mechanism for linking with the
- Library. A suitable mechanism is one that (1) uses at run time a
- copy of the library already present on the user's computer system,
- rather than copying library functions into the executable, and (2)
- will operate properly with a modified version of the library, if
- the user installs one, as long as the modified version is
- interface-compatible with the version that the work was made with.
-
- c) Accompany the work with a written offer, valid for at
- least three years, to give the same user the materials
- specified in Subsection 6a, above, for a charge no more
- than the cost of performing this distribution.
-
- d) If distribution of the work is made by offering access to copy
- from a designated place, offer equivalent access to copy the above
- specified materials from the same place.
-
- e) Verify that the user has already received a copy of these
- materials or that you have already sent this user a copy.
-
- For an executable, the required form of the "work that uses the
-Library" must include any data and utility programs needed for
-reproducing the executable from it. However, as a special exception,
-the materials to be distributed need not include anything that is
-normally distributed (in either source or binary form) with the major
-components (compiler, kernel, and so on) of the operating system on
-which the executable runs, unless that component itself accompanies
-the executable.
-
- It may happen that this requirement contradicts the license
-restrictions of other proprietary libraries that do not normally
-accompany the operating system. Such a contradiction means you cannot
-use both them and the Library together in an executable that you
-distribute.
-
-
- 7. You may place library facilities that are a work based on the
-Library side-by-side in a single library together with other library
-facilities not covered by this License, and distribute such a combined
-library, provided that the separate distribution of the work based on
-the Library and of the other library facilities is otherwise
-permitted, and provided that you do these two things:
-
- a) Accompany the combined library with a copy of the same work
- based on the Library, uncombined with any other library
- facilities. This must be distributed under the terms of the
- Sections above.
-
- b) Give prominent notice with the combined library of the fact
- that part of it is a work based on the Library, and explaining
- where to find the accompanying uncombined form of the same work.
-
- 8. You may not copy, modify, sublicense, link with, or distribute
-the Library except as expressly provided under this License. Any
-attempt otherwise to copy, modify, sublicense, link with, or
-distribute the Library is void, and will automatically terminate your
-rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses
-terminated so long as such parties remain in full compliance.
-
- 9. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Library or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Library or works based on it.
-
- 10. Each time you redistribute the Library (or any work based on the
-Library), the recipient automatically receives a license from the
-original licensor to copy, distribute, link with or modify the Library
-subject to these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties with
-this License.
-
-
- 11. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Library at all. For example, if a patent
-license would not permit royalty-free redistribution of the Library by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any
-particular circumstance, the balance of the section is intended to apply,
-and the section as a whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 12. If the distribution and/or use of the Library is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Library under this License may add
-an explicit geographical distribution limitation excluding those countries,
-so that distribution is permitted only in or among countries not thus
-excluded. In such case, this License incorporates the limitation as if
-written in the body of this License.
-
- 13. The Free Software Foundation may publish revised and/or new
-versions of the Lesser General Public License from time to time.
-Such new versions will be similar in spirit to the present version,
-but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library
-specifies a version number of this License which applies to it and
-"any later version", you have the option of following the terms and
-conditions either of that version or of any later version published by
-the Free Software Foundation. If the Library does not specify a
-license version number, you may choose any version ever published by
-the Free Software Foundation.
-
-
- 14. If you wish to incorporate parts of the Library into other free
-programs whose distribution conditions are incompatible with these,
-write to the author to ask for permission. For software which is
-copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this. Our
-decision will be guided by the two goals of preserving the free status
-of all derivatives of our free software and of promoting the sharing
-and reuse of software generally.
-
- NO WARRANTY
-
- 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
-WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
-OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
-KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
-LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
-THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
-WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
-AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
-FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
-RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
-FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
-SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGES.
-
- END OF TERMS AND CONDITIONS
-
-
- How to Apply These Terms to Your New Libraries
-
- If you develop a new library, and you want it to be of the greatest
-possible use to the public, we recommend making it free software that
-everyone can redistribute and change. You can do so by permitting
-redistribution under these terms (or, alternatively, under the terms of the
-ordinary General Public License).
-
- To apply these terms, attach the following notices to the library. 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 the
-"copyright" line and a pointer to where the full notice is found.
-
- <one line to give the library's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This library is free software; you can redistribute it and/or
- modify it under the terms of the GNU Lesser General Public
- License as published by the Free Software Foundation; either
- version 2.1 of the License, or (at your option) any later version.
-
- This library is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- Lesser General Public License for more details.
-
- You should have received a copy of the GNU Lesser General Public
- License along with this library; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
-
-Also add information on how to contact you by electronic and paper mail.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the library, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the
- library `Frob' (a library for tweaking knobs) written by James Random Hacker.
-
- <signature of Ty Coon>, 1 April 1990
- Ty Coon, President of Vice
-
-That's all there is to it!
-
-
-
- GNU LESSER GENERAL PUBLIC LICENSE
-
-
- Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-
- This version of the GNU Lesser General Public License incorporates
-the terms and conditions of version 3 of the GNU General Public
-License, supplemented by the additional permissions listed below.
-
- 0. Additional Definitions.
-
- As used herein, "this License" refers to version 3 of the GNU Lesser
-General Public License, and the "GNU GPL" refers to version 3 of the GNU
-General Public License.
-
- "The Library" refers to a covered work governed by this License,
-other than an Application or a Combined Work as defined below.
-
- An "Application" is any work that makes use of an interface provided
-by the Library, but which is not otherwise based on the Library.
-Defining a subclass of a class defined by the Library is deemed a mode
-of using an interface provided by the Library.
-
- A "Combined Work" is a work produced by combining or linking an
-Application with the Library. The particular version of the Library
-with which the Combined Work was made is also called the "Linked
-Version".
-
- The "Minimal Corresponding Source" for a Combined Work means the
-Corresponding Source for the Combined Work, excluding any source code
-for portions of the Combined Work that, considered in isolation, are
-based on the Application, and not on the Linked Version.
-
- The "Corresponding Application Code" for a Combined Work means the
-object code and/or source code for the Application, including any data
-and utility programs needed for reproducing the Combined Work from the
-Application, but excluding the System Libraries of the Combined Work.
-
- 1. Exception to Section 3 of the GNU GPL.
-
- You may convey a covered work under sections 3 and 4 of this License
-without being bound by section 3 of the GNU GPL.
-
- 2. Conveying Modified Versions.
-
- If you modify a copy of the Library, and, in your modifications, a
-facility refers to a function or data to be supplied by an Application
-that uses the facility (other than as an argument passed when the
-facility is invoked), then you may convey a copy of the modified
-version:
-
- a) under this License, provided that you make a good faith effort to
- ensure that, in the event an Application does not supply the
- function or data, the facility still operates, and performs
- whatever part of its purpose remains meaningful, or
-
- b) under the GNU GPL, with none of the additional permissions of
- this License applicable to that copy.
-
- 3. Object Code Incorporating Material from Library Header Files.
-
- The object code form of an Application may incorporate material from
-a header file that is part of the Library. You may convey such object
-code under terms of your choice, provided that, if the incorporated
-material is not limited to numerical parameters, data structure
-layouts and accessors, or small macros, inline functions and templates
-(ten or fewer lines in length), you do both of the following:
-
- a) Give prominent notice with each copy of the object code that the
- Library is used in it and that the Library and its use are
- covered by this License.
-
- b) Accompany the object code with a copy of the GNU GPL and this license
- document.
-
- 4. Combined Works.
-
- You may convey a Combined Work under terms of your choice that,
-taken together, effectively do not restrict modification of the
-portions of the Library contained in the Combined Work and reverse
-engineering for debugging such modifications, if you also do each of
-the following:
-
- a) Give prominent notice with each copy of the Combined Work that
- the Library is used in it and that the Library and its use are
- covered by this License.
-
- b) Accompany the Combined Work with a copy of the GNU GPL and this license
- document.
-
- c) For a Combined Work that displays copyright notices during
- execution, include the copyright notice for the Library among
- these notices, as well as a reference directing the user to the
- copies of the GNU GPL and this license document.
-
- d) Do one of the following:
-
- 0) Convey the Minimal Corresponding Source under the terms of this
- License, and the Corresponding Application Code in a form
- suitable for, and under terms that permit, the user to
- recombine or relink the Application with a modified version of
- the Linked Version to produce a modified Combined Work, in the
- manner specified by section 6 of the GNU GPL for conveying
- Corresponding Source.
-
- 1) Use a suitable shared library mechanism for linking with the
- Library. A suitable mechanism is one that (a) uses at run time
- a copy of the Library already present on the user's computer
- system, and (b) will operate properly with a modified version
- of the Library that is interface-compatible with the Linked
- Version.
-
- e) Provide Installation Information, but only if you would otherwise
- be required to provide such information under section 6 of the
- GNU GPL, and only to the extent that such information is
- necessary to install and execute a modified version of the
- Combined Work produced by recombining or relinking the
- Application with a modified version of the Linked Version. (If
- you use option 4d0, the Installation Information must accompany
- the Minimal Corresponding Source and Corresponding Application
- Code. If you use option 4d1, you must provide the Installation
- Information in the manner specified by section 6 of the GNU GPL
- for conveying Corresponding Source.)
-
- 5. Combined Libraries.
-
- You may place library facilities that are a work based on the
-Library side by side in a single library together with other library
-facilities that are not Applications and are not covered by this
-License, and convey such a combined library under terms of your
-choice, if you do both of the following:
-
- a) Accompany the combined library with a copy of the same work based
- on the Library, uncombined with any other library facilities,
- conveyed under the terms of this License.
-
- b) Give prominent notice with the combined library that part of it
- is a work based on the Library, and explaining where to find the
- accompanying uncombined form of the same work.
-
- 6. Revised Versions of the GNU Lesser General Public License.
-
- The Free Software Foundation may publish revised and/or new versions
-of the GNU Lesser General Public License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns.
-
- Each version is given a distinguishing version number. If the
-Library as you received it specifies that a certain numbered version
-of the GNU Lesser General Public License "or any later version"
-applies to it, you have the option of following the terms and
-conditions either of that published version or of any later version
-published by the Free Software Foundation. If the Library as you
-received it does not specify a version number of the GNU Lesser
-General Public License, you may choose any version of the GNU Lesser
-General Public License ever published by the Free Software Foundation.
-
- If the Library as you received it specifies that a proxy can decide
-whether future versions of the GNU Lesser General Public License shall
-apply, that proxy's public statement of acceptance of any version is
-permanent authorization for you to choose that version for the
-Library.
-
-
-
- jTDS
-
-
-License
-jTDS is Free Software. jTDS is made available under the terms of the
-GNU Lesser General Public License. The LGPL is sufficiently flexible to allow
-the use of jTDS in both open source and commercial projects. Using jTDS is
-considered to be dynamic linking; hence our interpretation of the LGPL is that
-the use of the unmodified jTDS source or binary does not affect the license of
-your application code.
-
-If you modify jTDS and redistribute your modifications, the LGPL applies,
-basically meaning that you'll have to make the modified version publicly
-available under the LGPL license too. This ensures that all users of the
-software have access to all future improvements.
-
-jTDS was initially based on software released under a BSD license by CDS
-Networks, Inc. and/or Craig Spannring, the author of the original FreeTDS JDBC
-driver from which jTDS is derived. Between releases 0.8.1 and 0.9 jTDS was
-completely rewritten so the original BSD license no longer applies.
-
-
-
- JSch
-
-JSch 0.0.* was released under the GNU LGPL license. Later, we have switched
-over to a BSD-style license.
-
-------------------------------------------------------------------------------
-Copyright (c) 2002-2015 Atsuhiko Yamanaka, JCraft,Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
- 1. Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the distribution.
-
- 3. The names of the authors may not be used to endorse or promote products
- derived from this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
-FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JCRAFT,
-INC. OR ANY CONTRIBUTORS TO THIS SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
-OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
- Jython
-
-
-The Jython License
-
-A. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING JYTHON
-
-PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
-
-1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"),
-and the Individual or Organization ("Licensee") accessing and otherwise using
-this software ("Jython") in source or binary form and its associated
-documentation.
-
-2. Subject to the terms and conditions of this License Agreement, PSF hereby
-grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
-analyze, test, perform and/or display publicly, prepare derivative works,
-distribute, and otherwise use Jython alone or in any derivative version,
-provided, however, that PSF's License Agreement and PSF's notice of copyright,
-i.e., "Copyright (c) 2007 Python Software Foundation; All Rights Reserved" are
-retained in Jython alone or in any derivative version prepared by Licensee.
-
-3. In the event Licensee prepares a derivative work that is based on or
-incorporates Jython or any part thereof, and wants to make the derivative work
-available to others as provided herein, then Licensee hereby agrees to include
-in any such work a brief summary of the changes made to Jython.
-
-4. PSF is making Jython available to Licensee on an "AS IS" basis. PSF MAKES NO
-REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT
-LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF
-MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF JYTHON
-WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.
-
-5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF JYTHON FOR ANY
-INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING,
-DISTRIBUTING, OR OTHERWISE USING JYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF
-ADVISED OF THE POSSIBILITY THEREOF.
-
-6. This License Agreement will automatically terminate upon a material breach
-of its terms and conditions.
-
-7. Nothing in this License Agreement shall be deemed to create any relationship
-of agency, partnership, or joint venture between PSF and Licensee. This License
-Agreement does not grant permission to use PSF trademarks or trade name in a
-trademark sense to endorse or promote products or services of Licensee, or any
-third party.
-
-8. By copying, installing or otherwise using Jython, Licensee agrees to be
-bound by the terms and conditions of this License Agreement.
-
-Jython 2.0, 2.1 License
-
-Copyright (c) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Jython Developers
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-Redistributions of source code must retain the above copyright notice, this
-list of conditions and the following disclaimer. Redistributions in binary form
-must reproduce the above copyright notice, this list of conditions and the
-following disclaimer in the documentation and/or other materials provided with
-the distribution. Neither the name of the Jython Developers nor the names of
-its contributors may be used to endorse or promote products derived from this
-software without specific prior written permission. THIS SOFTWARE IS PROVIDED
-BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS'' AND ANY EXPRESS OR IMPLIED
-WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
-EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
-OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
- Open Source Initiative OSI - The BSD 3-Clause License
-
-
-<b> Open Source Initiative OSI - The BSD 3-Clause License </b>
-
-Copyright (c) <YEAR>, <OWNER> All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-- Redistributions of source code must retain the above copyright notice, this
-list of conditions and the following disclaimer. - Redistributions in binary
-form must reproduce the above copyright notice, this list of conditions and the
-following disclaimer in the documentation and/or other materials provided with
-the distribution. - Neither the name of the <ORGANIZATION> nor the names
-of its contributors may be used to endorse or promote products derived from
-this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
- MOZILLA PUBLIC LICENSE
-
-
-MOZILLA PUBLIC LICENSE Version 1.1 1. Definitions.
-
-1.0.1. "Commercial Use" means distribution or otherwise making the Covered Code
-available to a third party. 1.1. ''Contributor'' means each entity that creates
-or contributes to the creation of Modifications.
-
-1.2. ''Contributor Version'' means the combination of the Original Code, prior
-Modifications used by a Contributor, and the Modifications made by that
-particular Contributor.
-
-1.3. ''Covered Code'' means the Original Code or Modifications or the
-combination of the Original Code and Modifications, in each case including
-portions thereof.
-
-1.4. ''Electronic Distribution Mechanism'' means a mechanism generally accepted
-in the software development community for the electronic transfer of data.
-
-1.5. ''Executable'' means Covered Code in any form other than Source Code.
-
-1.6. ''Initial Developer'' means the individual or entity identified as the
-Initial Developer in the Source Code notice required by Exhibit A.
-
-1.7. ''Larger Work'' means a work which combines Covered Code or portions
-thereof with code not governed by the terms of this License.
-
-1.8. ''License'' means this document.
-
-1.8.1. "Licensable" means having the right to grant, to the maximum extent
-possible, whether at the time of the initial grant or subsequently acquired,
-any and all of the rights conveyed herein.
-
-1.9. ''Modifications'' means any addition to or deletion from the substance or
-structure of either the Original Code or any previous Modifications. When
-Covered Code is released as a series of files, a Modification is:
-
-A. Any addition to or deletion from the contents of a file containing Original
-Code or previous Modifications. B. Any new file that contains any part of the
-Original Code or previous Modifications.
-
-
-
-1.10. ''Original Code'' means Source Code of computer software code which is
-described in the Source Code notice required by Exhibit A as Original Code, and
-which, at the time of its release under this License is not already Covered
-Code governed by this License. 1.10.1. "Patent Claims" means any patent claim(
-s), now owned or hereafter acquired, including without limitation, method,
-process, and apparatus claims, in any patent Licensable by grantor.
-
-1.11. ''Source Code'' means the preferred form of the Covered Code for making
-modifications to it, including all modules it contains, plus any associated
-interface definition files, scripts used to control compilation and
-installation of an Executable, or source code differential comparisons against
-either the Original Code or another well known, available Covered Code of the
-Contributor's choice. The Source Code can be in a compressed or archival form,
-provided the appropriate decompression or de-archiving software is widely
-available for no charge.
-
-1.12. "You'' (or "Your") means an individual or a legal entity exercising
-rights under, and complying with all of the terms of, this License or a future
-version of this License issued under Section 6.1. For legal entities, "You''
-includes any entity which controls, is controlled by, or is under common
-control with You. For purposes of this definition, "control'' means (a) the
-power, direct or indirect, to cause the direction or management of such entity,
-whether by contract or otherwise, or (b) ownership of more than fifty percent (
-50%) of the outstanding shares or beneficial ownership of such entity.
-
-2. Source Code License. 2.1. The Initial Developer Grant. The Initial Developer
-hereby grants You a world-wide, royalty-free, non-exclusive license, subject to
-third party intellectual property claims: (a) under intellectual property
-rights (other than patent or trademark) Licensable by Initial Developer to use,
-reproduce, modify, display, perform, sublicense and distribute the Original
-Code (or portions thereof) with or without Modifications, and/or as part of a
-Larger Work; and (b) under Patents Claims infringed by the making, using or
-selling of Original Code, to make, have made, use, practice, sell, and offer
-for sale, and/or otherwise dispose of the Original Code (or portions thereof). (
-c) the licenses granted in this Section 2.1(a) and (b) are effective on the
-date Initial Developer first distributes Original Code under the terms of this
-License. (d) Notwithstanding Section 2.1(b) above, no patent license is
-granted: 1) for code that You delete from the Original Code; 2) separate from
-the Original Code; or 3) for infringements caused by: i) the modification of
-the Original Code or ii) the combination of the Original Code with other
-software or devices.
-
-
-
-2.2. Contributor Grant. Subject to third party intellectual property claims,
-each Contributor hereby grants You a world-wide, royalty-free, non-exclusive
-license
-
-(a) under intellectual property rights (other than patent or trademark)
-Licensable by Contributor, to use, reproduce, modify, display, perform,
-sublicense and distribute the Modifications created by such Contributor (or
-portions thereof) either on an unmodified basis, with other Modifications, as
-Covered Code and/or as part of a Larger Work; and (b) under Patent Claims
-infringed by the making, using, or selling of Modifications made by that
-Contributor either alone and/or in combination with its Contributor Version (or
-portions of such combination), to make, use, sell, offer for sale, have made,
-and/or otherwise dispose of: 1) Modifications made by that Contributor (or
-portions thereof); and 2) the combination of Modifications made by that
-Contributor with its Contributor Version (or portions of such combination). (c)
-the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
-Contributor first makes Commercial Use of the Covered Code. (d) Notwithstanding
-Section 2.2(b) above, no patent license is granted: 1) for any code that
-Contributor has deleted from the Contributor Version; 2) separate from the
-Contributor Version; 3) for infringements caused by: i) third party
-modifications of Contributor Version or ii) the combination of Modifications
-made by that Contributor with other software (except as part of the
-Contributor Version) or other devices; or 4) under Patent Claims infringed by
-Covered Code in the absence of Modifications made by that Contributor.
-
-
-
-3. Distribution Obligations.
-
-3.1. Application of License. The Modifications which You create or to which You
-contribute are governed by the terms of this License, including without
-limitation Section 2.2. The Source Code version of Covered Code may be
-distributed only under the terms of this License or a future version of this
-License released under Section 6.1, and You must include a copy of this License
-with every copy of the Source Code You distribute. You may not offer or impose
-any terms on any Source Code version that alters or restricts the applicable
-version of this License or the recipients' rights hereunder. However, You may
-include an additional document offering the additional rights described in
-Section 3.5. 3.2. Availability of Source Code. Any Modification which You
-create or to which You contribute must be made available in Source Code form
-under the terms of this License either on the same media as an Executable
-version or via an accepted Electronic Distribution Mechanism to anyone to whom
-you made an Executable version available; and if made available via Electronic
-Distribution Mechanism, must remain available for at least twelve (12) months
-after the date it initially became available, or at least six (6) months after
-a subsequent version of that particular Modification has been made available to
-such recipients. You are responsible for ensuring that the Source Code version
-remains available even if the Electronic Distribution Mechanism is maintained
-by a third party.
-
-3.3. Description of Modifications. You must cause all Covered Code to which You
-contribute to contain a file documenting the changes You made to create that
-Covered Code and the date of any change. You must include a prominent statement
-that the Modification is derived, directly or indirectly, from Original Code
-provided by the Initial Developer and including the name of the Initial
-Developer in (a) the Source Code, and (b) in any notice in an Executable
-version or related documentation in which You describe the origin or ownership
-of the Covered Code.
-
-3.4. Intellectual Property Matters
-
-(a) Third Party Claims. If Contributor has knowledge that a license under a
-third party's intellectual property rights is required to exercise the rights
-granted by such Contributor under Sections 2.1 or 2.2, Contributor must include
-a text file with the Source Code distribution titled "LEGAL'' which describes
-the claim and the party making the claim in sufficient detail that a recipient
-will know whom to contact. If Contributor obtains such knowledge after the
-Modification is made available as described in Section 3.2, Contributor shall
-promptly modify the LEGAL file in all copies Contributor makes available
-thereafter and shall take other steps (such as notifying appropriate mailing
-lists or newsgroups) reasonably calculated to inform those who received the
-Covered Code that new knowledge has been obtained. (b) Contributor APIs. If
-Contributor's Modifications include an application programming interface and
-Contributor has knowledge of patent licenses which are reasonably necessary to
-implement that API, Contributor must also include this information in the LEGAL
-file.
-
-(c) Representations. Contributor represents that, except as disclosed pursuant
-to Section 3.4(a) above, Contributor believes that Contributor's Modifications
-are Contributor's original creation(s) and/or Contributor has sufficient rights
-to grant the rights conveyed by this License.
-
-3.5. Required Notices. You must duplicate the notice in Exhibit A in each file
-of the Source Code. If it is not possible to put such notice in a particular
-Source Code file due to its structure, then You must include such notice in a
-location (such as a relevant directory) where a user would be likely to look
-for such a notice. If You created one or more Modification(s) You may add your
-name as a Contributor to the notice described in Exhibit A. You must also
-duplicate this License in any documentation for the Source Code where You
-describe recipients' rights or ownership rights relating to Covered Code. You
-may choose to offer, and to charge a fee for, warranty, support, indemnity or
-liability obligations to one or more recipients of Covered Code. However, You
-may do so only on Your own behalf, and not on behalf of the Initial Developer
-or any Contributor. You must make it absolutely clear than any such warranty,
-support, indemnity or liability obligation is offered by You alone, and You
-hereby agree to indemnify the Initial Developer and every Contributor for any
-liability incurred by the Initial Developer or such Contributor as a result of
-warranty, support, indemnity or liability terms You offer.
-
-3.6. Distribution of Executable Versions. You may distribute Covered Code in
-Executable form only if the requirements of Section 3.1-3.5 have been met for
-that Covered Code, and if You include a notice stating that the Source Code
-version of the Covered Code is available under the terms of this License,
-including a description of how and where You have fulfilled the obligations of
-Section 3.2. The notice must be conspicuously included in any notice in an
-Executable version, related documentation or collateral in which You describe
-recipients' rights relating to the Covered Code. You may distribute the
-Executable version of Covered Code or ownership rights under a license of Your
-choice, which may contain terms different from this License, provided that You
-are in compliance with the terms of this License and that the license for the
-Executable version does not attempt to limit or alter the recipient's rights in
-the Source Code version from the rights set forth in this License. If You
-distribute the Executable version under a different license You must make it
-absolutely clear that any terms which differ from this License are offered by
-You alone, not by the Initial Developer or any Contributor. You hereby agree to
-indemnify the Initial Developer and every Contributor for any liability
-incurred by the Initial Developer or such Contributor as a result of any such
-terms You offer.
-
-3.7. Larger Works. You may create a Larger Work by combining Covered Code with
-other code not governed by the terms of this License and distribute the Larger
-Work as a single product. In such a case, You must make sure the requirements
-of this License are fulfilled for the Covered Code.
-
-4. Inability to Comply Due to Statute or Regulation. If it is impossible for
-You to comply with any of the terms of this License with respect to some or all
-of the Covered Code due to statute, judicial order, or regulation then You
-must: (a) comply with the terms of this License to the maximum extent possible;
-and (b) describe the limitations and the code they affect. Such description
-must be included in the LEGAL file described in Section 3.4 and must be
-included with all distributions of the Source Code. Except to the extent
-prohibited by statute or regulation, such description must be sufficiently
-detailed for a recipient of ordinary skill to be able to understand it. 5.
-Application of this License. This License applies to code to which the Initial
-Developer has attached the notice in Exhibit A and to related Covered Code. 6.
-Versions of the License. 6.1. New Versions. Netscape Communications
-Corporation (''Netscape'') may publish revised and/or new versions of the
-License from time to time. Each version will be given a distinguishing version
-number. 6.2. Effect of New Versions. Once Covered Code has been published under
-a particular version of the License, You may always continue to use it under
-the terms of that version. You may also choose to use such Covered Code under
-the terms of any subsequent version of the License published by Netscape. No
-one other than Netscape has the right to modify the terms applicable to Covered
-Code created under this License.
-
-6.3. Derivative Works. If You create or use a modified version of this License (
-which you may only do in order to apply it to code which is not already Covered
-Code governed by this License), You must (a) rename Your license so that the
-phrases ''Mozilla'', ''MOZILLAPL'', ''MOZPL'', ''Netscape'', "MPL", ''NPL'' or
-any confusingly similar phrase do not appear in your license (except to note
-that your license differs from this License) and (b) otherwise make it clear
-that Your version of the license contains terms which differ from the Mozilla
-Public License and Netscape Public License. (Filling in the name of the Initial
-Developer, Original Code or Contributor in the notice described in Exhibit A
-shall not of themselves be deemed to be modifications of this License.)
-
-7. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN
-"AS IS'' BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
-INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
-DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE
-ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU.
-SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL
-DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING,
-REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART
-OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT
-UNDER THIS DISCLAIMER. 8. TERMINATION. 8.1. This License and the rights
-granted hereunder will terminate automatically if You fail to comply with terms
-herein and fail to cure such breach within 30 days of becoming aware of the
-breach. All sublicenses to the Covered Code which are properly granted shall
-survive any termination of this License. Provisions which, by their nature,
-must remain in effect beyond the termination of this License shall survive.
-8.2. If You initiate litigation by asserting a patent infringement claim (
-excluding declatory judgment actions) against Initial Developer or a
-Contributor (the Initial Developer or Contributor against whom You file such
-action is referred to as "Participant") alleging that:
-
-(a) such Participant's Contributor Version directly or indirectly infringes
-any patent, then any and all rights granted by such Participant to You under
-Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from
-Participant terminate prospectively, unless if within 60 days after receipt of
-notice You either: (i) agree in writing to pay Participant a mutually
-agreeable reasonable royalty for Your past and future use of Modifications made
-by such Participant, or (ii) withdraw Your litigation claim with respect to the
-Contributor Version against such Participant. If within 60 days of notice, a
-reasonable royalty and payment arrangement are not mutually agreed upon in
-writing by the parties or the litigation claim is not withdrawn, the rights
-granted by Participant to You under Sections 2.1 and/or 2.2 automatically
-terminate at the expiration of the 60 day notice period specified above.
-
-(b) any software, hardware, or device, other than such Participant's
-Contributor Version, directly or indirectly infringes any patent, then any
-rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are
-revoked effective as of the date You first made, used, sold, distributed, or
-had made, Modifications made by that Participant.
-
-8.3. If You assert a patent infringement claim against Participant alleging
-that such Participant's Contributor Version directly or indirectly infringes
-any patent where such claim is resolved (such as by license or settlement)
-prior to the initiation of patent infringement litigation, then the reasonable
-value of the licenses granted by such Participant under Sections 2.1 or 2.2
-shall be taken into account in determining the amount or value of any payment
-or license.
-
-8.4. In the event of termination under Sections 8.1 or 8.2 above, all end
-user license agreements (excluding distributors and resellers) which have been
-validly granted by You or any distributor hereunder prior to termination shall
-survive termination.
-
-9. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY,
-WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU THE
-INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
-OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY
-INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER
-INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE,
-COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
-LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH
-DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
-PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE
-LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
-LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
-LIMITATION MAY NOT APPLY TO YOU. 10. U.S. GOVERNMENT END USERS. The Covered
-Code is a ''commercial item,'' as that term is defined in 48 C.F.R. 2.101 (Oct.
-1995), consisting of ''commercial computer software'' and ''commercial computer
-software documentation,'' as such terms are used in 48 C.F.R. 12.212 (Sept.
-1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through
-227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with
-only those rights set forth herein. 11. MISCELLANEOUS. This License represents
-the complete agreement concerning subject matter hereof. If any provision of
-this License is held to be unenforceable, such provision shall be reformed only
-to the extent necessary to make it enforceable. This License shall be governed
-by California law provisions (except to the extent applicable law, if any,
-provides otherwise), excluding its conflict-of-law provisions. With respect to
-disputes in which at least one party is a citizen of, or an entity chartered or
-registered to do business in the United States of America, any litigation
-relating to this License shall be subject to the jurisdiction of the Federal
-Courts of the Northern District of California, with venue lying in Santa Clara
-County, California, with the losing party responsible for costs, including
-without limitation, court costs and reasonable attorneys' fees and expenses.
-The application of the United Nations Convention on Contracts for the
-International Sale of Goods is expressly excluded. Any law or regulation which
-provides that the language of a contract shall be construed against the drafter
-shall not apply to this License. 12. RESPONSIBILITY FOR CLAIMS. As between
-Initial Developer and the Contributors, each party is responsible for claims
-and damages arising, directly or indirectly, out of its utilization of rights
-under this License and You agree to work with Initial Developer and
-Contributors to distribute such responsibility on an equitable basis. Nothing
-herein is intended or shall be deemed to constitute any admission of liability.
-13. MULTIPLE-LICENSED CODE. Initial Developer may designate portions of the
-Covered Code as �Multiple-Licensed?. �Multiple-Licensed? means that the
-Initial Developer permits you to utilize portions of the Covered Code under
-Your choice of the MPL or the alternative licenses, if any, specified by the
-Initial Developer in the file described in Exhibit A.
-
-EXHIBIT A -Mozilla Public License.
-
-The contents of this file are subject to the Mozilla Public License Version
-1.1 (the "License"); you may not use this file except in compliance with the
-License. You may obtain a copy of the License at http://www.mozilla.org/MPL/
-Software distributed under the License is distributed on an "AS IS" basis,
-WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for
-the specific language governing rights and limitations under the License.
-
-The Original Code is Javassist.
-
-The Initial Developer of the Original Code is Shigeru Chiba. Portions created
-by the Initial Developer are Copyright (C) 1999-2010 Shigeru Chiba. All Rights
-Reserved.
-
-Contributor(s): ______________________________________.
-
-Alternatively, the contents of this file may be used under the terms of the GNU
-Lesser General Public License Version 2.1 or later (the "LGPL"), in which case
-the provisions of the LGPL are applicable instead of those above. If you wish
-to allow use of your version of this file only under the terms of the LGPL, and
-not to allow others to use your version of this file under the terms of the
-MPL, indicate your decision by deleting the provisions above and replace them
-with the notice and other provisions required by the LGPL. If you do not delete
-the provisions above, a recipient may use your version of this file under the
-terms of either the MPL or the LGPL.
-
-
-
- Sun Microsystems, Inc. ("Sun") ENTITLEMENT for SOFTWARE
-
-<b>Sun Microsystems, Inc. ("Sun") ENTITLEMENT for SOFTWARE
-</b>
-Licensee/Company: Entity receiving Software.
-
-Effective Date: Date of delivery of the Software to You.
-
-Software: JavaMail 1.4.3
-
-License Term: Perpetual (subject to termination under the SLA).
-
-Licensed Unit: Software Copy.
-
-Licensed unit Count: Unlimited.
-
-Permitted Uses:
-
-1. You may reproduce and use the Software for Your own Individual,
-Commercial and Research and Instructional Use only for the purposes of
-designing, developing, testing, and running Your applets and
-applications ("Programs").
-
-2. Subject to the terms and conditions of this Agreement and
-restrictions and exceptions set forth in the Software's documentation,
-You may reproduce and distribute portions of Software identified as a
-redistributable in the documentation (each a "Redistributable"),
-provided that You comply with the following (note that You may be
-entitled to reproduce and distribute other portions of the Software not
-defined in the documentation as a Redistributable under certain other
-licenses as described in the THIRDPARTYLICENSEREADME, if applicable):
-
-(a) You distribute Redistributable complete and unmodified and only
-bundled as part of Your Programs,
-
-(b) Your Programs add significant and primary functionality to the
-Redistributable,
-
-(c) You distribute Redistributable for the sole purpose of running Your
-Programs,
-
-(d) You do not distribute additional software intended to replace any
-component(s) of the Redistributable,
-
-(e) You do not remove or alter any proprietary legends or notices
-contained in or on the Redistributable.
-
-(f) You only distribute the Redistributable subject to a license
-agreement that protects Sun's interests consistent with the terms
-contained in this Agreement, and
-
-(g) You agree to defend and indemnify Sun and its licensors from and
-against any damages, costs, liabilities, settlement amounts and/or
-expenses (including attorneys' fees) incurred in connection with any
-claim, lawsuit or action by any third party that arises or results from
-the use or distribution of any and all Programs and/or
-Redistributable.
-
-3. Java Technology Restrictions. You may not create, modify, or change
-the behavior of, or authorize Your licensees to create, modify, or
-change the behavior of, classes, interfaces, or subpackages that are in
-any way identified as "java", "javax", "sun" or similar convention as
-specified by Sun in any naming convention designation.
-
-4. No Diagnostic, Maintenance, Repair or Technical Support Services.
-The scope of Your license does not include any right, express or
-implied, (i) to access, copy, distribute, display or use the Software
-to provide diagnostic, maintenance, repair or technical support
-services for Sun softwa re or Sun hardware on behalf of any third party
-for Your direct or indirect commercial gain or advantage, without Sun's
-prior written authorization, or (ii) for any third party to access,
-copy, distribute, display or use the Software to provide diagnostic,
-maintenance, repair or technical support services for Sun software or
-Sun hardware on Your behalf for such party's direct or indirect
-commercial gain or advantage, without Sun's prior written
-authorization. The limitations set forth in this paragraph apply to any
-and all error corrections, patches, updates, and upgrades to the
-Software You may receive, access, download or otherwise obtain from
-Sun.
-
-5. Records and Documentation. During the term of the SLA and
-Entitlement, and for a period of three (3) years thereafter, You agree
-to keep proper records and documentation of Your compliance with the
-SLA and Entitlement. Upon Sun's reasonable request, You will provide
-copies of such records and documentation to Sun for the purpose of
-confirming Your compliance with the terms and conditions of the SLA and
-Entitlement. This section will survive any termination of the SLA and
-Entitlement. You may terminate this SLA and Entitlement at any time by
-destroying all copies of the Software in which case the obligations set
-forth in Section 7 of the SLA shall apply.
-
-
-Sun Microsystems, Inc. ("Sun")
-SOFTWARE LICENSE AGREEMENT
-
-READ THE TERMS OF THIS AGREEMENT ("AGREEMENT") CAREFULLY BEFORE OPENING
-SOFTWARE MEDIA PACKAGE. BY OPENING SOFTWARE MEDIA PACKAGE, YOU AGREE TO
-THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCESSING SOFTWARE
-ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING
-THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE
-TO ALL OF THE TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE
-OF PURCHASE FOR A REFUND OR, IF SOFTWARE IS ACCESSED ELECTRONICALLY,
-SELECT THE "DECLINE" (OR "EXIT") BUTTON AT THE END OF THIS AGREEMENT.
-IF YOU HAVE SEPARATELY AGREED TO LICENSE TERMS ("MASTER TERMS") FOR
-YOUR LICENSE TO THIS SOFTWARE, THEN SECTIONS 1-6 OF THIS AGREEMENT
-("SUPPLEMENTAL LICENSE TERMS") SHALL SUPPLEMENT AND SUPERSEDE THE
-MASTER TERMS IN RELATION TO THIS SOFTWARE.
-
-1. Definitions.
-
-(a) "Entitlement" means the collective set of applicable documents
-authorized by Sun evidencing your obligation to pay associated fees (if
-any) for the license, associated Services, and the authorized scope of
-use of Software under this Agreement.
-
-(b) "Licensed Unit" means the unit of measure by which your use of
-Software and/or Service is licensed, as described in your Entitlement.
-
-(c) "Permitted Use" means the licensed Software use(s) authorized
-in this Agreement as specified in your Entitlement. The Permitted Use
-for any bundled Sun software not specified in your Entitlement will be
-evaluation use as provided in Section 3.
-
-(d) "Service" means the service(s) that Sun or its delegate will
-provide, if any, as selected in your Entitlement and as further
-described in the applicable service listings at
-www.sun.com/service/servicelist.
-
-(e) "Software" means the Sun software described in your
-Entitlement. Also, certain software may be included for evaluation use
-under Section 3.
-
-(f) "You" and "Your" means the individual or legal entity specified
-in the Entitlement, or for evaluation purposes, the entity performing
-the evaluation.
-
-2. License Grant and Entitlement.
-
-Subject to the terms of your Entitlement, Sun grants you a
-nonexclusive, nontransferable limited license to use Software for its
-Permitted Use for the license term. Your Entitlement will specify (a)
-Software licensed, (b) the Permitted Use, (c) the license term, and (d)
-the Licensed Units.
-
-Additionally, if your Entitlement includes Services, then it will also
-specify the (e) Service and (f) service term.
-
-If your rights to Software or Services are limited in duration and the
-date such rights begin is other than the purchase date, your
-Entitlement will provide that beginning date(s).
-
-The Entitlement may be delivered to you in various ways depending on
-the manner in which you obtain Software and Services, for example, the
-Entitlement may be provided in your receipt, invoice or your contract
-with Sun or authorized Sun reseller. It may also be in electronic
-format if you download Software.
-
-3. Permitted Use.
-
-As selected in your Entitlement, one or more of the following Permitted
-Uses will apply to your use of Software. Unless you have an Entitlement
-that expressly permits it, you may not use Software for any of the
-other Permitted Uses. If you don't have an Entitlement, or if your
-Entitlement doesn't cover additional software delivered to you, then
-such software is for your Evaluation Use.
-
-(a) Evaluation Use. You may evaluate Software internally for a period
-of 90 days from your first use.
-
-(b) Research and Instructional Use. You may use Software internally to
-design, develop and test, and also to provide instruction on such
-uses.
-
-(c) Individual Use. You may use Software internally for personal,
-individual use.
-
-(d) Commercial Use. You may use Software internally for your own
-commercial purposes.
-
-(e) Service Provider Use. You may make Software functionality
-accessible (but not by providing Software itself or through outsourcing
-services) to your end users in an extranet deployment, but not to your
-affiliated companies or to government agencies.
-
-4. Licensed Units.
-
-Your Permitted Use is limited to the number of Licensed Units stated in
-your Entitlement. If you require additional Licensed Units, you will
-need additional Entitlement(s).
-
-5. Restrictions.
-
-(a) The copies of Software provided to you under this Agreement are
-licensed, not sold, to you by Sun. Sun reserves all rights not
-expressly granted. (b) You may make a single archival copy of Software,
-but otherwise may not copy, modify, or distribute Software. However if
-the Sun documentation accompanying Software lists specific portions of
-Software, such as header files, class libraries, reference source code,
-and/or redistributable files, that may be handled differently, you may
-do so only as provided in the Sun documentation. (c) You may not rent,
-lease, lend or encumber Software. (d) Unless enforcement is prohibited
-by applicable law, you may not decompile, or reverse engineer Software.
-(e) The terms and conditions of this Agreement will apply to any
-Software updates, provided to you at Sun's discretion, that replace
-and/or supplement the original Software, unless such update contains a
-separate license. (f) You may not publish or provide the results of any
-benchmark or comparison tests run on Software to any third party
-without the prior written consent of Sun. (g) Software is confidential
-and copyrighted. (h) Unless otherwise specified, if Software is
-delivered with embedded or bundled software that enables functionality
-of Software, you may not use such software on a stand-alone basis or
-use any portion of such software to interoperate with any program(s)
-other than Software. (i) Software may contain programs that perform
-automated collection of system data and/or automated software updating
-services. System data collected through such programs may be used by
-Sun, its subcontractors, and its service delivery partners for the
-purpose of providing you with remote system services and/or improving
-Sun's software and systems. (j) Software is not designed, licensed or
-intended for use in the design, construction, operation or maintenance
-of any nuclear facility and Sun and its licensors disclaim any express
-or implied warranty of fitness for such uses. (k) No right, title or
-interest in or to any trademark, service mark, logo or trade name of
-Sun or its licensors is granted under this Agreement.
-
-6. Java Compatibility and Open Source.
-
-Software may contain Java technology. You may not create additional
-classes to, or modifications of, the Java technology, except under
-compatibility requirements available under a separate agreement
-available at www.java.net.
-
-Sun supports and benefits from the global community of open source
-developers, and thanks the community for its important contributions
-and open standards-based technology, which Sun has adopted into many of
-its products.
-
-Please note that portions of Software may be provided with notices and
-open source licenses from such communities and third parties that
-govern the use of those portions, and any licenses granted hereunder do
-not alter any rights and obligations you may have under such open
-source licenses, however, the disclaimer of warranty and limitation of
-liability provisions in this Agreement will apply to all Software in
-this distribution.
-
-7. Term and Termination.
-
-The license and service term are set forth in your Entitlement(s). Your
-rights under this Agreement will terminate immediately without notice
-from Sun if you materially breach it or take any action in derogation
-of Sun's and/or its licensors' rights to Software. Sun may terminate
-this Agreement should any Software become, or in Sun's reasonable
-opinion likely to become, the subject of a claim of intellectual
-property infringement or trade secret misappropriation. Upon
-termination, you will cease use of, and destroy, Software and confirm
-compliance in writing to Sun. Sections 1, 5, 6, 7, and 9-15 will
-survive termination of the Agreement.
-
-8. Limited Warranty.
-
-Sun warrants to you that for a period of 90 days from the date of
-purchase, as evidenced by a copy of the receipt, the media on which
-Software is furnished (if any) will be free of defects in materials and
-workmanship under normal use. Except for the foregoing, Software is
-provided "AS IS". Your exclusive remedy and Sun's entire liability
-under this limited warranty will be at Sun's option to replace Software
-media or refund the fee paid for Software. Some states do not allow
-limitations on certain implied warranties, so the above may not apply
-to you. This limited warranty gives you specific legal rights. You may
-have others, which vary from state to state.
-
-9. Disclaimer of Warranty.
-
-UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS,
-REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT
-ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO
-BE LEGALLY INVALID.
-
-10. Limitation of Liability.
-
-TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS
-LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR
-SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
-HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR
-RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS
-BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's
-liability to you, whether in contract, tort (including negligence), or
-otherwise, exceed the amount paid by you for Software under this
-Agreement. The foregoing limitations will apply even if the above
-stated warranty fails of its essential purpose. Some states do not
-allow the exclusion of incidental or consequential damages, so some of
-the terms above may not be applicable to you.
-
-11. Export Regulations.
-
-All Software, documents, technical data, and any other materials
-delivered under this Agreement are subject to U.S. export control laws
-and may be subject to export or import regulations in other countries.
-You agree to comply strictly with these laws and regulations and
-acknowledge that you have the responsibility to obtain any licenses to
-export, re-export, or import as may be required after delivery to you.
-
-12. U.S. Government Restricted Rights.
-
-If Software is being acquired by or on behalf of the U.S. Government or
-by a U.S. Government prime contractor or subcontractor (at any tier),
-then the Government's rights in Software and accompanying documentation
-will be only as set forth in this Agreement; this is in accordance with
-48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD)
-acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD
-acquisitions).
-
-13. Governing Law.
-
-Any action related to this Agreement will be governed by California law
-and controlling U.S. federal law. No choice of law rules of any
-jurisdiction will apply.
-
-14. Severability.
-
-If any provision of this Agreement is held to be unenforceable, this
-Agreement will remain in effect with the provision omitted, unless
-omission would frustrate the intent of the parties, in which case this
-Agreement will immediately terminate.
-
-15. Integration.
-
-This Agreement, including any terms contained in your Entitlement, is
-the entire agreement between you and Sun relating to its subject
-matter. It supersedes all prior or contemporaneous oral or written
-communications, proposals, representations and warranties and prevails
-over any conflicting or additional terms of any quote, order,
-acknowledgment, or other communication between the parties relating to
-its subject matter during the term of this Agreement. No modification
-of this Agreement will be binding, unless in writing and signed by an
-authorized representative of each party.
-
-Please contact Sun Microsystems, Inc. 4150 Network Circle, Santa Clara,
-California 95054 if you have questions.
-
-
-
- COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.1
-
-<b>COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.1
-</b>
-
- 1. Definitions.
-1.1. "Contributor" means each individual or entity that creates or contributes to the
-creation of Modifications.
-1.2. "Contributor Version" means the combination of the Original Software, prior
-Modifications used by a Contributor (if any), and the Modifications
-made by that particular Contributor.
-1.3. "Covered Software" means (a) the Original Software, or (b) Modifications, or (c)
-the combination of files containing Original Software with files
-containing Modifications, in each case including portions thereof.
-1.4. "Executable" means the Covered Software in any form other than Source Code.
-1.5. "Initial Developer" means the individual or entity that first makes Original
-Software available under this License.
-1.6. "Larger Work" means a work which combines Covered Software or portions thereof
-with code not governed by the terms of this License.
-1.7. "License" means this document.
-1.8. "Licensable" means having the right to grant, to the maximum extent possible,
-whether at the time of the initial grant or subsequently acquired,
-any and all of the rights conveyed herein.
-1.9. "Modifications" means the Source Code and Executable form of any of the following:
-A. Any file that results from an addition to, deletion from or modification of the
-contents of a file containing Original Software or previous
-Modifications;
-B. Any new file that contains any part of the Original Software or previous
-Modification; or
-C. Any new file that is contributed or otherwise made available under the terms
-of this License.
-1.10. "Original Software" means the Source Code and Executable form of computer
-software code that is originally released under this License.
-1.11. "Patent Claims" means any patent claim(s), now owned or hereafter acquired,
-including without limitation, method, process, and apparatus claims,
-in any patent Licensable by grantor.
-1.12. "Source Code" means (a) the common form of computer software code in which
-modifications are made and (b) associated documentation included
-in or with such code.
-1.13. "You" (or "Your") means an individual or a legal entity exercising rights under,
-and complying with all of the terms of, this License. For legal
-entities, "You" includes any entity which controls, is controlled by,
-or is under common control with You. For purposes of this definition,
-"control" means (a) the power, direct or indirect, to cause the
-direction or management of such entity, whether by contract or otherwise,
-or (b) ownership of more than fifty percent (50%) of the outstanding
-shares or beneficial ownership of such entity.
-2. License Grants.
-2.1. The Initial Developer Grant.
-Conditioned upon Your compliance with Section 3.1 below and subject to third party
-intellectual property claims, the Initial Developer hereby grants
-You a world-wide, royalty-free, non-exclusive license:
-(a) under intellectual property rights (other than patent or trademark) Licensable
-by Initial Developer, to use, reproduce, modify, display, perform,
-sublicense and distribute the Original Software (or portions thereof),
-with or without Modifications, and/or as part of a Larger Work; and
-(b) under Patent Claims infringed by the making, using or selling of Original Software,
-to make, have made, use, practice, sell, and offer for sale, and/or
-otherwise dispose of the Original Software (or portions thereof).
-(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date
-Initial Developer first distributes or otherwise makes the
-Original Software available to a third party under the terms
-of this License.
-(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code
-that You delete from the Original Software, or (2) for infringements
-caused by: (i) the modification of the Original Software, or (ii)
-the combination of the Original Software with other software or devices.
-2.2. Contributor Grant.
-Conditioned upon Your compliance with Section 3.1 below and subject to third
-party intellectual property claims, each Contributor hereby grants
-You a world-wide, royalty-free, non-exclusive license:
-(a) under intellectual property rights (other than patent or trademark)
-Licensable by Contributor to use, reproduce, modify, display, perform,
-sublicense and distribute the Modifications created by such Contributor
-(or portions thereof), either on an unmodified basis, with other
-Modifications, as Covered Software and/or as part of a Larger Work; and
-(b) under Patent Claims infringed by the making, using, or selling of Modifications
-made by that Contributor either alone and/or in combination with its
-Contributor Version (or portions of such combination), to make, use, sell,
-offer for sale, have made, and/or otherwise dispose of: (1) Modifications
-made by that Contributor (or portions thereof); and (2) the combination
-of Modifications made by that Contributor with its Contributor Version
-(or portions of such combination).
-(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
-Contributor first distributes or otherwise makes the Modifications
-available to a third party.
-(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for
-any code that Contributor has deleted from the Contributor Version; (2) for
-infringements caused by: (i) third party modifications of
-Contributor Version, or (ii) the combination of Modifications made by that
-Contributor with other software (except as part of the Contributor Version)
-or other devices; or (3) under Patent Claims infringed by Covered Software
-in the absence of Modifications made by that Contributor.
-3. Distribution Obligations.
-3.1. Availability of Source Code.
-Any Covered Software that You distribute or otherwise make available in Executable
-form must also be made available in Source Code form and that Source Code form
-must be distributed only under the terms of this License. You must include
-a copy of this License with every copy of the Source Code form of the
-Covered Software You distribute or otherwise make available. You must inform
-recipients of any such Covered Software in Executable form as to how they
-can obtain such Covered Software in Source Code form in a reasonable manner
-on or through a medium customarily used for software exchange.
-3.2. Modifications.
-The Modifications that You create or to which You contribute are governed by the
-terms of this License. You represent that You believe Your Modifications are Your
-original creation(s) and/or You have sufficient rights to grant the rights
-conveyed by this License.
-3.3. Required Notices.
-You must include a notice in each of Your Modifications that identifies You as the
-Contributor of the Modification. You may not remove or alter any copyright,
-patent or trademark notices contained within the Covered Software, or any
-notices of licensing or any descriptive text giving attribution to any
-Contributor or the Initial Developer.
-3.4. Application of Additional Terms.
-You may not offer or impose any terms on any Covered Software in Source Code form that
-alters or restricts the applicable version of this License or the recipients' rights
-hereunder. You may choose to offer, and to charge a fee for, warranty, support,
-indemnity or liability obligations to one or more recipients of Covered Software.
-However, you may do so only on Your own behalf, and not on behalf of the
-Initial Developer or any Contributor. You must make it absolutely clear
-that any such warranty, support, indemnity or liability obligation is
-offered by You alone, and You hereby agree to indemnify the Initial Developer
-and every Contributor for any liability incurred by the Initial Developer or
-such Contributor as a result of warranty, support, indemnity or liability
-terms You offer.
-3.5. Distribution of Executable Versions.
-You may distribute the Executable form of the Covered Software under the terms of this
-License or under the terms of a license of Your choice, which may contain terms
-different from this License, provided that You are in compliance with the
-terms of this License and that the license for the Executable form does
-not attempt to limit or alter the recipient's rights in the Source Code
-form from the rights set forth in this License. If You distribute the
-Covered Software in Executable form under a different license, You must make
-it absolutely clear that any terms which differ from this License are offered
-by You alone, not by the Initial Developer or Contributor. You hereby agree to
-indemnify the Initial Developer and every Contributor for any liability
-incurred by the Initial Developer or such Contributor as a result of any
-such terms You offer.
-3.6. Larger Works.
-You may create a Larger Work by combining Covered Software with other code not
-governed by the terms of this License and distribute the Larger Work as a single
-product. In such a case, You must make sure the requirements of this License
-are fulfilled for the Covered Software.
-4. Versions of the License.
-4.1. New Versions.
-Oracle is the initial license steward and may publish revised and/or new versions of
-this License from time to time. Each version will be given a distinguishing
-version number. Except as provided in Section 4.3, no one other than
-the license steward has the right to modify this License.
-4.2. Effect of New Versions.
-You may always continue to use, distribute or otherwise make the Covered Software
-available under the terms of the version of the License under which You originally
-received the Covered Software. If the Initial Developer includes a notice
-in the Original Software prohibiting it from being distributed or otherwise
-made available under any subsequent version of the License, You must
-distribute and make the Covered Software available under the terms of the
-version of the License under which You originally received the Covered Software.
-Otherwise, You may also choose to use, distribute or otherwise make the
-Covered Software available under the terms of any subsequent version of the
-License published by the license steward.
-4.3. Modified Versions.
-When You are an Initial Developer and You want to create a new license for Your
-Original Software, You may create and use a modified version of this License if You:
-(a) rename the license and remove any references to the name of the license steward
-(except to note that the license differs from this License); and (b) otherwise
-make it clear that the license contains terms which differ from this License.
-5. DISCLAIMER OF WARRANTY.
-COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
-WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE,
-FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY
-AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE
-PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR
-ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING,
-REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART
-OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT
-UNDER THIS DISCLAIMER.
-
-6. TERMINATION.
-6.1. This License and the rights granted hereunder will terminate automatically if
-You fail to comply with terms herein and fail to cure such breach within 30 days
-of becoming aware of the breach. Provisions which, by their nature, must remain in
-effect beyond the termination of this License shall survive.
-6.2. If You assert a patent infringement claim (excluding declaratory judgment actions)
-against Initial Developer or a Contributor (the Initial Developer or Contributor
-against whom You assert such claim is referred to as "Participant") alleging that the
-Participant Software (meaning the Contributor Version where the Participant
-is a Contributor or the Original Software where the Participant is the Initial
-Developer) directly or indirectly infringes any patent, then any and all rights
-granted directly or indirectly to You by such Participant, the Initial Developer
-(if the Initial Developer is not the Participant) and all Contributors under
-Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant
-terminate prospectively and automatically at the expiration of such 60 day notice
-period, unless if within such 60 day period You withdraw Your claim with respect
-to the Participant Software against such Participant either unilaterally
-or pursuant to a written agreement with Participant.
-6.3. If You assert a patent infringement claim against Participant alleging that the
-Participant Software directly or indirectly infringes any patent where
-such claim is resolved (such as by license or settlement) prior to the
-initiation of patent infringement litigation, then the reasonable value
-of the licenses granted by such Participant under Sections 2.1 or 2.2
-shall be taken into account in determining the amount or value of any
-payment or license.
-6.4. In the event of termination under Sections 6.1 or 6.2 above, all end user licenses
-that have been validly granted by You or any distributor hereunder prior
-to termination (excluding licenses granted to You by any distributor)
-shall survive termination.
-7. LIMITATION OF LIABILITY.
-UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE),
-CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER
-CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER
-OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT,
-SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING,
-WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER
-FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES,
-EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
-THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR
-PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE
-LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
-LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
-LIMITATION MAY NOT APPLY TO YOU.
-
-8. U.S. GOVERNMENT END USERS.
-The Covered Software is a "commercial item," as that term is defined in 48 C.F.R. 2.101
-(Oct. 1995), consisting of "commercial computer software" (as that term
-is defined at 48 C.F.R. § 252.227-7014(a)(1)) and "commercial computer
-software documentation" as such terms are used in 48 C.F.R. 12.212
-(Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1
-through 227.7202-4 (June 1995), all U.S. Government End Users acquire
-Covered Software with only those rights set forth herein. This U.S. Government
-Rights clause is in lieu of, and supersedes, any other FAR, DFAR, or other
-clause or provision that addresses Government rights in computer software
-under this License.
-
-9. MISCELLANEOUS.
-This License represents the complete agreement concerning subject matter hereof. If any
-provision of this License is held to be unenforceable, such provision
-shall be reformed only to the extent necessary to make it enforceable.
-This License shall be governed by the law of the jurisdiction specified
-in a notice contained within the Original Software (except to the extent
-applicable law, if any, provides otherwise), excluding such jurisdiction's
-conflict-of-law provisions. Any litigation relating to this License
-shall be subject to the jurisdiction of the courts located in the
-jurisdiction and venue specified in a notice contained within the
-Original Software, with the losing party responsible for costs,
-including, without limitation, court costs and reasonable attorneys'
-fees and expenses. The application of the United Nations Convention on
-Contracts for the International Sale of Goods is expressly excluded.
-Any law or regulation which provides that the language of a contract
-shall be construed against the drafter shall not apply to this License.
-You agree that You alone are responsible for compliance with the
-United States export administration regulations (and the export control
-laws and regulation of any other countries) when You use, distribute
-or otherwise make available any Covered Software.
-
-10. RESPONSIBILITY FOR CLAIMS.
-As between Initial Developer and the Contributors, each party is responsible for
-claims and damages arising, directly or indirectly, out of its
-utilization of rights under this License and You agree to work with
-Initial Developer and Contributors to distribute such responsibility
-on an equitable basis. Nothing herein is intended or shall be
-deemed to constitute any admission of liability.
-
-NOTICE PURSUANT TO SECTION 9 OF THE COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
-The code released under the CDDL shall be governed by the laws of the State of
-California (excluding conflict-of-law provisions). Any litigation relating to this
-License shall be subject to the jurisdiction of the Federal Courts of
-the Northern District of California and the state courts of the State
-of California, with venue lying in Santa Clara County, California.
-
-
-
-
-
-
-
-GNU GENERAL PUBLIC LICENSE
-
-
- <b> GNU GENERAL PUBLIC LICENSE</b>
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software
- interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and
-"any later version", you have the option of following the terms and
-conditions either of that version or of any later version published by
-the Free Software Foundation. If the Program does not specify a
-version number of this License, you may choose any version ever
-published by the Free Software Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
-WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
-OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY
-KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
-PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME
-THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
-WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
-AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
-FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
-RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
-FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF
-SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGES.
-
- 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
-the "copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
-
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) year name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
-
-
-
-"CLASSPATH" EXCEPTION TO THE GPL VERSION 2
-
-Certain source files distributed by Sun Microsystems, Inc. are subject
-to the following clarification and special exception to the GPL Version
-2, but only where Sun has expressly included in the particular source
-file's header the words
-
-"Sun designates this particular file as subject to the "Classpath"
-exception as provided by Sun in the License file that accompanied this
-code."
-
-Linking this library statically or dynamically with other modules is
-making a combined work based on this library. Thus, the terms and
-conditions of the GNU General Public License Version 2 cover the whole
-combination.
-
-As a special exception, the copyright holders of this library give you
-permission to link this library with independent modules to produce an
-executable, regardless of the license terms of these independent modules,
-and to copy and distribute the resulting executable under terms of your
-choice, provided that you also meet, for each linked independent module,
-the terms and conditions of the license of that module.? An independent
-module is a module which is not derived from or based on this library.?
-If you modify this library, you may extend this exception to your
-version of the library, but you are not obligated to do so.? If you do
-not wish to do so, delete this exception statement from your version.
-
-
-
-PostgreSQL Database Management System
-
-PostgreSQL Database Management System
-(formerly known as Postgres, then as Postgres95)
-
-Portions Copyright (c) 1996-2012, The PostgreSQL Global Development Group
-
-Portions Copyright (c) 1994, The Regents of the University of California
-
-Permission to use, copy, modify, and distribute this software and its documentation
- for any purpose, without fee,
-and without a written agreement is hereby granted, provided that the above copyright
- notice and this paragraph and
-the following two paragraphs appear in all copies.
-
-IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT,
- INDIRECT, SPECIAL, INCIDENTAL, OR
-CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE
- AND ITS DOCUMENTATION, EVEN
-IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING,
- BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED
- HEREUNDER IS ON AN "AS IS" BASIS, AND THE
-UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT,
- UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
-
-
-
-PostgreSQL JDBC driver license
-
- PostgreSQL JDBC driver license
-
-Copyright (c) 1997-2011, PostgreSQL Global Development Group
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-1. Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-3. Neither the name of the PostgreSQL Global Development Group nor the names
- of its contributors may be used to endorse or promote products derived
- from this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
-LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-
-
-JDOM license
-
- JDOM license
-
- Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin.
- All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions, and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions, and the disclaimer that follows
- these conditions in the documentation and/or other materials
- provided with the distribution.
-
- 3. The name "JDOM" must not be used to endorse or promote products
- derived from this software without prior written permission. For
- written permission, please contact <request_AT_jdom_DOT_org>.
-
- 4. Products derived from this software may not be called "JDOM", nor
- may "JDOM" appear in their name, without prior written permission
- from the JDOM Project Management <request_AT_jdom_DOT_org>.
-
- In addition, we request (but do not require) that you include in the
- end-user documentation provided with the redistribution and/or in the
- software itself an acknowledgement equivalent to the following:
- "This product includes software developed by the
- JDOM Project (http://www.jdom.org/)."
- Alternatively, the acknowledgment may be graphical using the logos
- available at http://www.jdom.org/images/logos.
-
- THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
- WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
- DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT
- CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
- LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
- USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
- ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
- OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
- OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
- SUCH DAMAGE.
-
- This software consists of voluntary contributions made by many
- individuals on behalf of the JDOM Project and was originally
- created by Jason Hunter <jhunter_AT_jdom_DOT_org> and
- Brett McLaughlin <brett_AT_jdom_DOT_org>. For more information
- on the JDOM Project, please see <http://www.jdom.org/>.
-
-
-
-RoX
-
- RoX is licensed under the BSD license. This is the simplest way I know how to say
- "do as you please".
-
-Copyright (c) 2006, James Greenfield
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
- * Neither the name of the nor the names of its contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-UUID
-
-eaio: UUID - an implementation of the UUID specification
-Copyright (c) 2003-2007 Johann Burkard (jb@eaio.com) http://eaio.com.
-
-Permission is hereby granted, free of charge, to any person obtaining a
-copy of this software and associated documentation files (the "Software"),
-to deal in the Software without restriction, including without limitation
-the rights to use, copy, modify, merge, publish, distribute, sublicense,
-and/or sell copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included
-in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
-NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
-DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
-OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
-USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-
-24x24 Free Application Icons
-
-<b>24x24 Free Application Icons
-</b>
-This icon set is free for use in personal and commercial projects.
-
-License Agreement
-
-By purchasing icons from Aha-Soft, You (the purchaser)
-agree to the terms of this agreement, as detailed below.
-
-You may use the icons from Aha-Soft in commercial and
-personal design projects, software or Internet products.
-Icons can be displayed in documentation, help files, and
-advertising materials. You are free to sell and distribute
-products and projects using purchased icons without further
-royalty fees.
-
-All icon files are provided 'as is'. Aha-Soft cannot be
-held liable for any negative issues that may occur as a
-result of using the icons.
-
-You agree that all ownership and copyright of the icons
-remains the property of Aha-Soft. You may not resell,
-distribute, lease, license or sub-license the icons or
-modified icons (or a subset of the icons), to any third
-party unless they are incorporated into your software or
-design products.
-
-If you have any questions regarding copyright or licensing,
-including whether another license is required for icon use
-within products, please contact us here: www.aha-soft.com/support.htm
-
-Product page: http://www.small-icons.com/stock-icons/24x24-free-application-icons.htm
-
-Icon Design Service
-
-We can design custom icons for you. Please find the basic information
-about ordering icons, pricing and the portfolio here:
-www.aha-soft.com/customdev/design.htm
-
-
-Notice
-Web-site small-icons.com belongs to Aha-Soft.
-
-Support page: http://www.aha-soft.com/support.htm
-
-Copyright � 2009 Aha-Soft. All rights reserved.
-
-
-
-SLF4J License
-
- SLF4J License
-
-Copyright (c) 2004-2008 QOS.ch
-All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-
-Flot License
-
- Flot License
-
-Copyright (c) 2007-2014 IOLA and Ole Laursen
-
-Permission is hereby granted, free of charge, to any person
-obtaining a copy of this software and associated documentation
-files (the "Software"), to deal in the Software without
-restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following
-conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
-HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
-OTHER DEALINGS IN THE SOFTWARE.
-
-
-
-Coova JRadius License
-
-
-==========================================================================
-
-Coova JRadius License:
-
-The Coova extensions to JRadius library are licensed under the The GNU
-Library or "Lesser" General Public License (LGPL), while stand-alone
-applications within in the JRadius project, listed below, are released under
-the standard The GNU General Public License (GPL). For details, visit
-http://jradius.net/. See source files for details regarding stand-alone
-applications contained herein which are released under the GPL.
-
-Copyright 2006-2008 David Bird <david@coova.com>
-
-See doc/GPL-LICENSE, doc/LGPL-LICENSE, and source files for details.
-
-==========================================================================
-
-Original JRadius License:
-
-The JRadius core library is licensed under the The GNU Library or "Lesser"
-General Public License (LGPL), while stand-alone applications within in the
-JRadius project, listed below, are released under the standard The GNU
-General Public License (GPL). For details, visit http://jradius.net/
-
-This software is OSI Certified Open Source Software. OSI Certified is a
-certification mark of the Open Source Initiative.
-
-Stand-alone JRadius Applications:
-
- * JRadiusSimulator
- * JRadiusWiFiClient
- * RadClient
- * RadBench
- * RadiusDictionary
-
-Copyright 2004-2006 PicoPoint, B.V.
-Copyright 2006-2008 David Bird <david@coova.com>
-
-See doc/GPL-LICENSE, doc/LGPL-LICENSE, and source files for details.
-
-==========================================================================
-
-
-
-GNU Crypto
-
-==========================================================================
-
-GNU Crypto
-From the gnu-crypto WebSite:
-
-GNU Crypto, part of the GNU project, released under the aegis of GNU, aims at
-providing free, versatile, high-quality, and provably correct implementations
-of cryptographic primitives and tools in the Java programming language for use
-by programmers and end-users.
-
-GNU Crypto is licensed under the terms of the GNU General Public License, with
-the "library exception" which permits its use as a library in conjunction with
-non-Free software:
-
-"As a special exception, the copyright holders of this library give you
-permission to link this library with independent modules to produce an
-executable, regardless of the license terms of these independent modules, and
-to copy and distribute the resulting executable under terms of your choice,
-provided that you also meet, for each linked independent module, the terms and
-conditions of the license of that module. An independent module is a module
-which is not derived from or based on this library. If you modify this library,
-you may extend this exception to your version of the library, but you are not
-obligated to do so. If you do not wish to do so, delete this exception
-statement from your version."
-
-The effect of that license is similar to using the LGPL, except that static
-linking is permitted. GPL with that exception is sometimes called the Guile
-License, because the Guile implementation of Scheme (for embedding) uses this
-license.
-
-
-
-
-EasyMock
-
-==========================================================================
-
-EasyMock
-From the GitHub CONTRIBUTING.md:
-
-Project License: Apache License Version 2.0
-
-By contributing code you automatically agree with the following points regarding
- licensing:
-
- You will only Submit Contributions where You have authored 100% of the content.
- You will only Submit Contributions to which You have the necessary rights.
- This means that if You are employed You have received the necessary permissions
- from Your employer to make the Contributions.
- Whatever content You Contribute will be provided under the Project License.
-
-
-
-
-
-PowerMock
-
-==========================================================================
-
-PowerMock
-From the GitHub LICENSE.txt:
-
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright 2007-2017 PowerMock Contributors
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
-limitations under the License.
-
-
-
-
-Objenesis
-
-==========================================================================
-
-Objenesis
-From the GitHub LICENSE.txt:
-
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
-limitations under the License.
-
-
-
-ASM
-
-License
-ASM is released under the following 3-Clause BSD License:
-
-ASM: a very small and fast Java bytecode manipulation framework
-Copyright (c) 2000-2011 INRIA, France Telecom
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. Neither the name of the copyright holders nor the names of its
- contributors may be used to endorse or promote products derived from
- this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
-LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
-THE POSSIBILITY OF SUCH DAMAGE.
-
-
-
-
- JavaScript third-party licenses
-
-
- bootstrap@3.3.7 MIT
-The MIT License (MIT)
-
-Copyright (c) 2011-2016 Twitter, Inc.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-font-awesome@4.7.0 (OFL-1.1 AND MIT)
-
-babel-polyfill@6.23.0 MIT
-
-core-js@2.4.1 MIT
-Copyright (c) 2014-2016 Denis Pushkarev
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-regenerator-runtime@0.10.3 MIT
-
-process@0.11.9 MIT
-(The MIT License)
-
-Copyright (c) 2013 Roman Shtylman <shtylman@gmail.com>
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-'Software'), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-raf.js@0.0.4 MIT
-
-axios@0.13.1 MIT
-Copyright (c) 2014 Matt Zabriskie
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-react@15.4.2 BSD-3-Clause
-BSD License
-
-For React software
-
-Copyright (c) 2013-present, Facebook, Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- * Neither the name Facebook nor the names of its contributors may be used to
- endorse or promote products derived from this software without specific
- prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-object-assign@4.1.1 MIT
-The MIT License (MIT)
-
-Copyright (c) Sindre Sorhus <sindresorhus@gmail.com> (sindresorhus.com)
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-fbjs@0.8.12 BSD-3-Clause
-BSD License
-
-For fbjs software
-
-Copyright (c) 2013-present, Facebook, Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- * Neither the name Facebook nor the names of its contributors may be used to
- endorse or promote products derived from this software without specific
- prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-react-dom@15.4.2 BSD-3-Clause
-BSD License
-
-For React software
-
-Copyright (c) 2013-present, Facebook, Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- * Neither the name Facebook nor the names of its contributors may be used to
- endorse or promote products derived from this software without specific
- prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-clone@1.0.2 MIT
-Copyright © 2011-2015 Paul Vorbach <paul@vorba.ch>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the “Software”), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-buffer@4.9.1 MIT
-The MIT License (MIT)
-
-Copyright (c) Feross Aboukhadijeh, and other contributors.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-base64-js@1.2.0 MIT
-The MIT License (MIT)
-
-Copyright (c) 2014
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-ieee754@1.1.8 BSD-3-Clause
-Copyright (c) 2008, Fair Oaks Labs, Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice,
- this list of conditions and the following disclaimer.
-
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- * Neither the name of Fair Oaks Labs, Inc. nor the names of its contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
-LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-
-
-isarray@1.0.0 MIT
-
-react-modal@1.7.3 MIT
-Copyright (c) 2014 Ryan Florence
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
-of the Software, and to permit persons to whom the Software is furnished to do
-so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-exenv@1.2.0 BSD
-BSD License
-
-For React software
-
-Copyright (c) 2013-2015, Facebook, Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- * Neither the name Facebook nor the names of its contributors may be used to
- endorse or promote products derived from this software without specific
- prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-lodash.assign@4.2.0 MIT
-Copyright jQuery Foundation and other contributors <https://jquery.org/>
-
-Based on Underscore.js, copyright Jeremy Ashkenas,
-DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
-
-This software consists of voluntary contributions made by many
-individuals. For exact contribution history, see the revision history
-available at https://github.com/lodash/lodash
-
-The following license applies to all parts of this software except as
-documented below:
-
-====
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-====
-
-Copyright and related rights for sample code are waived via CC0. Sample
-code is defined as all source code displayed within the prose of the
-documentation.
-
-CC0: http://creativecommons.org/publicdomain/zero/1.0/
-
-====
-
-Files located in the node_modules and vendor directories are externally
-maintained libraries used by this software which have their own
-licenses; we recommend you read them, as their terms may differ from the
-terms above.
-
-
-element-class@0.2.2 ISC
-
-string-format@0.5.0 undefined
-
-json3@3.3.2 undefined
-Copyright (c) 2012-2014 Kit Cambridge.
-http://kitcambridge.be/
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
-of the Software, and to permit persons to whom the Software is furnished to do
-so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-webpack@1.14.0 MIT
-(The MIT License)
-
-Copyright (c) 2012 - 2015 Tobias Koppers
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-'Software'), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-rc-tooltip@3.4.2 undefined
-The MIT License (MIT)
-Copyright (c) 2015-present Alipay.com, https://www.alipay.com/
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-rc-trigger@1.9.1 undefined
-The MIT License (MIT)
-Copyright (c) 2015-present Alipay.com, https://www.alipay.com/
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-babel-runtime@6.23.0 MIT
-
-rc-util@4.0.2 undefined
-The MIT License (MIT)
-Copyright (c) 2015-present Alipay.com, https://www.alipay.com/
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-add-dom-event-listener@1.0.2 undefined
-The MIT License (MIT)
-
-Copyright (c) 2014-present yiminghe
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this
- software and associated documentation files (the "Software"), to deal in the
- Software without restriction, including without limitation the rights to use
- , copy, modify, merge, publish, distribute, sublicense, and/or sell copies
- of the Software, and to permit persons to whom the Software is furnished to
- do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies
- or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
- A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
- COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
- IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
- IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-rc-align@2.3.3 undefined
-
-dom-align@1.5.3 undefined
-The MIT License (MIT)
-
-Copyright (c) 2014-present yiminghe
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this
- software and associated documentation files (the "Software"), to deal in the
- Software without restriction, including without limitation the rights to use,
- copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
- the Software, and to permit persons to whom the Software is furnished to do
- so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies
- or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
- A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
- COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
- IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
- CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-rc-animate@2.3.3 undefined
-The MIT License (MIT)
-
-Copyright (c) 2014-present yiminghe
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this
- software and associated documentation files (the "Software"), to deal in the
- Software without restriction, including without limitation the rights to use,
- copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
- the Software, and to permit persons to whom the Software is furnished to do
- so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies
- or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
- A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
- COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
- IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
- CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-css-animation@1.3.2 undefined
-The MIT License (MIT)
-
-Copyright (c) 2014-present yiminghe
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this
- software and associated documentation files (the "Software"), to deal in the
- Software without restriction, including without limitation the rights to use,
- copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
- the Software, and to permit persons to whom the Software is furnished to do so,
- subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies
- or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
- A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
- COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
- IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
- IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-component-classes@1.2.6 MIT
-
-component-indexof@0.0.3 undefined
-
-react-redux@4.4.7 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Dan Abramov
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-redux@3.6.0 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015-present Dan Abramov
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-lodash@4.17.4 MIT
-Copyright JS Foundation and other contributors <https://js.foundation/>
-
-Based on Underscore.js, copyright Jeremy Ashkenas,
-DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
-
-This software consists of voluntary contributions made by many
-individuals. For exact contribution history, see the revision history
-available at https://github.com/lodash/lodash
-
-The following license applies to all parts of this software except as
-documented below:
-
-====
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-====
-
-Copyright and related rights for sample code are waived via CC0. Sample
-code is defined as all source code displayed within the prose of the
-documentation.
-
-CC0: http://creativecommons.org/publicdomain/zero/1.0/
-
-====
-
-Files located in the node_modules and vendor directories are externally
-maintained libraries used by this software which have their own
-licenses; we recommend you read them, as their terms may differ from the
-terms above.
-
-
-symbol-observable@1.0.4 MIT
-The MIT License (MIT)
-
-Copyright (c) Sindre Sorhus <sindresorhus@gmail.com> (sindresorhus.com)
-Copyright (c) Ben Lesh <ben@benlesh.com>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
-
-
-hoist-non-react-statics@1.2.0 undefined
-Software License Agreement (BSD License)
-========================================
-
-Copyright (c) 2015, Yahoo! Inc. All rights reserved.
-----------------------------------------------------
-
-Redistribution and use of this software in source and binary forms, with or
-without modification, are permitted provided that the following conditions are
-met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
- * Neither the name of Yahoo! Inc. nor the names of YUI's contributors may be
- used to endorse or promote products derived from this software without
- specific prior written permission of Yahoo! Inc.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-invariant@2.2.2 BSD-3-Clause
-Copyright (c) 2016, Andres Suarez
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of invariant nor the names of its
- contributors may be used to endorse or promote products derived from
- this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-moment@2.18.1 MIT
-Copyright (c) JS Foundation and other contributors
-
-Permission is hereby granted, free of charge, to any person
-obtaining a copy of this software and associated documentation
-files (the "Software"), to deal in the Software without
-restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following
-conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
-HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
-OTHER DEALINGS IN THE SOFTWARE.
-
-
-react-virtualized-select@3.0.1 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Brian Vaughn
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-
-prop-types@15.5.9 BSD-3-Clause
-BSD License
-
-For React software
-
-Copyright (c) 2013-present, Facebook, Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- * Neither the name Facebook nor the names of its contributors may be used to
- endorse or promote products derived from this software without specific
- prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-react-select@1.0.0-rc.3 MIT
-The MIT License (MIT)
-
-Copyright (c) 2016 Jed Watson
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-react-input-autosize@1.1.3 MIT
-The MIT License (MIT)
-
-Copyright (c) 2017 Jed Watson
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-create-react-class@15.5.3 BSD-3-Clause
-BSD License
-
-For React software
-
-Copyright (c) 2013-present, Facebook, Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- * Neither the name Facebook nor the names of its contributors may be used to
- endorse or promote products derived from this software without specific
- prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-classnames@2.2.5 MIT
-The MIT License (MIT)
-
-Copyright (c) 2016 Jed Watson
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-react-virtualized@9.7.5 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Brian Vaughn
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-
-dom-helpers@3.2.1 MIT
-
-react-tagsinput@3.15.1 MIT
-The MIT License
-
-Copyright (c) 2015 Ola Holmström <olaholmstrom+github@gmail.com>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
-of the Software, and to permit persons to whom the Software is furnished to do
-so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-recharts@0.20.8 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 recharts
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-
-d3-scale@1.0.4 BSD-3-Clause
-Copyright 2010-2015 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-array@1.1.1 BSD-3-Clause
-Copyright 2010-2016 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-collection@1.0.3 BSD-3-Clause
-Copyright 2010-2016, Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-interpolate@1.1.4 BSD-3-Clause
-Copyright 2010-2016 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-color@1.0.3 BSD-3-Clause
-Copyright 2010-2016 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-format@1.1.1 BSD-3-Clause
-Copyright 2010-2015 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-time@1.0.6 BSD-3-Clause
-Copyright 2010-2016 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-time-format@2.0.5 BSD-3-Clause
-Copyright 2010-2016 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-shape@1.0.4 BSD-3-Clause
-Copyright 2010-2015 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-d3-path@1.0.5 BSD-3-Clause
-Copyright 2015-2016 Mike Bostock
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
-* Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
-* Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
-* Neither the name of the author nor the names of contributors may be used to
- endorse or promote products derived from this software without specific prior
- written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-react-smooth@0.1.20 MIT
-The MIT License (MIT)
-
-Copyright (c) 2016 recharts
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-raf@3.3.0 MIT
-
-performance-now@0.2.0 MIT
-Copyright (c) 2013 Meryn Stol
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
- this software and associated documentation files (the "Software"), to deal
- in the Software without restriction, including without limitation the rights
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
- copies of the Software, and to permit persons to whom the Software is
- furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
- copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR
- A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
- COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
- WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
- OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-react-addons-transition-group@15.4.2 BSD-3-Clause
-BSD License
-
-For React software
-
-Copyright (c) 2013-present, Facebook, Inc.
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
- list of conditions and the following disclaimer.
-
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation
- and/or other materials provided with the distribution.
-
- * Neither the name Facebook nor the names of its contributors may be used to
- endorse or promote products derived from this software without specific
- prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
-react-resize-detector@0.3.3 MIT
-
-reduce-css-calc@1.3.0 MIT
-The MIT License (MIT)
-
-Copyright (c) 2014 Maxime Thirouin & Joakim Bengtson
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-balanced-match@0.4.2 MIT
-(MIT)
-
-Copyright (c) 2013 Julian Gruber <julian@juliangruber.com>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
-of the Software, and to permit persons to whom the Software is furnished to do
-so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-reduce-function-call@1.0.2 MIT
-The MIT License (MIT)
-
-Copyright (c) 2014 "MoOx" Maxime Thirouin
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-math-expression-evaluator@1.2.16 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Ankit G.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-
-recharts-scale@0.2.1 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Sen Yang
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-
-events@1.1.1 MIT
-MIT
-
-Copyright Joyent, Inc. and other Node contributors.
-
-Permission is hereby granted, free of charge, to any person obtaining a
-copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to permit
-persons to whom the Software is furnished to do so, subject to the
-following conditions:
-
-The above copyright notice and this permission notice shall be included
-in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
-NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
-DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
-OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
-USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-rc-collapse@1.6.12 MIT
-The MIT License (MIT)
-
-Copyright (c) 2014-present yiminghe
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
- of this software and associated documentation files (the "Software"),
- to deal in the Software without restriction, including without limitation
- the rights to use, copy, modify, merge, publish, distribute, sublicense,
- and/or sell copies of the Software, and to permit persons to whom the
- Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
- all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
- FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
- OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
- WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
- OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-react-sizeme@2.3.1 MIT
-The MIT License (MIT)
-
-Copyright (c) 2016 Sean Matheson
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-element-resize-detector@1.1.11 MIT
-The MIT License (MIT)
-
-Copyright (c) 2016 Lucas Wiener
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-batch-processor@1.0.0 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Lucas Wiener
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-
-react-color@2.11.4 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Case Sandberg
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-reactcss@1.2.2 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Case Sandberg
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-material-colors@1.2.5 ISC
-
-redux-replaceable-middleware@1.1.0 ISC
-
-redux-thunk@2.2.0 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Dan Abramov
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-redux-promise-middleware@3.3.2 MIT
-Copyright 2015-current Patrick Burtchaell <patrick@pburtchaell.com>
-
-The above copyright notice and this permission notice shall be included
-in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-
-redux-saga@0.12.1 MIT
-The MIT License (MIT)
-
-Copyright (c) 2015 Yassine Elouafi
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-
diff --git a/doc/book-enea-nfv-access-ucpem-open-source/swcomp.mk b/doc/book-enea-nfv-access-ucpem-open-source/swcomp.mk
deleted file mode 100644
index a7e39ab..0000000
--- a/doc/book-enea-nfv-access-ucpem-open-source/swcomp.mk
+++ /dev/null
@@ -1,10 +0,0 @@
-# Component build specification
-
-# Version of THIS book
-BOOK_VER ?= $(REL_VER)-dev
-
-DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
-
-BOOKPACKAGES := book-enea-nfv-access-ucpem-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea Edge Management Open Source Report"
-BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
--
cgit v1.2.3-54-g00ecf