Free dvd copy packages software for linux

DB Copy Plugin is a database copying plugin for the SQuirreL SQL Client. DB Copy Plugin makes it possible to copy and paste tables from one session to another and between different databases and includes primary key and foreign key constraints for copied tables, and uses Hibernate 3.0 internally to perform database object type mappings.
It supports Firebird, Oracle, Sybase, MS SQL Server, MySQL, HyperSonic, Pointbase, and PostgreSQL, and allows the user to select a Hibernate dialect for the destination database if one couldnt be determined automatically.
Enhancements:
- Ran latest version of findbugs (http://findbugs.sourceforge.net/) and fixed Ran latest version of findbugs (http://findbugs.sourceforge.net/) and fixed

DVD Manager provides an easy-to-use Web-based DVD management tool.

DVD Manager is an e107 CMS plugin. This plugin will enable users to manage their DVD collection and show it to other members via the Web whether it is online or offline.

MyBook World Edition Packages project collection provides pre-compiled packages for hacking Western Digital MyBook World Edition, to improve performance and add new features.

At least intermediate Linux experience is required for playing with MyBook. Please, if you do not meet this requirement, ask someone experienced to help you. Otherwise there is a risk that you will brick your MyBook!

Debian Package Tools FE application is the first part of the Debian Package Tools FE based on python-qt3.
Debian Package builder FE is a frontend for dh-make, dpkg-dev, debhelper. It is a tool to learn to build packages for Debian based systems without any knowlegde concerning the above command line applications. Debian Package builder cannot fix build dependences and repair non-standard sources. It is only a graphical frontend.
This debug release is only for testing on your system. Debian Package Tools FE is not intended for non Debian based systems. If it works, you are lucky, but if it does not, I will not restrict the ability of the application for the shake of a restricted system. (It will not work on SUSE, because Qscintilla package does not contain the full version Qscintilla.)
Debian Package Builder FE was not tested on Ubuntu. Theoretically, it could work from Breezy, but the package dependences may not allow you to install it. In this case, I will include an Ubuntu version, just test it.
This is a debug release. In case of any error, you can test it by the command (from running from the console):
dpkg-tools-fe full_path_to_the_tarball/tarball_name.tar.gz or tar.bz2,
or without argument:
dpkg-tools-fe.
Enhancements:
- Threading improvements to increase process stability
- A solution for a python-qt bug in Debian 4.0.
- Postinst script improvements. Prerm script to clean-up.

Vobcopy copies DVD .vob files to harddisk, decrypting (if you have libdvdcss installed) them on the way (thanks to libdvdread and libdvdcss) and merges them into file(s) with the name extracted from the DVD.
It checks for enough free space on the destination drive and compares the copied size to the size on DVD (in case something went wrong during the copying). Vobcopy project without any options will copy the first title into files of 2GB size into the current working directory.
There is one drawback though: at the moment vobcopy doesnt deal with multi-angle-dvds. But since these are rather sparse this shouldnt matter much.
Enhancements:
- A segfault in the log file writing routine was fixed.
- Small fixes and experimental "step over the bad part" code were added.

PkgTools are a set of utilities which are used to aid in the building of native Solaris packages. There are five separate utilities which are used to build packages, prepare a chroot() environment to install software into prior to building a package, copy package control scripts into place, a tool to aid in the starting of new projects, and a tool to check that packages are installed correctly.

Currently there are four tools in this set:

build-pkg
This is used to actually build the Solaris package, calling chroot-install if required.
chroot-install
A utility which creates an environment suitable for calling chroot() on and allowing the user to install software into it.
proj-template
A utility which asks the user questions and then copies files and directories from a specified template directory and performs macro expansion on them. This is designed to aid in the initial setup of the home directory of a new project.
simple-proj
A very similar utility to proj-template. However it does not ask questions and only deals with the setting up of a simple InstallPackage. This is useful when dealing with 3rd party software which just needs to have a number of package control scripts put into the package.
check-pkg
A utility which can be used to check to see if packages are installed correctly. It can also be given a pathname to check on which packages said pathname is a part of.

It should be noted that simple-proj is really proj-template wearing a different hat.

Mpak is being designed from the ground up to be a kernel and architecture independent package manager for free operating systems.
Main features:
- a single statically linked executable: The package manager is responsible for installing all packages, including packages like glibc, which the whole system depends on. In the event that a critical package is damaged, we should be able to use the package manager to install a replacement for the package, so other system functionality can be repaired. To install a new operating system, a user will only need a boot CD (or an already running system) and a copy of the mpak executable
- dependency tracking: Mpak will be able to find and install all the dependencies for a package. Dependency cycles will be automatically handled via a bootstrapping mechanism.
- the package tree: Package metadata will be kept in a directory tree, organized by category. An installation of an mpak based distribution will have a "system" tree. There will be support for external trees provided by other vendors. Developers may provide package trees for their own projects.
- support for building from source and binary packages: Mpak will be able to use binary packages and build packages automatically from source.
- optional feature support: Many packages have optional build-time features. Mpak will have support for these. Following autoconfs lead, we will divide them into supported packages (e.g. --with-gnome) and internal features (e.g. --enable-mmx).
- kernel and architecture indepence: mpak will have features to simplify porting to different kernels. This way, we can have a unified distribution with support for many kernels (Linux, Hurd, BSD, Darwin, etc.), with nearly identical functionality across kernels.
- package binding support: mpak will be able to bind an installation of a package to another installed package. For example, suppose you have 2 versions of the linux kernel installed, 2.4.19 and 2.4.20. You want to install the alsa-drivers package for both of these kernels. Normally, you would only be able to install one copy of alsa-drivers, but mpak will let you bind the package to the linux kernel package, so that you can have one installation of alsa-drivers for each version of the linux kernel package you have installed.
- hard and soft dependencies: mpak will have support for hard and soft dependencies. Suppose package A has a hard dependency on package B. Then, when package B is upgraded, package A will need to be rebuilt. If package A had a soft dependency on package B, then A would not need to be rebuilt.